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 136565 - "Clone WSDL Port to edit" copies the whole WSDL file into the Assembly
Summary: "Clone WSDL Port to edit" copies the whole WSDL file into the Assembly
Status: RESOLVED WONTFIX
Alias: None
Product: soa
Classification: Unclassified
Component: Composite Application (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Venkat Chellasamy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-05 16:40 UTC by davelane
Modified: 2008-06-27 17:14 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description davelane 2008-06-05 16:40:11 UTC
"Clone WSDL Port to edit" doesn't really do what it says. The WSDL file containing the Port is copied into the CASA
Project. This means that the abstract parts and the concrete parts are both duplicated. The parameters that are editable
in the CASA project belong to the category concrete. What happens when I change abstract elements in the original WSDL?
How do I get the original into the CASA Project? If I have changed concrete parameters in the CASA editor then the files
are even more out of sync.
Comment 1 Tientien Li 2008-06-27 17:14:34 UTC
David,

I understand what you are asking... but that is not what CASA was designed for. CASA is a service assembly editor that 
works directly on deployment artifacts like SU jar files within a service assembly. It does not have access to source 
WSDL files from service projects like bpel, xslt, or ejb. Please see the faq page for the background information on 
CASA:

   http://wiki.netbeans.org/SoaFaqWhatDoesCasaDo

The reason that the complete WSDL including abstract parts has to be cloned is because CASA can not make references to 
the source WSDL. There are many design issues involved here. For example, it is common to see the same WSDL copied 
multiple times from different service projects within a CompApp project. Which one of these WSDL copies should be 
linked to?  In your case, if the original abstract interface of a cloned WSDL was changed, then re-clone the WSDL is 
probably the simplest solution that can be offered at this time. We are not sure how complex elements like WS-* policy 
attachments, can be automatically refactored in such a scenario.

However, we like your suggestion and will change the ticket to an enhancement request for later consideration.

Thanks,

--
Tientien Li