So why are you insisting on using JNDI? If you're carrying along a list of JARs, you might as well use ACC and injection. Much more elegant IMO.
And as I've previously stated, I think if you want a lightweight (MB-wise) client, you need to look at using a RESTful approach.
I'm not saying there is no issue with the size of the jars you need to carry along, simply that you need to make a pragmatic architectural choice here.
Also I've got to ask, if your users have JavaFX installed, couldn't they also have the required GlassFish JARs there also?
-Alexis
On 8 nov. 2010, at 16:34, noreply_at_java.net wrote:
> FAQ doesn't help. After an hour of hacking the minimal configuration of jars
> that must be downloaded to the client I gave up. Inability of creating a
> light-weight jar for the client is a serious flaw of GlassFish. I hope I'm
> wrong and there is a way to use JNDI from an applet...
>
>
>
>
> --
>
> [Message sent by forum member 'yfain']
>
> View Post: http://forums.java.net/node/713592
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>