Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "JBI Runtimes"
| Line 4: | Line 4: | ||
Hereunder are the main thoughts related to this proposal ==> | Hereunder are the main thoughts related to this proposal ==> | ||
| − | '''Eclipse plugins''' | + | '''Eclipse plugins''' |
There are several types of plugins to be provided in STP to support JBI containers and more specifically Petals for: | There are several types of plugins to be provided in STP to support JBI containers and more specifically Petals for: | ||
| Line 12: | Line 12: | ||
* Petals runtime support | * Petals runtime support | ||
| − | '''Service Creation''' | + | '''Service Creation''' |
Some wizards will be provided to create a JBI Service Engine or Binding Component. | Some wizards will be provided to create a JBI Service Engine or Binding Component. | ||
This wizards will be based on a Binding component and Service Engine framework (including the Message Listener, a service unit manager skeleton, ...) | This wizards will be based on a Binding component and Service Engine framework (including the Message Listener, a service unit manager skeleton, ...) | ||
| Line 24: | Line 24: | ||
These wizards will either use a POJO as the base for code generation, or generate an empty class for implementation. | These wizards will either use a POJO as the base for code generation, or generate an empty class for implementation. | ||
| − | '''Service packaging''' | + | '''Service packaging''' |
A plugin will provide the capability to prepare for the deployment of JBI components, service units and service assemblies to a JBI compliant container: | A plugin will provide the capability to prepare for the deployment of JBI components, service units and service assemblies to a JBI compliant container: | ||
| Line 31: | Line 31: | ||
* Create and package a Service assembly | * Create and package a Service assembly | ||
| − | '''Tests''' | + | '''Tests''' |
The project will provide a Universal Test Client for JBI components. Such a client will be associated with a specific Binding Component and will give the opportunity to test a JBI component deployed on the container. | The project will provide a Universal Test Client for JBI components. Such a client will be associated with a specific Binding Component and will give the opportunity to test a JBI component deployed on the container. | ||
| Line 41: | Line 41: | ||
* The plugin sends the message to the client and displys the results | * The plugin sends the message to the client and displys the results | ||
| − | '''Petals runtime support''' | + | '''Petals runtime support''' |
Some tasks specific to Petals will be provided to : | Some tasks specific to Petals will be provided to : | ||
* Support Petals runtime inside Eclipse for debug purpose | * Support Petals runtime inside Eclipse for debug purpose | ||
* Package and configure Petals distribs by integrating several JBI components with the Petals runtime | * Package and configure Petals distribs by integrating several JBI components with the Petals runtime | ||
Revision as of 10:42, 17 July 2006
Check out Philip Dodds' work on Eclipse-based JBI tooling at goopen.org and watch his progress on FUSE tooling at his blog.
Refer to STP tooling proposal on the ObjectWeb's JBI Petals project wiki page [1] Hereunder are the main thoughts related to this proposal ==>
Eclipse plugins There are several types of plugins to be provided in STP to support JBI containers and more specifically Petals for:
- Service Creation
- Service packaging
- Test
- Petals runtime support
Service Creation Some wizards will be provided to create a JBI Service Engine or Binding Component. This wizards will be based on a Binding component and Service Engine framework (including the Message Listener, a service unit manager skeleton, ...)
Tasks to be supported by these wizards are :
- Generation of the component structure
- Generation of the deployment descriptors
- Generation of the WSDL to be procided to the JBI container by the component
- Generation of the Service Unit Manager
These wizards will either use a POJO as the base for code generation, or generate an empty class for implementation.
Service packaging A plugin will provide the capability to prepare for the deployment of JBI components, service units and service assemblies to a JBI compliant container:
- Create the jbi deployment descriptor for a component
- Create and package a Service unit descriptor
- Create and package a Service assembly
Tests The project will provide a Universal Test Client for JBI components. Such a client will be associated with a specific Binding Component and will give the opportunity to test a JBI component deployed on the container.
Typical steps are :
- The test client gets the service WSDL
- The plugin generates an interface from the service WSDL to neter parameters
- Users can specify some JBI metadata
- The plugin sends the message to the client and displys the results
Petals runtime support Some tasks specific to Petals will be provided to :
- Support Petals runtime inside Eclipse for debug purpose
- Package and configure Petals distribs by integrating several JBI components with the Petals runtime