You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Renat Zubairov <re...@gmail.com> on 2007/03/28 23:07:19 UTC
Latest OGNL 2.7-SNAPSHOT and Tapestry
Hello,
We have a application on Tapestry 4.1.2-SNAPSHOT and since already a
month or so we have _constant_ problems in running it (basically I
can't run it at all). The _only_ reasons for that is latest OGNL
2.7-SNAPSHOT dependency that is not working properly (see all bugs in
http://jira.opensymphony.com/browse/OGNL ). I can see in the mail list
that there are some other people having the same problems.
I'm curious, how it is possible to fix the tapestry version that is
not dependent on the latest OGNL changes?
Also it would be very interesting to know how close Tapestry 4.1.2 and
OGNL are working together, for example may we declare dependency on
Tap 4.1.2-SNAPSHOT but with OGNL-2.6?
--
Best regards,
Renat Zubairov
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Latest OGNL 2.7-SNAPSHOT and Tapestry
Posted by Kalle Korhonen <ka...@gmail.com>.
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
deploying the new ognl as a snapshot and letting the community come up with
real world samples of where the new ognl breaks. If you must use the latest
snapshot but continue with your own development, doesn't excluding 2.7 and
explicitly declaring dependency on 2.6 work?
Kalle
On 3/29/07, Renat Zubairov <re...@gmail.com> wrote:
>
> 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 (personally for me) to fix one bug at time and not to
> fix multiple in parallel, therefore dependency of one very instable
> snapshot to another very instable snapshot look very wired. I see
> Jesse is working very hard to fix all bugs and really appreciate it,
> but I my personal opinion our project will have ZERO or close to zero
> benefits from the new OGNL version. Performance is important but
> thinking about performance before all functional requirements are
> satisfied is in my personal opinion is a kind of premature
> optimization.
>
> On 29/03/07, Daniel Tabuenca <dt...@gmail.com> wrote:
> > 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 snapshot and as such is code under constant
> > development and in most cases not guaranteed to work. If you need
> > stability then stick to 4.1.1, or even better 4.0 ( if you aren't
> > using the new ajax stuff). If you are more adventurous try the
> > specific snapshot before the addition of the new OGNL. I too look
> > forward to a released version of 4.1.2 and don't think its fair to
> > complain that a snapshot release is unstable. I thought that was the
> > very definition of a snapshot release (unstable code in development).
> >
> >
> > On 3/28/07, Ben Dotte <bd...@widen.com> wrote:
> > > 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 separate workspace devoted to testing out the newest
> > > Tapestry/OGNL snapshots and I won't commit that to our source control
> > > system until most of the application works.
> > >
> > > If OGNL could be fixed fairly soon I'm fine with the dependency on 2.7
> .
> > > But I would agree that making new Tapestry 4.1.2 snapshot compatible
> > > with OGNL 2.6 would be a nice alternative if that isn't possible in
> the
> > > short term.
> > >
> > > Ben
> > >
> > > -----Original Message-----
> > > From: Renat Zubairov [mailto:renat.zubairov@gmail.com]
> > > Sent: Wednesday, March 28, 2007 4:07 PM
> > > To: Tapestry users
> > > Subject: Latest OGNL 2.7-SNAPSHOT and Tapestry
> > >
> > > Hello,
> > >
> > > We have a application on Tapestry 4.1.2-SNAPSHOT and since already a
> > > month or so we have _constant_ problems in running it (basically I
> > > can't run it at all). The _only_ reasons for that is latest OGNL
> > > 2.7-SNAPSHOT dependency that is not working properly (see all bugs in
> > > http://jira.opensymphony.com/browse/OGNL ). I can see in the mail list
> > > that there are some other people having the same problems.
> > > I'm curious, how it is possible to fix the tapestry version that is
> > > not dependent on the latest OGNL changes?
> > > Also it would be very interesting to know how close Tapestry 4.1.2 and
> > > OGNL are working together, for example may we declare dependency on
> > > Tap 4.1.2-SNAPSHOT but with OGNL-2.6?
> > >
> > > --
> > > Best regards,
> > > Renat Zubairov
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
> --
> Best regards,
> Renat Zubairov
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: Latest OGNL 2.7-SNAPSHOT and Tapestry
Posted by Renat Zubairov <re...@gmail.com>.
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 (personally for me) to fix one bug at time and not to
fix multiple in parallel, therefore dependency of one very instable
snapshot to another very instable snapshot look very wired. I see
Jesse is working very hard to fix all bugs and really appreciate it,
but I my personal opinion our project will have ZERO or close to zero
benefits from the new OGNL version. Performance is important but
thinking about performance before all functional requirements are
satisfied is in my personal opinion is a kind of premature
optimization.
On 29/03/07, Daniel Tabuenca <dt...@gmail.com> wrote:
> 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 snapshot and as such is code under constant
> development and in most cases not guaranteed to work. If you need
> stability then stick to 4.1.1, or even better 4.0 ( if you aren't
> using the new ajax stuff). If you are more adventurous try the
> specific snapshot before the addition of the new OGNL. I too look
> forward to a released version of 4.1.2 and don't think its fair to
> complain that a snapshot release is unstable. I thought that was the
> very definition of a snapshot release (unstable code in development).
>
>
> On 3/28/07, Ben Dotte <bd...@widen.com> wrote:
> > 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 separate workspace devoted to testing out the newest
> > Tapestry/OGNL snapshots and I won't commit that to our source control
> > system until most of the application works.
> >
> > If OGNL could be fixed fairly soon I'm fine with the dependency on 2.7.
> > But I would agree that making new Tapestry 4.1.2 snapshot compatible
> > with OGNL 2.6 would be a nice alternative if that isn't possible in the
> > short term.
> >
> > Ben
> >
> > -----Original Message-----
> > From: Renat Zubairov [mailto:renat.zubairov@gmail.com]
> > Sent: Wednesday, March 28, 2007 4:07 PM
> > To: Tapestry users
> > Subject: Latest OGNL 2.7-SNAPSHOT and Tapestry
> >
> > Hello,
> >
> > We have a application on Tapestry 4.1.2-SNAPSHOT and since already a
> > month or so we have _constant_ problems in running it (basically I
> > can't run it at all). The _only_ reasons for that is latest OGNL
> > 2.7-SNAPSHOT dependency that is not working properly (see all bugs in
> > http://jira.opensymphony.com/browse/OGNL ). I can see in the mail list
> > that there are some other people having the same problems.
> > I'm curious, how it is possible to fix the tapestry version that is
> > not dependent on the latest OGNL changes?
> > Also it would be very interesting to know how close Tapestry 4.1.2 and
> > OGNL are working together, for example may we declare dependency on
> > Tap 4.1.2-SNAPSHOT but with OGNL-2.6?
> >
> > --
> > Best regards,
> > Renat Zubairov
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Best regards,
Renat Zubairov
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Latest OGNL 2.7-SNAPSHOT and Tapestry
Posted by Daniel Tabuenca <dt...@gmail.com>.
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 snapshot and as such is code under constant
development and in most cases not guaranteed to work. If you need
stability then stick to 4.1.1, or even better 4.0 ( if you aren't
using the new ajax stuff). If you are more adventurous try the
specific snapshot before the addition of the new OGNL. I too look
forward to a released version of 4.1.2 and don't think its fair to
complain that a snapshot release is unstable. I thought that was the
very definition of a snapshot release (unstable code in development).
On 3/28/07, Ben Dotte <bd...@widen.com> wrote:
> 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 separate workspace devoted to testing out the newest
> Tapestry/OGNL snapshots and I won't commit that to our source control
> system until most of the application works.
>
> If OGNL could be fixed fairly soon I'm fine with the dependency on 2.7.
> But I would agree that making new Tapestry 4.1.2 snapshot compatible
> with OGNL 2.6 would be a nice alternative if that isn't possible in the
> short term.
>
> Ben
>
> -----Original Message-----
> From: Renat Zubairov [mailto:renat.zubairov@gmail.com]
> Sent: Wednesday, March 28, 2007 4:07 PM
> To: Tapestry users
> Subject: Latest OGNL 2.7-SNAPSHOT and Tapestry
>
> Hello,
>
> We have a application on Tapestry 4.1.2-SNAPSHOT and since already a
> month or so we have _constant_ problems in running it (basically I
> can't run it at all). The _only_ reasons for that is latest OGNL
> 2.7-SNAPSHOT dependency that is not working properly (see all bugs in
> http://jira.opensymphony.com/browse/OGNL ). I can see in the mail list
> that there are some other people having the same problems.
> I'm curious, how it is possible to fix the tapestry version that is
> not dependent on the latest OGNL changes?
> Also it would be very interesting to know how close Tapestry 4.1.2 and
> OGNL are working together, for example may we declare dependency on
> Tap 4.1.2-SNAPSHOT but with OGNL-2.6?
>
> --
> Best regards,
> Renat Zubairov
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: Latest OGNL 2.7-SNAPSHOT and Tapestry
Posted by Ma...@bmw.ch.
If it's just about sending stack-traces and code-snippets - I really,
really promise to do it ;). I've just rewound our current project to
4.1.1, but would be happy to return to 4.1.2, if ognl worked for my core
components.
Marcus
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> 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.
>
> Have no fear though, the people currently paying my bills are
> applying real pressure for this as well, so if things don't
> start looking much rosier next week I'll probably enable this
> fail-safe abilities but still log the exceptions somewhere in
> the hopes that some kind souls occasionally report them.
> (I'll probably just do a
> exception.printStackTrace() in the hopes that sysout dumps
> will be annoying enough to report ;) )
>
> On 3/30/07, Ben Dotte <bd...@widen.com> wrote:
> > Thanks Jesse, it is reassuring to know you're making
> progress and that
> > you have a backup plan for things that don't work when 4.1.2 is
> > released. Sorry if it sounds like I was complaining--it was just a
> > little disconcerting to see so many things break moving from one
> > snapshot to the next. I really don't mind tracking down and
> reporting
> > bugs though, it is the least the community can do to support open
> > source software. Good luck with the rest of your fixes, I
> don't envy
> > having to work with all that bytecode enhancement stuff!
> >
> > -----Original Message-----
> > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> > 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 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 do have a solution already implemented to handle "rough
> edge cases"
> > for expressions that won't compile but I've haven't enabled it yet
> > because then no one would ever give me my much needed bug reports.
> >
> > I have no intention of releasing 4.1.2 with OGNL 2.7 without this
> > fail-over feature enabled, but would like to give it a little more
> > time before giving up on it. I'm sure my last round of changes have
> > caused all manner of problems that are easily
> solved..Refactoring in
> > bytecode enhancements is a non trivial thing...bleh..
> >
> > On 3/28/07, Ben Dotte <bd...@widen.com> wrote:
> > > 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 separate workspace devoted to testing out the
> > > newest Tapestry/OGNL snapshots and I won't commit that to
> our source
> > > control system until most of the application works.
> > >
> > > If OGNL could be fixed fairly soon I'm fine with the dependency on
> > 2.7.
> > > But I would agree that making new Tapestry 4.1.2 snapshot
> compatible
> > > with OGNL 2.6 would be a nice alternative if that isn't
> possible in
> > the
> > > short term.
> > >
> > > Ben
> > >
> > > -----Original Message-----
> > > From: Renat Zubairov [mailto:renat.zubairov@gmail.com]
> > > Sent: Wednesday, March 28, 2007 4:07 PM
> > > To: Tapestry users
> > > Subject: Latest OGNL 2.7-SNAPSHOT and Tapestry
> > >
> > > Hello,
> > >
> > > We have a application on Tapestry 4.1.2-SNAPSHOT and
> since already a
> > > month or so we have _constant_ problems in running it
> (basically I
> > > can't run it at all). The _only_ reasons for that is latest OGNL
> > > 2.7-SNAPSHOT dependency that is not working properly (see
> all bugs
> > > in http://jira.opensymphony.com/browse/OGNL ). I can see
> in the mail
> > > list that there are some other people having the same problems.
> > > I'm curious, how it is possible to fix the tapestry
> version that is
> > > not dependent on the latest OGNL changes?
> > > Also it would be very interesting to know how close
> Tapestry 4.1.2
> > > and OGNL are working together, for example may we declare
> dependency
> > > on Tap 4.1.2-SNAPSHOT but with OGNL-2.6?
> > >
> > > --
> > > Best regards,
> > > Renat Zubairov
> > >
> > >
> --------------------------------------------------------------------
> > > - To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> > >
> --------------------------------------------------------------------
> > > - To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Latest OGNL 2.7-SNAPSHOT and Tapestry
Posted by Jesse Kuhnert <jk...@gmail.com>.
No I don't view it as complaining. Perfectly understandable. I wish it
weren't so brittle and error prone to work on.
Have no fear though, the people currently paying my bills are applying
real pressure for this as well, so if things don't start looking much
rosier next week I'll probably enable this fail-safe abilities but
still log the exceptions somewhere in the hopes that some kind souls
occasionally report them. (I'll probably just do a
exception.printStackTrace() in the hopes that sysout dumps will be
annoying enough to report ;) )
On 3/30/07, Ben Dotte <bd...@widen.com> wrote:
> Thanks Jesse, it is reassuring to know you're making progress and that
> you have a backup plan for things that don't work when 4.1.2 is
> released. Sorry if it sounds like I was complaining--it was just a
> little disconcerting to see so many things break moving from one
> snapshot to the next. I really don't mind tracking down and reporting
> bugs though, it is the least the community can do to support open source
> software. Good luck with the rest of your fixes, I don't envy having to
> work with all that bytecode enhancement stuff!
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> 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 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 do have a solution already implemented to handle "rough edge cases"
> for expressions that won't compile but I've haven't enabled it yet
> because then no one would ever give me my much needed bug reports.
>
> I have no intention of releasing 4.1.2 with OGNL 2.7 without this
> fail-over feature enabled, but would like to give it a little more
> time before giving up on it. I'm sure my last round of changes have
> caused all manner of problems that are easily solved..Refactoring in
> bytecode enhancements is a non trivial thing...bleh..
>
> On 3/28/07, Ben Dotte <bd...@widen.com> wrote:
> > 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 separate workspace devoted to testing out the newest
> > Tapestry/OGNL snapshots and I won't commit that to our source control
> > system until most of the application works.
> >
> > If OGNL could be fixed fairly soon I'm fine with the dependency on
> 2.7.
> > But I would agree that making new Tapestry 4.1.2 snapshot compatible
> > with OGNL 2.6 would be a nice alternative if that isn't possible in
> the
> > short term.
> >
> > Ben
> >
> > -----Original Message-----
> > From: Renat Zubairov [mailto:renat.zubairov@gmail.com]
> > Sent: Wednesday, March 28, 2007 4:07 PM
> > To: Tapestry users
> > Subject: Latest OGNL 2.7-SNAPSHOT and Tapestry
> >
> > Hello,
> >
> > We have a application on Tapestry 4.1.2-SNAPSHOT and since already a
> > month or so we have _constant_ problems in running it (basically I
> > can't run it at all). The _only_ reasons for that is latest OGNL
> > 2.7-SNAPSHOT dependency that is not working properly (see all bugs in
> > http://jira.opensymphony.com/browse/OGNL ). I can see in the mail list
> > that there are some other people having the same problems.
> > I'm curious, how it is possible to fix the tapestry version that is
> > not dependent on the latest OGNL changes?
> > Also it would be very interesting to know how close Tapestry 4.1.2 and
> > OGNL are working together, for example may we declare dependency on
> > Tap 4.1.2-SNAPSHOT but with OGNL-2.6?
> >
> > --
> > Best regards,
> > Renat Zubairov
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Latest OGNL 2.7-SNAPSHOT and Tapestry
Posted by Martino Piccinato <ma...@gmail.com>.
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 ;-)
Re: Latest OGNL 2.7-SNAPSHOT and Tapestry
Posted by Martino Piccinato <ma...@gmail.com>.
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
latest trunk if possible ;-)
This is the situation:
public interface I1 {
public String getXyz();
public void setXyz(String x);
public void doSomething();
}
abstract class A implements interface I1 {
public void doSomething() {
// blah blah blah
}
}
public class B extends A {
private String xyz;
public String getXyz() {
return xyz;
}
public void setXyz(String x);
this.xyz = x;
}
}
Now I have a page:
public abstract MyPage extends BasePage {
public A getObjectA()
@Component(bindings="value=objecta.xyz")
public abstract TextField getObjectATextField();
}
The page has a getter for object of type A but obviously I'm feeding it with
non abstract classes extending A that actually implement the
interface XYZ getters and setters.
now this WAS NOT failing with previous OGNL, it's failing with OGNL
2.7complaining for inconsistent method signatures.
After some experimenting I've discovered that in order for this to work I
need to implement, at least as an abstract method, in the A class the XYZ
getters ans setters that is turning A into:
abstract class A implements interface I1 {
public void doSomething() {
// blah blah blah
}
public abstract String getXyz();
public abstract void setXyz(String x);
}
After this modification it works like charms. So I think is missing proper
interface checking for accessing property: that is to say you might have to
do with an abstract class not directly implementing an interface method and
the expression evaluator should check for it. I think this should be
checked.
RE: Latest OGNL 2.7-SNAPSHOT and Tapestry
Posted by Ben Dotte <bd...@widen.com>.
Thanks Jesse, it is reassuring to know you're making progress and that
you have a backup plan for things that don't work when 4.1.2 is
released. Sorry if it sounds like I was complaining--it was just a
little disconcerting to see so many things break moving from one
snapshot to the next. I really don't mind tracking down and reporting
bugs though, it is the least the community can do to support open source
software. Good luck with the rest of your fixes, I don't envy having to
work with all that bytecode enhancement stuff!
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
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 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 do have a solution already implemented to handle "rough edge cases"
for expressions that won't compile but I've haven't enabled it yet
because then no one would ever give me my much needed bug reports.
I have no intention of releasing 4.1.2 with OGNL 2.7 without this
fail-over feature enabled, but would like to give it a little more
time before giving up on it. I'm sure my last round of changes have
caused all manner of problems that are easily solved..Refactoring in
bytecode enhancements is a non trivial thing...bleh..
On 3/28/07, Ben Dotte <bd...@widen.com> wrote:
> 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 separate workspace devoted to testing out the newest
> Tapestry/OGNL snapshots and I won't commit that to our source control
> system until most of the application works.
>
> If OGNL could be fixed fairly soon I'm fine with the dependency on
2.7.
> But I would agree that making new Tapestry 4.1.2 snapshot compatible
> with OGNL 2.6 would be a nice alternative if that isn't possible in
the
> short term.
>
> Ben
>
> -----Original Message-----
> From: Renat Zubairov [mailto:renat.zubairov@gmail.com]
> Sent: Wednesday, March 28, 2007 4:07 PM
> To: Tapestry users
> Subject: Latest OGNL 2.7-SNAPSHOT and Tapestry
>
> Hello,
>
> We have a application on Tapestry 4.1.2-SNAPSHOT and since already a
> month or so we have _constant_ problems in running it (basically I
> can't run it at all). The _only_ reasons for that is latest OGNL
> 2.7-SNAPSHOT dependency that is not working properly (see all bugs in
> http://jira.opensymphony.com/browse/OGNL ). I can see in the mail list
> that there are some other people having the same problems.
> I'm curious, how it is possible to fix the tapestry version that is
> not dependent on the latest OGNL changes?
> Also it would be very interesting to know how close Tapestry 4.1.2 and
> OGNL are working together, for example may we declare dependency on
> Tap 4.1.2-SNAPSHOT but with OGNL-2.6?
>
> --
> Best regards,
> Renat Zubairov
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Latest OGNL 2.7-SNAPSHOT and Tapestry
Posted by Jesse Kuhnert <jk...@gmail.com>.
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 do have a solution already implemented to handle "rough edge cases"
for expressions that won't compile but I've haven't enabled it yet
because then no one would ever give me my much needed bug reports.
I have no intention of releasing 4.1.2 with OGNL 2.7 without this
fail-over feature enabled, but would like to give it a little more
time before giving up on it. I'm sure my last round of changes have
caused all manner of problems that are easily solved..Refactoring in
bytecode enhancements is a non trivial thing...bleh..
On 3/28/07, Ben Dotte <bd...@widen.com> wrote:
> 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 separate workspace devoted to testing out the newest
> Tapestry/OGNL snapshots and I won't commit that to our source control
> system until most of the application works.
>
> If OGNL could be fixed fairly soon I'm fine with the dependency on 2.7.
> But I would agree that making new Tapestry 4.1.2 snapshot compatible
> with OGNL 2.6 would be a nice alternative if that isn't possible in the
> short term.
>
> Ben
>
> -----Original Message-----
> From: Renat Zubairov [mailto:renat.zubairov@gmail.com]
> Sent: Wednesday, March 28, 2007 4:07 PM
> To: Tapestry users
> Subject: Latest OGNL 2.7-SNAPSHOT and Tapestry
>
> Hello,
>
> We have a application on Tapestry 4.1.2-SNAPSHOT and since already a
> month or so we have _constant_ problems in running it (basically I
> can't run it at all). The _only_ reasons for that is latest OGNL
> 2.7-SNAPSHOT dependency that is not working properly (see all bugs in
> http://jira.opensymphony.com/browse/OGNL ). I can see in the mail list
> that there are some other people having the same problems.
> I'm curious, how it is possible to fix the tapestry version that is
> not dependent on the latest OGNL changes?
> Also it would be very interesting to know how close Tapestry 4.1.2 and
> OGNL are working together, for example may we declare dependency on
> Tap 4.1.2-SNAPSHOT but with OGNL-2.6?
>
> --
> Best regards,
> Renat Zubairov
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: Latest OGNL 2.7-SNAPSHOT and Tapestry
Posted by Ben Dotte <bd...@widen.com>.
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 separate workspace devoted to testing out the newest
Tapestry/OGNL snapshots and I won't commit that to our source control
system until most of the application works.
If OGNL could be fixed fairly soon I'm fine with the dependency on 2.7.
But I would agree that making new Tapestry 4.1.2 snapshot compatible
with OGNL 2.6 would be a nice alternative if that isn't possible in the
short term.
Ben
-----Original Message-----
From: Renat Zubairov [mailto:renat.zubairov@gmail.com]
Sent: Wednesday, March 28, 2007 4:07 PM
To: Tapestry users
Subject: Latest OGNL 2.7-SNAPSHOT and Tapestry
Hello,
We have a application on Tapestry 4.1.2-SNAPSHOT and since already a
month or so we have _constant_ problems in running it (basically I
can't run it at all). The _only_ reasons for that is latest OGNL
2.7-SNAPSHOT dependency that is not working properly (see all bugs in
http://jira.opensymphony.com/browse/OGNL ). I can see in the mail list
that there are some other people having the same problems.
I'm curious, how it is possible to fix the tapestry version that is
not dependent on the latest OGNL changes?
Also it would be very interesting to know how close Tapestry 4.1.2 and
OGNL are working together, for example may we declare dependency on
Tap 4.1.2-SNAPSHOT but with OGNL-2.6?
--
Best regards,
Renat Zubairov
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org