Yep - I added some code about a week ago to include cfcatch.detail in the nested exceptions but it was after the 1.0 rc1 tag. If you pull the latest from CVS you'll have it, otherwise it will be in the release. See here:
http://code.coldspringframework.org:9010/changelog/Coldspring2/?cs=MAIN:rossd:20060606124138 (I know you are behind a corporate firewall and can't get to this - but the changes are essentially the same). regardless, thanks! On 6/15/06, Dave Carabetta <[EMAIL PROTECTED]> wrote:
I've been using the CS 1.0 RC in conjunction with Model-Glue:Unity, and I ran into a situation where the DefaultXmlBeanFactory class threw an exception running the code between lines 499 and 541 of the constructBean() function, but the message was vague. The only way to really figure out what the problem was was to comment out the try/catch that surrounds that snippet. What I'm asking is whether or not it might be useful to add the cfcatch.detail to the "detail" attribute rather than having to come in and comment out the try/catch? "Bean creation exception during init() of #beanDef.getBeanClass()#" doesn't really give me the information I need to figure out what's going on. I wound up going in and changing the detail attribute of the cfthrow to read: detail="#cfcatch.message# #cfcatch.detail#" and I found that much more useful. The reason why I post this here is because I hate modifying the framework core files and thought that maybe adding this into the code base for future versions might be a useful enhancement. On the other hand, I might have just "gotten lucky" as far as seeing that the cfcatch.detail was more useful. Regards, Dave.
