Skip to Content
0

Exception when updating 3.1 to 4.1

Apr 11, 2017 at 03:39 PM

20

avatar image

I am updating my application that uses the java SDK to call reports from BI. This application is using rebean classes to call the reports. I was able to resolve the issues that I got initially due to refactoring of rebean classes. Following are different threads that I used from SAP community forum to address those issues.

https://archive.sap.com/discussions/thread/1736462

https://archive.sap.com/discussions/thread/3550435

https://archive.sap.com/discussions/thread/3446181

I have included all the jars that are mentioned in last thread above and attached is a list of those jar files from work space. I was hoping to get this issue fixed after updating the Jars, however, now I am getting following exception and not finding any solution to the problem.

Caused by: java.lang.SecurityException: Signers of 'org.eclipse.core.runtime.RegistryFactory' do not match signers of other classes in package

Will appreciate if someone can suggest a solution here.

This application is running in WebSphere 7 server.

I am not at a point to test it in the server yet. I am trying to get my JUnits working first.

I am using RAD 8 to make these changes and running my JUnits.

10 |10000 characters needed characters left characters exceeded

Attached are two files with exception and jar informationjars-suggusted.txtjars-in-my-app.txtexception.txt

0

Also attached is the code. It fails at following line.

documentInstance = buildPopulationPrompts(documentInstance, searchCriteria);

code.txt

code.txt (10.2 kB)
0
* Please Login or Register to Answer, Follow or Comment.

0 Answers