On a whim, I tried making a little tag in a toy application. The point of
the tag was to factor out a small but ugly blob of code involving the
field-metadata tag. Basically I wanted to package up the boilerplate
javascript I want to call.
Well the tag "worked" in that Resin found it and used it, but the
field-metadata tag was confused because it didn't know the action bean. I
didn't play with it much after that but my guess was that the tag is
processed kind-of like a jsp:include is processed - it's like a separate
page. Therefore, the contextual stripes:form object is nowhere to be found.
For this particular situation is no big deal, but I'm wondering what the
story might be should it become attractive to package up some common
patterns in tags, when those patterns involve stuff inside forms. I'm
guessing that other form-related tags might get kind-of nervous outside of
forms too. Is there a commonly-used trick to make that doable?
--
Turtle, turtle, on the ground,
Pink and shiny, turn around.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
