Support Article
External Jar File import not showing up
SA-98
Summary
This issue occurs in our sandbox environment. Extendable jar file is not showing up.
Error Messages
2014-06-30 13:58:42,470 [ WebContainer : 0] [ STANDARD] [OneClaimLOB:01.02.01] (nvoke.Rule_Connect_Java.Action) ERROR |Rule-Connect-Java.Shared-Java-CASL20-ServiceAccess-.ServiceAccess - constructor failed: javax.xml.rpc.ServiceException: WSWS5013E: No constructor with the signature (URL, Service) was found for generated Stub class CASLExtConsumingServicesWSDL.CASLExtConsumingServicesSOAPBindingStub: java.lang.NoSuchMethodException: CASLExtConsumingServicesWSDL.CASLExtConsumingServicesSOAPBindingStub.<init>(java.net.URL, javax.xml.rpc.Service)
javax.xml.rpc.ServiceException: WSWS5013E: No constructor with the signature (URL, Service) was found for generated Stub class CASLExtConsumingServicesWSDL.CASLExtConsumingServicesSOAPBindingStub: java.lang.NoSuchMethodException: CASLExtConsumingServicesWSDL.CASLExtConsumingServicesSOAPBindingStub.<init>(java.net.URL, javax.xml.rpc.Service)
at com.ibm.ws.webservices.multiprotocol.AgnosticService.getGeneratedStub(AgnosticService.java:637)
at com.ibm.ws.webservices.multiprotocol.AgnosticService.doGetPort(AgnosticService.java:494)
at com.ibm.ws.webservices.multiprotocol.AgnosticService.getStub(AgnosticService.java:437)
Steps to Reproduce
1) Remove the external jar file from ear file.
2) Import them in database using import wizard.
3) Restart the server.
4) Newly imported classes are not showing up.
Root Cause
The root cause of this problem is in a third-party product integrated with PRPC.
This issue was seen before when trying to import this same jar file into PRPC 6.1SP2.
======
The jar is basically a WEBSERVICE SOAP Binding stub classes, which act as a client to call the remote service.
So this jar is the webservice client which makes a SOAP request to the underlying webservice, via SOAP over http or RMI depending on the client stubs.
PEGA doesn't recommend to have those type of Stubs (calling RMI/soapclient) jar file to be loaded actually from the PegaRULES
database despite it's an external jar file.
Pega recommends to have this jar file outside the PegaRULES database. Our application class loader is not designed to load the RMI client stubs from the database.
======
Resolution
This issue is resolved by making the following change to software integrated with PRPC:
To keep the jar outside of the PRPC deployment, use a shared libary configuration since they are using WebSphere.
Published February 17, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.