Thanks Tim for your express reponse. sorry for not replying sooner.
I ve seen that the issue 2297 has been fixed, that's good news!
Concerning the incorrect login error handling, that's ok, we can live with it for the moment.
However, we are now really worried about the heavy ACC footprint concerning our project. Doing further investigations during our prototype, we found out that the ACC weights 39M on the client! That's too much just for a simple swing app calling a few ejbs, since some of our users have only a 128k bandwith to our servers.
We found that the acc includes a big bundle of jars: derbyclient.jar, webservices-rt.jar mail.jar etc, most of which we dont need for our app.
So, my question is there a way now to customize the acc to include just the minimal jars i need for a particular app, and by extension can we derive our custom jnlp from the one it is automatically generated by glassfish to fit our needs, and if possible how?
If not, I concluded that we should use instead a standalone client with a manual jnlp deployment instead using the ACC and auto JWS for now because of these limitations, so tell me i'm wrong ;).
Yves.
[Message sent by forum member 'ygillet' (ygillet)]
http://forums.java.net/jive/thread.jspa?messageID=209130