Rodney Schneider wrote:
Just for interest sake, what debugger are you using?
I'm using Intelli/J IDEA's built in debugger right now.
I think the names must be javabean compliant for the reflection to work, so I am pretty sure they need to be munged...
For JavaBeans, properties are generally considered to be lower case; the accessors are then upper-cased. So the property name (which is what the values in intake.xml map to) would be 'name' not 'Name'. But it depends on who's introspection semantics you're using ;-) You could always munge at the point the reflection is performed so that the munging isn't visible to the user when referencing properties.
NestedException :)
Right, I knew it was something like that :)
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.
Of course the danger of nestable exceptions is that they end up used as crutches to avoid doing real error handling and recovery... ;-)
L.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
