no package javax.ejb
Attempting to compile a session bean from the command line interface javac.
<y path includes a reference to c:\;c:\Program Files\Java\jdk1.5.0\bin;C:\Sun\AppServer\bin
I am running on Windows XP.
I am getting an error message package javax.ejb does not exist.
There was a step jar xvf src.jar with 1.4.0 to install the library source and documentation. I am guessing I missed a comparable step for 1.5.0.
Control panel indicates the following items are installed:J2SE Development kit 5.0, J2SE Runtime Environment 5.0, Java 2 Platform Enterprise Edition 1.4 SDK, Java 2 Runtime environment SE V1.4.1_07, Java 2 SDK Standard Edition v.1.3.1.
Would appreciate suggestions on addressing the exception.>
[750 byte] By [
rgmiltona] at [2007-10-2 8:46:02]
The issue turned out to be that javac is not locating the file in the jar even when the jar is in the same directory. Locate the j2ee.jar file which on my computer is in the directory C:Sun\Appserver\lib, and from that directory execute the command jar -xvf j2ee.jar. This command extracts the contents of the jar.
My suspicion is that my version of javac has a bug in opening jar files which the various power tools avoid, ie only a newbie will have this problem.
> The issue turned out to be that javac is not locating
> the file in the jar even when the jar is in the same
> directory. Locate the j2ee.jar file which on my
> computer is in the directory C:Sun\Appserver\lib, and
> from that directory execute the command jar -xvf
> j2ee.jar. This command extracts the contents of the
> jar.
>
> My suspicion is that my version of javac has a bug in
> opening jar files which the various power tools
> avoid, ie only a newbie will have this problem.
javac is not supposed to find any new jar you place. atleast, it has never been a feature of the compiler.
you have the -cp option to add it to the classpath at compile time.
javac -cp "%CLASSPATH%;mypath\j2ee.jar" *
I concur that my fix was crude, but it served as a temporary work around while I gaining understanding about the use of jar files.Independent of your post, I figured this out and changed my classpath to point to the j2ee.jar which has got to be a more efficient way to hunt for these components.
Personally, I would prefer to avoid adding a classpath to every command line execution of javac.
Thanks for the feedback, I have been off doing other things and just noted your post.
