Hello,
currently, we want to build a remote application which uses the application client container to inject JMS resources (ConnectionFactory and Queue) to access the application server (GF V2ur2). I have got some question related to this scenario:
1. Besides the HTTP port for the JavaWS JNLP download, which ports I have to keep open in the firewall?
2. How large is the footprint of the ACC files?
3. I know that the JavaWS caches the downloaded JARs. But: If my app changes but the ACC JAR files stay the same, are they downloaded again?
Alternative way:
I could use a version 2.5 servlet with inject JMS objects and let it return the serialized JMS objects to the client. Will this work or will the server optimize for local (EMBED type) access so that the JMS objects are not serializable and/or not usable in the client.
Thanks in advance for any comments/solutions!
Jörg
[Message sent by forum member 'jthoennes' (jthoennes)]
http://forums.java.net/jive/thread.jspa?messageID=278867