Help for deploying EJB on WAS 4.0

[Dharmesh Chheda]

Hello guys
I have a problem as mentioned in the subject .. i have written a stateless session bean using VAJ 3.5.3
The code works perfectly fine as i tested it in the WebSphere test environment. I tested by writing a servlet accessing the enterprise bean and the results were as required.
I exported the Client jar for deployment onto WAS 4.0
I did the following steps
1> I first created an EJB module and specified all that is required.. i mean the JNDI name, the home interface and stuff.
2> I then created a web module for my servlets which will be accessing me enterprise beans present in the EJB Module.
3>i created an enterprise application and bundled the EJB module and web module created in the first two steps.
ALL OF THE ABOVE WAS DONE USING AAT
i hope till here its clear..
*******************************************
before i proceed let me tell you that while using VAJ i specified the package name as
com.wiley.compBooks.roman.session.helloworld
**********************************************
When i use the wizard ( in WAS 4.0 ) Install Enterprise Application.. and when i come to the last step i.e. to generate deployed code. i get the following error
-------------------------------------------------
Failed to deploy file.
ejbModule/com/wiley/compBooks/roman/session/helloworld/EJSStatelessHelloWorldHomeBean.java(-1): This compilation unit indirectly references the missing type com.wiley.compBooks.roman.session.helloworld.HelloWorld (typically some required class file is referencing a type outside the classpath)
--------------------------------------------------
Can anyone plese reply soon and help me with this problem.
bye and thanks in advance
Dharmesh Chheda

[Tom Stevns]

Hello Dharmesh !
You are not the same version version level
of VA-JAVA and WAS respectively, I would
strongly recommend You to be so.
Get the best Redbooks about EJB like:
WebSphere V3.5 Handbook SG24-6161-00

Start to use one of the samples from VA-JAVA
or maybe even better one from the handbook.
When you are familiar with the EJB-platform so far you can start with your own EJB deployment.

[Dharmesh Chheda]

hello tom

thanks or your reply..
but i am using WAS 4.0 .. somebody told me to use the Patch EJB 1.1 Export Tool ..is it correct?
and where will i get it ?

[Tom Stevns]

Helle Dharmesh
Maybe someone in IBM/Alphaworks can help -
Not too negative -
but I think you really have to reconcider your
platform including your primary developing goal.

[Paresh Sharma]

You should have all the dependent classes in the class path. Include the home and remote classes in a jar file and append it to the classpath when you are generating the code.
Paresh

[Kyle Brown]

Arrgggh... Dharmesh, what Tom is trying to tell you is that if you move to VAJ 4.0 (a free upgrade from 3.5.3 for registered users) that there is a special menu option called "Export EJB 1.1. JAR" that will automatically handle this problem for you. I agree with Tom -- upgrade your VAJ.
Kyle

[Dharmesh Chheda]

Thanks tom and kyle
hehe kyle i think you got p****d off .. hehehe anyways i am now trying to get the update but in case any of you guys have the URL ready .. please pass it on to me .
thanks and bye
Dharmesh Chheda

[whiteagle]

Hi there guys.
I have some very similar problem. But I was using WAS 4.0.2 from the beginning, just began a new application (some stupidities like xml2txt conversion and so on). Wrote enough, all worked perfectly. Suddenly electricity got down, the machine has rebooted (somebody told me UPS is a good thing.. will think about it..), I started WAS and got the next error on my package: "This compilation unit indirectly references the missing type com.sun.java.util.collections.List ..." and the same thing about classpath.
Point is that I don't use any Lists or whatever, just org.jdom and file.io, nothing more. And before the crush all worked.
Restart doesn't help now, work is stopped and my boss gonna kill me.
Can somebody explain what's happening ?
Thanks in advance.
Igor Antonoff.

[whiteagle]

I solved it.
Just reinstalled all classes used.
Thanks for attention.