I think the problem here is Matt's change to make the name in AbstractUITag be a java.lang.Object and have the getName() method return an Object rather than a String. The problem is that when you have the getter and setter with different types, the javabeans framework gets confused about the type of the property you're trying to set. I'm not sure of the intention behind this, so I'm going to leave this one for you, Matt :-)
Ack! It looks like I should use Tomcat for compat testing :) My intent in changing the String types to Object was to allow users to pass in complex types into a Remote object. For example, it would be nice to call
<ui:component value="foo[0]" template="..."/>
and have foo[0] be a non-String value. I'll make sure to check fix this tonight.
-- Matt Ho Principal Indigo Egg, Inc.
------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
