If you are looking to keep e.g. foo.jar (containing
all the information like resources, classes, config
files etc.) that your application will look up
using ServletContext's getResource* methods, then,
you can keep it in:
<domain-folder>/lib/classes and it will be available
in the classpath of the domain, when it starts up.
This is by far the best location, because it will get
synchronized for all the instances that in the same
domain. This refers to the cluster environment.
Regards,
Kedar
glassfish_at_javadesktop.org wrote:
> Simply put, I have configuration data that is domain dependent (dev vs stage vs production) that I'd like to configure at the domain level, but outside of the EAR file (since I don't want to have to reassemble my EAR for each different domain).
>
> Is there any place that I can put this data that is accessible by both web apps and enterprise apps?
>
> About the only thing that I've found is to define a property on the Java start up that defines the full path to a property file that I can load.
>
> That works OK, but I was hoping for someplace that I could just drop a file in the domain directory tree that the app server just happens to "see" on its CLASSPATH.
>
> Any one have any suggestions? Is there a global place I put stuff in JNDI, perhaps?
>
> Kind of 6-to-1, 1/2 dozen to another, but I'd just like to know all of the options.
> [Message sent by forum member 'whartung' (whartung)]
>
> http://forums.java.net/jive/thread.jspa?messageID=211913
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>