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 97513 - process definition tag created when new BP created is confusing
Summary: process definition tag created when new BP created is confusing
Status: CLOSED DUPLICATE of bug 92272
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Nikita Krjukov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-08 23:04 UTC by Murali Pottlapelli
Modified: 2007-09-03 17:06 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
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 Murali Pottlapelli 2007-03-08 23:04:18 UTC 
This is the tag it creats 
<process
    name="BP1"
    targetNamespace="http://enterprise.netbeans.org/bpel/BP1"
    xmlns="http://docs.oasis-open.org/wsbpel/2.0/process/executable"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:bpws="http://docs.oasis-open.org/wsbpel/2.0/process/executable"
    xmlns:wsdlNS="http://enterprise.netbeans.org/bpel/BP1" 
xmlns:ns1="http://j2ee.netbeans.org/wsdl/PTwithTwoOperations">

1. Default namespace of this document is "http://docs.oasis-
open.org/wsbpel/2.0/process/executable", why same namespace needs to be 
associated with "bpws" prefix?
2. targetNamespace of the document is assoicated with "wsdlNS", it is 
misleading. Can it be assoicated with something intutive? say "tns".
Comment 1 Murali Pottlapelli 2007-03-08 23:06:47 UTC 
One more issue, each prefix showing up on its own line would improve 
readability.
Comment 2 Nikita Krjukov 2007-04-06 17:49:51 UTC 
It seems there was another issue about showing up prefixes on its own lines and 
now it is already fixed. 

I agree that it worth to specify the "tns" prefix by default for the 
targetNamespace. Also I suppose such specific prefix can be assigned by the 
user in the "New BPEL Process" wizard.
Comment 3 Nikita Krjukov 2007-04-10 13:51:17 UTC 
Fixed.
Comment 4 Murali Pottlapelli 2007-04-11 01:49:51 UTC 
Thanks for fixing the issue. There is one more glitch.

When I add additional name space, in this case
"http://j2ee.netbeans.org/wsdl/newWSDL" it is added in the same line as 
xmlns:tns="http://enterprise.netbeans.org/bpel/BpelModule1/newProcess". It
should be in separate line for readability.

Please keep prefix definitions on a line by itself.   

<process
    name="newProcess"
    targetNamespace="http://enterprise.netbeans.org/bpel/BpelModule1/newProcess"
    xmlns="http://docs.oasis-open.org/wsbpel/2.0/process/executable"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:tns="http://enterprise.netbeans.org/bpel/BpelModule1/newProcess"
xmlns:ns1="http://j2ee.netbeans.org/wsdl/newWSDL">
    <import namespace="http://j2ee.netbeans.org/wsdl/newWSDL"
location="newWSDL.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"/>
    <partnerLinks>
        <partnerLink name="PartnerLink1" partnerLinkType="ns1:newWSDL1"
myRole="newWSDLPortTypeRole"/>
    </partnerLinks>
    <sequence>
   </sequence>
</process>
Comment 5 Nikita Krjukov 2007-04-12 12:57:38 UTC 
Because of the modifications aren't performed directly to the text of XML 
source, but rather with the help of XAM API, it is the responsibility of that 
module. Just because of it I marked this issue as a duplicate of the issue 
#92272. Unfortunatelly that issue is an enhancement and has P3 priority. 
Please increase the priority of that issue if you consider this glitch so 
critical.

*** This issue has been marked as a duplicate of 92272 ***