Correct, many jar file names used in v2 are not applicable to v3 due to
a major change in product architecture so if you are following
instructions which assume that GlassFish v2 is being used, you will need
to adjust them to v3 file layout and content. FWIW,
glassfish/lib/javaee.jar and glassfish/lib/appserv-rt.jar in v3 are
provided as "wrapper" jars which contain references to all other v3 jars
you are expected to need. So, you could try using those jars in your
classpath.
glassfish_at_javadesktop.org wrote:
> Many thanks Snjezana for clarifying this. Actually I was trying out Ejb 3 in Action code samples. And it required toplink jar file. It mentioned in the build.xml file that it would be in <root>/lib folder, where I was not able to find. Hence the whole doubt raised in my mind. I can see a number of jar files in the modules folder as suggested by you. I can still not find the toplink jars but I observed javax.ejb and and jpa jar files in modules folder. Hence I assume in glassfish v3 there won't be any toplink file but rather jpa files.
>
> Thanks again.
> [Message sent by forum member 'arifsbs']
>
> http://forums.java.net/jive/thread.jspa?messageID=480478
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
--
Oracle <http://www.oracle.com>
Snjezana Sevo-Zenzerovic
Green Oracle <http://www.oracle.com/commitment> Oracle is committed to
developing practices and products that help protect the environment