-
This tracker is a duplicate of 1689969, which already contains a patch file with the required fix. Closing this tracker.
2007-08-20 10:19:31 UTC in Web Services Description Language for Ja
-
File Added: WSDLReaderImpl_parseOperation.patch1.txt.
2007-07-17 13:10:56 UTC in Web Services Description Language for Ja
-
A NPE occurs when parsing a WSDL with the defined before the element. See stack trace below. The cause is in parseOperation - the line that sets 'op' to null if retrieved = true should be moved after the invocation of parseExtensibilityAttributes. Testcase and patch are attached.
java.lang.NullPointerException
at...
2007-07-17 13:10:36 UTC in Web Services Description Language for Ja
-
The supposed second error (Duplicate Operation) was actually an error in my test client, not in the parseBinding method. The WSDL testcases contain portypes and bindings with 2 operations with the same name, one with named and messages and the other with unnamed messages. My test client was calling:
BindingOperation bop = bnd.getBindingOperation("hello", null, null);
This...
2007-04-02 15:00:45 UTC in Web Services Description Language for Ja
-
The attached testcase Hello1.wsdl recreates the NPE reported in this tracker. The patch in the patch1 file fixes this.
However, a further error occurs when WSDLReader attempts to parse the binding:
java.lang.IllegalArgumentException: Duplicate operation with name=hello, found in binding '{http://pxe/bpel/unit-test.wsdl}HelloSoapBinding'.
at...
2007-04-02 14:39:38 UTC in Web Services Description Language for Ja
-
File Added: Hello4.wsdl.
2007-04-02 14:33:05 UTC in Web Services Description Language for Ja
-
File Added: OperationNPE.1689969.patch1.txt.
2007-04-02 14:31:19 UTC in Web Services Description Language for Ja
-
File Added: Hello1.wsdl.
2007-04-02 14:30:20 UTC in Web Services Description Language for Ja
-
Yes, your right about DTDs. WSDLLocator won't help. We'll look into adding support for registering an EntityResolver via the javax.wsdl packages defined by JSR110 (the JWSDL API), rather adding a separate, implementation-specific method to the com.ibm.wsdl packages used by the WSDL4J implementation. However, this will need to be done as a maintenance release of JSR110.
To provide flexibility...
2007-02-21 16:42:22 UTC in Web Services Description Language for Ja
-
To determine whether to make the changes to WSDL4J that you propose I need to understand the underlying requirement - first of all to confirm that it is not already handled by WSDL4J and if not, then to confirm that your proposal is the best approach. What is it you need to do that requires a custom EntityResolver to be set on the DocumentBuilder? Can you please describe the actual use case and...
2007-02-15 17:08:58 UTC in Web Services Description Language for Ja
