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 106312 - Validation shows error, error is not clear & no help on how to fix it
Summary: Validation shows error, error is not clear & no help on how to fix it
Status: CLOSED INVALID
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Validation (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Nikita Krjukov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-11 20:14 UTC by Murali Pottlapelli
Modified: 2007-09-04 11:10 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
project (22.57 KB, application/octet-stream)
2007-06-11 20:15 UTC, Murali Pottlapelli
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Murali Pottlapelli 2007-06-11 20:14:11 UTC
Validation shows error, error is not clear & no help on how to fix
1. Open the attached project
2. open benchMark.wsdl
3. validate
It shows
XML validation started.

C:/openEsb/open-jbi-components/driver-tests/bpelse/benchamark/BenchmarkBpel/src/performance/benchMark.wsdl:22,4
Error: Can not find the element "string" at the namespace
"http://schemas.xmlsoap.org/wsdl/".  Expression: "string"

1 Error(s),  0 Warning(s).
XML validation finished.

It is fixed by modifying query "string" to "tns:string" as shown below, it would
 help user if we can point this out.
    <vprop:propertyAlias propertyName="tns:property"
                        messageType="tns:benchMarkMessage"
                        part="benchMarkPart">
    	<vprop:query>tns:string</vprop:query>
    </vprop:propertyAlias>
Comment 1 Murali Pottlapelli 2007-06-11 20:15:45 UTC
Created attachment 43521 [details]
project
Comment 2 Nikita Krjukov 2007-07-05 16:23:10 UTC
I agree that the message is a bit misleading. 

It only notifies that the validation algorithm was not be able to 
find the XML Schema element "string" which is used as a Query of 
the property alias declaration. 

But in the particular case the error has been caused by a mistake in the 
code (issue #106445) and because of that issue had been already fixed, 
now another validation message appears: 

Warning: The element "string" is qualified. It has to be prefixed with the "tns". 
Expression: "string"
  It means that the string has to be used with a prefix because of it 
is declared as having the qualified form in the schema. 

Warning: The schema with the namespace "http://localhost/MultiDepBpel/benchMark" 
has to be imported. Expression: "string"
  This message is incorrect because there is the corresponding schema in the WSDL. 
  So any additional importing isn't requred. I'm going to fix it now. 



Comment 3 Nikita Krjukov 2007-07-05 17:27:42 UTC
fixed
Comment 4 Murali Pottlapelli 2007-07-05 20:17:47 UTC
It is not fixed. Attached project benchMark.wsdl should spit errors on validation.

In query element string not qualified. Tool should identify that as an error.
Comment 5 Nikita Krjukov 2007-07-11 20:37:42 UTC
I changed the state to invalid again only in order to attract you attention.

I see the following message now:

   Warning: The element "string" is qualified. 
   It has to be prefixed with the "tns". Expression: "string"

So clarify me what is wrong, please. 
Do I understand right that you insist on absence of a prefix 
must be treated as an error but not as a warning? 

Honestly, I was not sure about it. 
Could you say if the presence of an unnecessary prefix 
also should be considered as error? 
Comment 6 Murali Pottlapelli 2007-07-11 23:02:49 UTC
Thanks for fixing the issue!

Warning is perfectly fine and it is better solution. Please refer to following description for the details.

In a WSDL a message part may be declared as "Person" type. If BP modeler knows that the document he would be getting for
the part is of type "Employee" (BP may not access to the schema document defining this type), it is perfectly fine to
define xpath query with "EmployeeId" on the path.

So I vote for warning.

would you be fixing the positions (C:/openEsb/projects/xpath/BenchmarkBpel/src/performance/benchMark.wsdl:22,4
Warning: The element "string" is qualified. It has to be prefixed with the "tns". Expression: "string"
, it should be 25.xx) to be accurate?

    
Comment 7 Nikita Krjukov 2007-07-12 15:32:24 UTC
Problem with the incorrect line numbers is fixed.