On Jul 17, 2009, at 11:09 AM, Grégory Joseph wrote:

Which OS are you running on ? I suspect linux and an issue similar to MAGNOLIA-1958. I'm hoping we can get rid of all xml-implementation specifics jar in the bundles asap.

It's actually a FreeBSD machine but will be running on Linux in production. I'll move it over to Linux machine that is a closer match to production and see if anything changes or post more details to that issue.

Tom

On Jul 17, 2009, at 6:05 PM, Thomas Duffey wrote:


Hi All,

This is probably not specific to Magnolia but thought someone here might have seen it. I am working on a Magnolia 4.1 module running w/JDK6 and Tomcat 6 that processes XML data from a remote source. Both the author and public side get deployed to the same instance of Tomcat.

Suppose I startup Tomcat and access a page on the author side that executes the XML code. Everything works great. Then, I request the same page on the public side but this time I get an error:

...
Caused by: javax.xml.xpath.XPathExpressionException
at com .sun .org .apache .xpath .internal .jaxp.XPathExpressionImpl.evaluate(XPathExpressionImpl.java:292) at org .apache .jsp .templates .admirals .templates.team.getPlayers_jsp._jspService(getPlayers_jsp.java:148)
  ... 120 more
Caused by: java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration
  at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
  at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.<init>(Unknown Source) at org .apache .xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(Unknown Source) at com .sun .org .apache .xpath .internal .jaxp.XPathExpressionImpl.evaluate(XPathExpressionImpl.java:288)
  ... 121 more

Similarly, if I request the page first on the public side and second on the author it works the first time and gives the same error the second time. I think this has something to do with an XML library conflict but am not an expert in any of this. First thing I tried was removing the xerces JARs bundled with Magnolia. This broke Magnolia activation. Next I removed the bundled xerces JARs and placed one copy in Tomcat's lib directory. This seems to be working but I'm wondering if I created some new problem that I haven't triggered yet.

Anyone else run into this or know what's going on?

Tom


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------




----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to