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.
At the moment the design for the PL wizard is to add the PLs to the end of the WSDL to which they relate. I am not convinced this is a good design... 1. The amended WSDL is probably imported into NB from an external source, it does not belong to NB 2. If the WSDL is changed externally and gets reimported what happens to my PLs? Do I lose them and my BP gets corrupted ? 3. Can we manage this situation with refactoring ? See issue 85416 for my suggestion to create automatically a ProjectExtensibilityElements.wsdl for Alias' (correlation keys) - it may be that this would be a good place for PLs as well. It would be available ot the user to amend if required.
yes, we agree that the best thing to do is to put the "additional" elements in separte WSDL file (either a FooWrapper.wsdl or a ProjectExtensibilityElements.wsdl as you suggest). However, it is too late for such a change. We cannot implement such a radical change and perform all necessary testing in a very short time. Therefore this must be considered an RFE that will be dealt with after this release.
I take it by "this release" you mean the forthcoming one in a month or so ? Something will be done after that ? From my perspective I will probably be taking the product out to to customers in the new year, can I expect it to be sorted by then ?
This release means the FCS scheduled to coincide with release of NB 5.5, yes, next month, but testing is in final stages so we cannot introduce new "feature". We can put critical improvements into a point release but I do not know timetable.
Ok, we will see what we can do right now.
Created attachment 34426 [details] BPEL Aansluting Project
Created attachment 34427 [details] CA Aansluiting Project
*** This issue has been marked as a duplicate of 88318 ***