> There's no reason I can think of that the field-metadata tag shouldn't use > this mechanism, but it may not currently. >
Something may be a little funny with the field-metadata tag, or maybe with the form tag itself; I'm not sure. What I see is that there seems to be some sort of namespace collision problem between attribute names on my tags and names somewhere in a relevant contextual domain. For example, if I create a custom tag with an attribute called "name", then when I get to the call to the field-metadata tag in that form there's a NullPointerException thrown from inside the PropertyExpressionEvaluation class (not clear to me why due to my general cluelessness about how the code works). If, however, I alter my tag in no way other than to change its attribute name to "banana" (also changing the invocation of my tag in my form, of course), then the page runs just fine. I'll attach the stacktrace. I don't think I'm smart enough to be doing anything exotic on my pages. Maybe the namespace collisions I'm seeing are part of everyday life with tag file libraries; I've only done a few of those. -- Turtle, turtle, on the ground, Pink and shiny, turn around.
exception
Description: Binary data
------------------------------------------------------------------------- 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
