NPE when interface extension used with Element API
--------------------------------------------------
Key: WODEN-189
URL: https://issues.apache.org/jira/browse/WODEN-189
Project: Woden
Issue Type: Bug
Reporter: John Kaputin
Assignee: John Kaputin
Fix For: M8
A null pointer exception can occur when the Element API is used with WSDL that
contains interface extension. This is because the Element API implementation
for handling interface extension reuses some of the code written to support the
Component API, but that code requires that the Component model is properly
initialized. Specifically, it requires that all Interfaces have a reference to
their containing Description. The initialization of this reference occurs
during correct use of the Component API. However, if the Element API is used
prior to the Component API this reference is uninitialized and a NPE will occur.
This problem was discovered running the Storage-4G testcase from the W3C WSDL
2.0 test suite standalone in a Woden test client. The document validator
attempts to resolve the InterfaceFaultElement for an
InterfaceFaultReferenceElement and in doing so the Woden implementation uses
the above mentioned interface extension code. The component model has not been
initialized at this time (this happens next when the component validator is
invoked), so the NPE is thrown in InterfaceImpl.getExtendedInterface(QName)
because the Description reference is null.
A solution is to ensure the component model is initialized as early as possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
