Paul Worrall wrote:
Hi,
Can you tell me if ${servername} in the list of locations for the
property initializer refers to the domain names used in the URL. I was
hoping to have a number of web addresses with their own content
configuration served by the same webapp instance.
Or is it resolved once when the webapps loads and ${servername} is the
primary servername of the server.
Therefore does it mean I have to have a webapp per instance of
Magnolia for each web site
he property initializer just being something that reduces the need to
have more than one source tree.
:-)
Hello Paul!
I am not sure if I got your point, but I will try to answer my solution
for it.
I have one magnolia war used for both public and admin instance. I have
configured
property initializer to have two repositories under
/repositories/public/*, /repositories/admin/*
You have to change paths used during bootstrap to actually use two
different configs!
One war deployed (under name magnolia), than two different application
names (admin and public) in
Tomcat conf. When loaded, proper magnolia instance name is passed to
property initializer
and properly bootstrap the admin and the public apps into their
respective directory under
repositories.
After that you can use Apache in the front of it and map it as you wish
but still having only
one war. The problem I run into, was the app name configured in tomcat
conf. The conf I
was using didn't want to respect given app name, but instead was using
dir name of the path given.
I created symbolic links from admin, public to this magnolia war and it
worked quite good.
I actually don't know if this is good approach at all, maybe some full
time magnolias could say
something about this. ;)
Cheers
Zoran
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
