Regards
KumarRaja
Regards
KumarRaja
Regards
KumarRaja
jboss-j2ee.jar
log4j.jar
xerces.jar
xml.jar
There is no specific reason for using 4.0.4 version. Since I'm just learning, I did not bother to have the latest version of AS. Do you suspect anything caused by older version.
jndiName=MyEJB/Facade,plugin=pool,service=EJB
jndiName=MyEJB/Facade,service=EJB
jndiName=local/Employee@17326134,plugin=cache,service=EJB
jndiName=local/Employee@17326134,plugin=pool,service=EJB
jndiName=local/Employee@17326134,service=EJB
module=MyEJB.jar,service=EjbModule
service=ClientDeployer
service=EARDeployer
service=EARDeployment,url='MyEJB.ear'
Regards
KumarRaja
By the way, EJB2.x is old too. You might want to start working with EJB3, but I'll leave that to you to decide depending on your technical requirements.
Regards
KumarRaja
Regards
KumarRaja
Kumar Raja wrote:Any help on this.
If this question needs to be moved to a different group, please advice how to do that.
Kumar Raja wrote:
I'm just curious to know, how far EJBs have travelled leaving 2.x behind (I mean literally in the practical world). To be honest with you, in our projects we are using ejbs 1.1 (I swear) and I assume this might be the case with many legacy projects.
Kumar Raja wrote:
Do you suggest it is not worthy, spending time in learning 2.x version, when 3.x is sweeping. I thought, it is only the way ejbs are coded, is different in 3.x from its earlier versions but soul remained the same.
Kumar Raja wrote:
Now coming to my problem. I was able to obtain the home reference of Session bean, but when I invoke create method on home interface, boom.... I'm getting an exception, which I never recollect of seeing before.
JaiKiran
A bit of patience is all that's required
Regards
KumarRaja
And then the entire population worshiped me like unto a god. Well, me and this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
|