Posted by [IP Address: 167.239.214.247] 'Bruce Tobin' on May 25, 2001 at 09:17:23 EST:
We have successfully called a component we built via the component interface from VB, but when we attempt to duplicate our client code in Java we get the following exception on the component save() method:
bea.jolt.ApplicationException: TPESVCFAIL - application level service failure
at bea.jolt.JoltRemoteService.decodeCALL(JoltRemoteService.java:405)
at bea.jolt.JoltRemoteService.call(JoltRemoteService.java:323)
at psft.pt8.net.NetReqRepSvc.sendRequest(NetReqRepSvc.java:376)
at psft.pt8.net.NetService.requestService(NetService.java:144)
at psft.pt8.joa.JOAService.joaRequestService(JOAService.java:49)
at psft.pt8.joa.CISvc.save(CISvc.java:47)
at psft.pt8.joa.CI.invokeMethod(CI.java:240)
at PeopleSoft.Generated.CompIntfc.ZValidation10.save(ZValidation10.java:
240)
The save is supposed to fail (our component is doing validation and we need to pass validation error messages back to the calling program), but it seems to be failing too early for the required messages to be passed back. In our VB code the PSMessages collection of the Session object contains the error messages after the save fails, but in our Java code this collection is empty. Is there a fundamental difference in the way the Java libraries and the VB libraries handle application errors?