You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by "Prasad, Kamakshya" <kp...@capitalservicing.co.jp> on 2004/05/03 08:24:59 UTC
RE: Split web.xml into multiple files
Hi,
We are using the container managed security and we have lot of action
mapping and roles. Specifying them in one web.xml making it too huge. We
want it to split into separate logical files
KP
-----Original Message-----
From: Bill Siggelkow [mailto:billsigg@bellsouth.net]
Sent: Friday, April 30, 2004 10:20 PM
To: user@struts.apache.org
Subject: Re: Split web.xml into multiple files
Prasad, Kamakshya wrote:
> Hi,
>
> Is it possible to split web.xml into multiple files?
>
> KP
>
AFAIK the web.xml cannot be split. Most containers, however, do utilize
a container-specific web app deployment descriptor that works with the
web.xml. The web.xml for a Struts-based application should be
relatively small and should not need to be frequently modified. Why do
you want/need to split the web.xml?
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Split web.xml into multiple files
Posted by Craig McClanahan <cr...@apache.org>.
Prasad, Kamakshya wrote:
>Hi,
>
>We are using the container managed security and we have lot of action
>mapping and roles. Specifying them in one web.xml making it too huge. We
>want it to split into separate logical files
>
>
>
If your container is reasonably intelligent about parsing XML documents
using entities that refer to files in the same directory, this should be
no problem using XML entities for this sort of thing. Check the Struts
documentation, Wiki, and mailing list archives for discussions of
dividing up a struts-config.xml file -- exactly the same techniques will
generally work for web.xml as well.
On the other hand, it makes a *lot* more sense to me to create a build
environment that dynamically combines all the stuff you need into a
single web.xml file, to be included in the deployable WAR file, as part
of the build process.
>KP
>
>
>
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org