This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Provide better syncing for Web Service EJB implementation to original WSDL changes | ||
---|---|---|---|
Product: | webservices | Reporter: | lpolycarpou <lpolycarpou> |
Component: | JAX-WS | Assignee: | Roderico Cruz <rcruz> |
Status: | NEW --- | ||
Severity: | blocker | CC: | mkuchtiak |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
lpolycarpou
2007-08-23 22:09:17 UTC
Related to the above, there does not seem to be a logical place to hold artefacts such as WSDLs, XSDs that are used across multiple projects and composite apps. It is a nightmare to keep everything synchronised manually and this is something that Java CAPS does quite well for us today since these could all be maintained in a single project hierarchy that is referenced from other business processes / Java collaborations. Reassigning to "j2ee". We should think about this. Currently we create services/clients from the local wsdl file that is copied from the original location. Though, there is an option to refresh Service/Client, there is no indication the original" wsdl has changed. However, take into the consideration the main scenarios that we are supporting now : Web Service : Original WSDL -> Local Copy -> Customized Local Copy(JAX-WS Customization) -> Service Client : Original WSDL -> Local Copy -> Customized Local Copy(JAX-WS Customization) -> Client Note: we only enable to customize the local copy of wsdl file, since we don't want to touch the original wsdl. Therefore, the original and local can easily be different after customization. moving opened issues where TM != dev to TM=TBD |