Is org.jboss.aspects.asynch.Future available in Maven repo f

[jaikiran]

I am using JBossAS-5.0 GA and trying to get an Asynchronous EJB working. Here's the documentation http://docs.jboss.org/ejb3/app-server/reference/build/reference/en/html/jboss_extensions.html#d0e427

As seen in that example, the client uses org.jboss.aspects.asynch.Future to hold the future result. I see that this org.jboss.aspects.asynch.Future is contained in %JBOSS_HOME%/client/jboss-aspect-jdk50-client.jar. I have a couple of related questions:

1) What's with the naming convention of this jar file? Is this jar meant only for JDK5?
2) The project that i am trying to use this Future object, is a Maven2 project. Is there a Maven artifact for the jboss-aspect-jdk50-client.jar? I could not locate it under the JBoss Maven2 repository.

[kabirkhan]

1) This is a hangover from AS 4.x where we had a JDK 1.4 and 5 version. The main difference was the JDK 5 version used real annotations, while the 1.4 version used the annotation compiler. It should work on JDK 6

2) No, it is created by the AS aspects/ build, and put in the client/ folder by the AS build-distr.xml script. AS has not been mavenized yet. Maybe Paul Gier can help with getting it into Maven?

[jaikiran]

Thanks Kabir. For the time being, i will add the jboss-aspect-jdk50-client.jar as a systemPath dependency in my Maven project.

[jaikiran]

2) No, it is created by the AS aspects/ build, and put in the client/ folder by the AS build-distr.xml script. AS has not been mavenized yet. Maybe Paul Gier can help with getting it into Maven?

Thanks for that pointer about build-distr.xml.

The package name org.jboss.aspects.* made me believe that the source resides in the aspects project :-) Turns out the org.jboss.aspects.asynch.* classes come from the EJBTHREE project while builing this jboss-aspect-deployer-jdk50.jar :

<!-- Build jboss-aspect-deployer-jdk50.jar -->
 <jar destfile="${build.lib}/jboss-aspect-library.jar" manifest="${build.etc}/default.mf"
 update="${jar.update}" index="${jar.index}">
 <fileset dir="${build.classes}">
 <include name="org/jboss/aop/junit/**"/>
 <include name="org/jboss/aspects/**"/>
 </fileset>
 <fileset dir="${build.etc}">
 <include name="org/jboss/**/*.xml"/>
 </fileset>
 <!-- include the broken out asynch aspects in the lib -->
 <zipfileset src="${org.jboss.ejb3.lib}/jboss-ejb3-async.jar">
 <include name="org/jboss/aspects/asynch/**.class"/>
 </zipfileset>
 ...

And EJBTHREE project is Mavenized. So i can add a dependency on

<groupId>org.jboss.ejb3</groupId>
 <artifactId>jboss-ejb3-async</artifactId>

[kabirkhan]

"jaikiran" wrote:

The package name org.jboss.aspects.* made me believe that the source resides in the aspects project :-) Turns out the org.jboss.aspects.asynch.* classes come from the EJBTHREE project while builing this jboss-aspect-deployer-jdk50.jar :

Yeah, it use to live in aspects/, but it was broken out since EJB 3 is the main user.