Andy, that's it. I am trapping the Java exceptions again. Thanks again for
looking into this so quickly.
On Feb 5, 2010 6:16am, Andy Wu <[email protected]> wrote:
That's it fixed now.
Andy
Andy Wu wrote:
Hi Jeff,
Sounds like you may have found another bug. Leave it with me and I'll
fix it asap.
Thanks for the feedback. Much appreciated.
Andy
J.Lucido wrote:
I think I may have discovered another gotcha with the new cfscript
parser. Specifically, the issue occurs when I declare an error type in
my catch statement that contains a period. Example:
try {
(some code that errors out)
} catch (typewith.dot excpt) {
(handle catch of type 'typewith.dot')
}
This issue popped after the cfscript re-write since it used to work
prior to the overhaul. The reason for the dot notation in the error
type is directly related to catching a custom Java exception class.
The Java class we are using has it's own exclusive error exception
class that contains an error code that we need (multiple types in fact
that are named using the '.' notation). The ability to get the unique
Java exception class was something Alan added in early January (ticket
#187).
Thanks again for the great work and super quick response times.
Kind regards,
-Jeff Lucido
--
Open BlueDragon Public Mailing List
http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon
mailing list - http://groups.google.com/group/openbd?hl=en
!! save a network - please trim replies before posting !!
--
Open BlueDragon Public Mailing List
http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon
mailing list - http://groups.google.com/group/openbd?hl=en
!! save a network - please trim replies before posting !!
