I think John already replied to this but just in case...
There are a couple primary reasons we selected to create a dependency on Xerces.
1. Not all XML parsers perform schema validation (that is, validation of an XML document against its schema grammar). Specifically, the Sun 1.4.2 JRE bundles Crimson, which will not perform schema validation. As Woden depends on schema validation for a good portion of the rules of the WSDL 2.0 spec it seems in the best interest of our clients that we require an XML parser that performs schema validation.
2. Xerces provides enhanced resources resolution interfaces (for URI resolvers) when compared with the JAXP standard interfaces. These enhanced interfaces have proven useful when working with Xerces for the Eclipse WTP project and they may be helpful for Woden as well. (I still have to take a look at Graham's URI resolver patch to see what the current state is of resource resolution in Woden.)
Do you have a specific requirement that's conflicting with the Xerces requirement or was your question simply one of good practice for Woden?
Thanks,
Lawrence
| "Jeremy Hughes"
<[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 09/21/2006 07:01 AM
|
|
Hi,
We're using some features and properties which are Xerces impl
dependent. If there is a way of achieving the equivalent function in a
standard way then sure we'll move to using that. Either no-one has
looked into that or they have and found it not possible.
John, Lawrence - do you know if there is a standard-based way of
achieving the same thing as the features and properties we set on the
DOMParser in DOMWSDLReader?
Cheers,
Jeremy
On 9/19/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> It seems that the DOMWSDLReader is strongly tied to
> xerces for parsing DOM. Even if the parsing is performed
> ouside, this class will still throw an CNFE if xerces is not
> in the classpath.
>
> Is there any plans to use standard DOM apis instead ?
>
> --
> Cheers,
> Guillaume Nodet
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
