Author |
Message
|
Karan |
Posted: Sat Oct 09, 2010 7:21 am Post subject: MB v7 , soap nodes and xsdzip |
|
|
Apprentice
Joined: 21 Oct 2009 Posts: 29
|
Hi,
I downloaded the trail version of MB7.0 from ibm , installed it, setup the default configuration , imported the soap nodes sample and tried to deploy the bar file.
It is giving an error for the xsdzip message set file. (Creation and preprocessing of xmlschemas in the messageset has failed)
Wanted to know if the soap nodes sample works for anyone in MB v7
(and did you use the trial version from the site or a purchased version)
Iv checked few other samples and they do work. Its only an issue with xsdzip. |
|
Back to top |
|
 |
Karan |
Posted: Mon Oct 11, 2010 5:26 am Post subject: |
|
|
Apprentice
Joined: 21 Oct 2009 Posts: 29
|
It works when I clear the classpath and restart the system.
If I put the classpath back and restart , it doesent deploy
Classpath:
C:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mqjms.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mq.jar;.;C:\;C:\providerutil.jar;C:\ldap.jar;C:\fscontext.jar;C:\Documents and Settings\admin\Desktop\Xerces-J-bin.1.4.4\xerces-1_4_4\xerces.jar;C:\soapfolder\javamail-1.4.3\javamail-1.4.3\mail.jar;C:\Program Files\Apache Software Foundation\Tomcat 5.5\bin\axis-bin-1_4\axis-1_4\lib\axis.jar;C:\Program Files\Apache Software Foundation\Tomcat 5.5\bin\axis-bin-1_4\axis-1_4\lib\axis-ant.jar;C:\Program Files\Apache Software Foundation\Tomcat 5.5\bin\axis-bin-1_4\axis-1_4\lib\commons-discovery-0.2.jar;C:\Program Files\Apache Software Foundation\Tomcat 5.5\bin\axis-bin-1_4\axis-1_4\lib\common-logging-1.0.4.jar;C:\Program Files\Apache Software Foundation\Tomcat 5.5\bin\axis-bin-1_4\axis-1_4\lib\jaxrpc.jar;C:\Program Files\Apache Software Foundation\Tomcat 5.5\bin\axis-bin-1_4\axis-1_4\lib\log4j-1.2.8.jar;C:\Program Files\Apache Software Foundation\Tomcat 5.5\bin\axis-bin-1_4\axis-1_4\lib\saaj.jar;C:\Program Files\Apache Software Foundation\Tomcat 5.5\bin\axis-bin-1_4\axis-1_4\lib\wsdl4j-1.5.1.jar;C:\Program Files\Apache Software Foundation\Tomcat 5.5\bin\axis-bin-1_4\axis-1_4\lib\Xerces-J-bin.1.4.4.jar;C:\soapfolder\jaf-1_0_2-upd2\jaf-1.0.2\activation.jar;C:\soapfolder\soap-bin-2.3.1\soap-2_3_1\lib\soap.jar;C:\Program Files\Java\jdk1.5.0_15\bin |
|
Back to top |
|
 |
Vitor |
Posted: Mon Oct 11, 2010 5:29 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
So what's different about the 2 classpaths?
Does the path that doesn't work include any jar files you've produced yourself, or any jars which are unsupported with WMB? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
WMBDEV1 |
Posted: Mon Oct 11, 2010 5:35 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009 Posts: 888 Location: UK
|
I almost posted an answer along these lines on Saturday but did not get round to it (and it sounded to me like it was a clean install of broker so i'd assumed you hadnt been tinkering with the classpath).
I've seen this issue before when you load your own versions of XML parsers on the classpath. By doing so this interferes with the parsers used by the broker and so these errors are seen when it attempts to parse the XSDs as part of the deployment.
I'd recommend removing the XML parsers (used by Tomcat in this instance) from the global classpath when starting the broker. |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Oct 11, 2010 6:31 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
In general DO NOT EVER add entries to the CLASSPATH that is in use by the Broker service user when it mqsistart's.
If you need to do something bizarre like use your own XML parser in a JavaCompute node, put it in shared_classes or put it in a folder pointed to by a JavaClassLoader configurable service. |
|
Back to top |
|
 |
kimbert |
Posted: Tue Oct 12, 2010 1:16 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Quote: |
In general DO NOT EVER add entries to the CLASSPATH that is in use by the Broker service user when it mqsistart's. |
This is true. I am not at all surprised that you got an error when deploying schemas if you changed WMB's classpath.
Hope you get it working - I have a lot of sympathy for anyone who wrestles with classpath issues. |
|
Back to top |
|
 |
Karan |
Posted: Fri Oct 15, 2010 10:26 am Post subject: |
|
|
Apprentice
Joined: 21 Oct 2009 Posts: 29
|
Had the same issue in existing 6.1 installation . But this time problem causing jars were not there in classpath. They were there in the jre15 folder.
Massive effort to find them |
|
Back to top |
|
 |
|