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.
BPEL ( 18nBasic2.bpel ) file fails validation only on Solaris machine. If the same bpel is validated on Windows machine it validates fine. I am attaching the BPEL Project. The offending bpel is packaged in the project. Validation error: XML validation started. space/alaska/jbicomps/test/httpsoapbc/i18n/I18nBpel/src/I18nBasic/I18nBasic2.bpel:15,8 Element "variable" has reference to external "WSDL" element ( via "messageType" attribute value ) and this element cannot be found.Please check namespace declarations, "import" elements, attribute value or name of referenced element. space/alaska/jbicomps/test/httpsoapbc/i18n/I18nBpel/src/I18nBasic/I18nBasic2.bpel:21,57 Element "to" has reference to external "WSDL" element ( via "part" attribute value ) and this element cannot be found.Please check namespace declarations, "import" elements, attribute value or name of referenced element. space/alaska/jbicomps/test/httpsoapbc/i18n/I18nBpel/src/I18nBasic/I18nBasic2.bpel:14,8 Element "variable" has reference to external "WSDL" element ( via "messageType" attribute value ) and this element cannot be found.Please check namespace declarations, "import" elements, attribute value or name of referenced element. space/alaska/jbicomps/test/httpsoapbc/i18n/I18nBpel/src/I18nBasic/I18nBasic2.bpel:21,12 Element "from" has reference to external "WSDL" element ( via "part" attribute value ) and this element cannot be found.Please check namespace declarations, "import" elements, attribute value or name of referenced element. 4 Error(s), 0 Warning(s). XML validation finished.
Created attachment 35584 [details] bpel project
Is this still a problem? Can you please make sure this is a problem in more than one project. Perhaps there was something peculiar about that one project installation.
This issue was filed on behalf of Alex Fung. Alex, Can you please verify.
can you elaborate on details - is it the use of non ascii or multibyte in some places or names of things that is the cause ? Can a gif of the error be shown - especially if it shows some multibyte that is not displayed correctly ? ken.frank@sun.com
There was an objection from Ken against waiving it. Waiting for resolution between Ken and Venkat.
Not a stopper accoriding to Ken. However migh be visible for users: "I was just clarifying that some i18n things, like these bugs, would be visible to users of the en beta, who run in other locales"
Removed Beta EP551_WAIVER_APPROVED keyword - we are going forward to FCS.
tried with the build 20070425, can't reproduce it.
18nBasic2.bpel from the issue wasn't pass validation in M9, build 070427 Output is below: XML validation started. C:/Downloads/I18nBpel/src/I18nBasic/I18nBasic2.bpel:8,115 Error: cvc-elt.1: Cannot find the declaration of element 'process'. 1 Error(s), 0 Warning(s). XML validation finished.
File I18nBasic2.bpel uses I18nBasic2.wsdl file which fails on validation, see log. So, reassign to xml validation. Wsdl file should pass first.
Created attachment 42047 [details] Validation log
is the wsdl valid? It looks like it has some junk characters in the message name. Can you retry with a newly created wsdl file?
For the bpel validation, the bpel has older namespaces which are not valid anymore. Also the wsdl validates fine now, I am guessing after the fix for 111955. Please verify.
On WinXp validation passed. On Sparc S10 there is 1 error:
Created attachment 48669 [details] error S10 Sparc
was the namespace's corrected in the solaris while testing?
assigning to bpel validation
For QE: 1. Please change old namespace in all bpel files from http://schemas.xmlsoap.org/ws/2004/03/business-process/ to http://docs.oasis-open.org/wsbpel/2.0/process/executable 2. Also update old and deprecated xmlns:plink in all wsdl files from http://schemas.xmlsoap.org/ws/2004/03/partner-link/ to http://docs.oasis-open.org/wsbpel/2.0/plnktype 3. Remove from the project conflict files .#.* 4. Zip and attach update project. 5. Verify the issue with the *updated* project.
about the steps for QE in comment below: if we use new build and new userdir, would those steps below need to be done ? we want to verify it just as user would ? that is, what was the problem with this issue that was fixed ? that will let us know what scenario to use since am assuming it was some kind of problem not unique just to the project that was attached by filer ? sreenig and alex fung, could you also provide some information about the scenario of the project that was attached ? ken.frank@sun.com
Created attachment 48911 [details] Updated project
verified: build 0927, updated project