Remoting nullPointerException for ALL Errors

Lucee is running well - I’m working on an Enterprise Flex project and
didn’t take long to move from ADCF.

Everything is now running as expected - the only issue I’m running into is
when an error is thrown - the only error returned to the flex client is
this nullPointerException. The actual error - in this case an error I
threw - is being logged in Tomcat’s stderr - then immediately after the
nullPointerException is thrown by lucee - and it’s this error that gets
returned to the remoting client.

I’ve logged this error:
https://bitbucket.org/lucee/lucee/issue/269/remoting-nullpointerexception-for-all

Also including the snap of the stderr and the debug dump from BlazeDS to
stdout

https://lh3.googleusercontent.com/-u9eyWo3CeQY/VSbYYzi4hAI/AAAAAAAAAAM/1uLDUY2uyqU/s1600/stderr-stdout_fault.png
Is there a way to stop Lucee from throwing this error? Or a way to catch
and send the original back to BlazeDS?

Lucee is running well - I’m working on an Enterprise Flex project and
didn’t take long to move from ADCF.

Everything is now running as expected - the only issue I’m running into is
when an error is thrown - the only error returned to the flex client is
this nullPointerException. The actual error - in this case an error I
threw - is being logged in Tomcat’s stderr - then immediately after the
nullPointerException is thrown by lucee - and it’s this error that gets
returned to the remoting client.

I’ve logged this error:
https://bitbucket.org/lucee/lucee/issue/269/remoting-nullpointerexception-for-all

Also including the snap of the stderr and the debug dump from BlazeDS to
stdout

https://lh3.googleusercontent.com/-u9eyWo3CeQY/VSbYYzi4hAI/AAAAAAAAAAM/1uLDUY2uyqU/s1600/stderr-stdout_fault.png
Is there a way to stop Lucee from throwing this error? Or a way to catch
and send the original back to BlazeDS?

It seem that Railo 4.2.0.007 is unaffected by this issue - every version
after this has the same issue. Is there someone out there that can point
me in the right direction?On Thursday, April 9, 2015 at 12:58:48 PM UTC-7, littler...@gmail.com wrote:

This is affecting me as well.On Thursday, April 9, 2015 at 10:58:48 PM UTC+3, littler...@gmail.com wrote:

Lucee is running well - I’m working on an Enterprise Flex project and
didn’t take long to move from ADCF.

Everything is now running as expected - the only issue I’m running into is
when an error is thrown - the only error returned to the flex client is
this nullPointerException. The actual error - in this case an error I
threw - is being logged in Tomcat’s stderr - then immediately after the
nullPointerException is thrown by lucee - and it’s this error that gets
returned to the remoting client.

I’ve logged this error:
https://bitbucket.org/lucee/lucee/issue/269/remoting-nullpointerexception-for-all
https://www.google.com/url?q=https%3A%2F%2Fbitbucket.org%2Flucee%2Flucee%2Fissue%2F269%2Fremoting-nullpointerexception-for-all&sa=D&sntz=1&usg=AFQjCNEayvoXG-7Cc69wt7RknShaE2JDdA

Also including the snap of the stderr and the debug dump from BlazeDS to
stdout

https://lh3.googleusercontent.com/-u9eyWo3CeQY/VSbYYzi4hAI/AAAAAAAAAAM/1uLDUY2uyqU/s1600/stderr-stdout_fault.png
Is there a way to stop Lucee from throwing this error? Or a way to catch
and send the original back to BlazeDS?