Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-incubator-dev] JAX-WS Contribution. Meeting Summary.
Below is a summary of the meeting with SAP AG that took place on the 30th of March 2009 in relation to a proposed contribution to the JAX-WS Tools component in the WTP Incubator Project.

Contribution details:
  • JAX-WS runtime based on Java 6 SE's JAX-WS RI. Currently using internal API's, which will be replaced.

  • Top-down & Bottom-up web services support in wizards:
    • Uses the Java Bean Web Service Type.

  • Bottom-up Web Services:
  • Supported in EJB Projects and Dynamic Web Projects.
  • Start from source type. Message shown if attempting to start from binary.
  • Ability to select an SEI or create one within the wizard.

  • Top-down Web Services:
  • Supported in EJB Projects only.
  • Namespace mapping collision detection and resolution in web service & client wizards.
  • Supply binding customization files in web service and client wizards.

  • Undo support in wizards.

  • Common Navigator Framework content extensions for JAX-WS Web Services and SEI's within projects.

  • Properties sheets for editing JAX-WS nodes in the tree.

  • Annotation Validation. Using the JDT AST, EMF.

Additional Information:
The code has been in production for ~3 years and has 90%+ test coverage.

SAP AG have set aside 2 months preferably beginning on or before the 1st May to integrate the code with the existing JAX-WS tools codebase. Dependent on the Eclipse IP process of course.

After the 2 month period a nominated committer will be available for bug fixes and maintenance.

Some initial thoughts.

Looks like there is a lot of new functionality that we can use in the JAX-WS component:
  • Additional JAX-WS runtime.
  • CNF features & Properties for viewing/editing Web Service and SEI nodes within projects.
  • Namespace mapping collision detection and resolution. User interactive or auto resolved.

Along with some features that closely mirror the existing tooling for the CXF runtime and would fit in nicely as an alternate JAX-WS runtime.
  • Selecting an SEI or creating one from within the wizard.
  • Supplying binding customization files.
  • Undo support in wizards.

Some differences in the tooling:
  • Approach used in validating annotations.
  • Different "Web Service Type" in wizards.

In relation to the contribution and integrating the code. I think it would be best to contribute the code in one piece rather than several and then look to integrate individual pieces one step at a time.
 
I'll do a follow up post outlining the next steps to take, i.e. Contribution proposal, bugzilla entry etc..

Hristo, Danail or Oisin if there is anything you'd like to add, correct or update please do so.

Thanks,
Shane


Get the next generation of Free Windows Live Services Click here!

Back to the top