Kedar,
I understand and am very grateful that the glassfish team is working hard on a great number of things and I didn't really expect this to be a top priority so I definitely don't want you guys to think I'm complaining.
If I understand your reply, I think you're asking "is there no other way I can point to these property files without passing java args." If that is your question let me explain what we're doing and maybe there is an alternative way.
Basically the scenario is we have property files that the application has to find on startup. They define aspects in the application as well as settings for things like location for log files in log4j and in a cluster of 4 instances, maybe only the first one will run jobs and has job manager settings. So we need some way of telling the application where this property file exists for each instance. Right now we're using a Java properties via -D java args.
We could use an environment variable or java arg.. we just need some way to access where we put this file from the application.
I talked to one of our developers and we can continue to test clustering by making a special build that includes the property file in the application. But ultimately for dev / qa / production use we'd need for this to be dynamic.
Outside of this functionality, I don't think there's anything else we need to use Glassfish as a solution. I'm eager to test and really would like to supplement Jboss with Glassfish where possible.
90% of the reason I'm looking at Glassfish is because the ease of administration, because we don't have java developers deploying these applications in production. Often we have people deploying into production with a more narrow scope of knowledge which is why I was wondering if the feature could be added via the admin console as well.
I hope this answers your question. If not please let me know and I'll do my best to clarify better.
Thanks Much,
Andrew
[Message sent by forum member 'areplogle' (areplogle)]
http://forums.java.net/jive/thread.jspa?messageID=203494