Petals 4.1/BC-SOAP : SAX driver error!

classic Classic list List threaded Threaded
24 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Petals 4.1/BC-SOAP : SAX driver error!

Philip
Hi, I have just installes Petals ESB 4.1 on several servers. Topology is smaster-slave, with the same topology.xml on all the servers. I have installed SOAP-BC on the ESB servers, and everything runs fine. Now, I try to install a service unit generated with Petals Studio 1.3.3 ( I did this operation quite a few times in the past, without any problem) the SU is not installed, and I see this in the petals.log : Error to read default parent => SchemaException: Can not get schema: : org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not found What could be the cause ? Full log follows: MYSERVER 2013/04/12 12:20:25,208 GMT+0200 INFO [Petals.Container.Components.petals-bc-soap] : Component Information is available at http://1.2.3.4:8084/ MYSERVER 2013/04/12 12:20:25,208 GMT+0200 INFO [Petals.Container.Components.petals-bc-soap] : Component started MYSERVER 2013/04/12 12:21:38,162 GMT+0200 INFO [Petals.Container.Components.petals-bc-soap] : Deploy Service Unit 'su-SOAP-mywebservice-provide_test' MYSERVER 2013/04/12 12:21:40,444 GMT+0200 WARNING [org.ow2.easywsdl.schema.DefaultSchemaImpl] : Error to read default parent => SchemaException: Can not get schema: : org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not found MYSERVER 2013/04/12 12:21:40,444 GMT+0200 SEVERE [Petals.Container.Components.petals-bc-soap] : Service Unit 'su-SOAP-mywebservice-provide_test' failed to deploy java.lang.NullPointerException at org.ow2.easywsdl.schema.api.abstractElmt.AbstractSchemaImpl.getType(AbstractSchemaImpl.java:293) at org.ow2.easywsdl.schema.impl.ElementImpl.findType(ElementImpl.java:81) at org.ow2.easywsdl.schema.impl.ElementImpl.(ElementImpl.java:69) at org.ow2.easywsdl.schema.impl.SequenceImpl.(SequenceImpl.java:60) at org.ow2.easywsdl.schema.impl.ComplexTypeImpl.(ComplexTypeImpl.java:79) at org.ow2.easywsdl.schema.impl.SchemaImpl.initialize(SchemaImpl.java:143) at org.ow2.easywsdl.extensions.wsdl4complexwsdl.impl.DocumentImpl.(DocumentImpl.java:99) at org.ow2.easywsdl.extensions.wsdl4complexwsdl.impl.ImportedDocumentsImpl.(ImportedDocumentsImpl.java:67) at org.ow2.easywsdl.extensions.wsdl4complexwsdl.util.ImportedDocumentsFilter.(ImportedDocumentsFilter.java:65) at org.ow2.easywsdl.extensions.wsdl4complexwsdl.impl.inout.WSDL4ComplexWsdlReaderImpl.read(WSDL4ComplexWsdlReaderImpl.java:146) at org.ow2.easywsdl.extensions.wsdl4complexwsdl.impl.inout.WSDL4ComplexWsdlReaderImpl.read(WSDL4ComplexWsdlReaderImpl.java:222) at org.ow2.petals.jbi.component.context.ComponentContextImpl.getInterfacesFromComponentDescription(ComponentContextImpl.java:767) at org.ow2.petals.jbi.component.context.ComponentContextImpl.activateEndpoint(ComponentContextImpl.java:157) at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.processProvidesNode(AbstractServiceUnitManager.java:957) at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.processProvidesNodes(AbstractServiceUnitManager.java:1017) at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.deploy(AbstractServiceUnitManager.java:286) at org.ow2.petals.jbi.management.task.deployment.deploy.DeploySUToComponentTask.deploySUtoComponent(DeploySUToComponentTask.java:123) at org.ow2.petals.jbi.management.task.deployment.deploy.DeploySUToComponentTask.execute(DeploySUToComponentTask.java:75) at org.ow2.petals.jbi.management.TaskProcessor.process(TaskProcessor.java:76) at org.ow2.petals.jbi.management.task.deployment.deploy.DeployAllSUTask.registerAndDeploySU(DeployAllSUTask.java:168) at org.ow2.petals.jbi.management.task.deployment.deploy.DeployAllSUTask.deploySUS(DeployAllSUTask.java:124) at org.ow2.petals.jbi.management.task.deployment.deploy.DeployAllSUTask.execute(DeployAllSUTask.java:82) at org.ow2.petals.jbi.management.TaskProcessor.process(TaskProcessor.java:76) at org.ow2.petals.jbi.management.deployment.DeploymentServiceImpl.deploy(DeploymentServiceImpl.java:175) at org.objectweb.fractal.julia.generated.C9ae71627_0.deploy(INTERCEPTOR[DeploymentService]) at org.objectweb.fractal.julia.generated.C59d5ff32_0.deploy(INTERFACE[DeploymentService]) at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.performDeploySA(AutoLoaderServiceImpl.java:436) at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.install(AutoLoaderServiceImpl.java:164) at org.ow2.petals.jbi.management.autoload.InstallDirectoryScanner.run(InstallDirectoryScanner.java:82) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source) MYSERVER 2013/04/12 12:21:40,444 GMT+0200 WARNING [Petals.JBI-Management.DeploymentService] : A component Service Unit Manager failed to deploy a Service Unit : petals-bc-soap deploy FAILED ERROR 1 jbimsg Failed to deploy Service Unit : {1} su-SOAP-mywebservice-provide_test java.lang.NullPointerException at org.ow2.easywsdl.schema.api.abstractElmt.AbstractSchemaImpl.getType(AbstractSchemaImpl.java:293) at org.ow2.easywsdl.schema.impl.ElementImpl.findType(ElementImpl.java:81) at org.ow2.easywsdl.schema.impl.ElementImpl.(ElementImpl.java:69) at org.ow2.easywsdl.schema.impl.SequenceImpl.(SequenceImpl.java:60) at org.ow2.easywsdl.schema.impl.ComplexTypeImpl.(ComplexTypeImpl.java:79) at org.ow2.easywsdl.schema.impl.SchemaImpl.initialize(SchemaImpl.java:143) at org.ow2.easywsdl.extensions.wsdl4complexwsdl.impl.DocumentImpl.(DocumentImpl.java:99) at org.ow2.easywsdl.extensions.wsdl4complexwsdl.impl.ImportedDocumentsImpl.(ImportedDocumentsImpl.java:67) at org.ow2.easywsdl.extensions.wsdl4complexwsdl.util.ImportedDocumentsFilter.(ImportedDocumentsFilter.java:65) at org.ow2.easywsdl.extensions.wsdl4complexwsdl.impl.inout.WSDL4ComplexWsdlReaderImpl.read(WSDL4ComplexWsdlReaderImpl.java:146) at org.ow2.easywsdl.extensions.wsdl4complexwsdl.impl.inout.WSDL4ComplexWsdlReaderImpl.read(WSDL4ComplexWsdlReaderImpl.java:222) at org.ow2.petals.jbi.component.context.ComponentContextImpl.getInterfacesFromComponentDescription(ComponentContextImpl.java:767) at org.ow2.petals.jbi.component.context.ComponentContextImpl.activateEndpoint(ComponentContextImpl.java:157) at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.processProvidesNode(AbstractServiceUnitManager.java:957) at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.processProvidesNodes(AbstractServiceUnitManager.java:1017) at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.deploy(AbstractServiceUnitManager.java:286) at org.ow2.petals.jbi.management.task.deployment.deploy.DeploySUToComponentTask.deploySUtoComponent(DeploySUToComponentTask.java:123) at org.ow2.petals.jbi.management.task.deployment.deploy.DeploySUToComponentTask.execute(DeploySUToComponentTask.java:75) at org.ow2.petals.jbi.management.TaskProcessor.process(TaskProcessor.java:76) at org.ow2.petals.jbi.management.task.deployment.deploy.DeployAllSUTask.registerAndDeploySU(DeployAllSUTask.java:168) at org.ow2.petals.jbi.management.task.deployment.deploy.DeployAllSUTask.deploySUS(DeployAllSUTask.java:124) at org.ow2.petals.jbi.management.task.deployment.deploy.DeployAllSUTask.execute(DeployAllSUTask.java:82) at org.ow2.petals.jbi.management.TaskProcessor.process(TaskProcessor.java:76) at org.ow2.petals.jbi.management.deployment.DeploymentServiceImpl.deploy(DeploymentServiceImpl.java:175) at org.objectweb.fractal.julia.generated.C9ae71627_0.deploy(INTERCEPTOR[DeploymentService]) at org.objectweb.fractal.julia.generated.C59d5ff32_0.deploy(INTERFACE[DeploymentService]) at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.performDeploySA(AutoLoaderServiceImpl.java:436) at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.install(AutoLoaderServiceImpl.java:164) at org.ow2.petals.jbi.management.autoload.InstallDirectoryScanner.run(InstallDirectoryScanner.java:82) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source) MYSERVER 2013/04/12 12:21:40,459 GMT+0200 SEVERE [Petals.JBI-Management.DeploymentService] : Unable to deploy the service assembly at 'file:/D:/PetalsESB/petals-esb-4.1/install/sa-SOAP-mywebservice-provide_test.zip' javax.jbi.management.DeploymentException: The deployment of the Service Assembly 'file:/D:/PetalsESB/petals-esb-4.1/install/sa-SOAP-mywebservice-provide_test.zip' failed. at org.ow2.petals.jbi.management.deployment.DeploymentServiceImpl.deploy(DeploymentServiceImpl.java:179) at org.objectweb.fractal.julia.generated.C9ae71627_0.deploy(INTERCEPTOR[DeploymentService]) at org.objectweb.fractal.julia.generated.C59d5ff32_0.deploy(INTERFACE[DeploymentService]) at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.performDeploySA(AutoLoaderServiceImpl.java:436) at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.install(AutoLoaderServiceImpl.java:164) at org.ow2.petals.jbi.management.autoload.InstallDirectoryScanner.run(InstallDirectoryScanner.java:82) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source) Caused by: javax.jbi.management.DeploymentException: All the Service Unit deployment has failed at org.ow2.petals.jbi.management.task.deployment.deploy.DeployAllSUTask.execute(DeployAllSUTask.java:85) at org.ow2.petals.jbi.management.TaskProcessor.process(TaskProcessor.java:76) at org.ow2.petals.jbi.management.deployment.DeploymentServiceImpl.deploy(DeploymentServiceImpl.java:175) ... 7 more MYSERVER 2013/04/12 12:21:40,459 GMT+0200 SEVERE [Petals.AutoLoaderService] : Error during the deployment of a service assembly: java.lang.Exception: javax.jbi.management.DeploymentException: The deployment of the Service Assembly 'file:/D:/PetalsESB/petals-esb-4.1/install/sa-SOAP-mywebservice-provide_test.zip' failed. at org.ow2.petals.jbi.management.deployment.DeploymentServiceImpl.deploy(DeploymentServiceImpl.java:179) at org.objectweb.fractal.julia.generated.C9ae71627_0.deploy(INTERCEPTOR[DeploymentService]) at org.objectweb.fractal.julia.generated.C59d5ff32_0.deploy(INTERFACE[DeploymentService]) at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.performDeploySA(AutoLoaderServiceImpl.java:436) at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.install(AutoLoaderServiceImpl.java:164) at org.ow2.petals.jbi.management.autoload.InstallDirectoryScanner.run(InstallDirectoryScanner.java:82) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source) Caused by: javax.jbi.management.DeploymentException: All the Service Unit deployment has failed at org.ow2.petals.jbi.management.task.deployment.deploy.DeployAllSUTask.execute(DeployAllSUTask.java:85) at org.ow2.petals.jbi.management.TaskProcessor.process(TaskProcessor.java:76) at org.ow2.petals.jbi.management.deployment.DeploymentServiceImpl.deploy(DeploymentServiceImpl.java:175) ... 7 more at org.ow2.petals.jbi.management.deployment.DeploymentServiceImpl.deploy(DeploymentServiceImpl.java:195) at org.objectweb.fractal.julia.generated.C9ae71627_0.deploy(INTERCEPTOR[DeploymentService]) at org.objectweb.fractal.julia.generated.C59d5ff32_0.deploy(INTERFACE[DeploymentService]) at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.performDeploySA(AutoLoaderServiceImpl.java:436) at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.install(AutoLoaderServiceImpl.java:164) at org.ow2.petals.jbi.management.autoload.InstallDirectoryScanner.run(InstallDirectoryScanner.java:82) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source)
Reply | Threaded
Open this post in threaded view
|

Re: Petals 4.1/BC-SOAP : SAX driver error!

Christophe DENEUX
Administrator
This post has NOT been accepted by the mailing list yet.
Hi Philip,

Strange error, can you join us your service assembly ?
Christophe DENEUX
Petals ESB Architect
Linagora
Twitter: @ChrisDENEUX
Reply | Threaded
Open this post in threaded view
|

RE: Petals 4.1/BC-SOAP : SAX driver error!

Philip

I think that Petals does not like wsdl generated with  WCF (.NET). As you can see, they have a wsdl :import clause to reference another wsdl, which in turn refers to xsd files.

I have tried with older .NET ( asmx) webservices, and it works fine on thos.

 

Thanks

 

 

<?xml version="1.0" encoding="UTF-8"?>

<wsdl:definitions xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:i0="http://namespace.domain.com" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:tns="http://tempuri.org/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://tempuri.org/" name="n_deploy"><wsdl:import location="http://myserver.domain.com/ws_deploy_wcfservice/n_deploy.svc?wsdl=wsdl0" namespace="http://namespace.domain.com"/><wsdl:types/><wsdl:service name="n_deploy"><wsdl:port name="ws_deploy_11" binding="i0:ws_deploy_11"><soap:address location="http://myserver.domain.com/ws_deploy_wcfservice/n_deploy.svc"/></wsdl:port><wsdl:port name="ws_deploy_12" binding="i0:ws_deploy_12"><soap12:address location="http://myserver.domain.com/ws_deploy_wcfservice/n_deploy.svc/soap12"/></wsdl:port></wsdl:service></wsdl:definitions>

 

From: Christophe DENEUX [via Petals Forums] [mailto:[hidden email]]
Sent: vendredi 12 avril 2013 14:14
To: Sidgwick Philip
Subject: Re: Petals 4.1/BC-SOAP : SAX driver error!

 

Hi Philip,

Strange error, can you join us your service assembly ?

Christophe DENEUX
Petals ESB Architect
Linagora
Twitter: @ChrisDENEUX

 


If you reply to this email, your message will be added to the discussion below:

http://forum.petalslink.com/Petals-4-1-BC-SOAP-SAX-driver-error-tp4025515p4025516.html

To unsubscribe from Petals 4.1/BC-SOAP : SAX driver error!, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: Petals 4.1/BC-SOAP : SAX driver error!

Vincent Zurczak
Hi Philip,

If I remember well, the problem with these WSDL was an empty mark-up at some point. Something which was not validated in the studio. Otherwise, Petals supports WSDL with various and multiple imports (WSDL, XSD).
« Petals M.D. »
Reply | Threaded
Open this post in threaded view
|

RE: Petals 4.1/BC-SOAP : SAX driver error!

Philip

Here is the SU. Thanks

 

 

From: Vincent Zurczak [via Petals Forums] [mailto:[hidden email]]
Sent: vendredi 12 avril 2013 15:06
To: Sidgwick Philip
Subject: RE: Petals 4.1/BC-SOAP : SAX driver error!

 

Hi Philip,

If I remember well, the problem with these WSDL was an empty mark-up at some point. Something which was not validated in the studio. Otherwise, Petals supports WSDL with various and multiple imports (WSDL, XSD).

« Petals M.D. »

 


If you reply to this email, your message will be added to the discussion below:

http://forum.petalslink.com/Petals-4-1-BC-SOAP-SAX-driver-error-tp4025515p4025518.html

To unsubscribe from Petals 4.1/BC-SOAP : SAX driver error!, click here.
NAML


sa-SOAP-n_deploy-provide.zip (6K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: Petals 4.1/BC-SOAP : SAX driver error!

Vincent Zurczak
Hi,

Your WSDL is marked as invalid in Eclipse's validation.
You have two ports with the same name. I guess this is the cause of the problem.
« Petals M.D. »
Reply | Threaded
Open this post in threaded view
|

RE: Petals 4.1/BC-SOAP : SAX driver error!

Philip

The problem  comes from Petals Studio (I use 1.3.3 ) !

 

The WSDL of the real webservice contains the following section : ( note that the port names are different : ws_deploy_11 and ws_deploy_12)

 

<wsdl:service name="n_deploy">

<wsdl:port name="ws_deploy_11" binding="i0:ws_deploy_11">

<soap:address location="http://dvlp.websvc.gial.be/ws_deploy_wcfservice/n_deploy.svc"/>

</wsdl:port>

<wsdl:port name="ws_deploy_12" binding="i0:ws_deploy_12">

<soap12:address location="http://dvlp.websvc.gial.be/ws_deploy_wcfservice/n_deploy.svc/soap12"/>

</wsdl:port>

</wsdl:service>

 

When I create a Petals Service Provider, the wsdl imported in Petals Studio contains the modified corresponding section :

<wsdl:service name="n_deploy">

    <wsdl:port name="ws_deploy_12" binding="i0:ws_deploy_11">

      <soap:address location="http://dvlp.websvc.gial.be/ws_deploy_wcfservice/n_deploy.svc"/>

    </wsdl:port>

    <wsdl:port name="ws_deploy_12" binding="i0:ws_deploy_12">

      <soap12:address location="http://dvlp.websvc.gial.be/ws_deploy_wcfservice/n_deploy.svc/soap12"/>

    </wsdl:port>

  </wsdl:service>

 

Please note the double occurrence of  <wsdl:port name="ws_deploy_12"

 

Is there a later release of Petals Studio fixing this bug ?

 

Philip

 

From: Vincent Zurczak [via Petals Forums] [mailto:[hidden email]]
Sent: lundi 15 avril 2013 10:59
To: Sidgwick Philip
Subject: RE: Petals 4.1/BC-SOAP : SAX driver error!

 

Hi,

Your WSDL is marked as invalid in Eclipse's validation.
You have two ports with the same name. I guess this is the cause of the problem.

« Petals M.D. »

 


If you reply to this email, your message will be added to the discussion below:

http://forum.petalslink.com/Petals-4-1-BC-SOAP-SAX-driver-error-tp4025515p4025522.html

To unsubscribe from Petals 4.1/BC-SOAP : SAX driver error!, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: Petals 4.1/BC-SOAP : SAX driver error!

Vincent Zurczak
Philip wrote
The problem  comes from Petals Studio (I use 1.3.3 ) !
Indeed, it looks like a wrong implementation (not a bug but a wrong behavior).
The studio may have to update an end-point name and by default, it looks for a SOAP binding or SOAP 1.2 binding. And you have both in your WSDL.

We need to have a more precise search.
I will create a bug entry in our JIRA about this.
« Petals M.D. »
Reply | Threaded
Open this post in threaded view
|

Re: Petals 4.1/BC-SOAP : SAX driver error!

Philip
Is the problem only in the Studio? If so, I could modify the jbi.xml by hand, and use CTRL-F5 to create the zip to be installed.
But if the problem is also present in the ESB implementation, I am stuck...
Thanks

Philip

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Vincent Zurczak
Sent: lundi 15 avril 2013 13:34
To: [hidden email]
Subject: Re: [Users] Petals 4.1/BC-SOAP : SAX driver error!

Philip wrote
> The problem  comes from Petals Studio (I use 1.3.3 ) !

Indeed, it looks like a wrong implementation (not a bug but a wrong behavior).
The studio may have to update an end-point name and by default, it looks for a SOAP binding or SOAP 1.2 binding. And you have both in your WSDL.

We need to have a more precise search.
I will create a bug entry in our JIRA about this.



-----
&laquo; Petals M.D. &raquo;
--
View this message in context: http://forum.petalslink.com/Petals-4-1-BC-SOAP-SAX-driver-error-tp4025515p4025524.html
Sent from the Users (get help, provide help) mailing list archive at Nabble.com.
_______________________________________________
Users mailing list
[hidden email]
http://forum-list.petalslink.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[hidden email]
http://forum-list.petalslink.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Petals 4.1/BC-SOAP : SAX driver error!

Vincent Zurczak
This post was updated on .
In reply to this post by Philip
> Is the problem only in the Studio? If so, I could modify the jbi.xml by hand, and use CTRL-F5 to
> create the zip to be installed.
> But if the problem is also present in the ESB implementation, I am stuck...

The problem is in the studio.
It updates the imported WSDL. And in your case, it does it badly. Juste check the port names in the WSDL files of your Petals projects. Deployment should be fine then.
« Petals M.D. »
Reply | Threaded
Open this post in threaded view
|

RE: Petals 4.1/BC-SOAP : SAX driver error!

Philip

Ok, thanks

 

From: Vincent Zurczak [via Petals Forums] [mailto:[hidden email]]
Sent: mardi 16 avril 2013 16:15
To: Sidgwick Philip
Subject: Re: Petals 4.1/BC-SOAP : SAX driver error!

 

> Is the problem only in the Studio? If so, I could modify the jbi.xml by hand, and use CTRL-F5 to
> create the zip to be installed.
> But if the problem is also present in the ESB implementation, I am stuck...

The problem is in the studio.
It updates the imported WSDL. And in your case, it does it badly. Juste check the port names in the WSDL files of your Petals projets. Deployment should be fine then.

« Petals M.D. »

 


If you reply to this email, your message will be added to the discussion below:

http://forum.petalslink.com/Petals-4-1-BC-SOAP-SAX-driver-error-tp4025515p4025525.html

To unsubscribe from Petals 4.1/BC-SOAP : SAX driver error!, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: Petals 4.1/BC-SOAP : SAX driver error!

Philip
In reply to this post by Vincent Zurczak

I have modified the wsdl for the endpoint problem. I have also checked that it is correct in the generated zip file.

But when installing it on Petals (4.1), I still have a problem : => SchemaException: Can not get schema: : org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not found

 

Does it mean that the sax parser is missing ? How to fix that ?

 

Thanks

 

 

Here is the stack

 

SWNET002 2013/04/17 11:31:00,254 GMT+0200 INFO [Petals.Container.Components.petals-bc-soap] : Deploy Service Unit 'su-SOAP-n_deploy-provide9989'

SWNET002 2013/04/17 11:31:04,066 GMT+0200 WARNING [org.ow2.easywsdl.schema.DefaultSchemaImpl] : Error to read default parent => SchemaException: Can not get schema: : org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not found

SWNET002 2013/04/17 11:31:04,066 GMT+0200 SEVERE [Petals.Container.Components.petals-bc-soap] : Service Unit 'su-SOAP-n_deploy-provide9989' failed to deploy

java.lang.NullPointerException

                at org.ow2.easywsdl.schema.api.abstractElmt.AbstractSchemaImpl.getType(AbstractSchemaImpl.java:293)

                at org.ow2.easywsdl.schema.impl.ElementImpl.findType(ElementImpl.java:81)

                at org.ow2.easywsdl.schema.impl.ElementImpl.<init>(ElementImpl.java:69)

                at org.ow2.easywsdl.schema.impl.SequenceImpl.<init>(SequenceImpl.java:60)

                at org.ow2.easywsdl.schema.impl.ComplexTypeImpl.<init>(ComplexTypeImpl.java:79)

                at org.ow2.easywsdl.schema.impl.SchemaImpl.initialize(SchemaImpl.java:143)

                at org.ow2.easywsdl.extensions.wsdl4complexwsdl.impl.DocumentImpl.<init>(DocumentImpl.java:99)

                at org.ow2.easywsdl.extensions.wsdl4complexwsdl.impl.ImportedDocumentsImpl.<init>(ImportedDocumentsImpl.java:67)

                at org.ow2.easywsdl.extensions.wsdl4complexwsdl.util.ImportedDocumentsFilter.<init>(ImportedDocumentsFilter.java:65)

                at org.ow2.easywsdl.extensions.wsdl4complexwsdl.impl.inout.WSDL4ComplexWsdlReaderImpl.read(WSDL4ComplexWsdlReaderImpl.java:146)

                at org.ow2.easywsdl.extensions.wsdl4complexwsdl.impl.inout.WSDL4ComplexWsdlReaderImpl.read(WSDL4ComplexWsdlReaderImpl.java:222)

                at org.ow2.petals.jbi.component.context.ComponentContextImpl.getInterfacesFromComponentDescription(ComponentContextImpl.java:767)

                at org.ow2.petals.jbi.component.context.ComponentContextImpl.activateEndpoint(ComponentContextImpl.java:157)

                at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.processProvidesNode(AbstractServiceUnitManager.java:957)

                at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.processProvidesNodes(AbstractServiceUnitManager.java:1017)

                at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.deploy(AbstractServiceUnitManager.java:286)

                at org.ow2.petals.jbi.management.task.deployment.deploy.DeploySUToComponentTask.deploySUtoComponent(DeploySUToComponentTask.java:123)

                at org.ow2.petals.jbi.management.task.deployment.deploy.DeploySUToComponentTask.execute(DeploySUToComponentTask.java:75)

                at org.ow2.petals.jbi.management.TaskProcessor.process(TaskProcessor.java:76)

                at org.ow2.petals.jbi.management.task.deployment.deploy.DeployAllSUTask.registerAndDeploySU(DeployAllSUTask.java:168)

                at org.ow2.petals.jbi.management.task.deployment.deploy.DeployAllSUTask.deploySUS(DeployAllSUTask.java:124)

                at org.ow2.petals.jbi.management.task.deployment.deploy.DeployAllSUTask.execute(DeployAllSUTask.java:82)

                at org.ow2.petals.jbi.management.TaskProcessor.process(TaskProcessor.java:76)

                at org.ow2.petals.jbi.management.deployment.DeploymentServiceImpl.deploy(DeploymentServiceImpl.java:175)

                at org.objectweb.fractal.julia.generated.C9ae71627_0.deploy(INTERCEPTOR[DeploymentService])

                at org.objectweb.fractal.julia.generated.C59d5ff32_0.deploy(INTERFACE[DeploymentService])

                at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.performDeploySA(AutoLoaderServiceImpl.java:436)

                at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.install(AutoLoaderServiceImpl.java:164)

                at org.ow2.petals.jbi.management.autoload.InstallDirectoryScanner.run(InstallDirectoryScanner.java:82)

                at java.util.TimerThread.mainLoop(Unknown Source)

                at java.util.TimerThread.run(Unknown Source)

SWNET002 2013/04/17 11:31:04,066 GMT+0200 WARNING [Petals.JBI-Management.DeploymentService] : A component Service Unit Manager failed to deploy a Service Unit :

                               <component-task-result>

                                               <component-name>petals-bc-soap</component-name>

                                               <component-task-result-details xmlns='http://java.sun.com/xml/ns/jbi/management-message'>

                                                               <task-result-details>

                                                                              <task-id>deploy</task-id>

                                                                              <task-result>FAILED</task-result>

                                                                              <message-type>ERROR</message-type>

                                                                              <exception-info>

                                                                                              <nesting-level>1</nesting-level>

                                                                                              <msg-loc-info>

                                                                                                              <loc-token>jbimsg</loc-token>

                                                                                                              <loc-message>Failed to deploy Service Unit : {1}</loc-message>

                                                                                                              <loc-param>su-SOAP-n_deploy-provide9989</loc-param>

                                                                                              </msg-loc-info>

                                                                                              <stack-trace>java.lang.NullPointerException

                at org.ow2.easywsdl.schema.api.abstractElmt.AbstractSchemaImpl.getType(AbstractSchemaImpl.java:293)

                at org.ow2.easywsdl.schema.impl.ElementImpl.findType(ElementImpl.java:81)

                at org.ow2.easywsdl.schema.impl.ElementImpl.<init>(ElementImpl.java:69)

                at org.ow2.easywsdl.schema.impl.SequenceImpl.<init>(SequenceImpl.java:60)

                at org.ow2.easywsdl.schema.impl.ComplexTypeImpl.<init>(ComplexTypeImpl.java:79)

                at org.ow2.easywsdl.schema.impl.SchemaImpl.initialize(SchemaImpl.java:143)

                at org.ow2.easywsdl.extensions.wsdl4complexwsdl.impl.DocumentImpl.<init>(DocumentImpl.java:99)

                at org.ow2.easywsdl.extensions.wsdl4complexwsdl.impl.ImportedDocumentsImpl.<init>(ImportedDocumentsImpl.java:67)

                at org.ow2.easywsdl.extensions.wsdl4complexwsdl.util.ImportedDocumentsFilter.<init>(ImportedDocumentsFilter.java:65)

                at org.ow2.easywsdl.extensions.wsdl4complexwsdl.impl.inout.WSDL4ComplexWsdlReaderImpl.read(WSDL4ComplexWsdlReaderImpl.java:146)

                at org.ow2.easywsdl.extensions.wsdl4complexwsdl.impl.inout.WSDL4ComplexWsdlReaderImpl.read(WSDL4ComplexWsdlReaderImpl.java:222)

                at org.ow2.petals.jbi.component.context.ComponentContextImpl.getInterfacesFromComponentDescription(ComponentContextImpl.java:767)

                at org.ow2.petals.jbi.component.context.ComponentContextImpl.activateEndpoint(ComponentContextImpl.java:157)

                at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.processProvidesNode(AbstractServiceUnitManager.java:957)

                at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.processProvidesNodes(AbstractServiceUnitManager.java:1017)

                at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.deploy(AbstractServiceUnitManager.java:286)

                at org.ow2.petals.jbi.management.task.deployment.deploy.DeploySUToComponentTask.deploySUtoComponent(DeploySUToComponentTask.java:123)

                at org.ow2.petals.jbi.management.task.deployment.deploy.DeploySUToComponentTask.execute(DeploySUToComponentTask.java:75)

                at org.ow2.petals.jbi.management.TaskProcessor.process(TaskProcessor.java:76)

                at org.ow2.petals.jbi.management.task.deployment.deploy.DeployAllSUTask.registerAndDeploySU(DeployAllSUTask.java:168)

                at org.ow2.petals.jbi.management.task.deployment.deploy.DeployAllSUTask.deploySUS(DeployAllSUTask.java:124)

                at org.ow2.petals.jbi.management.task.deployment.deploy.DeployAllSUTask.execute(DeployAllSUTask.java:82)

                at org.ow2.petals.jbi.management.TaskProcessor.process(TaskProcessor.java:76)

                at org.ow2.petals.jbi.management.deployment.DeploymentServiceImpl.deploy(DeploymentServiceImpl.java:175)

                at org.objectweb.fractal.julia.generated.C9ae71627_0.deploy(INTERCEPTOR[DeploymentService])

                at org.objectweb.fractal.julia.generated.C59d5ff32_0.deploy(INTERFACE[DeploymentService])

                at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.performDeploySA(AutoLoaderServiceImpl.java:436)

                at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.install(AutoLoaderServiceImpl.java:164)

                at org.ow2.petals.jbi.management.autoload.InstallDirectoryScanner.run(InstallDirectoryScanner.java:82)

                at java.util.TimerThread.mainLoop(Unknown Source)

                at java.util.TimerThread.run(Unknown Source)

</stack-trace>

                                                               </exception-info>

                                                               </task-result-details>

                                               </component-task-result-details>

                               </component-task-result>

 

SWNET002 2013/04/17 11:31:04,082 GMT+0200 SEVERE [Petals.JBI-Management.DeploymentService] : Unable to deploy the service assembly at 'file:/D:/PetalsESB/petals-esb-4.1/install/sa-SOAP-n_deploy-provide9989.zip'

javax.jbi.management.DeploymentException: The deployment of the Service Assembly 'file:/D:/PetalsESB/petals-esb-4.1/install/sa-SOAP-n_deploy-provide9989.zip' failed.

                at org.ow2.petals.jbi.management.deployment.DeploymentServiceImpl.deploy(DeploymentServiceImpl.java:179)

                at org.objectweb.fractal.julia.generated.C9ae71627_0.deploy(INTERCEPTOR[DeploymentService])

                at org.objectweb.fractal.julia.generated.C59d5ff32_0.deploy(INTERFACE[DeploymentService])

                at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.performDeploySA(AutoLoaderServiceImpl.java:436)

                at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.install(AutoLoaderServiceImpl.java:164)

                at org.ow2.petals.jbi.management.autoload.InstallDirectoryScanner.run(InstallDirectoryScanner.java:82)

                at java.util.TimerThread.mainLoop(Unknown Source)

                at java.util.TimerThread.run(Unknown Source)

Caused by: javax.jbi.management.DeploymentException: All the Service Unit deployment has failed

                at org.ow2.petals.jbi.management.task.deployment.deploy.DeployAllSUTask.execute(DeployAllSUTask.java:85)

                at org.ow2.petals.jbi.management.TaskProcessor.process(TaskProcessor.java:76)

                at org.ow2.petals.jbi.management.deployment.DeploymentServiceImpl.deploy(DeploymentServiceImpl.java:175)

                ... 7 more

SWNET002 2013/04/17 11:31:04,082 GMT+0200 SEVERE [Petals.AutoLoaderService] : Error during the deployment of a service assembly:

java.lang.Exception: javax.jbi.management.DeploymentException: The deployment of the Service Assembly 'file:/D:/PetalsESB/petals-esb-4.1/install/sa-SOAP-n_deploy-provide9989.zip' failed.

                at org.ow2.petals.jbi.management.deployment.DeploymentServiceImpl.deploy(DeploymentServiceImpl.java:179)

                at org.objectweb.fractal.julia.generated.C9ae71627_0.deploy(INTERCEPTOR[DeploymentService])

                at org.objectweb.fractal.julia.generated.C59d5ff32_0.deploy(INTERFACE[DeploymentService])

                at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.performDeploySA(AutoLoaderServiceImpl.java:436)

                at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.install(AutoLoaderServiceImpl.java:164)

                at org.ow2.petals.jbi.management.autoload.InstallDirectoryScanner.run(InstallDirectoryScanner.java:82)

                at java.util.TimerThread.mainLoop(Unknown Source)

                at java.util.TimerThread.run(Unknown Source)

Caused by: javax.jbi.management.DeploymentException: All the Service Unit deployment has failed

                at org.ow2.petals.jbi.management.task.deployment.deploy.DeployAllSUTask.execute(DeployAllSUTask.java:85)

                at org.ow2.petals.jbi.management.TaskProcessor.process(TaskProcessor.java:76)

                at org.ow2.petals.jbi.management.deployment.DeploymentServiceImpl.deploy(DeploymentServiceImpl.java:175)

                ... 7 more

 

                at org.ow2.petals.jbi.management.deployment.DeploymentServiceImpl.deploy(DeploymentServiceImpl.java:195)

                at org.objectweb.fractal.julia.generated.C9ae71627_0.deploy(INTERCEPTOR[DeploymentService])

                at org.objectweb.fractal.julia.generated.C59d5ff32_0.deploy(INTERFACE[DeploymentService])

                at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.performDeploySA(AutoLoaderServiceImpl.java:436)

                at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.install(AutoLoaderServiceImpl.java:164)

                at org.ow2.petals.jbi.management.autoload.InstallDirectoryScanner.run(InstallDirectoryScanner.java:82)

                at java.util.TimerThread.mainLoop(Unknown Source)

                at java.util.TimerThread.run(Unknown Source)

 

From: Sidgwick Philip
Sent: mardi 16 avril 2013 16:17
To: 'Vincent Zurczak [via Petals Forums]'
Subject: RE: Petals 4.1/BC-SOAP : SAX driver error!

 

Ok, thanks

 

From: Vincent Zurczak [via Petals Forums] [[hidden email]]
Sent: mardi 16 avril 2013 16:15
To: Sidgwick Philip
Subject: Re: Petals 4.1/BC-SOAP : SAX driver error!

 

> Is the problem only in the Studio? If so, I could modify the jbi.xml by hand, and use CTRL-F5 to
> create the zip to be installed.
> But if the problem is also present in the ESB implementation, I am stuck...

The problem is in the studio.
It updates the imported WSDL. And in your case, it does it badly. Juste check the port names in the WSDL files of your Petals projets. Deployment should be fine then.

« Petals M.D. »

 


If you reply to this email, your message will be added to the discussion below:

http://forum.petalslink.com/Petals-4-1-BC-SOAP-SAX-driver-error-tp4025515p4025525.html

To unsubscribe from Petals 4.1/BC-SOAP : SAX driver error!, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: Petals 4.1/BC-SOAP : SAX driver error!

Christophe DENEUX
Administrator
This post has NOT been accepted by the mailing list yet.
This post was updated on .
I have just got a similar error running Petals and BC SOAP on a new VM installed with Ubuntu.

I'm investigating about differences between OpenJDK (installed on the VM) and SunJDK installed on my laptop where Petals ESB is running fine.

Which JVM are you using ?
Christophe DENEUX
Petals ESB Architect
Linagora
Twitter: @ChrisDENEUX
Reply | Threaded
Open this post in threaded view
|

RE: Petals 4.1/BC-SOAP : SAX driver error!

Philip

I am using the latest Java 7 : jre-7u17-windows-i586

The problem arises indeed on newly installed servers , with java patched to the last security update.

 

 

From: Christophe DENEUX [via Petals Forums] [mailto:[hidden email]]
Sent: jeudi 18 avril 2013 11:35
To: Sidgwick Philip
Subject: RE: Petals 4.1/BC-SOAP : SAX driver error!

 

I have just get a similar error running Petals and BC SOAP on a new VM installed with Ubuntu.

I'm investigating about differences between OpenJDK (installed on the VM) and SunJDK installed on my laptop where Petals ESB is running fine.

Which JVM are you using ?

Christophe DENEUX
Petals ESB Architect
Linagora
Twitter: @ChrisDENEUX

 


If you reply to this email, your message will be added to the discussion below:

http://forum.petalslink.com/Petals-4-1-BC-SOAP-SAX-driver-error-tp4025515p4025529.html

To unsubscribe from Petals 4.1/BC-SOAP : SAX driver error!, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: Petals 4.1/BC-SOAP : SAX driver error!

Christophe DENEUX
Administrator
This post has NOT been accepted by the mailing list yet.
Philip,

I removed the JAR $PETALS_HOME/lib/stax-api-1.0.2.jar that is a duplicate of geronimo-stax-api_1.0_spec-1.0.1.jar, and Petals ESB seems to work fine.

Can you test removing or renaming the JAR ? I don't understand why Petals ESB is working on my environment removing this JAR
Christophe DENEUX
Petals ESB Architect
Linagora
Twitter: @ChrisDENEUX
Reply | Threaded
Open this post in threaded view
|

RE: Petals 4.1/BC-SOAP : SAX driver error!

Christophe DENEUX
Administrator
This post has NOT been accepted by the mailing list yet.
Sorry for the previous post. The problem is not solved removing the JAR. I reproduce it again.
Christophe DENEUX
Petals ESB Architect
Linagora
Twitter: @ChrisDENEUX
Reply | Threaded
Open this post in threaded view
|

RE: Petals 4.1/BC-SOAP : SAX driver error!

Christophe DENEUX
Administrator
This post has NOT been accepted by the mailing list yet.
It seems the problem is solved removing the JAR xercesImpl-2.8.1 from the BC SOAP. With OpenJDK7 and Java7 (that is based on OpenJDK7), Xerces is found as SAX parser from the BC SOAP classloader but the JDK is not able to load the class. I don't known why.

As Petals ESB can use the SAX2 parser provided by the JVM, it is sufficient to remove the JAR xercesImpl-2.8.1 from the BC SOAP. In the zip file, rename the JAR xercesImpl-2.8.1, and update the JBI descriptor removing the two entries associated to xercesImpl-2.8.1.jar

This workaround is working on my environments. Can you test it and give us feedback ?
Christophe DENEUX
Petals ESB Architect
Linagora
Twitter: @ChrisDENEUX
Reply | Threaded
Open this post in threaded view
|

RE: Petals 4.1/BC-SOAP : SAX driver error!

Philip

I also succeeded by modifying the petals-esb.bat file :  I have added -

Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser

But it only works when launching petals from the command line, not when running as a service

 

I will try your suggestions also.

 

 

if "x%JAVA_OPTS%"=="x" (

   set JAVA_OPTS=-Djava.net.preferIPv4Stack=true -

Djavax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl -

Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser -Xmx1024m -XX:MaxPermSize=256m

)

 

From: Christophe DENEUX [via Petals Forums] [mailto:[hidden email]]
Sent: jeudi 18 avril 2013 18:06
To: Sidgwick Philip
Subject: RE: Petals 4.1/BC-SOAP : SAX driver error!

 

It seems the problem is solved removing the JAR xercesImpl-2.8.1 from the BC SOAP. With OpenJDK7 and Java7 (that is based on OpenJDK7), Xerces is found as SAX parser from the BC SOAP classloader but the JDK is not able to load the class. I don't known why.

As Petals ESB can use the SAX2 parser provided by the JVM, it is sufficient to remove the JAR xercesImpl-2.8.1 from the BC SOAP. In the zip file, rename the JAR xercesImpl-2.8.1, and update the JBI descriptor removing the two entries associated to xercesImpl-2.8.1.jar

This workaround is working on my environments. Can you test it and give us feedback ?

Christophe DENEUX
Petals ESB Architect
Linagora
Twitter: @ChrisDENEUX

 


If you reply to this email, your message will be added to the discussion below:

http://forum.petalslink.com/Petals-4-1-BC-SOAP-SAX-driver-error-tp4025515p4025533.html

To unsubscribe from Petals 4.1/BC-SOAP : SAX driver error!, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: Petals 4.1/BC-SOAP : SAX driver error!

Christophe DENEUX
Administrator
This post has NOT been accepted by the mailing list yet.
Hi Philip,

Have you can try our suggestion removing a JAR from the BC Soap ?
Christophe DENEUX
Petals ESB Architect
Linagora
Twitter: @ChrisDENEUX
Reply | Threaded
Open this post in threaded view
|

RE: Petals 4.1/BC-SOAP : SAX driver error!

Philip

I tried it , and indeed it works. But it is not very « clean »…

 I have found another solution ( as I am using JRE7) : I have added the following in our wrapper.conf

 

# Java Additional Parameters

# .1 is a fix for petals 4.1 with java7

wrapper.java.additional.1=-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser

wrapper.java.additional.2=-Dpetals.home=%PETALS_HOME%

 

 

From: Christophe DENEUX [via Petals Forums] [mailto:[hidden email]]
Sent: vendredi 26 avril 2013 10:54
To: Sidgwick Philip
Subject: RE: Petals 4.1/BC-SOAP : SAX driver error!

 

Hi Philip,

Have you can try our suggestion removing a JAR from the BC Soap ?

Christophe DENEUX
Petals ESB Architect
Linagora
Twitter: @ChrisDENEUX

 


If you reply to this email, your message will be added to the discussion below:

http://forum.petalslink.com/Petals-4-1-BC-SOAP-SAX-driver-error-tp4025515p4025542.html

To unsubscribe from Petals 4.1/BC-SOAP : SAX driver error!, click here.
NAML

12