[
https://issues.jboss.org/browse/JBESB-3673?page=com.atlassian.jira.plugin...
]
Kevin Conner commented on JBESB-3673:
-------------------------------------
I did some searching around and found
http://community.jboss.org/thread/130339 and
https://issues.jboss.org/browse/JBAOP-163.
The forum thread suggests that some work may have already been done on this so it may work
for runtime transformations. I'll chase this up with the AOP guys and see what they
say.
As for removing the signing, this is a requirement of the productisation process for the
platforms and cannot be removed.
jbossesb-rosetta.jar is signed
------------------------------
Key: JBESB-3673
URL:
https://issues.jboss.org/browse/JBESB-3673
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.6
Reporter: David Tucker
Currently the jbossesb-rosetta.jar contains signing files. This has the potential to
create issues if the keys do not match each other. I discovered this when I was trying to
instrument some classes for AOP that are contained in the jar. I kept running into a
java.lang.SecurityException for any classes contained in the rosetta jar and eventually
discovered that signature files were the source of the issue. Removing the RSA and RF
files from the archive would solve this issue for AOP.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira