I've added a bug in ognl issue tracker for the bug I though I've found with
some more information on the issue. Sorry but I did not understood at first
that Jesse is also OGNL Project Lead so I thought he wanted bug reports for
tapestry-ognl and not for ognl ;-)
t [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 30, 2007 4:33 PM
> To: Tapestry users
> Subject: Re: Latest OGNL 2.7-SNAPSHOT and Tapestry
>
> No I don't view it as complaining. Perfectly understandable.
> I wish it weren't so brittle and error prone to work on.
&g
e-
From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 29, 2007 7:57 PM
To: Tapestry users
Subject: Re: Latest OGNL 2.7-SNAPSHOT and Tapestry
Sorry I've been away for a couple days...
I'm sure things must look very dire indeed. Though they do appear out
of hand rig
hnert [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 29, 2007 7:57 PM
To: Tapestry users
Subject: Re: Latest OGNL 2.7-SNAPSHOT and Tapestry
Sorry I've been away for a couple days...
I'm sure things must look very dire indeed. Though they do appear out
of hand right now I promise it's
I've found a bug or at least a "notable difference" with previous behaviour
regarding this.
I send it as a mail, if you find it interesting I can open a ticket for
this. It took me some to understand what was going on.
And yes: I'd like too to have the possibility to stick to ognl 2.6.7 with
lat
Sorry I've been away for a couple days...
I'm sure things must look very dire indeed. Though they do appear out
of hand right now I promise it's moving forward by leaps and bounds.
The only crappy part is that the compiler is extremely unforgiving, so
the slightest slip up and you're hosed..
I d
Oh functional requirements were long satisfied with 2.6, 2.7 doesn't do
anything to change it. The performance benefits are well proven on paper,
but it was known from the begininning there'd be corner cases that would
emerge later. As painful as it is, I think Jesse made the right choice by
deplo
Very good comment. I can understand that SNAPSHOT releases are very
instable and in our project we are using snapshot releases because the
project is not in production yet and we are trying to get the most out
of new AJAX functionality in Tap 4.1.2. However based on my experience
it is simpler (pe
If I recall, Jesse announced when the dependency on OGNL 2.7 was added
that things would be broken for a while. If I recall he even included
the particular snapshot version you should use if you wanted to avoid
going to the snapshot dependent on 2.7. You have to keep in mind that
a snapshot is a s
I would have to agree that until OGNL 2.7 is much more stable, the new
Tapestry snapshots are pretty useless to us. Jesse has been kind enough
to fix several bugs I have found in record time (thanks Jesse!) but
we're still at a point where most of our pages don't work at all yet.
For now I have a s
10 matches
Mail list logo
