RE: [ismicro-commons] Proximity: possible to have config files outsideof WEB-INF?

[Jeff Jensen <je...@upstairstechnology.com>]

Thank you very much for a prompt reply and solution!  :-)  Very much
appreciated.  I wasn't sure if there was some type of property I hadn't seen
yet to allow doing so.

Do you have any thoughts on enhancing the configuration to allow config
files outside of web-inf without the spec violation?  It's really great when
one can just install the war (especially with new releases) and it picks up
existing config files elsewhere, not touching any files in WAR.

Most of the time, this means a system property so users can define on the
container.

With the solution you sent, we still have to update the
applicationContext.xml file in the war, so it is a tradeoff of remaining the
same as the original release structure and copying over the two edited files
from SCM workspace vs non-release structure and copying one file.  I'm
leaning towards just copying over the two edited each time to remain as
release-standard as possible.

WDYT?

(even though I am narrowing on a small configuration issue to facilitate
reproducibility and ongoing updates, the setup and config of Proximity was
very easy and trouble free :-).


-----Original Message-----
From: ismicro-commons-bounces@is-micro.myip.hu
[mailto:ismicro-commons-bounces@is-micro.myip.hu] On Behalf Of Cservenak
Tamas
Sent: Friday, May 26, 2006 5:52 AM
To: ISmicro Common Components; Maven Users List
Subject: Re: [ismicro-commons] Proximity: possible to have config files
outsideof WEB-INF?

Hi Jeff,

first of all, i would like to ask you to continue this debate on Maven
Users List <us...@maven.apache.org>, since this mailing list is hosted
on "site" (my machine) with very lousy (adsl) uplink and is not meant to
be public :) It is my mistake that on Proximity site I listed this
mailing list.


Well, your question regards mere the J2EE webapp then Proximity itself.
It is possible what you asking, but this way you will VIOLATE the J2EE
guidelines. Nevertheless, as long as you use some "relaxed" container
(eg. Tomcat and not JBoss) everything should be fine (i think, never
tested it actually).

Since in web.xml you cannot reference file outside the webapp root, you
should create a Spring "stub" application context, which will in turn
include the "real" application context. Since this configuration is done
by Spring, not the servlet container it would be possible to achieve it.

I modelled this by placing files in my $HOME/tmp. Files attached.

Steps to achieve this:

1. Move /WEB-INF/applicationContext.xml to where you want and rename it
to proximity.xml (in my case $HOME/tmp)
2. Move /WEB-INF/proximity.properties to be beside proximity.xml (in my
case $HOME/tmp)
3. Set up both files as you want, use SCM on it etc.
4. I attached a Spring "stub" context, drop it in
/WEB-INF/applicationContext.xml REPLACING the original one.
5. Configure the stub to point where your proximity.xml is.

And that's it!

The bad thing about this config is that in case of path modification you
have TWO places to update: one in /WEB-INF/applicationContext.xml "stub"
and one in proximity.xml. But since you have "taken-out" the config from
webapp, you could simply drop the proximity properties file, replace and
maintain the proximity.xml file only by inserting values directly and
remove the "propertyConfigurer" bean from proximity.xml. The properties
file in this case is not a benefit.

Have fun
cstamas



Jeff Jensen wrote:
> Hi,
>
> Since we source control product config files, it is much easier for us
when
> we can configure products to point to their config files in our desired
> location (i.e. into a dir in the SCM's workspace).
>
> So far with Proximity, we have changed settings in proximity.properties
and
> applicationContext.xml.
>
> Not sure of all settings yet - is it possible to customize Proximity to
load
> those files from a specified location instead of always from web-inf?
>
> _______________________________________________
> ismicro-commons mailing list
> ismicro-commons@is-micro.myip.hu
> http://mail.is-micro.hu/mailman/listinfo/ismicro-commons
>   



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org