REST Web Service Component Palette

Introduction

REST Component architecture, allows

1. Exposing 3rd party services (a.k.a. partner services) as palette items through partner modules. 2. Users would drag-n-drop these services onto java source to generate the necessary wrapper code for that service. 3. Partner service is dynamically shown on the Netbeans palette. They may update these modules periodically, and users would get updated modules from update center. 4. The Palette with partner services show up only when a REST java file (identified using @UriTemplate annotation)

Use Cases and Scenarios

A. Use Case: Adding a Google Map REST service as a sub-resource on a static resource.

User drag-n-drop Google Map palette item onto a Resource (for eg. CustomerResource.java). Upon this action, we show a dialog (a panel) that collects relevant information from user that gets added to the new method in the Resource code.

B. Use Case: Adding a Yahoo News Search REST service as a sub-resource on a static resource.

User drag-n-drop Google Map palette item onto a Resource (for eg. CustomerResource.java). Upon this action, we show a dialog (a panel) that collects relevant information from user that gets added to the new method in the Resource code.

C. Use Case: Adding a Srike Iron JAXWS service as a sub-resource on a static resource.

User drag-n-drop StrikeIron Email Verification palette item onto a Resource (for eg. CustomerResource.java). Upon this action, we do show only a progress panel, during which the relevant code to invoke StrikeIron JAXWS service.

Attachments

YahooNSDND.png		64047 bytes
googlemap_dnd.PNG		65745 bytes
googlemap_dnd.png		65745 bytes
palette_snapshot.PNG		63376 bytes
palette_snapshot.png		63376 bytes
yahoons_dnd.PNG		64047 bytes