DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12201>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12201 Problme defining values for type element in attributes of custom actions [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2002-09-03 22:37 ------- Fixed. Problem occurred with *any* primitive type specified with the <type> subelement of the <attribute> element, not just with "boolean", because we were passing the type string to Class.forName() in order to determine an attribute's expected type. Of course, Class.forName() will fail for any primitive types. Added special treatment for primitive types, which determines the Class object for a primitive type by appending ".class" to the keyword of the primitive type (e.g., "boolean.class"). -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
