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 143867 - Cannot make new namespace in CASA editor
Summary: Cannot make new namespace in CASA editor
Status: NEW
Alias: None
Product: soa
Classification: Unclassified
Component: Composite Application (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Jun Qian
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-14 07:44 UTC by trondstromme
Modified: 2009-01-14 22:12 UTC (History)
2 users (show)

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 trondstromme 2008-08-14 07:44:33 UTC
Cannot create new namespace for SOAP BC in CASA editor.
How to recreate:
1. Create new Composite Application (NamespaceTestCA)
2. Add SOAP Binding Component
3. Click on Consume (purple) arrow in binding component
4. Select the ... widget for the Service Name entry in the properties sheet.
5. In the popup, select new namespace, give it a URI and a prefix. http://www.somewhere.org/bob and prefix: bob
6. press OK
7. An error popup shows, stating: "The service should be defined in the WSDL's target namespace 'NamespaceTestCA'

Editing the CASA code from the source view is impossible so the new namespace cannot be added.
Comment 1 trondstromme 2008-08-14 08:07:08 UTC
contents of platform8/build_number:
netbeans hudson build: netbeans-6.1-200805300101-ml.zip
sierra hudson: 2763
sierra build: 20080807_1600
Comment 2 Sergey Lunegov 2008-10-01 15:20:42 UTC
Changed target milestone.
Comment 3 Jun Qian 2008-10-23 00:20:04 UTC
By design, all the user-created WSDL ports (DnD'ed from the WSDL binding section of CASA palette) are defined in the
same WSDL file (<compapp>.wsdl). Changing the namespace of one user-created WSDL service would change the target
namespace of that WSDL and therefore change the namespace of all the user-created services in that WSDL. This might not
be desired.

One possible fix is to introduce a new WSDL file for each user-created WSDL port, so the user can change each
user-created WSDL service's namespace independently. Unless there is a good use case to support this new design, this is
unlikely to happen.

If the user really wants to have control over the namespace, she can always define her own WSDL inside the compapp
project, and then load the WSDL port into CASA using the "Load WSDL Port..." action from the "WSDL Ports" region.

I think the easiest fix to the reported problem is to disable the namespace editing part of the QName editor (but still
enable the service name editing part) in step 5.



Comment 4 Tientien Li 2009-01-14 22:12:39 UTC
We will consider this as an enhancement, not bug.