You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Ben Dotte <bd...@widen.com> on 2007/04/25 20:09:37 UTC
Couple OGNL 2.7 questions
We've been working with the latest 4.1.2 snapshots and OGNL 2.7
snapshots for about a week now and things seem to be working a lot
better than they were. There are still plenty of places where OGNL is
broken but thankfully the failsafe feature seems to handle most of these
situations. I have a couple questions about that though:
1. Is it possible to suppress the OGNL failsafe stack traces that get
output to the console? I can understand why this is done so people will
report the OGNL bugs but given the volume of these that we see it makes
our console unusable when we need it for other things.
2. I can't seem to get the OGNL Jira system to send me any notifications
about anything. If a bug I reported is commented on, resolved, or
closed, I don't get any e-mail about it. I have even tried Watching my
own cases but still nothing. Is this just me or is there some setting on
the Jira system that needs to be fixed by an administrator?
Thanks,
Ben
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Couple OGNL 2.7 questions
Posted by Andreas Andreou <an...@di.uoa.gr>.
Yep, that jira not sending mails was a huge wtf...
I remember seeing that my issues were resolved two weeks after jesse had
fixed them!
On 4/25/07, Ben Dotte <bd...@widen.com> wrote:
>
> Great, please let us know how to suppress the stack traces once you have
> it checked in. As far as I can tell there is no way to control the log
> output because it is directly calling t.printStackTrace(), sending the
> output to System.err (HivemindExpressionCompiler.java lines 165 and
> 212):
>
> try {
> classFab.addMethod(Modifier.PUBLIC, valueGetter, getBody);
> } catch (Throwable t) {
>
> t.printStackTrace();
>
> generateFailSafe(context, expression, root);
> return;
> }
>
> Wouldn't you need to be using the _log logger on there instead of
> t.printStackTrace() in order to suppress these?
>
> If you get the Jira e-mails working that would be great too; I wouldn't
> have to check the system every day to see what has happened :)
>
> Thanks again,
> Ben
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Wednesday, April 25, 2007 1:18 PM
> To: Tapestry users
> Subject: Re: Couple OGNL 2.7 questions
>
> For option 1 yes I've done this locally but not checked it in yet, you
> should be able to control everything via logging categories / levels.
> I'm
> still a little worried about turning this off for get operations as
> they're
> definitely bad and I'm not sure anyone will ever notice them otherwise.
> Are
> you really getting that many ? I might have accidently turned on "too
> many"
> during the last deploy.
>
> WRT Jira emails I'm not sure why people aren't getting notified of
> ticket
> changes but that definitely can't be a good thing. Here I was adding
> comments and thinking people were ignoring me and it was really just the
> system not sending emails the whole time. :) I'll poke around and see if
> this is an option on that jira instance.
>
> On 4/25/07, Ben Dotte <bd...@widen.com> wrote:
> >
> > We've been working with the latest 4.1.2 snapshots and OGNL 2.7
> > snapshots for about a week now and things seem to be working a lot
> > better than they were. There are still plenty of places where OGNL is
> > broken but thankfully the failsafe feature seems to handle most of
> these
> > situations. I have a couple questions about that though:
> >
> > 1. Is it possible to suppress the OGNL failsafe stack traces that get
> > output to the console? I can understand why this is done so people
> will
> > report the OGNL bugs but given the volume of these that we see it
> makes
> > our console unusable when we need it for other things.
> >
> > 2. I can't seem to get the OGNL Jira system to send me any
> notifications
> > about anything. If a bug I reported is commented on, resolved, or
> > closed, I don't get any e-mail about it. I have even tried Watching my
> > own cases but still nothing. Is this just me or is there some setting
> on
> > the Jira system that needs to be fixed by an administrator?
> >
> > Thanks,
> > Ben
> >
> > ---------------------------------------------------------------------
> > 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
>
>
>
--
Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
Tapestry / Tacos developer
Open Source / JEE Consulting
RE: Couple OGNL 2.7 questions
Posted by Ben Dotte <bd...@widen.com>.
Great, please let us know how to suppress the stack traces once you have
it checked in. As far as I can tell there is no way to control the log
output because it is directly calling t.printStackTrace(), sending the
output to System.err (HivemindExpressionCompiler.java lines 165 and
212):
try {
classFab.addMethod(Modifier.PUBLIC, valueGetter, getBody);
} catch (Throwable t) {
t.printStackTrace();
generateFailSafe(context, expression, root);
return;
}
Wouldn't you need to be using the _log logger on there instead of
t.printStackTrace() in order to suppress these?
If you get the Jira e-mails working that would be great too; I wouldn't
have to check the system every day to see what has happened :)
Thanks again,
Ben
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
Sent: Wednesday, April 25, 2007 1:18 PM
To: Tapestry users
Subject: Re: Couple OGNL 2.7 questions
For option 1 yes I've done this locally but not checked it in yet, you
should be able to control everything via logging categories / levels.
I'm
still a little worried about turning this off for get operations as
they're
definitely bad and I'm not sure anyone will ever notice them otherwise.
Are
you really getting that many ? I might have accidently turned on "too
many"
during the last deploy.
WRT Jira emails I'm not sure why people aren't getting notified of
ticket
changes but that definitely can't be a good thing. Here I was adding
comments and thinking people were ignoring me and it was really just the
system not sending emails the whole time. :) I'll poke around and see if
this is an option on that jira instance.
On 4/25/07, Ben Dotte <bd...@widen.com> wrote:
>
> We've been working with the latest 4.1.2 snapshots and OGNL 2.7
> snapshots for about a week now and things seem to be working a lot
> better than they were. There are still plenty of places where OGNL is
> broken but thankfully the failsafe feature seems to handle most of
these
> situations. I have a couple questions about that though:
>
> 1. Is it possible to suppress the OGNL failsafe stack traces that get
> output to the console? I can understand why this is done so people
will
> report the OGNL bugs but given the volume of these that we see it
makes
> our console unusable when we need it for other things.
>
> 2. I can't seem to get the OGNL Jira system to send me any
notifications
> about anything. If a bug I reported is commented on, resolved, or
> closed, I don't get any e-mail about it. I have even tried Watching my
> own cases but still nothing. Is this just me or is there some setting
on
> the Jira system that needs to be fixed by an administrator?
>
> Thanks,
> Ben
>
> ---------------------------------------------------------------------
> 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: Couple OGNL 2.7 questions
Posted by Jesse Kuhnert <jk...@gmail.com>.
For option 1 yes I've done this locally but not checked it in yet, you
should be able to control everything via logging categories / levels. I'm
still a little worried about turning this off for get operations as they're
definitely bad and I'm not sure anyone will ever notice them otherwise. Are
you really getting that many ? I might have accidently turned on "too many"
during the last deploy.
WRT Jira emails I'm not sure why people aren't getting notified of ticket
changes but that definitely can't be a good thing. Here I was adding
comments and thinking people were ignoring me and it was really just the
system not sending emails the whole time. :) I'll poke around and see if
this is an option on that jira instance.
On 4/25/07, Ben Dotte <bd...@widen.com> wrote:
>
> We've been working with the latest 4.1.2 snapshots and OGNL 2.7
> snapshots for about a week now and things seem to be working a lot
> better than they were. There are still plenty of places where OGNL is
> broken but thankfully the failsafe feature seems to handle most of these
> situations. I have a couple questions about that though:
>
> 1. Is it possible to suppress the OGNL failsafe stack traces that get
> output to the console? I can understand why this is done so people will
> report the OGNL bugs but given the volume of these that we see it makes
> our console unusable when we need it for other things.
>
> 2. I can't seem to get the OGNL Jira system to send me any notifications
> about anything. If a bug I reported is commented on, resolved, or
> closed, I don't get any e-mail about it. I have even tried Watching my
> own cases but still nothing. Is this just me or is there some setting on
> the Jira system that needs to be fixed by an administrator?
>
> Thanks,
> Ben
>
> ---------------------------------------------------------------------
> 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