Simple question with no helpful responses so far.
I must therefore conclude either a)Noone uses tiles because they are broken b)Noone understands tiles c)The way I am proposing to use tiles is so dramatically wrong at a design level that noone has a clue what I am asking.
or d) members of this list are people who have things to do, so sometimes they don't read every message or devote time to answering every question.
Tiles are certainly not broken; lots of people use them all the time, and even use them without using Struts. As for whether or not they understand what they're using... you've got me.
Unfortunately while the form action gets correctly rendered with the right action passed from the jsp that uses the layout, the checkbox rendering fails with the message "Cannot find bean org.apache.struts.taglib.html.BEAN in any scope". As far as I understand this means the html form tag is not being put in scope for the checkbox to find.
Actually, this means that the checkbox tag is not finding the form bean, not the form tag. The form bean object is looked up according to the action mapping associated with the value of the form tag's "action" attribute, and the object is placed into request scope, explicitly so that it would be available to other JSP fragments besides the one in which the opening form tag is invoked. If it is not found, an error is thrown by the form tag before the checkbox tag is ever executed.
Have you ensured that this works in the simplest case, where you have a single JSP rather than tiles? If so, then we'd need more to go on - in theory, this is something which can be done. I've worked on applications which include form fragments using jsp:include, which should be similar enough for these purposes. I can't think of any offhand which use tiles instead.
At 4:20 PM -0500 11/30/04, Bill Siggelkow wrote:
I don't think it is possible to "split" a form across multiple Tiles because the Tile is a complete (translated) response. A form must be complete on a Tile.
I don't think this is true. If you look at the TilesRequestProcessor's implementation of doForward, it checks to see if the response has been committed yet, and if it has, then it uses requestDispatcher.include(...), which should mean that the tiles all have access to the same request scope.
http://svn.apache.org/viewcvs.cgi/struts/core/trunk/src/share/org/apache/struts/tiles/TilesRequestProcessor.java?view=markup
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com
"Narrow minds are weapons made for mass destruction" -The Ex
