Jordi,
You mentioned that you are using Java Web Start. Are you using the built-in
support for Java Web Start?
I have two suggestions:
1. Try deploying your EAR as follows:
asadmin deploy --retrieve localdir *photogallery_app-1.0.ear*
Then try launching your appclient using
appclient -jar localdir/photogallery_app-1.0Client.jar
and see if that reports any errors.
2. In GlassFish 2.x the contents of any EJB JAR was made accessible to all
app clients from the same EAR. The Java EE 6 spec - of which GlassFish 3.x
is an implementation - mandates stricter rules about what JARs in the EAR are
accessible to other modules, including app clients. The spec now requires a
module such as your app client to explicitly declare a dependency on (in this
case) the EJB JAR by listing it in your app client JAR's manifest
Class-Path.
Having said that, you can also try deploying the application using
asadmin deploy ... --property /compatibility/=v2 photogallery_app-1.0.ear
This should allow your app client to see the EJB JAR contents automatically,
as in GlassFish v2. Keep in mind, though, that your app is not compaible,
strictly speaking, with Java EE 6.
- Tim
--
[Message sent by forum member 'tjquinn']
View Post: http://forums.java.net/node/800112