Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Axis2 Integration meeting - Dec 21, 2006"
| Line 5: | Line 5: | ||
=== Agenda === | === Agenda === | ||
* Any questions/clarification on [[Use cases for Axis2 Integration in WTP]]? | * Any questions/clarification on [[Use cases for Axis2 Integration in WTP]]? | ||
| − | * Progress with prototyping | + | * Progress with prototyping addition of Axis2 runtime to Web services creation framework. |
| − | * Discuss the list of the prioritized requirements for Axis2 integration in WTP | + | * Discuss the list of the prioritized requirements for Axis2 integration in WTP. Refer to [[Requirements document for Axis2 Integration in WTP]] for details. Are any requirements missing? Is the priority about right? What's the rough sizing and a first cut on what could be achieved in which milestones? |
==== Requirements for Axis2 Integration in WTP ==== | ==== Requirements for Axis2 Integration in WTP ==== | ||
| − | #User can choose Axis2 runtime | + | #User can choose the Axis2 runtime via the wizards, pop-up actions and Ant tasks to create bottom-up or top-down Java Web services and Web service clients fully exploiting the Web services creation framework (develop, assemble, deploy, install, start, test): |
| − | #* | + | #*Wizard controls are defaulted based on Axis2 preference page. |
| − | #* | + | #*Only commonly used controls are exposed. More advanced controls are hidden under sections, buttons or optional pages. |
| − | #*Axis2 code generators | + | #*Axis2 code generators read from and write to resources in Eclipse workspace directory respecting Web service resource management preferences with no manual refresh necessary. |
| − | #*If the Web project already contains an existing Axis2 Web service, the services.xml | + | #*If the Web project already contains an existing Axis2 Web service, the services.xml is merged with that of the newly generated service. |
| − | #*Generated artifacts | + | #*Generated artifacts are organized into an exploded AAR for deployment to server without the need for an explicit builder to build an AAR. |
| − | #User can set Axis2 preferences in Web service | + | #User can set Axis2 preferences in a Web service preferences page. |
| − | #User can specify which version of Axis2 | + | #User can specify which version of Axis2 to use by pointing to an Axis2 install location (i.e. not shipping Axis2 Jars in WTP). |
| − | #User can equip a project for Axis2 development without using the Web service wizards. | + | #User can equip a project for Axis2 development without using the Web service wizards (i.e. by adding an Axis2 facet to the project). |
#User can export an AAR. | #User can export an AAR. | ||
#User can import an AAR. | #User can import an AAR. | ||
| − | #User can do hot deployment | + | #User can do hot deployment in which any change to the Java implementation class of a deployed Axis2 Web service is automatically loaded by the Axis2 servlet. |
| − | #User can do hot update | + | #User can do hot update in which any change to the services.xml file or service directory of a deployed Axis2 Web service prompts for or causes the servlet to be recycled. |
| − | #User can discover and test Axis2 Web services | + | #User can discover and test Axis2 Web services under their own category via the WSE. |
#User can test Axis2 Web services using automatically generated JUnits. | #User can test Axis2 Web services using automatically generated JUnits. | ||
| − | #User can see Axis2 Web services in a | + | #User can see Axis2 Web services in a branch of Project Explorer |
| − | #Axis2 Web | + | #Axis2 Web services and clients (e.g. services.xml) are validated. |
| − | #The Axis2 Web service tools (emitters and wizards) | + | #The Axis2 Web service tools (emitters and wizards) are extensible so that support for other Axis2 Modules such as JAX-WS, Sandesha, Kandula2 and Rampart can be easily added at a later time. |
| − | #User can test Axis2 Web services using Web services sample | + | #User can test Axis2 Web services using Web services sample JSPs. |
| − | #User can easily add | + | #User can easily add, remove and edit handlers on Axis2 Web services and clients using a handler configuration wizard or a services.xml editor. |
| − | #User can dynamically locate different versions of Axis2 Web service | + | #User can dynamically locate different versions of Axis2 Web service runtimes and tools available to install. |
Revision as of 09:48, 21 December 2006
Contents
Teleconference on Axis2 Integration into WTP - Dec 21, 2006
Attendance
Agenda
- Any questions/clarification on Use cases for Axis2 Integration in WTP?
- Progress with prototyping addition of Axis2 runtime to Web services creation framework.
- Discuss the list of the prioritized requirements for Axis2 integration in WTP. Refer to Requirements document for Axis2 Integration in WTP for details. Are any requirements missing? Is the priority about right? What's the rough sizing and a first cut on what could be achieved in which milestones?
Requirements for Axis2 Integration in WTP
- User can choose the Axis2 runtime via the wizards, pop-up actions and Ant tasks to create bottom-up or top-down Java Web services and Web service clients fully exploiting the Web services creation framework (develop, assemble, deploy, install, start, test):
- Wizard controls are defaulted based on Axis2 preference page.
- Only commonly used controls are exposed. More advanced controls are hidden under sections, buttons or optional pages.
- Axis2 code generators read from and write to resources in Eclipse workspace directory respecting Web service resource management preferences with no manual refresh necessary.
- If the Web project already contains an existing Axis2 Web service, the services.xml is merged with that of the newly generated service.
- Generated artifacts are organized into an exploded AAR for deployment to server without the need for an explicit builder to build an AAR.
- User can set Axis2 preferences in a Web service preferences page.
- User can specify which version of Axis2 to use by pointing to an Axis2 install location (i.e. not shipping Axis2 Jars in WTP).
- User can equip a project for Axis2 development without using the Web service wizards (i.e. by adding an Axis2 facet to the project).
- User can export an AAR.
- User can import an AAR.
- User can do hot deployment in which any change to the Java implementation class of a deployed Axis2 Web service is automatically loaded by the Axis2 servlet.
- User can do hot update in which any change to the services.xml file or service directory of a deployed Axis2 Web service prompts for or causes the servlet to be recycled.
- User can discover and test Axis2 Web services under their own category via the WSE.
- User can test Axis2 Web services using automatically generated JUnits.
- User can see Axis2 Web services in a branch of Project Explorer
- Axis2 Web services and clients (e.g. services.xml) are validated.
- The Axis2 Web service tools (emitters and wizards) are extensible so that support for other Axis2 Modules such as JAX-WS, Sandesha, Kandula2 and Rampart can be easily added at a later time.
- User can test Axis2 Web services using Web services sample JSPs.
- User can easily add, remove and edit handlers on Axis2 Web services and clients using a handler configuration wizard or a services.xml editor.
- User can dynamically locate different versions of Axis2 Web service runtimes and tools available to install.