You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Sagara Gunathunga <sa...@gmail.com> on 2012/03/01 08:12:57 UTC
Re: axis2 xml parser issue
On Wed, Feb 29, 2012 at 10:11 PM, Anthony Seniunas <
anthony.seniunas@kirona.com> wrote:
> Hi all,
> I was wondering whether anyone could help me troubleshoot a
> problem with an axis2 web service running in a web app. The basic
> details are:-
>
> Linux server
> Java 1.6
> Tomcat 6
> xml-api and xercesImpl jars in the web app container lib folder
>
> This configuration is widely used and proven to work however on a new
> install the following error occurs when I try and obtain the wsdl from a
> web service deployed in a web app running in the tomcat container.
>
> DOMSource cannot be processed: check that saxon8-dom.jar is on the
> classpath
>
We don't use any Saxon dependency on Axis2 and it's unusual to see above
issue. Can you try with clean Tomcat installation if the issue still exists
share a sample with this list.
Thanks !
>
> I've checked the web app directory folder permissions and all folders
> and files have at least other read privileges. I don't have any axis2
> tools or means of diagnosing this problem.
>
> Please can anyone advise how I could try and troubleshoot or resolve
> this issue?
>
> --
> Regards,
>
> Anthony Seniunas
> Developer
> Kirona
> Tel: 01625 585511
> Fax: 08702 200764
> www.kirona.com
>
> This email and any attachments are confidential and should only be read by
> those to whom they are addressed. If you are not the intended recipient,
> please contact us on 01625 585511, delete the email (including any
> attachment) from your computer and destroy any copies. Any distribution or
> copying without our prior permission is prohibited.
> Internet communications are not always secure and may be subject to
> delays, non-delivery and unauthorised alterations. Therefore, information
> expressed in this message is not given or endorsed by Kirona Solutions
> Limited ("Kirona") unless otherwise notified by our duly authorised
> representative independent of this message. No warranty is given that this
> email (including any attachment) is virus free. Any views or opinions
> presented are solely those of the author and do not necessarily represent
> those of Kirona.
>
> Registered addresses: Kirona Solutions Limited, Barrington House, Heyes
> Lane, Alderley Edge, Cheshire. SK9 7LA Registered in England and Wales No:
> 04678711
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.**apache.org<ja...@axis.apache.org>
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
LinkedIn - http://www.linkedin.com/in/ssagara
Re: axis2 xml parser issue
Posted by Andreas Veithen <an...@gmail.com>.
Your application contains 3 different XSLT processor implementations:
saxon8.jar
xalan-2.7.0.jar
xalan.jar
In that situation, JAXP doesn't select the implementation in a
deterministic way. My guess is that the error occurs when JAXP selects
Saxon and that your application works on other systems because on
these systems JAXP selects one of the Xalan versions. You should start
by resolving that issue.
Andreas
On Thu, Mar 1, 2012 at 08:43, Anthony Seniunas
<an...@kirona.com> wrote:
> Hi Sagara,
> Thanks for that. I've done some research and think the
> problem is related to running a set of application libraries compatible with
> Java 1.5 on a Java 1.6 Tomcat container.I've found out that Java 1.6
> includes the following
>
> SAAJ1.3
> JAXB 2.0
> JAXP 1.4
>
> The last two are Xerces and Xalan
>
> I think there are two options to resolve this problem:-
>
> Option 1 - Remove conflicting jars
>
> This would involve removing jars conflicting with the above. The list of
> .jars in usage is as follows:-
>
> FastInfoset.jar
> PngEncoder.jar
> XMBMobileGateway.jar
> XmlSchema-1.4.2.jar
> activation-1.1.jar
> annogen-0.1.0.jar
> aopalliance.jar
> aspectjweaver.jar
> axiom-api-1.2.7.jar
> axiom-dom-1.2.7.jar
> axiom-impl-1.2.7.jar
> axis.jar
> axis2-adb-1.4.1.jar
> axis2-adb-codegen-1.4.1.ja
> axis2-ant-plugin-1.4.1.jar
> axis2-clustering-1.4.1.jar
> axis2-codegen-1.4.1.jar
> axis2-corba-1.4.1.jar
> axis2-fastinfoset-1.4.1.ja
> axis2-java2wsdl-1.4.1.jar
> axis2-jaxbri-1.4.1.jar
> axis2-jaxws-1.4.1.jar
> axis2-jaxws-api-1.4.1.jar
> axis2-jibx-1.4.1.jar
> axis2-json-1.4.1.jar
> axis2-jws-api-1.4.1.jar
> axis2-kernel-1.4.1.jar
> axis2-metadata-1.4.1.jar
> axis2-mtompolicy-1.4.1.jar
> axis2-saaj-1.4.1.jar
> axis2-saaj-api-1.4.1.jar
> axis2-spring-1.4.1.jar
> axis2-xmlbeans-1.4.1.jar
> backport-util-concurrent-3
> bicmn.jar
> bipres.jar
> clibwrapper_jiio.jar
> collections.jar
> com.springsource.com.thoug
> com.springsource.org.xmlpu
> commons-codec-1.3.jar
> commons-dbcp.jar
> commons-discovery-0.2.jar
> commons-fileupload-1.2.jar
> commons-httpclient-3.1.jar
> commons-io-1.4.jar
> commons-lang-2.6.jar
> commons-net-1.3.0.jar
> commons-pool.jar
> cos.jar
> geronimo-annotation_1.0_sp
> geronimo-stax-api_1.0_spec
> httpcore-4.0-beta1.jar
> httpcore-nio-4.0-beta1.jar
> i18nAPI_v3.jar
> iText-rtf-2.1.7.jar
> iText.jar
> iTextXML.jar
> jai_codec.jar
> jai_core.jar
> jai_imageio.jar
> jakarta-oro-2.0.8.jar
> jalopy-1.5rc3.jar
> jaxb-api-2.1.jar
> jaxb-impl-2.1.6.jar
> jaxb-xjc-2.1.6.jar
> jaxen-1.1.1.jar
> jaxr-api.jar
> jaxr-impl.jar
> jaxrpc-api.jar
> jaxrpc-impl.jar
> jaxrpc.jar
> jcl-over-slf4j-1.5.6.jar
> jcommon-0.9.5.jar
> jec.jar
> jettison-1.0-RC2.jar
> jewt4.jar
> jfreechart-0.9.20-demo.jar
> jfreechart-0.9.20.jar
> jibx-bind-1.1.5.jar
> jibx-run-1.1.5.jar
> json_simple-1.1.jar
> jsr173_1.0_api.jar
> junit.jar
> log4j-1.2.15.jar
> mail-1.4.jar
> mex-1.4.1.jar
> msbase.jar
> mssqlserver.jar
> msutil.jar
> neethi-2.0.4.jar
> ojdbc14.jar
> orai18n.jar
> quartz-all-1.6.6.jar
> resolver.jar
> rowset.jar
> saaj-api.jar
> saaj-impl.jar
> saxon8.jar
> share.jar
> slf4j-api-1.5.6.jar
> slf4j-log4j12-1.5.6.jar
> soap.jar
> soapmonitor-1.4.1.jar
> spring-aop-2.5.6.jar
> spring-aspects.jar
> spring-batch-infrastructur
> spring-beans-2.5.6.jar
> spring-context-2.5.6.jar
> spring-context-support.jar
> spring-core-2.5.6.jar
> spring-jdbc-2.5.6.jar
> spring-jms-2.5.6.jar
> spring-orm-2.5.6.jar
> spring-test.jar
> spring-tx-2.5.6.jar
> spring-web-2.5.6.jar
> spring-webmvc-2.5.6.jar
> spring-ws-1.5.9-all.jar
> ujac.jar
> versioninfo.jar
> woden-api-1.0M8.jar
> woden-impl-dom-1.0M8.jar
> wsdl4j-1.5.1.jar
> wsdl4j-1.6.2.jar
> wstx-asl-3.2.4.jar
> xalan-2.7.0.jar
> xalan.jar
> xbean.jar
> xdocore.jar
> xdoparser.jar
> xercesImpl-2.8.1.jar
> xercesImpl.jar
> xml-apis-1.3.04.jar
> xml-resolver-1.2.jar
> xmlbeans-2.3.0.jar
> xmlbeans-qname.jar
> xmlparserv2.jar
>
> As you can see there is potential for conflicts in such a large library
> list. A cursory look at the above library I think I might have to remove the
> following if I wanted to use Java 1.6 inbuilt libraries.
>
> Remove to avoid JAXB Conflicts
>
> jaxb-api-2.1.jar
> jaxb-impl-2.1.6.jar
> jaxb-xjc-2.1.6.jar
>
> Remove to avoid SAAJ conflicts
>
> axis2-saaj-1.4.1.jar
> axis2-saaj-api-1.4.1.jar
>
> saaj-api.jar
> saaj-impl.jar
>
> Remove to avoid JAXB/JAXP Conflicts
>
> xalan-2.7.0.jar
> xalan.jar
>
> xercesImpl-2.8.1.jar
> xercesImpl.jar
>
> The following are not so clear.
>
> You mentioned axis2 does not have a saxon dependency so can the following
> jar be removed also?
>
> saxon8.jar
>
> and not sure whether these can be removed?
>
> xml-apis-1.3.04.jar
> xmlparserv2.jar
>
> Option 2 - Set Java properties to run axis2 SOAP factories etc...
>
> I found the following config in a post to force usage of axis2 SOAP
> factories as opposed to Java 1.6 SOAP factories (I think the switches the
> JAXB/JAXP back to axis2)
>
> java -Djavax.xml.soap.SOAPFactory=org.apache.axis.soap.SOAPFactoryImpl
> -Djavax.xml.soap.MessageFactory=org.apache.axis.soap.MessageFactoryImpl
> -Djavax.xml.soap.SOAPConnectionFactory=org.apache.axis.soap.SOAPConnectionFactoryImpl
> example.MainClass
>
> Please can you review and comment on the above options and maybe suggest
> which option is best?
>
> Regards,
>
> Anthony Seniunas
> Developer
> Kirona
> Tel: 01625 585511
> Fax: 08702 200764
> www.kirona.com
>
> This email and any attachments are confidential and should only be read by
> those to whom they are addressed. If you are not the intended recipient,
> please contact us on 01625 585511, delete the email (including any
> attachment) from your computer and destroy any copies. Any distribution or
> copying without our prior permission is prohibited.
> Internet communications are not always secure and may be subject to delays,
> non-delivery and unauthorised alterations. Therefore, information expressed
> in this message is not given or endorsed by Kirona Solutions Limited
> ("Kirona") unless otherwise notified by our duly authorised representative
> independent of this message. No warranty is given that this email (including
> any attachment) is virus free. Any views or opinions presented are solely
> those of the author and do not necessarily represent those of Kirona.
>
> Registered addresses: Kirona Solutions Limited, Barrington House, Heyes
> Lane, Alderley Edge, Cheshire. SK9 7LA Registered in England and Wales No:
> 04678711
>
>
> On 01/03/2012 07:12, Sagara Gunathunga wrote:
>
>
>
> On Wed, Feb 29, 2012 at 10:11 PM, Anthony Seniunas
> <an...@kirona.com> wrote:
>>
>> Hi all,
>> I was wondering whether anyone could help me troubleshoot a
>> problem with an axis2 web service running in a web app. The basic
>> details are:-
>>
>> Linux server
>> Java 1.6
>> Tomcat 6
>> xml-api and xercesImpl jars in the web app container lib folder
>>
>> This configuration is widely used and proven to work however on a new
>> install the following error occurs when I try and obtain the wsdl from a
>> web service deployed in a web app running in the tomcat container.
>>
>> DOMSource cannot be processed: check that saxon8-dom.jar is on the
>> classpath
>
>
> We don't use any Saxon dependency on Axis2 and it's unusual to see above
> issue. Can you try with clean Tomcat installation if the issue still exists
> share a sample with this list.
>
> Thanks !
>>
>>
>> I've checked the web app directory folder permissions and all folders
>> and files have at least other read privileges. I don't have any axis2
>> tools or means of diagnosing this problem.
>>
>> Please can anyone advise how I could try and troubleshoot or resolve
>> this issue?
>>
>> --
>> Regards,
>>
>> Anthony Seniunas
>> Developer
>> Kirona
>> Tel: 01625 585511
>> Fax: 08702 200764
>> www.kirona.com
>>
>> This email and any attachments are confidential and should only be read by
>> those to whom they are addressed. If you are not the intended recipient,
>> please contact us on 01625 585511, delete the email (including any
>> attachment) from your computer and destroy any copies. Any distribution or
>> copying without our prior permission is prohibited.
>> Internet communications are not always secure and may be subject to
>> delays, non-delivery and unauthorised alterations. Therefore, information
>> expressed in this message is not given or endorsed by Kirona Solutions
>> Limited ("Kirona") unless otherwise notified by our duly authorised
>> representative independent of this message. No warranty is given that this
>> email (including any attachment) is virus free. Any views or opinions
>> presented are solely those of the author and do not necessarily represent
>> those of Kirona.
>>
>> Registered addresses: Kirona Solutions Limited, Barrington House, Heyes
>> Lane, Alderley Edge, Cheshire. SK9 7LA Registered in England and Wales No:
>> 04678711
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-user-help@axis.apache.org
>>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> LinkedIn - http://www.linkedin.com/in/ssagara
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
Re: axis2 xml parser issue
Posted by Anthony Seniunas <an...@kirona.com>.
Hi Sagara,
Thanks for that. I've done some research and think
the problem is related to running a set of application libraries
compatible with Java 1.5 on a Java 1.6 Tomcat container.I've found out
that Java 1.6 includes the following
SAAJ1.3
JAXB 2.0
JAXP 1.4
The last two are Xerces and Xalan
I think there are two options to resolve this problem:-
Option 1 - Remove conflicting jars
This would involve removing jars conflicting with the above. The list of
.jars in usage is as follows:-
FastInfoset.jar
PngEncoder.jar
XMBMobileGateway.jar
XmlSchema-1.4.2.jar
activation-1.1.jar
annogen-0.1.0.jar
aopalliance.jar
aspectjweaver.jar
axiom-api-1.2.7.jar
axiom-dom-1.2.7.jar
axiom-impl-1.2.7.jar
axis.jar
axis2-adb-1.4.1.jar
axis2-adb-codegen-1.4.1.ja
axis2-ant-plugin-1.4.1.jar
axis2-clustering-1.4.1.jar
axis2-codegen-1.4.1.jar
axis2-corba-1.4.1.jar
axis2-fastinfoset-1.4.1.ja
axis2-java2wsdl-1.4.1.jar
axis2-jaxbri-1.4.1.jar
axis2-jaxws-1.4.1.jar
axis2-jaxws-api-1.4.1.jar
axis2-jibx-1.4.1.jar
axis2-json-1.4.1.jar
axis2-jws-api-1.4.1.jar
axis2-kernel-1.4.1.jar
axis2-metadata-1.4.1.jar
axis2-mtompolicy-1.4.1.jar
axis2-saaj-1.4.1.jar
axis2-saaj-api-1.4.1.jar
axis2-spring-1.4.1.jar
axis2-xmlbeans-1.4.1.jar
backport-util-concurrent-3
bicmn.jar
bipres.jar
clibwrapper_jiio.jar
collections.jar
com.springsource.com.thoug
com.springsource.org.xmlpu
commons-codec-1.3.jar
commons-dbcp.jar
commons-discovery-0.2.jar
commons-fileupload-1.2.jar
commons-httpclient-3.1.jar
commons-io-1.4.jar
commons-lang-2.6.jar
commons-net-1.3.0.jar
commons-pool.jar
cos.jar
geronimo-annotation_1.0_sp
geronimo-stax-api_1.0_spec
httpcore-4.0-beta1.jar
httpcore-nio-4.0-beta1.jar
i18nAPI_v3.jar
iText-rtf-2.1.7.jar
iText.jar
iTextXML.jar
jai_codec.jar
jai_core.jar
jai_imageio.jar
jakarta-oro-2.0.8.jar
jalopy-1.5rc3.jar
jaxb-api-2.1.jar
jaxb-impl-2.1.6.jar
jaxb-xjc-2.1.6.jar
jaxen-1.1.1.jar
jaxr-api.jar
jaxr-impl.jar
jaxrpc-api.jar
jaxrpc-impl.jar
jaxrpc.jar
jcl-over-slf4j-1.5.6.jar
jcommon-0.9.5.jar
jec.jar
jettison-1.0-RC2.jar
jewt4.jar
jfreechart-0.9.20-demo.jar
jfreechart-0.9.20.jar
jibx-bind-1.1.5.jar
jibx-run-1.1.5.jar
json_simple-1.1.jar
jsr173_1.0_api.jar
junit.jar
log4j-1.2.15.jar
mail-1.4.jar
mex-1.4.1.jar
msbase.jar
mssqlserver.jar
msutil.jar
neethi-2.0.4.jar
ojdbc14.jar
orai18n.jar
quartz-all-1.6.6.jar
resolver.jar
rowset.jar
saaj-api.jar
saaj-impl.jar
saxon8.jar
share.jar
slf4j-api-1.5.6.jar
slf4j-log4j12-1.5.6.jar
soap.jar
soapmonitor-1.4.1.jar
spring-aop-2.5.6.jar
spring-aspects.jar
spring-batch-infrastructur
spring-beans-2.5.6.jar
spring-context-2.5.6.jar
spring-context-support.jar
spring-core-2.5.6.jar
spring-jdbc-2.5.6.jar
spring-jms-2.5.6.jar
spring-orm-2.5.6.jar
spring-test.jar
spring-tx-2.5.6.jar
spring-web-2.5.6.jar
spring-webmvc-2.5.6.jar
spring-ws-1.5.9-all.jar
ujac.jar
versioninfo.jar
woden-api-1.0M8.jar
woden-impl-dom-1.0M8.jar
wsdl4j-1.5.1.jar
wsdl4j-1.6.2.jar
wstx-asl-3.2.4.jar
xalan-2.7.0.jar
xalan.jar
xbean.jar
xdocore.jar
xdoparser.jar
xercesImpl-2.8.1.jar
xercesImpl.jar
xml-apis-1.3.04.jar
xml-resolver-1.2.jar
xmlbeans-2.3.0.jar
xmlbeans-qname.jar
xmlparserv2.jar
As you can see there is potential for conflicts in such a large library
list. A cursory look at the above library I think I might have to remove
the following if I wanted to use Java 1.6 inbuilt libraries.
Remove to avoid JAXB Conflicts
jaxb-api-2.1.jar
jaxb-impl-2.1.6.jar
jaxb-xjc-2.1.6.jar
Remove to avoid SAAJ conflicts
axis2-saaj-1.4.1.jar
axis2-saaj-api-1.4.1.jar
saaj-api.jar
saaj-impl.jar
Remove to avoid JAXB/JAXP Conflicts
xalan-2.7.0.jar
xalan.jar
xercesImpl-2.8.1.jar
xercesImpl.jar
The following are not so clear.
You mentioned axis2 does not have a saxon dependency so can the
following jar be removed also?
saxon8.jar
and not sure whether these can be removed?
xml-apis-1.3.04.jar
xmlparserv2.jar
Option 2 - Set Java properties to run axis2 SOAP factories etc...
I found the following config in a post to force usage of axis2 SOAP
factories as opposed to Java 1.6 SOAP factories (I think the switches
the JAXB/JAXP back to axis2)
java -Djavax.xml.soap.SOAPFactory=org.apache.axis.soap.SOAPFactoryImpl
-Djavax.xml.soap.MessageFactory=org.apache.axis.soap.MessageFactoryImpl
-Djavax.xml.soap.SOAPConnectionFactory=org.apache.axis.soap.SOAPConnectionFactoryImpl
example.MainClass
Please can you review and comment on the above options and maybe suggest
which option is best?
Regards,
Anthony Seniunas
Developer
Kirona
Tel: 01625 585511
Fax: 08702 200764
www.kirona.com
This email and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us on 01625 585511, delete the email (including any attachment) from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited.
Internet communications are not always secure and may be subject to delays, non-delivery and unauthorised alterations. Therefore, information expressed in this message is not given or endorsed by Kirona Solutions Limited ("Kirona") unless otherwise notified by our duly authorised representative independent of this message. No warranty is given that this email (including any attachment) is virus free. Any views or opinions presented are solely those of the author and do not necessarily represent those of Kirona.
Registered addresses: Kirona Solutions Limited, Barrington House, Heyes Lane, Alderley Edge, Cheshire. SK9 7LA Registered in England and Wales No: 04678711
On 01/03/2012 07:12, Sagara Gunathunga wrote:
>
>
> On Wed, Feb 29, 2012 at 10:11 PM, Anthony Seniunas
> <anthony.seniunas@kirona.com <ma...@kirona.com>> wrote:
>
> Hi all,
> I was wondering whether anyone could help me troubleshoot a
> problem with an axis2 web service running in a web app. The basic
> details are:-
>
> Linux server
> Java 1.6
> Tomcat 6
> xml-api and xercesImpl jars in the web app container lib folder
>
> This configuration is widely used and proven to work however on a new
> install the following error occurs when I try and obtain the wsdl
> from a
> web service deployed in a web app running in the tomcat container.
>
> DOMSource cannot be processed: check that saxon8-dom.jar is on the
> classpath
>
>
> We don't use any Saxon dependency on Axis2 and it's unusual to see
> above issue. Can you try with clean Tomcat installation if the issue
> still exists share a sample with this list.
>
> Thanks !
>
>
> I've checked the web app directory folder permissions and all folders
> and files have at least other read privileges. I don't have any axis2
> tools or means of diagnosing this problem.
>
> Please can anyone advise how I could try and troubleshoot or resolve
> this issue?
>
> --
> Regards,
>
> Anthony Seniunas
> Developer
> Kirona
> Tel: 01625 585511
> Fax: 08702 200764
> www.kirona.com <http://www.kirona.com>
>
> This email and any attachments are confidential and should only be
> read by those to whom they are addressed. If you are not the
> intended recipient, please contact us on 01625 585511, delete the
> email (including any attachment) from your computer and destroy
> any copies. Any distribution or copying without our prior
> permission is prohibited.
> Internet communications are not always secure and may be subject
> to delays, non-delivery and unauthorised alterations. Therefore,
> information expressed in this message is not given or endorsed by
> Kirona Solutions Limited ("Kirona") unless otherwise notified by
> our duly authorised representative independent of this message. No
> warranty is given that this email (including any attachment) is
> virus free. Any views or opinions presented are solely those of
> the author and do not necessarily represent those of Kirona.
>
> Registered addresses: Kirona Solutions Limited, Barrington House,
> Heyes Lane, Alderley Edge, Cheshire. SK9 7LA Registered in England
> and Wales No: 04678711
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> <ma...@axis.apache.org>
> For additional commands, e-mail: java-user-help@axis.apache.org
> <ma...@axis.apache.org>
>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> <http://people.apache.org/%7Esagara/>
> LinkedIn - http://www.linkedin.com/in/ssagara