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.
Build 200708130000. Stept to reproduce: 1. Create BluePrint1 sample and BPEL module. 2. Add to Module sample LoanApplication Schema. 3. Add to Sample reference to Module. 4. Import to purchaseOrder reference to newLoanApplication. Check that reference showed as Broken. 5. Open import dialog again and import same file again. 6. Step 5 can be repeated many times. All references are broken. See screenshot also.
Created attachment 46520 [details] screenshot
BTW this is SHOWSTOPPER for cross project references testing on MacOS platform.
Tony, can you please try it on your Mac?
If it is indeed reproducible in Mac, please attach the log file...wondering if this is related to yet another JDK problem in Mac. Seems to be working nicely on Windows and Linux.
I cannot reproduce this with this system configuration- Product Version: NetBeans IDE Dev (Build 200708130000) Java: 1.5.0_07; Java HotSpot(TM) Client VM 1.5.0_07-87 System: Mac OS X version 10.4.10 running on i386; MacRoman; en_US (nb) Maybe the steps are not clear enough to be done in the exact way to cause the problem. If you can still reproduce this can you please give more detailed steps. see screenshot.
Created attachment 46539 [details] Screenshot of not broken references
Tony, You did not use cross-project reference feature to reproduce this issue. Please try the following steps again to see if you still can't reproduce the issue. Thanks. 1. Create a BluePrint1 sample project 2. Create a new BPEL module project BpelModule1. (File -> New Project -> SOA -> BPEL Module) 3. Add Loan Application Sample XML Schema newLoanApplication.xsd to BpelModule1. 4. Configure BluePrint1 project to reference to BpelModule1. * Right-click BluePrint1, select Properties * In Properties window, select Categories: Project References" * Click "Add Project" button to add BpelModule1 as a project reference to BluePrint1. * Click OK to close Properties window. 5. Open purchaseOrder.xsd in BluePrint1 project. 6. In Schema view, import newLoanApplication.xsd to purchaseOrder.xsd. (Right-click Reference Schemas -> Add -> Import). 7. Expand the import item in the second column. Will see "Broken reference" message in the third column. 8. Import the same file again. 9. Step 9 can be repeated many times. All references are broken.
Yes, Tony, you used both schemas within same project without cross-project reference. This works fine.
Created attachment 46593 [details] working with cross project reference
Trying again with the detailed steps, using cross project reference, I still see no problem. (see screenshot) And I can't add the project again, I guess because it is not broken unless I am still getting the steps wrong. This was done using Build 200708140000 on Mac.
I'll have to mark it worksforme, and please do not create P1 bugs unless you're dead sure. All bugs can't be just P1.
Hi Sam, we can reproduce this bug here. I tried today as well. We will try again with a new build tomorrow. It was a stopper for Cross-Project Reference, P1 was necessary. There were some changes, bug fixes this week which caused Cross-Project Reference not very stable.
BTW, Tony, Thanks for verifying this issue for us.
It'll be nice if the log file is attached.
yes, you are right. Will do it tomorrow.
I never set P1 just for fun and always check issue at least two times before filing. So I'm "dead sure"! Hong, thanks for confirmation.
Created attachment 46672 [details] Log
Checked with todays (Aug 15) build. Reproducible as well. Check attached log.
This might be related to issue 112458 . There was some refactoring of BPEL and XSLT projects.
I did not mean to mark as FIXED.
Looking at the log file, this issue looks same as 98212. I believe if we fix one the other should be fixed. Hoping the xml-commons source code from apache will give us some clue.
Created attachment 46758 [details] new resolver jar
Copy the attached jar to <NB_INSTALL_DIR>/netbeans/ide8/modules/ext and restart the IDE. You may see a lot of INFO exceptions in console, but thats OK, do not panic. I just want you to verify if the issues get resolved or not? Once you guys verify the same, I'll see how the console messages can be suppressed.
Yes, looks like this jar file helps!
The patch works for this on Mac OS also. I was actually able to reproduce this (finally) and now I can say that the jar file resolves the problem.
I've couple of questions w.r.t. the naming/patching/licensing of this jar and as soon as I have the right answer I'll commit the jar. Please stay tuned.
Added: /cvs/libs/resolver/external/resolver.jar, initial revision: 1.1 /cvs/libs/resolver/external/resolver.patch,v <-- resolver.patch initial revision: 1.1 /cvs/libs/resolver/external/resolver-license.txt,v <-- resolver-license.txt initial revision: 1.1 /cvs/libs/resolver/external/readme.txt,v <-- readme.txt initial revision: 1.1 Removed: /cvs/libs/resolver/external/resolver-1_1_nb.jar /cvs/libs/resolver/external/resolver-1_1_nb.patch /cvs/libs/resolver/external/resolver-1_1_nb-license.txt Updated: /cvs/libs/resolver/nbproject/project.properties, new revision: 1.4; previous revision: 1.3 /cvs/libs/resolver/nbproject/project.xml new revision: 1.4; previous revision: 1.3 /cvs/libs/resolver/manifest.mf, new revision: 1.4; previous revision: 1.3 /cvs/libs/resolver/src/org/apache/xml/resolver/Bundle.properties, new revision: 1.3; previous revision: 1.2
Fixed VERIFIED in Build 200709180000.