On Tue, 10 Dec 2002 17:05, you wrote: > Rodney Schneider wrote: > > Would it be possible for you to either supply a patch or at least > > log an issue in Scarab for this problem? > > I can certainly file bug reports. Posting patches will need me to get > motivated ;-) I had to get setup so I could hook a debugger into > Turbine to get Intake figured out (that shows how much room for > improvement there is!) so tracking down poor error reporting should > be relatively easy. I'll try and put some patches together.
Just for interest sake, what debugger are you using? > > I have always used (note the capitals). This > > should be mentioned in the Intake Howto. > > A note in the howto would be a good interim measure. Not munging the > names the user specifies would be better :-) I think the names must be javabean compliant for the reflection to work, so I am pretty sure they need to be munged... > > TurbineException for you to retrieve its nested exception so you > > can log a decent error message. > > You might want to look at using commons-lang's ChainedException (I > think that's right) NestedException :) > rather the re-inventing it ;-) My prefered style > is generally to define a ChainedExceptionInterface and > ChainedExceptionHelper; that lets me extend existing exception > classes where appropriate, and include chaining functionality on > every exception :) Yeah, that is what the TurbineException class in the Turbine 3 repository does, and I am pretty sure it will make it into the Turbine 2.x repository eventually. Regards, -- Rodney -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
