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 88121 - I18N: validation of a BPEL file fails only on solaris
Summary: I18N: validation of a BPEL file fails only on solaris
Status: VERIFIED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Validation (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Vladimir Yaroslavskiy
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2006-10-27 00:27 UTC by Sreenivasan Genipudi
Modified: 2007-10-02 17:05 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
bpel project (20.22 KB, application/octet-stream)
2006-10-27 00:27 UTC, Sreenivasan Genipudi
Details
Validation log (1.83 KB, text/plain)
2007-05-02 14:20 UTC, Vladimir Yaroslavskiy
Details
error S10 Sparc (23.31 KB, image/jpeg)
2007-09-12 16:37 UTC, kaa
Details
Updated project (13.04 KB, application/octet-stream)
2007-09-17 09:52 UTC, Vladimir Yaroslavskiy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sreenivasan Genipudi 2006-10-27 00:27:08 UTC
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.
Comment 1 Sreenivasan Genipudi 2006-10-27 00:27:34 UTC
Created attachment 35584 [details]
bpel project
Comment 2 Michael Frisino 2006-11-20 14:14:03 UTC
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.

Comment 3 Sreenivasan Genipudi 2006-12-01 00:15:37 UTC
This issue was filed on behalf of Alex Fung. 

Alex, 
 Can you please verify.
Comment 4 Ken Frank 2007-02-15 19:41:37 UTC
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
Comment 5 Alexei Mokeev 2007-02-19 07:05:39 UTC
There was an objection from Ken against waiving it. Waiting for resolution
between Ken and Venkat.
Comment 6 Alexei Mokeev 2007-02-20 07:36:15 UTC
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"
Comment 7 Alexei Mokeev 2007-03-05 17:24:16 UTC
Removed Beta EP551_WAIVER_APPROVED keyword - we are going forward to FCS.
Comment 8 Vladimir Yaroslavskiy 2007-04-25 14:21:54 UTC
tried with the build 20070425, can't reproduce it.
Comment 9 kaa 2007-04-27 18:26:58 UTC
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.

Comment 10 Vladimir Yaroslavskiy 2007-05-02 14:17:24 UTC
File I18nBasic2.bpel uses I18nBasic2.wsdl file which fails on validation, see
log. So, reassign to xml validation. Wsdl file should pass first.
Comment 11 Vladimir Yaroslavskiy 2007-05-02 14:20:38 UTC
Created attachment 42047 [details]
Validation log
Comment 12 Shivanand Kini 2007-07-09 20:31:39 UTC
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?

Comment 13 Shivanand Kini 2007-08-21 22:57:22 UTC
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.

Comment 14 kaa 2007-09-12 16:36:52 UTC
On WinXp validation passed.
On Sparc S10 there is 1 error:


Comment 15 kaa 2007-09-12 16:37:33 UTC
Created attachment 48669 [details]
error S10 Sparc
Comment 16 Shivanand Kini 2007-09-12 19:49:14 UTC
was the namespace's corrected in the solaris while testing?
Comment 17 Shivanand Kini 2007-09-12 19:50:41 UTC
assigning to bpel validation
Comment 18 Vladimir Yaroslavskiy 2007-09-14 13:38:47 UTC
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.
Comment 19 Ken Frank 2007-09-14 17:00:37 UTC
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
Comment 20 Vladimir Yaroslavskiy 2007-09-17 09:52:29 UTC
Created attachment 48911 [details]
Updated project
Comment 21 kaa 2007-10-02 17:05:41 UTC
verified: build 0927, updated project