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.

Bug 113669 - Provide better syncing for Web Service EJB implementation to original WSDL changes
Summary: Provide better syncing for Web Service EJB implementation to original WSDL ch...
Status: NEW
Alias: None
Product: webservices
Classification: Unclassified
Component: JAX-WS (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Roderico Cruz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-23 22:09 UTC by lpolycarpou
Modified: 2008-04-14 17:17 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description lpolycarpou 2007-08-23 22:09:17 UTC 
When working with OpenESB, it is common to implement a WSDL binding as an EJB Web Service.  Often the WSDL may reside in
a  different NB6 project than that of the EJB project implementation (e.g. possibly the composite app itself).  When a
WS is implemented from a WSDL, the original WSDL is copied to a "Configuration Files" sub-folder.  Any changes to the
original WSDL or the WSDL copied in the configuration files sub-folder are not immediately obvious to the user.

I propose two enhancements to improve working with EJB implementations that depend on WSDL that may frequently change:

1) Supporting configuration files should be *optionally* used "by reference" within the IDE.  Therefore, the WSDL
contained under Configuration Files is actually a reference to WSDL contained in another project that gets updated with
the new WSDL whenever the WSDL changes.

2) The Web Service EJB implementing a WSDL is indicated visually whenever the original WSDL which it implements changes
(if based on a local file).  This allows the user to quickly identify EJBs that are out of date and require refreshing
from the original WDSL.
Comment 1 lpolycarpou 2007-08-23 22:11:55 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.
Comment 2 Peter Pis 2007-10-01 13:47:53 UTC 
Reassigning to "j2ee".
Comment 3 Milan Kuchtiak 2008-01-21 09:37:45 UTC 
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.
Comment 4 Lukas Jungmann 2008-04-14 17:17:08 UTC 
moving opened issues where TM != dev to TM=TBD