[
https://issues.apache.org/jira/browse/WODEN-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710422#action_12710422
]
Sagara Gunathunga commented on WODEN-152:
------------------------------------------
I have fixed the issue with JAXP API and tested successfully with following
parser options.
1. Apache Xerces on Classpath.
2. Apache Crimson on Classpath.
3. Only default JAXP implementation on Classpath.
Following classes are depend on Xerces and in the same line i have described
the possible solutions.
(1) - DOMSchemaResolverAdapter use XMLSerializer for serialization. Here JAXP
javax.xml.transform.Transformer can be used as an alternative for
XMLSerializer. ( Other alternative is DOM Level-3 API but still lot of Parsers
does not support for this. )
(2) DOMWSDLReader use Xerces DOMParser to read the WSDL document.It is
possible to use JAXP javax.xml.parsers.DocumentBuilder API to read the document
instead of Xerces DOMParser. Also JAXP new javax.xml.validation.Schema based
validation approach can be used for validation.
(3) Some of the tests depend on Xerces DOMParser but those can be modified with
JAXP API.
If there is no any concern with above approach i will continue with this and
will upload my patches.I 'd appreciate any comments .
> Woden shouldn't be dependent on Xerces
> --------------------------------------
>
> Key: WODEN-152
> URL: https://issues.apache.org/jira/browse/WODEN-152
> Project: Woden
> Issue Type: Bug
> Components: Parser
> Environment: Any
> Reporter: Paul Fremantle
> Assignee: John Kaputin
> Priority: Minor
>
> Woden is hard-coded to use Xerces. This is based on schema validation.
> However, not all users want schema validation. The dependency should be
> loosened so that any DOM parser will work. If schema validation is required
> and Xerces isn't loaded, it can throw an exception.
--
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]
