On Wed, 16 Jul 2008, Dave Newton wrote:
--- On Tue, 7/15/08, Dave Belfer-Shevett <[EMAIL PROTECTED]> wrote:
[...] the documentation page for this, naturally, provides
no examples of what the include file should look like.

"Naturally?"

Sniping aside: the "include" documentation [1] states the following:

"Each included file must be in the same format as struts.xml, including the DOCTYPE. The 
include files can be placed anywhere on the classpath and should be referred to by that path by the 
"file" attribute."

To me that implies a well-formed, complete S2 config file.

And was completely unmentioned in the document I was looking at:
http://struts.apache.org/2.x/docs/can-we-break-up-a-large-strutsxml-file-into-smaller-pieces.html

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

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. 1-2 lines referring to other bits of information would have been enormously helpful.

I did finally get it working, using an <include> in struts.xml, and in the included struts.xml, added dtd, a new package definition, and an 'extends=' reference to the parent package.


--
-------------------.--------.-------------------------------.
Dave Belfer-Shevett \ KB1FWR \ JID: [EMAIL PROTECTED] \
blog:planet-geek.com >--------'-----------------------------------.
[EMAIL PROTECTED]    /   Windows98 Err#021 - Error Parsing Error    \
-------------------<        List; Please Wait For Next Error        |
                    \______________________________________________/

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

Reply via email to