Rickard �berg wrote:
> Second, your choice of parser might conflict with what EJBOss 1.0 uses,
> which is ProjectX. Can you try and use the supplied parser instead? Does
> that remove this problem?
>
Not a very good solution :-( There are many good reasons to use Xerces and not
sun xml, not the least of which are DOM2/SAX2, which are really used for server
side applications to allow you to not have the entire DOM tree in memory at the
same time.
Since this is probably what you would wish to do in an EJB, maybe a better
solution would be for jboss to use JAXP to make its parser into a plugin and
therefore not interfere with anyone's beans. This should be quite simple as long
as you are just doing simple parsing.
Actually now that I think about it the question arises as to whether 2 beans
which are deployed which contain different versions of the org.w3c.dom classes
will interfere with each other? Or any other beans which come with "outdated
versions" of utility classes? Anyone know?
Regards
Geoff Hill.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
