anonymous wrote : QueueExecuterBean which holds the reference to QueueRunner
should be started AS SOON AS the application is deployed.
@PostConstruct will not be called when the application is deployed. What you
are trying to do, can be achieved through JBoss specific @Service
As for the exit() not being called:
https://jira.jboss.org/jira/browse/EJBTHREE-1496
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4177976#4177976
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4177976
@jakiran: I already tried the @Service extension for EJB 3.0 in JBoss but it
didn't work out properly.
@wolfc: Will this bug be fixed in the next release of JBoss?
As such, I am open to any other design solution to this problem. I am not
saying that my @PostConstruct/@PreDestroy solution
aojensen wrote : @jakiran: I already tried the @Service extension for EJB 3.0
in JBoss but it didn't work out properly.
|
When you say, it doesn't work, what exactly happens? Any exceptions?
aojensen wrote :
| I am developing a simple mail daemon/service) that looks up new entries in
a
