[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tapestry-user
Subject:    RE: Tapestry 3.x DEAD
From:       "Mark Stang" <mstang () pingidentity ! com>
Date:       2007-01-31 21:59:22
Message-ID: EB178A5944D70843A3B413BEB9373E4647494C () ex2 ! corp ! pingidentity ! com
[Download RAW message or body]


Jesse,
In other words, 3.0.4 has a fairly significant bug and nobody is maintaining it.  So, \
at the very least someone should update the Tapestry 3 website with a WARNING that \
3.0.4 has a threading bug.  Of course, 3.0.3 has a bunch of bugs that were fixed in \
3.0.4 so someone should annotate the website with a WARNING that 3.0.3 has many bugs. \


Which sounds like to me, that 3.X is DEAD and no longer being maintained.

So, let's have a wake, toss back a few and tell everyone to move onto 4.x which is \
the only version being maintained at this time.

thanks,

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:jkuhnert@gmail.com]
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 release but don't
think mirrors having / not having them have anything to do with anyone
thinking it was fully / not fully released.

Really "released" just means the core downloads && website are done. I
don't think the 3.0.4 website was updated because the forrest
documentation runtime wasn't playing very well, but the actual jars
were.

After looking at the thread I do recognize that section of code and
can say with confidence that it ~has~ been fully fixed in >= 4.1.1
versions.

Opening the old project up / using the ant definitions is a real PITA,
but if you felt strongly enough about it I suppose you could always
make a patch and file it in JIRA.

The ultimate fix was achieved in the DisableCachingFilter (for 4.x at
least), instead of the ComponentClass enhancer. The synchronized
blocks can probably be taken out. (or replaced with more thread
efficient backport-util counterparts - unless you are using more
recent jres in production where it looks like the old synchronized
speed issues have potentially been fixed)

On 1/31/07, Mark Stang <mstang@pingidentity.com> wrote:
> Jesse,
> I don't think the dynamic url stuff is the issue.  Actually, there are two issues.  \
> The first issue is the threading bug.  The next issue is that 3.0.4 was never fully \
> released, as I understand it, due to the threading bug.  Which is why it isn't on \
> the mirrors.  It is supposed to be "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:jkuhnert@gmail.com]
> Sent: Wed 1/31/2007 1:27 PM
> To: Tapestry users
> Cc: hlship@gmail.com
> 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 <mstang@pingidentity.com> wrote:
> > 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 ago.  The 3.0.4 is not on any of the \
> > mirrors, I guess because of the bug. 
> > All-in-all, it appears that not only is 3.x dead but there is a "bad" version \
> > sitting out there mis-leading potential users.  Unless someone is going to pick \
> > up 3.x, the web site should be reverted back to 3.0.3.  Then 3.0.4 and 3.0.5 \
> > should be deleted and all JIRA issues reflecting the fixes that were done should \
> > be re-listed as outstanding.  Those "fixes" which happened in 3.0.4 are still a \
> > problem for anyone using 3.0.3 but JIRA says they were fixed. 
> > The web site might as well show that 3.x is dead and tell everyone that it will \
> > no longer be maintained. 
> > Mark
> > 
> > Mark J. Stang
> > Senior Engineer/Architect
> > office: +1 303.468.2900
> > mobile: +1 303.507.2833
> > Ping Identity
> > 
> > 
> > 
> > -----Original Message-----
> > From: Mark Stang
> > Sent: Tue 1/30/2007 11:33 PM
> > To: Tapestry users; Tapestry users
> > Subject: RE: FW: Tapestry 3.0.4..not on mirrors
> > 
> > Nick,
> > Thanks for pointing that out, I finally found the e-mail trail.  I decided that I \
> > couldn't take a chance on 3.0.4 and reverted back to 3.0.3.  I guess we are done \
> > with 3.x and will wait for 5.x or the next great GUI Framework.  Tapestry has \
> > been fun and very interesting. 
> > regards,
> > 
> > Mark
> > 
> > Mark J. Stang
> > Senior Engineer/Architect
> > office: +1 303.468.2900
> > mobile: +1 303.507.2833
> > Ping Identity
> > 
> > 
> > 
> > -----Original Message-----
> > From: Nick Westgate [mailto:nick@key-planning.co.jp]
> > Sent: Tue 1/30/2007 8:10 PM
> > To: Tapestry users
> > Subject: Re: FW: Tapestry 3.0.4..not on mirrors
> > 
> > Hi Mark.
> > 
> > I'm referring to this thread:
> > "3.0.4 and repetitive method name/signature problem (class enhancement)"
> > http://thread.gmane.org/gmane.comp.java.tapestry.user/43121
> > 
> > Take it to the dev list when you've read that.
> > (I'm not a dev, so as to who is managing 3 now ...)
> > 
> > Cheers,
> > Nick.
> > 
> > 
> > Mark Stang wrote:
> > > Nick,
> > > I did a quick look and only saw references to 4.x.  If 3.0.4 is not the current \
> > > release, then why does the Tapestry Web site have it listed as such? 
> > > http://tapestry.apache.org/tapestry3/
> > > 
> > > Who is managing this?
> > > 
> > > thanks,
> > > 
> > > Mark
> > 
> > ---------------------------------------------------------------------
> > 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
> 
> 
> 


-- 
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



[prev in list] [next in list] [prev in thread] [next in thread]