This content has been marked as final.
Show 2 replies
-
1. Re: Sources and build for 1.0.2
fnasser Nov 19, 2007 12:10 PM (in response to adrian.brock)The Wiki page sahys we should get:
# cvs co aop-mc-int
# cvs co container
# cvs co -d dependency jboss-dependency
# cvs co -d kernel microkernel
I can get the JBossMC_1_0_2 tag for container, jboss-dependency and microkernel with commands like:
cvs -d:pserver:anonymous@anoncvs.forge.jboss.com:/cvsroot/jboss export -r JBossMC_1_0_2 container
But there is no such tag for aop-mc-int. Should I assume that component is just for the 2.x version and that it does not exist and is not necessary for the 1.0.2 version?
Thanks. -
2. Re: Sources and build for 1.0.2
alesj Nov 19, 2007 3:04 PM (in response to adrian.brock)"fnasser@redhat.com" wrote:
But there is no such tag for aop-mc-int. Should I assume that component is just for the 2.x version and that it does not exist and is not necessary for the 1.0.2 version?
aop-mc-int was only introduced in version 2.x (perhaps there was some notion in the late 1.0.2 code base, but the real full impl is for 2.x).
It's optional module/component - transparent AOP support for beans.
If the aop-mc-int artifact is present in MC's classpath, together with jboss-aop lib, then the AOP bean support is used by default. Otherwise it silently falls back to plain POJO - no AOP.