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 125954 - Validation should provide error on unqualified query element
Summary: Validation should provide error on unqualified query element
Status: CLOSED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Validation (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Vladimir Yaroslavskiy
URL:
Keywords:
Depends on:
Blocks: 124787
  Show dependency tree
 
Reported: 2008-01-24 19:27 UTC by Shivanand Kini
Modified: 2008-10-20 12:23 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Validation - No Error (86.83 KB, image/jpeg)
2008-04-02 10:11 UTC, senthilprabhu 		Details
Apr 18 - No Validation Error (250.16 KB, image/jpeg)
2008-04-18 15:05 UTC, senthilprabhu 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Shivanand Kini 2008-01-24 19:27:27 UTC 
See http://www.netbeans.org/issues/show_bug.cgi?id=124787

Since property alias schema allows for any element, wsdl editor validation, cannot generate error messages for unknown
extensibility elements, which are possible as per the schema definition.
This needs to be handled by the extensiblity element providers. In this case, the wsdlext module.
Comment 1 Sergey Lunegov 2008-01-25 08:02:25 UTC 
Vladimir, please look at this.
Comment 2 Vladimir Yaroslavskiy 2008-01-25 11:54:37 UTC 
Nikita,

Your wrote validation for qualified/not qualified elements.
Please adjust your code to process wsdl ext elements correctly.
Comment 3 Vladimir Yaroslavskiy 2008-02-19 11:51:59 UTC 
fixed.

1. Create BluePrint1 sample
2. Open POService.wsdl file
3. Change line 101 from
   <bpws:query>/sns:purchaseOrder/sns:orderId</bpws:query>
   to
   <query>/sns:purchaseOrder/sns:orderId</query>
4. See validation error.
Comment 4 senthilprabhu 2008-04-02 10:07:41 UTC 
I'm not finding the validation error in MS8 build
I have attached the screenshot

I tried the Bpel Blueprint1 application also. Validation is not working
Comment 5 senthilprabhu 2008-04-02 10:11:55 UTC 
Created attachment 59528 [details]
Validation - No Error
Comment 6 Vladimir Yaroslavskiy 2008-04-02 10:14:34 UTC 
P2 -> P3: minor issue
Comment 7 Vladimir Yaroslavskiy 2008-04-02 14:21:33 UTC 
first fix: 7c914c89aab7
Comment 8 Vladimir Yaroslavskiy 2008-04-02 14:22:42 UTC 
second fix: 143e6ebec5e1

fixed in trunk
Comment 9 Vladimir Yaroslavskiy 2008-04-02 14:26:13 UTC 
Steps to reproduce:

1. Create BluePrint1 sample
2. Open POService.wsdl file
3. Switch to Source view
4. Change line 98 from
   <bpws:query>/sns:purchaseOrder/sns:orderId</bpws:query>
     to
   <query>/sns:purchaseOrder/sns:orderId</query>
5. Press Validate XML button (Alt+Shift+F9)

See validation error:
ERROR: Property alias has <query> element with wrong prefix or without prefix at all.
Comment 10 senthilprabhu 2008-04-18 15:02:51 UTC 
I am using Caps Nightly build 20080416-0500  and Netbeans build 200804100130

This validation is not working. 

Since it worked for the Developer and not for me, I've raised the priority to take it to the notice of the Developer.

I have attached the screenshot - No validation error
Comment 11 senthilprabhu 2008-04-18 15:05:32 UTC 
Created attachment 60414 [details]
Apr 18 - No Validation Error
Comment 12 Shivanand Kini 2008-04-18 18:20:19 UTC 
caps build does not have this fix, since its based on the release61 branch.
This should be a 6.1 patch candidate.
Comment 13 Vladimir Yaroslavskiy 2008-04-21 11:02:20 UTC 
fixed in release61: 2ae410229a99
Comment 14 senthilprabhu 2008-10-20 12:23:24 UTC 
Checked with the GFESB build 20081019-0702 and verified to work correctly
The following validation error is thrown
"C:/Documents and Settings/sp201017/Desktop/AirlineRes_Errored/BpelModule1/src/AirlineReservationWSDL.wsdl:85,4
ERROR: Property alias has <query> element with wrong prefix or without prefix at all."

This issue can be closed