2 Replies Latest reply on Nov 19, 2007 3:04 PM by Ales Justin

    Sources and build for 1.0.2

    Adrian Brock Master

       



      Fernando Nasser wrote:
      > I need to find the sources for the microcontainer sources (including
      > microkernel, container and dependency modules) that was used to build
      >
      > <componentref name="jboss/microcontainer" version="1.0.2"/>
      >
      > I can see a
      >
      > https://svn.jboss.org/repos/jbossas/tags/JBossMC_1_0_2/
      >
      > but that seems to apply to the whole AS source tree and I don't know
      > what to extract out of it.
      >
      > Also, some hints on how to build the 3 JARs independently would also be
      > appreciated.
      >
      > jboss-container.jar 09-Apr-2007 11:58 58K
      > jboss-dependency.jar 09-Apr-2007 11:58 19K
      > jboss-microcontainer.jar 09-Apr-2007 11:58 211K



      The 1.0.x version of the Microcontainer WAS developed as part of the application server
      as described on this old WIKI page:
      http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMicrocontainer&version=10


        • 1. Re: Sources and build for 1.0.2
          Fernando Nasser Newbie

          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
            Ales Justin Master

             

            "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.