I was able to finally get this to work, but only after I added the @Depends
annotation like Klaus did before. I'm not sure why my case works and his
doesn't.
Anyway, here's the start of the MBean that now works.
| @Service(objectName="chief:service=InvoiceFileService")
| @Management(InvoiceFileService.class)
| public class InvoiceFileServiceMBean implements InvoiceFileService {
|
@Depends("jboss.j2ee:ear=chief.ear,jar=business.ejb3,name=InvoiceFileHistoryFinderBean,service=EJB3")
| @EJB InvoiceFileHistoryFinder invoiceFileHistoryFinder;
|
I had to do something similar for all @EJB within each MBean in my project.
The error I received before this was that InvoiceFileService was not known. I
did see where it was registering later in the deployment, so adding the
@Depends annotation makes sense. However, this wasn't a problem in RC3 so I'm
not sure what changed. All of these classes are in the same EAR (and EJB3
archive within that) so I'm not sure why the depolyment order matters all of
the sudden.
I'd like to know if this is the way things must be done from now on or if
there's a better way. I'm guessing the latter is true.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922995#3922995
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922995
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
