|
Hil, all, I'm working with an
external applicaition (SPECjAppServer2004 Driver) that uses JNDI to access the
EJBs deployed in Geronimo 1.0. I have had to provide a
rather long classpath for that application to work normally, containing: ${GERONIMO}/bin/server.jar ${GERONIMO}/repository/org.apache.geronimo.specs/jars/geronimo-ejb_2.1_spec-1.0.jar ${GERONIMO}/repository/org.apache.geronimo.specs/jars/geronimo-j2ee-jacc_1.0_spec-1.0.jar ${GERONIMO}/repository/geronimo/jars/geronimo-security-1.0.jar ${GERONIMO}/repository/openejb/jars/openejb-core-2.0.jar I wonder if there is a
smarter way to provide an external application with a reasonable classpath.
Maybe some manifest-only jar exists for that purpose, or something. Any good news on that? :) Vasily Zakharov Intel Middleware Products
Division
|
- Classpath for an external application Zakharov, Vasily M
- Re: Classpath for an external application John Sisson
- RE: Classpath for an external application Zakharov, Vasily M
