---

Web Service Manager Enhancements for NetBeans 6.1

Objective:

To expose consumer aspect of all type of web services under 'Web Services' node in Service tab.

• planned Software-as-a-Service (SAAS) components
• Nodes from REST Component palette for SOAP-based services like StrikeIron and Google AdSense are consolidated with their corresponding operation nodes under Web Services nodes. This consolidation would help eliminate the observable confusion over the difference between the duo.
• Current Google Map, Yahoo News Search will show up under Services tab Web Services node, instead of under the REST component palette.

Existing Functionalities:

• Web Services nodes
• REST component palette
• REST component registration

User View:

• There would be no change to the existing hierarchical structure of Web Services nodes.
• Web service component nodes will be badged according to 3 component classifications:
  • SOAP
  • RESTful
  • Customed: consists of client code generators that consume multiple WSDL or WADL services.
• Component nodes are be grouped by partner or provider. Each provider group could have any hierarchy. For example:

Web Services
   |-
   |- ShieldIron
        |- Credit
        |    |- Visa Charge
        |    |- Credit Fast Check
        |
        |- Stock Market
            | - Real-Time Quotes
            | - 5-Minute Quotes

Same as current UI, user can interactively add more service components stand-alone or under existing groups.

• Preliminary Saas UI nodes screenshorts

Declarative Installation of Services by Partner:

• Provider of the components will define components through layer.xml and an enhanced version of component descriptor file (component.xml).
• There should be no needs to redeclare information already defined in WSDL or WADL.
• The component descriptor file should allow customizations such as:
  • provider specified code snippets or code generators for each target consumer type in DnD action.
  • restrict list of displayed operations or resources.
  • specify the search UI for adding more WSDL or WADL components
• Detailed design of component.xml

Drag-n-Drop Behavior of Service Node:

• Specifically for 6.1, supported DnD combinations are:

Node Type	Consumer Type	Result
SOAP Operation	Java or JSP	WSDL client code inserted
	Resource Java	Wrapper resource generated, sub-resource locator inserted
	Visual Web Form	Designer bean added, datab binding code generated
	BPEL form	partnerLink to service generated
RESTful Resource	Java or JSP	JSR-311 client code inserted
	Resource Java	Wrapper resource generated, sub-resource locator inserted
	Visual Web Form	(none planned for 6.1)
	BPEL form	N/A
Customized	Java or JSP	Customed client code generated
	Resource Java	Wrapper resource generated, sub-resource locator inserted
	Visual Web Form	(none planned for 6.1)
	BPEL form	N/A

Direct Search and Use:

• The motivation of this is to avoid situation that the list of service components grow too large.
• User should be able to search and use REST components on the fly.
• DnD of provider node with search capability will initiate a search and user could use select resulted search service to use directly.
• Note: this is only a stretch goal. Might not be able to accomplish in 6.1 time frame.