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 (herse.apache.org: local policy)
From: Piero Sartini <lists@pierosartini.de>
To: "Struts Users Mailing List" <user@struts.apache.org>
Subject: Re: sub-struts
Date: Sun, 8 Apr 2007 02:12:33 +0200
User-Agent: KMail/1.9.6
References: <ef62ed050704071524h4c5e3df1w744cc792876ec1d4@mail.gmail.com>
 <200704080143.31399.lists@pierosartini.de>
 <ef62ed050704071701lb4de92eu13b19e577636eabc@mail.gmail.com>
In-Reply-To: <ef62ed050704071701lb4de92eu13b19e577636eabc@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200704080212.33405.lists@pierosartini.de>

On Sunday 08 April 2007 02:01:24 Asaf Paris Mandoki wrote:
> I forgot to say that the directory structure i wrote on my first post
> (which was wrong [forgot the web-inf directory]), should be inside a
> directory of the application. So each widget should have it's own
> "classes" directory, struts.xml, etc.
>
> The directory nesting is not necessary, but the widgets will work as
> children to the main application will be nested so it makes more sense
> to me.
>
> The objective is to have struts within struts.

Yes, I did understand that. Just did not understand why you would want that 
and tried to show other solutions that may solve your needs :-)

If you really want to make several struts2 applications and "compose" them 
somehow, you could use sitemesh to do so. But I think configuring and 
developing several stand-alone webapps is much more work than developing 
everything within one s2 application.

Piero

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