What next with VAJ

[Dharmesh Chheda]

Hello everyone
i have developed a simple EJB using VAJ and tested it using a servlet and WebSphere Test Environment.. its working fine there
Can you now help me how to deploy it on WebSphere 4.0 .
In VAJ it gives me three options ..
1> Client jar
2> EJB JAR
3> Deployed JAR
which one to use .. its a stateless session bean .. which is accessed by a servlet
bye and thanks in advance
Dharmesh Chheda

[Kyle Brown]

You're not using VAJ 4.0, are you?
Kyle

[Dharmesh Chheda]

hello kyle
i am using VAJ 3.5.3 .. can you help me with the query i have

[Paresh Sharma]

You need to use VAJ 4.0 for deploying your bean onto WAS 4.0. The deployed code generated from VAj 4.0 will have the required xml files as required by WAS 4.0.
Paresh

[Dharmesh Chheda]

Thanks for giving me the information Paresh
but since i dont have VAJ 4.0 what shall i do .. there has to be some alternative
bye and thanks in advance
Dharmesh Chheda

[Paresh Sharma]

Either WSAD 4.0 or VAJ 4.0 have to be used to generate the code.
The other way might be to generate the deployed code from AAT in WAS 4.0 and use VAJ 3.5.
However this approach would not be applicable for entity beans as AAT would generate a top down approach mapping.
Paresh

[Malli Raman]

hi Dharmesh Chheda,
In WAS3.5, EJBContainer will contain all the Enterprise Beans. To deploy use DeployedJar option in the VAJ
1.because the Deployed Jar will contain all the stub and skeleton information(Deployment Descriptor information).
2.Client Jar is used for to access the ejb in the client side, for that we need the clientJar in the classpath.
3.EJB jar will contain only the EJB Classes(ie remote interface, home interface and bean class)
Regards,
M.S.Raman.
p.s.:
1. I hope that u already configured websphere3.5 with database (DB2).
2. If you want to use WAS4.0 use EJBJar option in VAJ with AAT.