> The property binding engine tries to make that call reflectively. Really it > should check to see if such a constructor exists before just calling it and > then spitting out an exception. Some things were changed in > this area between 1.4.3 and 1.5, I'm not sure if all were for the better, > or at least done with the proper supporting code to handle such corner cases.
Not sure what's going on here, but for what it's work, the property binding engine /does/ check the existence of the Constructor(String) before trying to call it, and has been that way since 1.4.3 or earlier. The type converter is null as per the logs.. I would put Stripes in debug mode and check all the traces for more information on what's happening. Cheers, Freddy ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
