When is that secheduled for a release?
At a minimum for the jbossas5 beta3 I think we need:
- externalize the name of the aop-messaging-server.xml so these aspects can be overriden in the server integration project.
- externalize the SecurityStore implementation so this can be overriden by the server integration project:
| <mbean code="org.jboss.jms.server.ServerPeer"
| name="jboss.messaging:service=ServerPeer"
| xmbean-dd="xmdesc/ServerPeer-xmbean.xml">
| ...
| <attribute name="AopConfig">jbossas5-aop-messaging-server.xml</attribute>
| <depends optional-attribute-name="SecurityStore">jboss.messaging:service=JBossAS5SecurityStore</depends>
| ...
|
I'll take a look at making these changes.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111476#4111476
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111476
I added a notion of cleaning up after the annotation apply check.
When we do the uninstall of the bean, we check if there are some annotations present that need cleaning up.
In order for an annotation to be applied for a cleanup check, that annotation must be marked with @Cleanup meta annotation.
If we want that annotation is only used for cleanup, not for the apply phase, we can mark it with @CleanupOnly meta annotation.
This notion was needed for the @Aliases annotation plugin to be symmetric, since it's the only one that acts directly on the Controller(Context), and not on the BeanMetaData.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111458#4111458
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111458
"scott.stark(a)jboss.org" wrote : In looking at where jbossas dependencies start, the org.jboss.jms.server.ServerPeer bean needs major refactoring
|
|
Yes indeed. The factoring has pretty much already been done in TRUNK to move us away from the old 1.x design (which is what you're looking at). The new model is a big selling point for us - is completeley POJOised, runnable in MC, bootstrappable etc.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111434#4111434
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111434
"pete.muir(a)jboss.org" wrote :
| By far the easiest way is to use maven ant tasks as it will do all of the above in about 6 lines of ant. But I don't know if this is an acceptable dependency for JBoss AS testsuite. Otherwise we have to write some horrible ant stuff.
|
Paul has been working on getting jbossas to build using maven, so its not a problem to start introducing maven dependencies.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111431#4111431
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111431