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: | REGRESSION: Bpel calls to SQL engine fail | ||
---|---|---|---|
Product: | soa | Reporter: | siitpe <siitpe> |
Component: | SQL Project | Assignee: | issues@soa <issues> |
Status: | NEW --- | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
Failing NB6.1 Bpel project
Working project with manually corrected SQL and WSDL |
Description
siitpe
2008-06-11 12:06:10 UTC
So you're saying that the same exact project works fine in NB 6.0.1? If so, we'd move this issue to the runtime issue tracking system. May I also ask you to attach the project you're working with, so we could use it as a test case? Hi, No, not exactly the same project, because WSDL file generated by SQL module is different in NB6.1 and NB6.01 from exactly the same sql command file. To make operation output parameters match to SQL module output parameters I created different XSD and WSDL into NB6.1 and NB6.01 Bpel projects as well. So the scenario was: - created SQL module, used the same sql command file (.sql) in NB6.01 and NB6.1, generated WSDL, clean and build - created Composite Application for SQL module, deployed, tested, worked OK in both NB6.01 and NB6.1 - created Bpel module, created XSD and WSDL using WSDL generated by SQL module above (to match variable types) - created Composite Application for Bpel module, deployed, tested, worked OK in NB6.01 and failed in NB6.1 Error occurs when running test case of Bpel Composite application, so You may be right when suspecting runtime problem. I am sorry if this forum is wrong but the issue path was Community-Enter issue-Enterprise-Bpel project. OK, NB6.1 trying to include test projects. Regards Pentti Created attachment 62738 [details]
Failing NB6.1 Bpel project
Sorry for it having taken that long to look at the issue. Th real cause is in the WSDL generated by the SQL SE support module. According to it, the response structure of the SQL SE call should be: <xsd:element name="newSQLResponse"> <xsd:complexType> <xsd:sequence> <xsd:element maxOccurs="unbounded" ref="record"/> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="record"> <xsd:complexType> <xsd:sequence> <xsd:element name="maxPersonId" type="xsd:int"/> </xsd:sequence> </xsd:complexType> </xsd:element> While in fact the returned xml is: <newSQLResponse xmlns:msgns="http://com.sun.jbi/sqlse/sqlseengine" xmlns="http://com.sun.jbi/sqlse/sqlseengine"> <maxPersonId>100</maxPersonId> </newSQLResponse> Voila! No 'record' tags. Hence the selectionFailure in BPEL, which means that some XPath failed to evaluate to a value. Transferring. Created attachment 73931 [details]
Working project with manually corrected SQL and WSDL
|