Mailing-List: contact user-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Message-ID;
  b=etv/fUsQjebqLf/JUC1NkW12T0lACdacC/t6h5r385ThVJGxnSzL7OGD/3mHZnVji6VNTPU3YbIiB0Yc5/g31Ssga1mkLYWQQElLRIhyhWo0ARZKSRhikKScQCu0MZwv7Ohe0Brod6qlTFqmMnDc4MZaGGJbmYuKWetTeq2mHkY=;
Date: Wed, 16 Jul 2008 06:39:41 -0700 (PDT)
From: Dave Newton <newton.dave@yahoo.com>
Reply-To: newton.dave@yahoo.com
Subject: Re: 'include' struts.xml stuff is broken?
To: Struts Users Mailing List <user@struts.apache.org>
In-Reply-To: <Pine.LNX.4.62.0807160850240.2291@boomer.homeport.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Message-ID: <499578.93617.qm@web56707.mail.re3.yahoo.com>

--- On Wed, 7/16/08, Dave Belfer-Shevett <dbs@homeport.org> wrote:
> And was completely unmentioned in the document I was looking at:

Sorry we didn't put it where you looked. In general I usually recommend looking at core documentation in addition to FAQs, it provides context for the more free-form, supplementary nature of FAQs.

I've changed the FAQ entry [1] to point to the core documentation. (Note that changes are not immediately visible.)

> That FAQ should have had a link along the lines of
> "Full documentation for include is [here...].

Feel free to file a CLA and contribute to the documentation or file JIRA issues against existing documentation; input and contributions are helpful and appreciated (even more so without sniping and implied obligation :)

> What neither document mentions is how to configure both the
> top level struts.xml and the secondary files to avoid duplicating
> entire interceptor stacks using packages.

You lost me there; once an element (interceptor, stack, whatever) is defined it's available to subsequent elements. The <package...> documentation [2] describes the use of the "extends" attribute and states:

"The extends attribute is optional and allows one package to inherit the configuration of one or more previous packages - including all interceptor, interceptor-stack, and action configurations."

Dave

[1] Breaking up config files FAQ entry:
http://struts.apache.org/2.x/docs/can-we-break-up-a-large-strutsxml-file-into-smaller-pieces.html

[2] <package...> documentation:
http://struts.apache.org/2.x/docs/package-configuration.html


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org