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.
Created a BPEL Module, LoanRequestor Created XML Schema, LoanRequestor.xsd Created a BPEL Process Create a New WSDL Document Check Import XML Schema, select LoanRequestor.xsd. In the Abstract Configuration wizard do the following: In the Input area, set the message part name to requestLoanMessage . In the Input area, under Element Or Type, click the ellipsis button. Expand LoanRequestor > src/LoanRequestor.xsd > Elements Select processApplication and click Ok. In the Output area, set the message part name to responsePart . In the Output area, under Element Or Type, click the ellipsis button. Expand LoanRequestor > src/LoanRequestor.xsd > Elements Select processApplicationResponse and click OK. Click Next. The Concrete Configuration page opens. For Binding Subtype, make sure the Document Literal is selected. Click Finish. there are 2 identical nodes under Types > Reference Schema Open the WSDL source, there are two imports: <types> <xsd:schema targetNamespace="http://j2ee.netbeans.org/wsdl/LoanRequestor" xmlns:ns1="http://xml.netbeans.org/schema/LoanRequestor"> <xsd:import namespace="http://xml.netbeans.org/schema/LoanRequestor" schemaLocation="../../../../Demo/LoanRequestor/src/LoanRequestor.xsd"/> <xsd:import namespace="http://xml.netbeans.org/schema/LoanRequestor" schemaLocation="LoanRequestor.xsd"/> </xsd:schema> </types>
Created attachment 34548 [details] loanrequestor.zip is added
Which build? I just verified the fix for a similar issue 85656 in the 060925_1 build.
used the following: http://balui.sfbay/kits/oriondev/main/Build060925_1/installers/
I am having problems reproducing this scenario. Which .xsd file from your zip am I supposed to use to create the XML schema in the second step? There are a bunch, and most of them complain when I try to import them because of a reference to a Demo directory?
You are usinng 9/25 build http://balui.sfbay/kits/oriondev/main/Build060925_1/installers/ This bug was fixed on 9/25, I just verified your use case and it works fine. please retest withe today's build. *** This issue has been marked as a duplicate of 85656 ***
Created attachment 34553 [details] loanrequestor.xsd
loanRequestor.xsd is under src folder. I just attached it.
when I go to bug 85656 It says: Verified on Windows XP with NB 55 060925_1. I am using the same build!! What am I missing?
I cannot recreate this problem with the 060925_1 build. Does the build you're running have 200609260000 or 200609250000 in the title bar?
Created attachment 34554 [details] screenshot running 200609260000
If you just import the schema but do not select the message type for input type and output type then you are not able to see the problem. follow my steps using the imported schema.
I followed steps exactly as written, starting with creating a new BPEL model. The issue that this is marked duplicate of (issue 85656) also changes the message part types to be an element defined in the imported schema (specified in Name and Location pane). It failed in 060925, works today in 060925_1. I noticed that the .zip file contains a lot of artifacts besides the wsdl, bpel, and xsd. Might those be causing this unexpected behavior? I'm trying to pinpoint where your scenario and mine are importantly different. (Thinking . . . thinking . . . )
I opened up the project in the .zip file, and I noticed that when I look at the generated WSDL, the two generated import statements aren't identical: <xsd:schema targetNamespace="http://j2ee.netbeans.org/wsdl/LoanRequestor" xmlns:ns1="http://xml.netbeans.org/schema/LoanRequestor"> <xsd:import namespace="http://xml.netbeans.org/schema/LoanRequestor" schemaLocation="../../../../Demo/LoanRequestor/src/LoanRequestor.xsd"/> <xsd:import namespace="http://xml.netbeans.org/schema/LoanRequestor" schemaLocation="LoanRequestor.xsd"/> </xsd:schema> The first import is showing up in the graphical WSDL editor as a Broken reference. Any ideas why it's looking for something in a Demo directory that isn't included in the project?
As I mentioned eariler, there was a bug where the import was not getting generated correctly when you finish the wizard. import was generated something like the one you are refering: schemaLocation="../../../../Demo/LoanRequestor/src/LoanRequestor.xsd"/> This has been fixed so correct import is generated. It will show broken refernce now since there is no xsd at ../../../../Demo/LoanRequestor/src/LoanRequestor.xsd
radval -- which bug fix are you referencing in your last comment? issue 85400 is about broken references . . . ? issue 85656 doesn't describe what the fix was either . . . I'm not sure where to go from here.
Verified with the 060925_1 build (java-tools-bundle-main-060925_1-windows.exe). Not able to reproduce the bug. I can see only one import. Please see attachment. Marking the bug verified.
Created attachment 34559 [details] WSDL File showing Single import node
Created attachment 34560 [details] Source view of single import
Reopening this. I was not able to reproduce this before, but now on the 0928 build I can. I do not think this is consistently reproduceable on all machines, but it is consistently reproduceable on my machine. I have installed the same build (same JDK version) on two WindowsXP machine. On one machine it can be constantly reproduced, on the other machine, i do not see the issue at all. I would like for a developer to come take a look at my machine as I do not see any diffrences between the two, but this is definitely an issue for me.
After debugging this, in some cases model.findSchemas(namespace) returned a empty list even though the schema was present in the model.
assigning to model.
Skini, your debug observation does not correspond to bug description. Could you explain more why you think this is model bug. Also confirm that you are able to reproduce this bug.
I cannot reproduce this bug on my computer. The inconsistent nature of the bug probably tells of the timing issue. Without know much about how the wizard pages dispatch model mutaions, I guess there might be 2 places of interest: (1) where we call addImport directly (corresponds to import schema on first page) and, (2) where addImport is called indirectly as result of Part.setElement(). In both places, make sure skip addImport call if there already exists import with the same schemalocation or namespace. Reassign back to wsdltools.
i was not able to reproduce this on my machine. But I used the QE machine and debugged on it. Based on that observation, i found that the model.findSchemas(namespace) gave empty result. Thats why I felt it was a model problem. I will debug through the model, as soon as I find a build that I can reproduce it on. Sherry was also able to reproduce it on her machine with todays build. So i installed it on my machine, but I am not able to reproduce it.
cc ing Nam with comments
This is reproduceable if you set your windows TEMP dir to C:\Windows\Temp and you project is in some space seperated folder like "Document And Settings". The fix would be encode the url so that spaces are replaced by %20 and other such character by their encoded versions.
Currently, the fix is going to as follows: There are two steps while creating a wsdl through the wizard. 1. Create a temporary wsdl model 2. Copy this temporary wsdl to the correct wsdl. So the schema location in first step is generated relative to the temp wsdl. The relative path in this case has spaces in it, which needs to be escaped. Then later, when the finish is clicked on wizard, the temp model is copied to new one and the imports are processed to put the correct relative path. Current fix is to use absolute URI's for temp model for schema location. In post process, the schema locations are adjusted.
Fixed in release55 and release55_dev. Code reviewed by Ritesh. Tested by me.
Verified that the now only one import will appear: <types> <xsd:schema targetNamespace="http://j2ee.netbeans.org/wsdl/LoanRequestor"> <xsd:import namespace="http://xml.netbeans.org/schema/LoanRequestor" schemaLocation="LoanRequestor.xsd"/> </xsd:schema> </types>