[ http://issues.apache.org/jira/browse/TAPESTRY-929?page=all ]
Andreas Andreou resolved TAPESTRY-929:
--------------------------------------
Fix Version: 4.1
Resolution: Fixed
There's a configuration point now, "tapestry.ognl.NullHandlers".
For instance:
<contribution configuration-id="tapestry.ognl.NullHandlers">
<null-handler class="my.company.class"
object="instance:my.company.MyNullHandler"/>
</contribution>
Your MyNullHandler should implement ognl.NullHandler.
With this configuration, every time OGNL accesses a property
(or calls a method) of 'my.company.class' that returns null,
it will pass control to your handler.
> OGNL Null Handler
> -----------------
>
> Key: TAPESTRY-929
> URL: http://issues.apache.org/jira/browse/TAPESTRY-929
> Project: Tapestry
> Type: Improvement
> Components: Framework
> Versions: 4.0, 4.0.1, 4.0.2
> Reporter: Angelo Luís
> Assignee: Andreas Andreou
> Fix For: 4.1
>
> When navigate with OGNL in a object graph can result in a null pointer
> exception, do a improvement a la Webwork that if the object is null create a
> new one. Probably implementing the NullHandler interface
> (http://www.opensymphony.com/ognl/html/DeveloperGuide/nullHandler.html).
> According to
> http://jakarta.apache.org/tapestry/tapestry/hivedocs/module/tapestry.ognl.html
> tapestry only support custom property accessors
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
