From what I know j2ee.jar is the one that contains these classes.
Can you run echo %CLASSPATH% in the same cmd window where you are able to reproduce the error and see it?
Also see this thread if it helps..
J2EE_HOME should point to the home dir (i.e. C:\j2sdkee1.3\) not a jar file.
thekashyap
Practically a Posting Shark
811 posts since Feb 2007
Reputation Points: 254
Solved Threads: 75
What was teh result of this -> " Can you run echo %CLASSPATH% in the same cmd window where you are able to reproduce the error and see it?"
thekashyap
Practically a Posting Shark
811 posts since Feb 2007
Reputation Points: 254
Solved Threads: 75
and i am running myproject in apache tomcat...not on dos prompt
Is the same classpath reported in cataline.out ?
If catalina.bat doesn't print the command it executes to start up, just add an echo in it before in ":execCmd" section just before execution.
If after this also the same classpath is reported there can't be anything else than the fact that none of the jar files in reported classpath contain javax classes ! So get the new ones. Or just reinstall your test machine from scratch if you have an image or something..
thekashyap
Practically a Posting Shark
811 posts since Feb 2007
Reputation Points: 254
Solved Threads: 75
Changing your web serv coz you're facing problems with CLASSPATH isn't the thing I would do but if you want please go ahead..
thekashyap
Practically a Posting Shark
811 posts since Feb 2007
Reputation Points: 254
Solved Threads: 75
You can't use EJBs in Tomcat as Tomcat is no EJB container.
Setting your classpath to include j2ee.jar (which is indeed the one you need, if you insist on using an ancient version of the spec) isn't going to do a thing to change that.
Not only wouldn't it work even if Tomcat picked it up because Tomcat can't run EJBs, but Tomcat is a sensible application and will set its own classpath in its startup script.
jwenting
duckman
8,392 posts since Nov 2004
Reputation Points: 1,662
Solved Threads: 337