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 125634 - namespace declaration disappears from WSDL
Summary: namespace declaration disappears from WSDL
Status: VERIFIED WORKSFORME
Alias: None
Product: xml
Classification: Unclassified
Component: WSDL Tools (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P1 blocker (vote)
Assignee: Shivanand Kini
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-21 01:30 UTC by Lukas Jungmann
Modified: 2008-02-07 16:31 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Jungmann 2008-01-21 01:30:07 UTC
reported by Greg Parker on nbusers list:

"I am developing a WSDL file in NetBeans.  For some reason the namespace
declaration:

xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype"

gets automatically removed from the file.  When I try to reinsert it
manually, two seconds later it disappears.  What's up with that?  Very
annoying! "
Comment 1 parkerg 2008-01-21 01:56:34 UTC
Product Version: NetBeans IDE 6.0 (Build 200711261600)
Java: 1.5.0_12; Java HotSpot(TM) Client VM 1.5.0_12-b04
System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb)
Userdir: C:\Documents and Settings\greg.parker\.netbeans\sierra
Comment 2 Nam Nguyen 2008-01-21 19:51:13 UTC
What platform and JDK you are on?  Could you help with more detailed steps or attach a refined WSDL to reproduce this
behavior?

No matter hov many duplicate namespace declarations xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype" I added
to top or to sub nodes, I could not reproduce the described behavior.  

I am using:

Product Version: NetBeans IDE 6.0 (Build 200711261600)
Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b05
System: SunOS version 5.11 running on x86; ISO646-US; en (nb)

I could not reproduce with latest NB 6.1 either.
Comment 3 Lukas Jungmann 2008-01-21 20:14:21 UTC
Nam, details are in desc2.

I saw the same behavior in the past, but it has been quite random.
If I recall correctly it usually happened to me when I was tweaking definitions element in the WSDL directly in the
editor (and I had full IDE installed), particularly:
-I had some existing WSDL file
-I added some xmlns:sth="someNamespace"

Case 1)
-went to the some other element, ie portType
-invoked CC

Case 2)
-paste some pre-existing xml fragment which used elements from "sth" namespace somewhere to the wsdl
-validate WSDL file

but as I said it has been quite random, I was never successful to reproduce it with clean userdir, I was able to do so
only when I was running some build for more days
Comment 4 Nam Nguyen 2008-01-21 22:08:52 UTC
I used environment as in "desc 2" with full NB 6 installed on windows with jdk5, tried your 2 suggested scenario and
also the plnk namespace, and still could not reproduce.  Please provide more refined test case to reproduce.
Comment 5 parkerg 2008-01-22 00:35:28 UTC
I can now reproduce this error at will.  Here is how:

- Open Netbeans
- Create a new BPEL module
- Right click on the project and choose "New -> WSDL Document..."
- Keep the default values and hit "Next"
- Choose finish
- The WSDL document should now be open to the "WSDL" view
- Switch to the "Source" view
- Put your cursor just before xmlns:tns="http://j2ee.netbeans.org/wsdl/newWSDL" namespace declaration and hit <enter>
- Put you cursor just before xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype" namespace declaration and hit
<enter>
- Select xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype" with your mouse
- Hit <CTL>X
- Hit the up arrow
- Hit <CTRL>V to paste
- Hit <enter>
- Wait for a second or two and plnk should disappear (at least it does for me)


Comment 6 Nam Nguyen 2008-01-22 04:39:45 UTC
Thanks for the detailed test case.  However I still could not reproduce.  It seems you are using some special version of
NB 6.0 called "sierra" ?  If so where could I get the same version to confirm?
Comment 7 parkerg 2008-01-22 13:40:28 UTC
The install came from the Open ESB project at https://open-esb.dev.java.net/Downloads.html.  I applied a few available
updates on my version of NetBeans this morning, an retested the problem.  I tried three times and have not been able to
reproduce the problem so far.

Comment 8 Nam Nguyen 2008-01-22 17:47:54 UTC
OK.  So this is just some bad behavior isolated in the various branching/merging points of sierra branch.
I would just leave the bug as closed for now and will forward the matter to sierra team to see if any actions needed at
this time regarding the branch.
Comment 9 Shivanand Kini 2008-01-22 18:08:28 UTC
This has been fixed in 6.1. Once the open-esb installer uses the newer build, this will get resolved.
Comment 10 jlautz 2008-02-07 16:31:45 UTC
I could not reproduce this problem with 
Product Version: NetBeans IDE Dev (Build 200802041203)
Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b05
System: SunOS version 5.10 running on x86; ISO646-US; en (nb)
Userdir: /Users/lautz/.netbeans/dev