incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herter, Scott" <>
Subject RE: Problem using Java for integration from JBoss 5.1
Date Wed, 14 Sep 2011 13:22:03 GMT
Your assumption is correct.

1. In OOo 2.x we included the all the Jars in \program\classes since those were the only ones
outside of Help and samples and it seemed to work.  When searching for what jars to use I
only ever found stuff on developing plug-ins in java as opposed to external Java programs.
 Since we never had any problems with any of the Application servers this worked fine.  When
it came time to upgrade to 3.x (we have been a bit behind) the jars got broken up in to two
directories \Basis\program\classes and \URE\java.  Not knowing what the difference was at
first I just dumped all of them in.  I have latter discovered that we only need the ones in
\URE\java if we are not a plug-in.  Unfortunately that hasn't helped, but it was late last
night and my testing wasn't as controlled as it could have been.

2. Not really, but since we freeze our release on a specific version and then use the jars
from that version in our build and packaging it shouldn't really matter.  What was surprising
at first was all our XML stuff breaking, but it makes sense since now OOo is supporting two
different XML formats so it will need more generic XML processing.  The newer Application
Servers provide their own implementations for the javax.xml.* packages so a collision was

 I am trying to find a way to minimize what we need to communicate with OpenOffice since it
will run as a separate process and thereby better standardize what does and does not go in
to our EAR file.  We are a JavaEE application that uses UNO to talk to running instances of
OpenOffice to manipulate Word RTF documents.

-----Original Message-----
From: J├╝rgen Schmidt [] 
Sent: Wednesday, September 14, 2011 1:49 AM
Subject: Re: Problem using Java for integration from JBoss 5.1


can you explain a little bit more what exactly are you doing.

I assume you take some of the OOo jars and put them together with your own stuff in the EAR

1. which jars do you include?
2. is it possible to use the jars from the original location  in the office?


On Tue, Sep 13, 2011 at 6:07 PM, Herter, Scott

> 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- Error 
> DOMSource cannot be processed: check that saxon9-dom.jar is on the 
> classpath
> 2011-09-13 10:58:19,725 ERROR [STDERR] (http-
> 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-   at
> net.sf.saxon.event.Sender.send(
> 2011-09-13 10:58:19,725 ERROR [STDERR] (http-   at
> net.sf.saxon.IdentityTransformer.transform(
> 2011-09-13 10:58:19,725 ERROR [STDERR] (http-   at
> com.napersoft.databases.R70.NRUtils.decodeXML(
> ...
> 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.
View raw message