But then we need a patched ognl lib. That is also something that doesn't bring a smile on my face.... :(
I think this is such a basic thing that i think that they want this behaviour somehow. Can't think about
anything else if you are this far in the development and still throw an exception like this. That is just a choice of them (i think)
On 10/19/05, Eelco Hillenius <[EMAIL PROTECTED]
> wrote:
last time I proposed a patch, it took them half a year. Not sure
whether we want to wait for that :)
Eelco
On 10/19/05, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
> may be we can address this question to an OGNL mailing list?
>
> Juergen
>
> On 10/19/05, Nick Heudecker <[EMAIL PROTECTED]> wrote:
> > I also ran into this and think it's pretty annoying. I haven't come up with
> > a workaround, but I'm also not happy with yours. :) Unfortunately, I think
> > the only way to handle it correctly is to change OGNL.
> >
> > What if a primitive should be returned instead of an object? That breaks
> > if null is returned.
> >
> >
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Wicket-develop mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wicket-develop
>
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
