|
| 58238 | modified | kabir.khan@jboss.com | //projects/microcontainer/trunk/aop-mc-int/src/main/org/jboss/aop/microcontainer/integration/AOPDependencyBuilder.java | Fixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names" |
| 58238 | modified | kabir.khan@jboss.com | //projects/microcontainer/trunk/container/src/main/org/jboss/repository/spi/MetaDataContextFactory.java | Fixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names" |
| 58238 | added | kabir.khan@jboss.com | //projects/microcontainer/trunk/aop-mc-int/src/main/org/jboss/aop/microcontainer/integration/AOPMetaDataContextFactoryDelegate.java | Fixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names" |
| 58238 | added | kabir.khan@jboss.com | //projects/microcontainer/trunk/aop-mc-int/src/main/org/jboss/aop/microcontainer/integration/AOPDeployedChecker.java | Fixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names" |
| 58238 | modified | kabir.khan@jboss.com | //projects/microcontainer/trunk/kernel/src/main/org/jboss/kernel/plugins/dependency/DescribeAction.java | Fixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names" |
| 58238 | modified | kabir.khan@jboss.com | //projects/microcontainer/trunk/aop-mc-int/src/main/org/jboss/aop/microcontainer/integration/AOPMetaDataContextFactory.java | Fixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names" |
| 58238 | modified | kabir.khan@jboss.com | //projects/microcontainer/trunk/aop-mc-int/build.xml | Fixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names" |
| 58238 | modified | kabir.khan@jboss.com | //projects/microcontainer/trunk/aop-mc-int/src/main/org/jboss/aop/microcontainer/integration/AOPConstructorJoinpoint.java | Fixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names" |
| 58238 | added | kabir.khan@jboss.com | //projects/microcontainer/trunk/aop-mc-int/src/main/org/jboss/aop/microcontainer/integration/AOPDependencyBuilderDelegate.java | Fixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names" |
| 58238 | modified | kabir.khan@jboss.com | //projects/microcontainer/trunk/container/src/main/org/jboss/repository/plugins/basic/BasicMetaDataContextFactory.java | Fixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names" |
| 58238 | modified | kabir.khan@jboss.com | //projects/microcontainer/trunk/aop-mc-int/src/main/org/jboss/aop/microcontainer/integration/AOPJoinpointFactory.java | Fixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names" |
| 58238 | modified | kabir.khan@jboss.com | //projects/microcontainer/trunk/aop-mc-int/src/main/org/jboss/aop/microcontainer/beans/AspectBeanMetaDataFactory.java | Fixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names" |