You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Sean Schofield <se...@gmail.com> on 2005/09/22 18:47:22 UTC

[shale] Unexpected behavior with TilesViewHandler and ConverterException

I've just run into a strange issue with Tiles and JSF Converters.  My
converter was cataching a NPE while converting and rethrew as a
ConverterException.  I was expecting to see the default converter
message displayed above my component but instead I got a 500 sever
error.

org.apache.taglib.tiles.InsertTag - 2005-09-22 12:35:36,672

This suggests to me that Tiles is returning the 500 error code without
allowing the exception to propogate up to where it can be handled
properly by JSF.  Is that possible?

On a related note, what is a good strategy for generating/handling
exceptions during conversion?  Does it make sense to put a try-catch
around everything in your getAsObject, getAsString methods and rethrow
as ConverterException?

TIA,

sean

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: [shale] Unexpected behavior with TilesViewHandler and ConverterException

Posted by Sean Schofield <se...@gmail.com>.
I believe this is a bug with MyFaces
(http://issues.apache.org/jira/browse/MYFACES-611).

sean

On 9/22/05, Sean Schofield <se...@gmail.com> wrote:
> I've just run into a strange issue with Tiles and JSF Converters.  My
> converter was cataching a NPE while converting and rethrew as a
> ConverterException.  I was expecting to see the default converter
> message displayed above my component but instead I got a 500 sever
> error.
>
> org.apache.taglib.tiles.InsertTag - 2005-09-22 12:35:36,672
>
> This suggests to me that Tiles is returning the 500 error code without
> allowing the exception to propogate up to where it can be handled
> properly by JSF.  Is that possible?
>
> On a related note, what is a good strategy for generating/handling
> exceptions during conversion?  Does it make sense to put a try-catch
> around everything in your getAsObject, getAsString methods and rethrow
> as ConverterException?
>
> TIA,
>
> sean
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org