Better handling of unused import package by Javassist at runtime
----------------------------------------------------------------
Key: JBAOP-56
URL: http://jira.jboss.com/jira/browse/JBAOP-56
Project: JBoss AOP
Type: Feature Request
Reporter: Ben Wang
Assigned to: Bill Burke
Fix For: 1.1
We run into this problem in JBossCache and I have seen this at a customer site
as well.
In JBossCache, for example, we import a jboss jndi package since we need to
expose jndi inside JBoss AS. However, this code path is not used when running
as a standalone. So once it is compiled properly inside JBoss, I can still run
JBossCache outside the container.
But this will generate error when running JBossCacheAop as a standalone. The
reason is that Javassist will try to byte-code generate every single import
package specified in the class. If not found, an exception will be thrown and
stopped. In the aforementioned example, I should expect to see Javassist to
just generate a warning against this and keep going.
So I see two possible enhancements:
1. Generate better debugging message so user realize what's going on. Current
one is burried inside a huge stack trace.
2. Have a switch somewhere (can be inside aopc) that allows the user to carry
forward.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
