Thanks for you reply. To be safe, I will replace the jar.
Later on, I noticed this entry in server.log:
[quote]A bundle with the same symbolic name
(org.glassfish.web.weld-integration) and version (3.1.1) is already
installed. Updating this bundle instead.[/quote]
This suggests GlassFish replaces the /modules jar by the customized deployed
jar and suggests to support updating existing module jars.
Another thought, when replacing the jar in /modules you also have to remove
the dir /osgi-cache in the domain dir. So I wonder if GlassFish ever uses the
jars in /modules when /osgi-cache is created . Does it ever check for renewed
jars in /modules to refresh the osgi-cache? If not, it would be safe to
deploy instead of replace.
Nevertheless, like I said, I will replace the jar.
It would be stupid to run into problems at production servers because of
this.
--
[Message sent by forum member 'dj_canard']
View Post: http://forums.java.net/node/869180