On Fri, Aug 26, 2005 at 11:47:54PM -0700, Patrick Lacson wrote:
: jdbc config options, common file system info, http urls for external
: sites, things of that nature.  we have a complex multitenant system
: that needs to be configured by our sysadmins.

What about having separate config files that can be compiled into the
WAR at build time?  A little Ant magic, a few replacement rules, and
you're in business.  Your sysadmins will (hopefully) like that more
because there would be less for them to do.


: currently we are hosting it on tomcat and later possibly websphere.  i
: was wondering if there was a way to do this portably.

"Portability" is a broad term; you must decide the direction and depth
of your portability and go from there.  For example: using an external
file means you have to specify an absolute path.  That's portable
between containers but not OS flavors.


: how about reading comments from an external url?  has this been done before?

URL is also an option, silly me for not having mentioned it.  -but
again, your app has to somehow bootstrap this information, which means
you must include the URL in your app at build time.  Furthermore, the
service that responds to the URL call must be available at all times or
your webapps won't start. =)

You could get creative with the URL bit: include the context name as a
parameter, let the remote service analyze the incoming IP address,
etc... but that would require some serious planning and design such that
you don't end up with a nightmare long-term.

Using an exploded-dir format webapp would require the least work on your
part.  While it's not techically required by the spec (only WAR files
are required, when I last checked), I'd doubt there are any containers
that don't support it.

Pick your poison.

-QM

-- 

software   -- http://www.brandxdev.net/
tech news  -- http://www.RoarNetworX.com/
code scan  -- http://www.JxRef.org/


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to