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.
| Summary: | validation for property alias. | ||
|---|---|---|---|
| Product: | soa | Reporter: | kiran_bhumana <kiran_bhumana> |
| Component: | BPEL Validation | Assignee: | Vladimir Yaroslavskiy <yaroslavskiy> |
| Status: | VERIFIED FIXED | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: |
bpel project
updated test project for verification |
||
Created attachment 33221 [details]
bpel project
This validation is related to a wsdl extension. This should be handled by the wsdl validator. I don't think we can really have a validation for this. The reason is that what if a message/part points to xsd elememt which has any element and an xpath query is written which includes steps from this any element. There is no way of knowing the content of any element in design time. if no query specified then message/part combination should point to an schema simple type. This is doable but again we can do it only if part is not of any element type. if query is specified then we need to run the xpath query against an instance document to be able to really check the result to be a simple type. For complex query which can have function , it is not possibly to do this unless there an instance document, so I think this better left at runtime to do this validation. You have pointed some valid reasons and cases where validation can't be done. BUt we can do validation for the rest of the 80% situations. In the 5.x experience, i have never seen usage of functions in property alias. You should confirm this with the field folks as to how many times they use or not. Regardless, there are so many other situations we can validate based on the schema. Why can't we solve those? Btw, any is not a simple type. any as i understand is a complex type. If the query leads to an any element then it should be wrong. This is validation enhancement to propertyAlias, this can not be fixed now in current release. Making this enhancement. is this feature not present currently? I thought the validation was added last month or so. I think i have seen some related things happened. But don't know for sure if this is fixed. Could you please verify and close the bug? nikita, can you verify whether the property alias validation that was added includes this scenario? Created attachment 56972 [details]
updated test project for verification
fixed: if a property alias has query and combination of query and a combination of message part + query + associated property points to the same type, validation checks whether this type is simple. For verification: open attached updated project "checktype", see that first property alias passes validation (type is string), but second property alias has error: it points to the complex type VeryComplexType. v/w lb related 148447 |
Validation should point out if the property alias doesn't resolve to a simpl dataType. for example, in the following propertyAlias, first one resolves to a simple data type but not the second one ,because the query was absent. A combination of Message part and query should resolve to a simple data type. <bpws:propertyAlias propertyName="tns:propJMSHeadersName1" messageType="tns:messageRequestReply" part="partReqReply"> <bpws:query>correlationID</bpws:query> </bpws:propertyAlias> <bpws:propertyAlias propertyName="tns:propJMSHeadersName2" messageType="tns:messageRequestReply" part="partReqReply"> <bpws:query></bpws:query> </bpws:propertyAlias>