PS, have tried this with a combination of jdk1.4 / 1.5 and also jboss 3.2.5 +
4.0.2 / 3 and both different deployers.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919962#3919962
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=
Yep, this is a problem with current version of deployer.
You cannot get the bean from bean factory unless explicity injecting it in EJB
enterprise bean.
The reason for this is that the actual bean factory is really just a bean
factory implementation and NOT an application context (which is capabl
Aha, missed this one -- spring 1.2.6.
That's even better. I thought you were using version from when deployer was
first introduced.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919977#3919977
Reply to the post :
http://www.jboss.com/index.html?module=bb&o
Hi Ales,
Great! Thanks ,love your work!
I had a feeeling that that may be the case, is just hard to figure out exactly
what it should and shouldnt do docco at the moment and there dont seem to be to
omany ppl out there using it yet (not a heap of threads found on the issuce on
news groups etc)
Well, i wish all fixes could be that easy. with about 3 minutes of downlaoding
files, moving them to the server and redeploying by .spring archive, everything
is now working as expected. My MBean is now being instatiated at deploy time
and is visible and working from the jmx console.
All is wor
