XOM API for Processing XML with Java

[Wolfgang Hoschek <whoschek AT lbl.gov>]

I tentatively tried this and the fix works fine. I'm not sure users  
with existing XOM production apps (that therefore don't use XPath)  
would appreciate having to bundle jaxen for no good reason...

On Jan 18, 2005, at 10:01 AM, Wolfgang Hoschek wrote:

> I think the fix is to add an additional level of indirection:
> Have Node.query() delegate to a helper class, say XPathHelper.query()  
> and do the Jaxen imports in the XPathHelper rather than Node. That  
> should fix it, because the class is looked up at a later stage, and  
> only if it's really needed.
> The diff wrt. normalizer is that classes inherit from Node but not  
> from Serializer.
>
> Wolfgang.
>
> On Jan 18, 2005, at 9:53 AM, Elliotte Harold wrote:
>
> > OK. I think I see why this is happening. It's the JaxenNavigator
> > and JaxenConnector classes. Even though these are non-public
> > classes, they do extend and publicly reference the Jaxen classes.
> > I'm not sure why JaxenException is the first class it complains about,
> > but that's probably what's going on.
> >
> > I'm not sure there's an easy way to fix this. Long term I do plan  
> > that the XPath engine will be a pretty critical part of XOM, so I'm  
> > inclined to just require it.
> >
> > --  
> > Elliotte Rusty Harold  elharo AT metalab.unc.edu
> > XML in a Nutshell 3rd Edition Just Published!
> > http://www.cafeconleche.org/books/xian3/
> > http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ 
> > ref=nosim
>
> _______________________________________________
> XOM-interest mailing list
> XOM-interest AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/xom-interest