Question
Marsh
US
Last activity: 9 Sep 2015 10:37 EDT
AXIS2 and Metro jar conflict
Pega internally uses AXIS2 Web Services implementation and Velocity SDK (our integration service) is using JAX-WS(Metro) Implementation.
Currently, we are doing velocity integration directly using Jar on the classpath (We are not using any connectors).
AXIS2 jars are taking precedence over Metro Jars and we are getting weird exception while calling Velocity Web Service.
This kind of issues are anticipated when we have two web service implementations on classpath.
Pega internally uses AXIS2 Web Services implementation and Velocity SDK (our integration service) is using JAX-WS(Metro) Implementation.
Currently, we are doing velocity integration directly using Jar on the classpath (We are not using any connectors).
AXIS2 jars are taking precedence over Metro Jars and we are getting weird exception while calling Velocity Web Service.
This kind of issues are anticipated when we have two web service implementations on classpath.
[8/17/15 15:27:19:612 EDT] 0000003b SystemErr R javax.xml.ws.WebServiceException: javax.wsdl.WSDLException: WSDLException (at /html): faultCode=INVALID_WSDL: Expected element '{http://schemas.xmlsoap.org/wsdl/}definitions'.
[8/17/15 15:27:19:613 EDT] 0000003b SystemErr R at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:175)
[8/17/15 15:27:19:613 EDT] 0000003b SystemErr R at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:70)
[8/17/15 15:27:19:613 EDT] 0000003b SystemErr R at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:128)
[8/17/15 15:27:19:613 EDT] 0000003b SystemErr R at org.apache.axis2.jaxws.util.WSDL4JWrapper.loadDefinition(WSDL4JWrapper.java:741)
[8/17/15 15:27:19:613 EDT] 0000003b SystemErr R at org.apache.axis2.jaxws.util.WSDL4JWrapper.getDefinition(WSDL4JWrapper.java:657)
[8/17/15 15:27:19:613 EDT] 0000003b SystemErr R at org.apache.axis2.jaxws.util.WSDL4JWrapper.commonPartsURLConstructor(WSDL4JWrapper.java:224)
[8/17/15 15:27:19:613 EDT] 0000003b SystemErr R at org.apache.axis2.jaxws.util.WSDL4JWrapper.<init>(WSDL4JWrapper.java:156)
[8/17/15 15:27:19:613 EDT] 0000003b SystemErr R at org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.setupWsdlDefinition(ServiceDescriptionImpl.java:1182)
[8/17/15 15:27:19:613 EDT] 0000003b SystemErr R at org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.<init>(ServiceDescriptionImpl.java:249)
[8/17/15 15:27:19:614 EDT] 0000003b SystemErr R at org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.<init>(ServiceDescriptionImpl.java:172)
[8/17/15 15:27:19:614 EDT] 0000003b SystemErr R at org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.createServiceDescription(DescriptionFactoryImpl.java:143)
[8/17/15 15:27:19:614 EDT] 0000003b SystemErr R at org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.createServiceDescription(DescriptionFactoryImpl.java:79)
[8/17/15 15:27:19:614 EDT] 0000003b SystemErr R at org.apache.axis2.jaxws.description.DescriptionFactory.createServiceDescription(DescriptionFactory.java:78)
[8/17/15 15:27:19:614 EDT] 0000003b SystemErr R at org.apache.axis2.jaxws.spi.ServiceDelegate.<init>(ServiceDelegate.java:218)
[8/17/15 15:27:19:614 EDT] 0000003b SystemErr R at org.apache.axis2.jaxws.spi.Provider.createServiceDelegate(Provider.java:83)
[8/17/15 15:27:19:614 EDT] 0000003b SystemErr R at org.apache.axis2.jaxws.spi.Provider.createServiceDelegate(Provider.java:79)
[8/17/15 15:27:19:614 EDT] 0000003b SystemErr R at javax.xml.ws.Service.<init>(Service.java:57)
[8/17/15 15:27:19:614 EDT] 0000003b SystemErr R at com.vrcis.webservices.VelocityWebServiceAPI_Service.<init>(VelocityWebServiceAPI_Service.java:42)
[8/17/15 15:27:19:614 EDT] 0000003b SystemErr R at com.vrcis.webservices.client.VelocityWebServiceSDK.<init>(VelocityWebServiceSDK.java:66)
[8/17/15 15:27:19:614 EDT] 0000003b SystemErr R at com.vrcis.webservices.client.VelocityWebServiceSDK.<init>(VelocityWebServiceSDK.java:59)
[8/17/15 15:27:19:614 EDT] 0000003b SystemErr R at com.marsh.velocity.business.VelocityServiceImpl.getVelocityWebServiceSDK(VelocityServiceImpl.java:243)
[8/17/15 15:27:19:614 EDT] 0000003b SystemErr R at com.marsh.velocity.business.VelocityServiceImpl.CreateCustomer(VelocityServiceImpl.java:1451)
[8/17/15 15:27:19:614 EDT] 0000003b SystemErr R at com.pegarules.generated.activity.ra_action_createcustomer_101516750436b1cda4ff18c0744b3894.step3_circum0(ra_action_createcustomer_101516750436b1cda4ff18c0744b3894.java:388)
Pegasystems Inc.
US
Have you tried to put all your velocity related jars into the Websphere shared lib (or any app server specific location)? That should be your first option to avoid any potential conflict.
Marsh
US
Hi Aditya & Kevin,
Putting all the velocity related jars in shared lib in websphere was our first approach. That was when we faced a onflict with the jars in websphere plugins.
We later pulled them offf from shared lib and imported them to pega. This has not solved the issue yet. We have opened a SR and working with pegasystems to get this resolved.
Thank you.