There are two ways to get EJB 3 support in JBoss.
First, download and run the installer jar file. One of the installation opitons will be EJB3 support (I think selecting 'all' also installs EJB3 support).
Second, download the source tar.gz file and build JBoss using JVM 5.0 (go to the build directory and run build.sh or build.bat). This results in two builds of JBoss, one with EJB3 support, and the other without.
This I know and am running jboss-4.0.3SP1, but I am wondering which archive (jar-file) I must use when I want to import the annotations...
Look at the jars in ejb3.deployer.
After a bit of jar searching, I found the classes in the jar file named jboss-annotations-ejb3.jar localed in JBOSS_SERVER\deploy\ejb3.deployer folder. However; I get a compilation error:
[javac] Compiling 1 source file to C:\Data\mine\hjemme\bin [javac] C:\Data\mine\hjemme\src\<src.folder>\<MBean>.java:14: cannot find symbol [javac] symbol : method value() [javac] location: @interface org.jboss.annotation.ejb.Management [javac] @Management (<interface>.class) [javac] ^ [javac] 1 error
In the JBoss Eclipse IDE, I get the error message 'The attribute value is undefined for the annotation type Management.' This is located in the source
The interface is implemented without any errors and I do not know what might be wrong. Please help me solve this.
Can you make sure you have the latest jboss-annotations.ejb3.jar? I suspect you have an old version that did not have the 'value' attribute in the annotation. In older versions, this annotation was only allowed on the interface, not on the Service class, so there was no value attribute used to specify the interface class.
Sure I can make sure that I have the latest release... But HOW?
My jar file is dated the 23 october 2005 (23:57 hours). How do I check if this is the latest?
Try running against the latest JBossAS 4.0.4.GA.
Or look hiw this diff's from last EJB3 embeddable.
I was worried for a second since it was not present in the 4.0.4 all release, but I found it in the ejb3 release... I hope it works on jboss-4.0.3SP1 all...
Thanx for the info, but after a brainstorm the mbean must be "general" mbean which has made me create a "regular" mbean and discovering other problems: