Sometimes individuals on the Apache Tomcat users list will reluctantly answer 
questions about JBoss. Not so reluctantly on classloading.

http://tomcat.apache.org/lists.html#tomcat-users

Try the archives first.

Regards,
Dave

On Sep 13, 2011, at 1:20 PM, Herter, Scott wrote:

> Thanks, that at least gives me a clue.
> 
> As for the list, I looked around, there isn't much here yet so this seemed 
> the best fit.
> 
> Are there other lists that would be better or is the project not quite that 
> far along yet?
> 
> Thanks.
> 
> -----Original Message-----
> From: Pedro F. Giffuni [mailto:[email protected]] 
> Sent: Tuesday, September 13, 2011 2:55 PM
> To: [email protected]
> Cc: Herter, Scott
> Subject: RE: Problem using Java for integration from JBoss 5.1
> 
> Hi;
> 
> I think JBoss is trying to use saxon but the version in OpenOffice conflicts 
> with what JBoss expects.
> 
> Installing the complete saxon may work but maybe it's a CLASSPATH issue and 
> reinstalling JBoss does the trick. It's not an issue to be solved in this 
> list though, except for reminding us to replace saxon with Apache Xalan in 
> the future :(.
> 
> Pedro.
> 
> --- On Tue, 9/13/11, Herter, Scott <[email protected]> wrote:
> 
>> The problem is that we were not using
>> Saxon to begin with, it is something in the OpenOffice 3.3 jars that 
>> is causing this.  Unfortunately I have been unable to find anything 
>> that says you only need jars x,y, and z in order to use the UNO API 
>> from Java to OpenOffice so we just dumped all of them in the EAR file.  
>> With earlier versions it didn't seem to matter, now it does.  Looks 
>> like I am in for some long nights trying to figure out what Jars we 
>> don't really need or we wait for the next version and hope the problem 
>> goes away.
>> 
>> Thanks for the help.
>> 
>> -----Original Message-----
>> From: Pedro F. Giffuni [mailto:[email protected]]
>> 
>> Sent: Tuesday, September 13, 2011 12:57 PM
>> To: [email protected]
>> Cc: Herter, Scott
>> Subject: Re: Problem using Java for integration from JBoss
>> 5.1
>> 
>> Interesting ...
>> 
>> We carry an older version of saxon but we don't carry saxon9-dom.jar
>> 
>> Newer versions of saxon don't carry saxon9-dom either.
>> 
>> Try getting Saxon-B from http://saxon.sourceforge.net/
>> 
>> cheers,
>> 
>> Pedro.
>> 
>> --- On Tue, 9/13/11, Herter, Scott <[email protected]>
>> wrote:
>> ...
>>> We have been using OpenOffice in the past to convert RTF documents 
>>> to PDF and to print
>> them.  We have
>>> upgraded and after updating the Jar files in our EAR
>> file we now get
>>> an exception:
>>> 
>>> 2011-09-13 10:58:19,725 ERROR [STDERR]
>>> (http-0.0.0.0-8080-1) Error   DOMSource cannot be
>> processed: check
>>> that saxon9-dom.jar is on the classpath
>>> 2011-09-13 10:58:19,725 ERROR [STDERR]
>>> (http-0.0.0.0-8080-1)
>> net.sf.saxon.trans.XPathException:
>>> DOMSource cannot be processed: check that
>> saxon9-dom.jar is on the
>>> classpath
>>> 2011-09-13 10:58:19,725 ERROR [STDERR]
>>> (http-0.0.0.0-8080-1)   at
>>> net.sf.saxon.event.Sender.send(Sender.java:226)
>>> 2011-09-13 10:58:19,725 ERROR [STDERR]
>>> (http-0.0.0.0-8080-1)   at
>>> 
>> net.sf.saxon.IdentityTransformer.transform(IdentityTransformer.java:29
>>> )
>>> 2011-09-13 10:58:19,725 ERROR [STDERR]
>>> (http-0.0.0.0-8080-1)   at
>>> 
>> com.napersoft.databases.R70.NRUtils.decodeXML(NRUtils.java:1160)
>>> ...
>>> 
>>> Without the OpenOffice 3.3 jar files that code works
>> fine, with the
>>> 3.3 Jar files it fails with the message above.  The
>> code being invoked
>>> has nothing to do with OpenOffice, it has to do with
>> formatting some
>>> XML for display.  I noticed that there is a
>> saxon9.jar as part of the
>>> 3.3 jars and that is included in the manifest as a jar
>> file dependency
>>> and it is bundled with the EAR file.  It is like some
>> of the Jar files
>>> are replacing or interfering with the javax.xml.*
>> packages provided by
>>> JBoss.
>>> 
>>> Is there some minimal set of 3.3 jars I can use?
>> Most of the time we
>>> are loading an RTF document and converting it to PDF
>> or printing it.
>>> We also use cursors to search for bookmarks and insert
>> page breaks as
>>> well as get a page count.
>>> 
>>> Any help would be appreciated.
>>> 
>>> Thanks.
>>> 
>>> 
>> 
>> 
>> 
>> 
> 
> 

Reply via email to