Created: (JBAOP-366) Ability to attach a .aop deployment to a particular s

Thread: Created: (JBAOP-366) Ability to attach a .aop deployment to a particular s

Search this list only Search all lists
Created: (JBAOP-366) Ability to attach a .aop deployment to a particular s
United States	2007-02-23 12:19:37
Ability to attach a .aop deployment to a particular scoped classloader ------------------------------------------------------------ ---------- Key: JBAOP-366 URL: http://ji ra.jboss.com/jira/browse/JBAOP-366 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha2 Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha3, 1.5.4.GA e.g. if an .ear file has been scoped with: <jboss-app> <loader-repository> dot.com:loader=ear1test </loader-repository> </jboss-app> It should be possible to deploy at a later time a .aop file like: <aop> <attach-scoped-loader>dot.com:loader=ear1test</atta ch-scoped-loader> <!-- aspects, bindings etc. --> </aop> The classloader for the scoped repository "dot.com:loader=ear1test" should be used to deploy the contents of the .aop file in the same way as if the .aop file had been deployed as part of the .ear. -- 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 - For more information on JIRA, see: http://www.atl assian.com/software/jira _______________________________________________ jboss-jira mailing list jboss-jiralists.jboss.org h ttps://lists.jboss.org/mailman/listinfo/jboss-jira

Updated: (JBAOP-366) Ability to attach a .aop deployment to a particular s
United States	2007-02-23 12:21:35
[ http://jira.jboss.com/jira/browse/JBAOP-366?page=all ] Kabir Khan updated JBAOP-366: ----------------------------- Fix Version/s: 2.0.0.alpha4 (was: 1.5.4.GA) (was: 2.0.0.alpha3) Affects Version/s: 2.0.0.alpha3 (was: 2.0.0.alpha2) Will need to create another deployer in the chain that steps in once the JMXKernel has been deployed > Ability to attach a .aop deployment to a particular scoped classloader > ------------------------------------------------------------ ---------- > > Key: JBAOP-366 > URL: http://ji ra.jboss.com/jira/browse/JBAOP-366 > Project: JBoss AOP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.alpha3 > Reporter: Kabir Khan > Assigned To: Kabir Khan > Fix For: 2.0.0.alpha4 > > > e.g. if an .ear file has been scoped with: > <jboss-app> > <loader-repository> > dot.com:loader=ear1test > </loader-repository> > </jboss-app> > It should be possible to deploy at a later time a .aop file like: > <aop> > <attach-scoped-loader>dot.com:loader=ear1test</atta ch-scoped-loader> > <!-- aspects, bindings etc. --> > </aop> > The classloader for the scoped repository "dot.com:loader=ear1test" should be used to deploy the contents of the .aop file in the same way as if the .aop file had been deployed as part of the .ear. -- 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 - For more information on JIRA, see: http://www.atl assian.com/software/jira _______________________________________________ jboss-jira mailing list jboss-jiralists.jboss.org h ttps://lists.jboss.org/mailman/listinfo/jboss-jira

Commented: (JBAOP-366) Ability to attach a .aop deployment to a particular
United States	2007-02-23 12:21:35
[ http://jira.jboss.com/jira/browse/JBAOP -366?page=comments#action_12354108 ] Kabir Khan commented on JBAOP-366: ---------------------------------- ...since we need the MBeanServer to get hold of the repository > Ability to attach a .aop deployment to a particular scoped classloader > ------------------------------------------------------------ ---------- > > Key: JBAOP-366 > URL: http://ji ra.jboss.com/jira/browse/JBAOP-366 > Project: JBoss AOP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.alpha3 > Reporter: Kabir Khan > Assigned To: Kabir Khan > Fix For: 2.0.0.alpha4 > > > e.g. if an .ear file has been scoped with: > <jboss-app> > <loader-repository> > dot.com:loader=ear1test > </loader-repository> > </jboss-app> > It should be possible to deploy at a later time a .aop file like: > <aop> > <attach-scoped-loader>dot.com:loader=ear1test</atta ch-scoped-loader> > <!-- aspects, bindings etc. --> > </aop> > The classloader for the scoped repository "dot.com:loader=ear1test" should be used to deploy the contents of the .aop file in the same way as if the .aop file had been deployed as part of the .ear. -- 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 - For more information on JIRA, see: http://www.atl assian.com/software/jira _______________________________________________ jboss-jira mailing list jboss-jiralists.jboss.org h ttps://lists.jboss.org/mailman/listinfo/jboss-jira

Updated: (JBAOP-366) Ability to attach a .aop deployment to a particular s
United States	2007-03-21 13:18:52
[ http://jira.jboss.com/jira/browse/JBAOP-366?page=all ] Kabir Khan updated JBAOP-366: ----------------------------- Fix Version/s: 2.0.0.alpha5 (was: 2.0.0.alpha4) > Ability to attach a .aop deployment to a particular scoped classloader > ------------------------------------------------------------ ---------- > > Key: JBAOP-366 > URL: http://ji ra.jboss.com/jira/browse/JBAOP-366 > Project: JBoss AOP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.alpha3 > Reporter: Kabir Khan > Assigned To: Kabir Khan > Fix For: 2.0.0.alpha5 > > > e.g. if an .ear file has been scoped with: > <jboss-app> > <loader-repository> > dot.com:loader=ear1test > </loader-repository> > </jboss-app> > It should be possible to deploy at a later time a .aop file like: > <aop> > <attach-scoped-loader>dot.com:loader=ear1test</atta ch-scoped-loader> > <!-- aspects, bindings etc. --> > </aop> > The classloader for the scoped repository "dot.com:loader=ear1test" should be used to deploy the contents of the .aop file in the same way as if the .aop file had been deployed as part of the .ear. -- 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 - For more information on JIRA, see: http://www.atl assian.com/software/jira _______________________________________________ jboss-jira mailing list jboss-jiralists.jboss.org h ttps://lists.jboss.org/mailman/listinfo/jboss-jira

Updated: (JBAOP-366) Ability to attach a .aop deployment to a particular s
United States	2007-05-10 05:17:54
[ http://jira.jboss.com/jira/browse/JBAOP-366?page=all ] Kabir Khan updated JBAOP-366: ----------------------------- Fix Version/s: 2.0.0.alpha6 (was: 2.0.0.alpha5) > Ability to attach a .aop deployment to a particular scoped classloader > ------------------------------------------------------------ ---------- > > Key: JBAOP-366 > URL: http://ji ra.jboss.com/jira/browse/JBAOP-366 > Project: JBoss AOP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.alpha3 > Reporter: Kabir Khan > Assigned To: Kabir Khan > Fix For: 2.0.0.alpha6 > > > e.g. if an .ear file has been scoped with: > <jboss-app> > <loader-repository> > dot.com:loader=ear1test > </loader-repository> > </jboss-app> > It should be possible to deploy at a later time a .aop file like: > <aop> > <attach-scoped-loader>dot.com:loader=ear1test</atta ch-scoped-loader> > <!-- aspects, bindings etc. --> > </aop> > The classloader for the scoped repository "dot.com:loader=ear1test" should be used to deploy the contents of the .aop file in the same way as if the .aop file had been deployed as part of the .ear. -- 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 - For more information on JIRA, see: http://www.atl assian.com/software/jira _______________________________________________ jboss-jira mailing list jboss-jiralists.jboss.org h ttps://lists.jboss.org/mailman/listinfo/jboss-jira

Updated: (JBAOP-366) Ability to attach a .aop deployment to a particular s
United States	2007-06-21 15:19:56
[ http://jira.jboss.com/jira/browse/JBAOP-366?page=all ] Kabir Khan updated JBAOP-366: ----------------------------- Fix Version/s: 2.0.0.CR1 (was: 2.0.0.beta) > Ability to attach a .aop deployment to a particular scoped classloader > ------------------------------------------------------------ ---------- > > Key: JBAOP-366 > URL: http://ji ra.jboss.com/jira/browse/JBAOP-366 > Project: JBoss AOP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.alpha3 > Reporter: Kabir Khan > Assigned To: Kabir Khan > Fix For: 2.0.0.CR1 > > > e.g. if an .ear file has been scoped with: > <jboss-app> > <loader-repository> > dot.com:loader=ear1test > </loader-repository> > </jboss-app> > It should be possible to deploy at a later time a .aop file like: > <aop> > <attach-scoped-loader>dot.com:loader=ear1test</atta ch-scoped-loader> > <!-- aspects, bindings etc. --> > </aop> > The classloader for the scoped repository "dot.com:loader=ear1test" should be used to deploy the contents of the .aop file in the same way as if the .aop file had been deployed as part of the .ear. -- 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 - For more information on JIRA, see: http://www.atl assian.com/software/jira _______________________________________________ jboss-jira mailing list jboss-jiralists.jboss.org h ttps://lists.jboss.org/mailman/listinfo/jboss-jira

Closed: (JBAOP-366) Ability to attach a .aop deployment to a particular sc
United States	2007-10-31 15:20:45
[ http://jira.jboss.com/jira/browse/JBAOP-366?page=all ] Kabir Khan closed JBAOP-366. ---------------------------- Resolution: Done > Ability to attach a .aop deployment to a particular scoped classloader > ------------------------------------------------------------ ---------- > > Key: JBAOP-366 > URL: http://ji ra.jboss.com/jira/browse/JBAOP-366 > Project: JBoss AOP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.alpha3 > Reporter: Kabir Khan > Assigned To: Kabir Khan > Fix For: 2.0.0.CR1 > > > e.g. if an .ear file has been scoped with: > <jboss-app> > <loader-repository> > dot.com:loader=ear1test > </loader-repository> > </jboss-app> > It should be possible to deploy at a later time a .aop file like: > <aop> > <attach-scoped-loader>dot.com:loader=ear1test</atta ch-scoped-loader> > <!-- aspects, bindings etc. --> > </aop> > The classloader for the scoped repository "dot.com:loader=ear1test" should be used to deploy the contents of the .aop file in the same way as if the .aop file had been deployed as part of the .ear. -- 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 - For more information on JIRA, see: http://www.atl assian.com/software/jira _______________________________________________ jboss-jira mailing list jboss-jiralists.jboss.org h ttps://lists.jboss.org/mailman/listinfo/jboss-jira

[1-7]

about | contact Other archives ( Real Estate discussion Medical topics )