[jboss-jira] [JBoss JIRA] Updated: (JBAOP-698) Generate proxies in org.jboss.aop.generatedproxies package rather than in default package

[Kabir Khan (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAOP-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kabir Khan updated JBAOP-698:
-----------------------------

                  Summary: Generate proxies in org.jboss.aop.generatedproxies package rather than in default package  (was: Generate proxies in org.jboss.aop.generatedclasses package rather than in default package)
            Fix Version/s: 2.1.0.GA
    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=147105&start=10
              Description: 
ClassProxies were always generated in the default package
ContainerProxies were generated in the default package if proxying a jdk class (e.g. java.util.ArrayList)

This causes problems with the new jboss-cl classloaders since only packages exported by the loader on creation are registered with the domain. If the default package was not exported, then these classes will not be found.

As a first step from the AOP side we will generate the proxies in a different package, and some work will be needed on the jboss-cl/AS side to make sure that this package is exported when creating the deployment classloaders


> Generate proxies in org.jboss.aop.generatedproxies package rather than in default package
> -----------------------------------------------------------------------------------------
>
>                 Key: JBAOP-698
>                 URL: https://jira.jboss.org/jira/browse/JBAOP-698
>             Project: JBoss AOP
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Kabir Khan
>            Assignee: Kabir Khan
>             Fix For: 2.1.0.GA
>
>
> ClassProxies were always generated in the default package
> ContainerProxies were generated in the default package if proxying a jdk class (e.g. java.util.ArrayList)
> This causes problems with the new jboss-cl classloaders since only packages exported by the loader on creation are registered with the domain. If the default package was not exported, then these classes will not be found.
> As a first step from the AOP side we will generate the proxies in a different package, and some work will be needed on the jboss-cl/AS side to make sure that this package is exported when creating the deployment classloaders

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira