I applied this change, but changed the "instantiation" part of the error message to "initialization", since that's really where it could throw an exception. The instantiation is done further down.
Jason > -----Original Message----- > From: Jordan Harrison [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 25, 2003 12:24 PM > To: [EMAIL PROTECTED] > Subject: [OS-webwork] Suggested change to the > JavaActionFactory exception reporting > > > Hey Guys, > > I have a suggested change to the JavaActionFactory if > possible. I have been pulling my hair out trying to work out > why Webwork cannot load my class only to find it WAS being > found, just not instantiated due to an error. > > The JavaActionFactory currently only catches a generic > Exception while trying to load the Action class. So if there > is (for example) an exception being thrown in the Action's > constructor all that is reported is the Action not being found. > > I have simply added to the thrown IllegalArgumentException so > people don't sit there all day wondering why their class > can't be found (see attached java file line 62). > > It would be appreciated if someone will accept this tiny alteration. > > Thanks a lot, > Jordan > > > > ------------------------------------------------------- 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
