The NPEs from OGNL strings (like foo.bar.name) are more of an OGNL
issue than a Cayenne issue. At least in my opinion. I think the best
thing to do, especially with regards to Tapestry and OGNL and Cayenne,
is to add a cayenne: prefix extension to Tapestry (just like HLS added
a prop: prefix --
On 12/15/06, Michael Gentry [EMAIL PROTECTED] wrote:
The NPEs from OGNL strings (like foo.bar.name) are more of an OGNL
issue than a Cayenne issue. At least in my opinion.
Actually we're trying to move away from OGNL because it breaks
refactoring. The fact that Spindle died didn't help. In
On Dec 14, 2006, at 9:11 , Øyvind Harboe wrote:
Could I implement my own NeverNullString datatype where I'm thinking
that .toString() returns the either what Cayenne java.lang.String
returns today or e.g. for the case where it represents a database
null?
Or perhaps map java.lang.CharSequence
On Dec 14, 2006, at 14:09 , Øyvind Harboe wrote:
Q++: Is it a good idea to use ExtendedType to represent database null
as something else than Java null pointer?
I do not think it is a good idea in my project as I try to use not
null as much as possible. The places where I allow null, there
On 12/14/06, Tore Halset [EMAIL PROTECTED] wrote:
On Dec 14, 2006, at 9:11 , Øyvind Harboe wrote:
Could I implement my own NeverNullString datatype where I'm thinking
that .toString() returns the either what Cayenne java.lang.String
returns today or e.g. for the case where it represents a
