RE: Problem using Java for integration from JBoss 5.1 SOLVED User Error
As promised here is what happened. Turns out my Eclipse project had a bunch of old xerces, OpenOffice.org, and other DLLs copied directly in to it. It was favoring those over the Jar files I was setting up through the properties interface. Once I figured that out and cleaned out all the old crap it started working just fine. Once again it is user error. -Original Message- From: Herter, Scott [mailto:scott.her...@napersoft.com] Sent: Friday, September 16, 2011 7:01 AM To: ooo-dev@incubator.apache.org Subject: RE: Problem using Java for integration from JBoss 5.1 Will do, we are trying to get a new release of our software out so it may take a couple of weeks to sort everything out, but I will send a message to let everyone know what the solution was. -Original Message- From: Jürgen Schmidt [mailto:jogischm...@googlemail.com] Sent: Friday, September 16, 2011 2:29 AM To: ooo-dev@incubator.apache.org Subject: Re: Problem using Java for integration from JBoss 5.1 if it is a separate process anyway you should take a look on Java UNO client applications. I think Ariel has already posted some infos about it. This should at least ensure that the jars doesn't conflict. Let us know it solves your problem. Juergen
Re: Problem using Java for integration from JBoss 5.1
On Wed, Sep 14, 2011 at 3:22 PM, Herter, Scott scott.her...@napersoft.comwrote: 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 inevitable. 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. if it is a separate process anyway you should take a look on Java UNO client applications. I think Ariel has already posted some infos about it. This should at least ensure that the jars doesn't conflict. Let us know it solves your problem. Juergen -Original Message- From: Jürgen Schmidt [mailto:jogischm...@googlemail.com] Sent: Wednesday, September 14, 2011 1:49 AM To: ooo-dev@incubator.apache.org Subject: Re: Problem using Java for integration from JBoss 5.1 Hi, 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 file. 1. which jars do you include? 2. is it possible to use the jars from the original location in the office? Juergen On Tue, Sep 13, 2011 at 6:07 PM, Herter, Scott scott.her...@napersoft.comwrote: 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.
Re: Problem using Java for integration from JBoss 5.1
Hi, 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 file. 1. which jars do you include? 2. is it possible to use the jars from the original location in the office? Juergen On Tue, Sep 13, 2011 at 6:07 PM, Herter, Scott scott.her...@napersoft.comwrote: 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.
RE: Problem using Java for integration from JBoss 5.1
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:giffu...@tutopia.com] Sent: Tuesday, September 13, 2011 12:57 PM To: ooo-dev@incubator.apache.org 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 scott.her...@napersoft.com 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.
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 scott.her...@napersoft.com 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:giffu...@tutopia.com] Sent: Tuesday, September 13, 2011 12:57 PM To: ooo-dev@incubator.apache.org 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 scott.her...@napersoft.com 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.
RE: Problem using Java for integration from JBoss 5.1
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:giffu...@tutopia.com] Sent: Tuesday, September 13, 2011 2:55 PM To: ooo-dev@incubator.apache.org 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 scott.her...@napersoft.com 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:giffu...@tutopia.com] Sent: Tuesday, September 13, 2011 12:57 PM To: ooo-dev@incubator.apache.org 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 scott.her...@napersoft.com 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.
Re: Problem using Java for integration from JBoss 5.1
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:giffu...@tutopia.com] Sent: Tuesday, September 13, 2011 2:55 PM To: ooo-dev@incubator.apache.org 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 scott.her...@napersoft.com 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:giffu...@tutopia.com] Sent: Tuesday, September 13, 2011 12:57 PM To: ooo-dev@incubator.apache.org 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 scott.her...@napersoft.com 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.
RE: Problem using Java for integration from JBoss 5.1
Hi; ooo-users@ may be more appropriate although I admit that type of questions may not be that easy to solve there either :(. Perhaps on the JBoss lists ... cheers, Pedro. --- On Tue, 9/13/11, Herter, Scott scott.her...@napersoft.com 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:giffu...@tutopia.com] Sent: Tuesday, September 13, 2011 2:55 PM To: ooo-dev@incubator.apache.org 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 scott.her...@napersoft.com 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:giffu...@tutopia.com] Sent: Tuesday, September 13, 2011 12:57 PM To: ooo-dev@incubator.apache.org 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 scott.her...@napersoft.com 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.
