RE: [announce] ognl 2.7 fail-safe enabled

2007-04-11 Thread Marcus.Schulte
Sorry to bring this up again, but I was too quick with my positive
feedback, although it IS better than before ;). There are still problems
which the workaround doesn't catch:

Unable to process client request: Unable to parse OGNL expression '
value || !okOnly': Unable to add method java.lang.Object
ref2(ognl.OgnlContext, java.lang.Object) to class
ognl.ASTOr9607468Accessor: [source error] ; is missing

I'll file a bug once the opensymphony-jira is back at work. Otherwise
we've to go back to 4.1.1 for the time being, unfortunately. But I'll
try from time to time when I feel like it ...

Marcus

 -Original Message-
 From: Ben Dotte [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, April 05, 2007 6:36 PM
 To: Tapestry users
 Subject: RE: [announce] ognl 2.7 fail-safe enabled
 
 I'm close to being able to upgrade but this one is a real blocker for
 us:
 
 http://jira.opensymphony.com/browse/OGNL-35
 
 Even with the fail-safe this is a problem because it ends up 
 evaluating things it isn't supposed to (which causes our code 
 to throw exceptions).
 
 Ben
 
 -Original Message-
 From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
 Sent: Thursday, April 05, 2007 9:26 AM
 To: Tapestry users
 Subject: Re: [announce] ognl 2.7 fail-safe enabled
 
 Great, I'm glad it's working out.
 
 If the stack traces contain exceptions in the javassist 
 package it'd be nice to have them go into the ognl jira:
 
 http://jira.opensymphony.com/browse/OGNL
 
 On 4/5/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
  Jesse, thanks a bunch!
  It works great now - and we're back on the snapshot ;) 
 Shall I enter 
  my stacktraces into the Tap-Jira or the Ognl-Jira, preferably?
  Marcus
 
   -Original Message-
   From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
   Sent: Wednesday, April 04, 2007 5:46 PM
   To: Tapestry users
   Subject: Re: [announce] ognl 2.7 fail-safe enabled
  
   Fix deploying nowSorry boot that.
  
   On 4/4/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
Hey Marcus,
   
Yeah I just ran into that yesterday as well... Was just a
   dumb catch
block mistake. There will be a new tapestry update in a couple
 more
hours. (have to go to dr. first)
   
On 4/4/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 Hi Jesse

 first of all, thanks a lot for your efforts!
 Unfortunately this doesn't seem to work for me right now 
 (pom.properties says it's from Mon Apr 02 09:33:49 EST
   2007 ) I'll
 file the exception I'm getting in Jira.

 Marcus

  -Original Message-
  From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
  Sent: Monday, April 02, 2007 5:29 PM
  To: Tapestry users
  Subject: [announce] ognl 2.7 fail-safe enabled
 
  I think I've resolved most of the issues over the
   weekend already,
  but since I ran across a new ognl jira issue this
   morning I went
  ahead and enabled the promised fail-safe 
 compilation features.
 
  If anyone gets any exceptions related to ognl 
 javassist please 
  report them asap, if they're just stack dumps to 
 system.out it 
  would be ~nice~ if you filed the bugs but hopefully 
 they won't 
  affect the operation of your respective apps.
 
  This was only enabled / deployed an hour or so ago so
   you'll need
  to get the new snapshot to see the changes.
 
  --
  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:
   [EMAIL PROTECTED]
  For additional commands, e-mail:
 [EMAIL PROTECTED]
 
 


   
 
 - To unsubscribe, e-mail: 
 [EMAIL PROTECTED]
 For additional commands, e-mail: 
 [EMAIL PROTECTED]


   
   
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
   
Open source based consulting work centered around 
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
   
  
  
   --
   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: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
  
 -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 --
 Jesse Kuhnert
 Tapestry/Dojo team member/developer
 
 Open source based consulting work centered around 
 dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com

RE: [announce] ognl 2.7 fail-safe enabled

2007-04-05 Thread Marcus.Schulte
Jesse, thanks a bunch!
It works great now - and we're back on the snapshot ;) 
Shall I enter my stacktraces into the Tap-Jira or the Ognl-Jira,
preferably?
Marcus

 -Original Message-
 From: Jesse Kuhnert [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, April 04, 2007 5:46 PM
 To: Tapestry users
 Subject: Re: [announce] ognl 2.7 fail-safe enabled
 
 Fix deploying nowSorry boot that.
 
 On 4/4/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
  Hey Marcus,
 
  Yeah I just ran into that yesterday as well... Was just a 
 dumb catch 
  block mistake. There will be a new tapestry update in a couple more 
  hours. (have to go to dr. first)
 
  On 4/4/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
   Hi Jesse
  
   first of all, thanks a lot for your efforts!
   Unfortunately this doesn't seem to work for me right now 
   (pom.properties says it's from Mon Apr 02 09:33:49 EST 
 2007 ) I'll 
   file the exception I'm getting in Jira.
  
   Marcus
  
-Original Message-
From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
Sent: Monday, April 02, 2007 5:29 PM
To: Tapestry users
Subject: [announce] ognl 2.7 fail-safe enabled
   
I think I've resolved most of the issues over the 
 weekend already, 
but since I ran across a new ognl jira issue this 
 morning I went 
ahead and enabled the promised fail-safe compilation features.
   
If anyone gets any exceptions related to ognl javassist please 
report them asap, if they're just stack dumps to system.out it 
would be ~nice~ if you filed the bugs but hopefully they won't 
affect the operation of your respective apps.
   
This was only enabled / deployed an hour or so ago so 
 you'll need 
to get the new snapshot to see the changes.
   
--
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: 
 [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   
   
  
   
 
   - To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 
  --
  Jesse Kuhnert
  Tapestry/Dojo team member/developer
 
  Open source based consulting work centered around 
  dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
 
 
 
 --
 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: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [announce] ognl 2.7 fail-safe enabled

2007-04-05 Thread Patrick Klein

Hi, Jesse,

I just tried the latest snapshot of tapestry but still got the same 
result as in my last post (If-component and T4.1.2-Snapshot) from the 
28th of march. Rendering of the page differs major between T4.1.1 and 
T4.1.2 Snapshot.


Regards,
   Patrick

I think I've resolved most of the issues over the weekend already, but
since I ran across a new ognl jira issue this morning I went ahead and
enabled the promised fail-safe compilation features.

If anyone gets any exceptions related to ognl javassist please report
them asap, if they're just stack dumps to system.out it would be
~nice~ if you filed the bugs but hopefully they won't affect the
operation of your respective apps.

This was only enabled / deployed an hour or so ago so you'll need to
get the new snapshot to see the changes.




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [announce] ognl 2.7 fail-safe enabled

2007-04-05 Thread Jesse Kuhnert

I have no idea what you are talking about Patrick. Was there something
more specific you found problems with?

On 4/5/07, Patrick Klein [EMAIL PROTECTED] wrote:

Hi, Jesse,

I just tried the latest snapshot of tapestry but still got the same
result as in my last post (If-component and T4.1.2-Snapshot) from the
28th of march. Rendering of the page differs major between T4.1.1 and
T4.1.2 Snapshot.

Regards,
Patrick
 I think I've resolved most of the issues over the weekend already, but
 since I ran across a new ognl jira issue this morning I went ahead and
 enabled the promised fail-safe compilation features.

 If anyone gets any exceptions related to ognl javassist please report
 them asap, if they're just stack dumps to system.out it would be
 ~nice~ if you filed the bugs but hopefully they won't affect the
 operation of your respective apps.

 This was only enabled / deployed an hour or so ago so you'll need to
 get the new snapshot to see the changes.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [announce] ognl 2.7 fail-safe enabled

2007-04-05 Thread Patrick Klein

Hi Jesse,

had to look up the message myself again...
here is a quote of what i wrote:

--

i'm experiencing some trouble here with Tapestry4.1.2 SNAPSHOT and 
ognl-expressions.


I've got the following construct in a table-component in my template:

div jwcid=[EMAIL PROTECTED]
span jwcid=@If condition=ognl:showPrices
span jwcid=@If condition=ognl:positionEditable
 input jwcid=[EMAIL PROTECTED] 
value=ognl:orderPosition.price.netPrice size=6 
translator=translator:bisoNumber,pattern=#0.00# 
displayName=message:PRICE validators=validators:required/

/span
span jwcid=@Else
 span jwcid=@Insert value=ognl:netPrice/
/span
/span
/div

from the state of the application both methods isShowPrices() and 
isPositionEditable() both should return true.


T4.1.1 builds html-code like following:

td class=PRICEColumnValue id=informal_18
   span
   span
   input type=text name=price value=365,00 id=price 
size=6 /

   /span
   /span
/td

however, if i switch to T4.1.2 SNAPSHOT i get the following:

td class=PRICEColumnValue id=informal_18
   span
   span
   365,00
   /span
   /span
/td

using the identical application state, which would imply that 
isPositionEditable has returned false which it shouldn't. I've put some 
debug output
into the isPositionEditable() method to track it's result and had to 
realize that the method was called only once for a table containing 6 
rows in

each of which it should've been called.

Additionally to that i'm experiencing some trouble with the latest 
tap/ognl snapshot as expressions like ognl:conditionA||conditionB 
result in an exception.


Does anyone have an idea about to avoid the first first problem?

I guess the second one came with the latest snapshot of ognl as it 
worked with 4.1.2-SNAPSHOT last week...




The snipplet is part of a table in one of our pages which is also the 
only one showing this behavior in our application. We got other 
order-related pages which are working perfectly with very similar code 
to that one...


Regards,
   Patrick


I have no idea what you are talking about Patrick. Was there something
more specific you found problems with?

On 4/5/07, Patrick Klein [EMAIL PROTECTED] wrote:

Hi, Jesse,

I just tried the latest snapshot of tapestry but still got the same
result as in my last post (If-component and T4.1.2-Snapshot) from the
28th of march. Rendering of the page differs major between T4.1.1 and
T4.1.2 Snapshot.

Regards,
Patrick
 I think I've resolved most of the issues over the weekend already, but
 since I ran across a new ognl jira issue this morning I went ahead and
 enabled the promised fail-safe compilation features.

 If anyone gets any exceptions related to ognl javassist please report
 them asap, if they're just stack dumps to system.out it would be
 ~nice~ if you filed the bugs but hopefully they won't affect the
 operation of your respective apps.

 This was only enabled / deployed an hour or so ago so you'll need to
 get the new snapshot to see the changes.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]








-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [announce] ognl 2.7 fail-safe enabled

2007-04-05 Thread Jesse Kuhnert

Great, I'm glad it's working out.

If the stack traces contain exceptions in the javassist package it'd
be nice to have them go into the ognl jira:

http://jira.opensymphony.com/browse/OGNL

On 4/5/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

Jesse, thanks a bunch!
It works great now - and we're back on the snapshot ;)
Shall I enter my stacktraces into the Tap-Jira or the Ognl-Jira,
preferably?
Marcus

 -Original Message-
 From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, April 04, 2007 5:46 PM
 To: Tapestry users
 Subject: Re: [announce] ognl 2.7 fail-safe enabled

 Fix deploying nowSorry boot that.

 On 4/4/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
  Hey Marcus,
 
  Yeah I just ran into that yesterday as well... Was just a
 dumb catch
  block mistake. There will be a new tapestry update in a couple more
  hours. (have to go to dr. first)
 
  On 4/4/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
   Hi Jesse
  
   first of all, thanks a lot for your efforts!
   Unfortunately this doesn't seem to work for me right now
   (pom.properties says it's from Mon Apr 02 09:33:49 EST
 2007 ) I'll
   file the exception I'm getting in Jira.
  
   Marcus
  
-Original Message-
From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
Sent: Monday, April 02, 2007 5:29 PM
To: Tapestry users
Subject: [announce] ognl 2.7 fail-safe enabled
   
I think I've resolved most of the issues over the
 weekend already,
but since I ran across a new ognl jira issue this
 morning I went
ahead and enabled the promised fail-safe compilation features.
   
If anyone gets any exceptions related to ognl javassist please
report them asap, if they're just stack dumps to system.out it
would be ~nice~ if you filed the bugs but hopefully they won't
affect the operation of your respective apps.
   
This was only enabled / deployed an hour or so ago so
 you'll need
to get the new snapshot to see the changes.
   
--
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:
 [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   
   
  
  
 
   - To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 
  --
  Jesse Kuhnert
  Tapestry/Dojo team member/developer
 
  Open source based consulting work centered around
  dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
 


 --
 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: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [announce] ognl 2.7 fail-safe enabled

2007-04-05 Thread Ben Dotte
I'm close to being able to upgrade but this one is a real blocker for
us:

http://jira.opensymphony.com/browse/OGNL-35

Even with the fail-safe this is a problem because it ends up evaluating
things it isn't supposed to (which causes our code to throw exceptions).

Ben

-Original Message-
From: Jesse Kuhnert [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 05, 2007 9:26 AM
To: Tapestry users
Subject: Re: [announce] ognl 2.7 fail-safe enabled

Great, I'm glad it's working out.

If the stack traces contain exceptions in the javassist package it'd
be nice to have them go into the ognl jira:

http://jira.opensymphony.com/browse/OGNL

On 4/5/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 Jesse, thanks a bunch!
 It works great now - and we're back on the snapshot ;)
 Shall I enter my stacktraces into the Tap-Jira or the Ognl-Jira,
 preferably?
 Marcus

  -Original Message-
  From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
  Sent: Wednesday, April 04, 2007 5:46 PM
  To: Tapestry users
  Subject: Re: [announce] ognl 2.7 fail-safe enabled
 
  Fix deploying nowSorry boot that.
 
  On 4/4/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
   Hey Marcus,
  
   Yeah I just ran into that yesterday as well... Was just a
  dumb catch
   block mistake. There will be a new tapestry update in a couple
more
   hours. (have to go to dr. first)
  
   On 4/4/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi Jesse
   
first of all, thanks a lot for your efforts!
Unfortunately this doesn't seem to work for me right now
(pom.properties says it's from Mon Apr 02 09:33:49 EST
  2007 ) I'll
file the exception I'm getting in Jira.
   
Marcus
   
 -Original Message-
 From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
 Sent: Monday, April 02, 2007 5:29 PM
 To: Tapestry users
 Subject: [announce] ognl 2.7 fail-safe enabled

 I think I've resolved most of the issues over the
  weekend already,
 but since I ran across a new ognl jira issue this
  morning I went
 ahead and enabled the promised fail-safe compilation features.

 If anyone gets any exceptions related to ognl javassist please
 report them asap, if they're just stack dumps to system.out it
 would be ~nice~ if you filed the bugs but hopefully they won't
 affect the operation of your respective apps.

 This was only enabled / deployed an hour or so ago so
  you'll need
 to get the new snapshot to see the changes.

 --
 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:
  [EMAIL PROTECTED]
 For additional commands, e-mail:
[EMAIL PROTECTED]


   
   
  
- To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   
   
  
  
   --
   Jesse Kuhnert
   Tapestry/Dojo team member/developer
  
   Open source based consulting work centered around
   dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
  
 
 
  --
  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: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [announce] ognl 2.7 fail-safe enabled

2007-04-04 Thread Marcus.Schulte
Hi Jesse

first of all, thanks a lot for your efforts!
Unfortunately this doesn't seem to work for me right now 
(pom.properties says it's from Mon Apr 02 09:33:49 EST 2007 )
I'll file the exception I'm getting in Jira.

Marcus

 -Original Message-
 From: Jesse Kuhnert [mailto:[EMAIL PROTECTED] 
 Sent: Monday, April 02, 2007 5:29 PM
 To: Tapestry users
 Subject: [announce] ognl 2.7 fail-safe enabled
 
 I think I've resolved most of the issues over the weekend 
 already, but since I ran across a new ognl jira issue this 
 morning I went ahead and enabled the promised fail-safe 
 compilation features.
 
 If anyone gets any exceptions related to ognl javassist 
 please report them asap, if they're just stack dumps to 
 system.out it would be ~nice~ if you filed the bugs but 
 hopefully they won't affect the operation of your respective apps.
 
 This was only enabled / deployed an hour or so ago so you'll 
 need to get the new snapshot to see the changes.
 
 --
 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: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [announce] ognl 2.7 fail-safe enabled

2007-04-04 Thread Jesse Kuhnert

Hey Marcus,

Yeah I just ran into that yesterday as well... Was just a dumb catch
block mistake. There will be a new tapestry update in a couple more
hours. (have to go to dr. first)

On 4/4/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

Hi Jesse

first of all, thanks a lot for your efforts!
Unfortunately this doesn't seem to work for me right now
(pom.properties says it's from Mon Apr 02 09:33:49 EST 2007 )
I'll file the exception I'm getting in Jira.

Marcus

 -Original Message-
 From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
 Sent: Monday, April 02, 2007 5:29 PM
 To: Tapestry users
 Subject: [announce] ognl 2.7 fail-safe enabled

 I think I've resolved most of the issues over the weekend
 already, but since I ran across a new ognl jira issue this
 morning I went ahead and enabled the promised fail-safe
 compilation features.

 If anyone gets any exceptions related to ognl javassist
 please report them asap, if they're just stack dumps to
 system.out it would be ~nice~ if you filed the bugs but
 hopefully they won't affect the operation of your respective apps.

 This was only enabled / deployed an hour or so ago so you'll
 need to get the new snapshot to see the changes.

 --
 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: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [announce] ognl 2.7 fail-safe enabled

2007-04-04 Thread Jesse Kuhnert

Fix deploying nowSorry boot that.

On 4/4/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:

Hey Marcus,

Yeah I just ran into that yesterday as well... Was just a dumb catch
block mistake. There will be a new tapestry update in a couple more
hours. (have to go to dr. first)

On 4/4/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 Hi Jesse

 first of all, thanks a lot for your efforts!
 Unfortunately this doesn't seem to work for me right now
 (pom.properties says it's from Mon Apr 02 09:33:49 EST 2007 )
 I'll file the exception I'm getting in Jira.

 Marcus

  -Original Message-
  From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
  Sent: Monday, April 02, 2007 5:29 PM
  To: Tapestry users
  Subject: [announce] ognl 2.7 fail-safe enabled
 
  I think I've resolved most of the issues over the weekend
  already, but since I ran across a new ognl jira issue this
  morning I went ahead and enabled the promised fail-safe
  compilation features.
 
  If anyone gets any exceptions related to ognl javassist
  please report them asap, if they're just stack dumps to
  system.out it would be ~nice~ if you filed the bugs but
  hopefully they won't affect the operation of your respective apps.
 
  This was only enabled / deployed an hour or so ago so you'll
  need to get the new snapshot to see the changes.
 
  --
  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: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




--
Jesse Kuhnert
Tapestry/Dojo team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com




--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [announce] ognl 2.7 fail-safe enabled

2007-04-02 Thread Patrick Moore

Hi Jesse --

It is nice that you care enough to put both a workaround and to ask for the
people to report issues...

-Pat

On 4/2/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:


I think I've resolved most of the issues over the weekend already, but
since I ran across a new ognl jira issue this morning I went ahead and
enabled the promised fail-safe compilation features.

If anyone gets any exceptions related to ognl javassist please report
them asap, if they're just stack dumps to system.out it would be
~nice~ if you filed the bugs but hopefully they won't affect the
operation of your respective apps.

This was only enabled / deployed an hour or so ago so you'll need to
get the new snapshot to see the changes.

--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: [announce] ognl 2.7 fail-safe enabled

2007-04-02 Thread Norbert Sándor

This is a very user-friendly solution, thanks!
I will give it a try soon.

Jesse Kuhnert írta:

I think I've resolved most of the issues over the weekend already, but
since I ran across a new ognl jira issue this morning I went ahead and
enabled the promised fail-safe compilation features.

If anyone gets any exceptions related to ognl javassist please report
them asap, if they're just stack dumps to system.out it would be
~nice~ if you filed the bugs but hopefully they won't affect the
operation of your respective apps.

This was only enabled / deployed an hour or so ago so you'll need to
get the new snapshot to see the changes.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]