To anybody whom it may concern...
The threading problem referred to in this thread, can be worked
around by overriding the AbstractEngine's protected
createComponentClassEnhancer method to return a synchronized version
of the enhancer. This makes 3.0.4 work like earlier versions of
Tapest
enior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
-Original Message-
From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
Sent: Wed 1/31/2007 2:13 PM
To: Tapestry users
Subject: Re: Tapestry 3.x DEAD
I don't remember the details surrounding the 3.0.4 r
ot;released", but it looks like it got half way there and then
died.
regards,
Mark
Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
-Original Message-
From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
Sent: Wed 1/31/2007 1:27 PM
To:
1:27 PM
To: Tapestry users
Cc: [EMAIL PROTECTED]
Subject: Re: Tapestry 3.x DEAD
I don't know what's wrong with the dynamic url stuff (I did test it
before updating the main site), but you can always get it from:
http://www.apache.org/dist/tapestry/
On 1/31/07, Mark Stang <[EMAIL
I don't know what's wrong with the dynamic url stuff (I did test it
before updating the main site), but you can always get it from:
http://www.apache.org/dist/tapestry/
On 1/31/07, Mark Stang <[EMAIL PROTECTED]> wrote:
Howard,
It appears that development on 3.x has stalled to a complete stop.
Howard,
It appears that development on 3.x has stalled to a complete stop. The
web-site lists the latest 3.x release as 3.0.4. According to the "news" it
says 3.0.4 has hundreds of bug fixes. What it doesn't show is that 3.0.4 has a
threading issue. The issue was identified over two months ag
