tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Howard Lewis Ship <hls...@gmail.com>
Subject Re: Tapestry 3.0.3 status
Date Wed, 16 Mar 2005 13:10:48 GMT
JanitorThread:  the ApplicationServlet's destory() method should
locate the JanitorTask and ask it to shutdow2n.  There's nothing there
to do that today.  That's the likely source of the problem.


On Tue, 15 Mar 2005 20:07:37 -0800, Paul Ferraro <pmf8@columbia.edu> wrote:
> Comments inline...
> 
> David Taylor wrote:
> 
> > Anyone know what is happening with Tapestry 3.0.3?
> 
> I will probably get a chance to complete all of the 3.0.3 fixes over the
> next several days.  After that, we'll vote on the release and, assuming
> it passes, I'll begin the release process.
> 
> >   I have several applications under development and would love to see
> > some bug fixes rolled into an official release. Patching the official
> > release version for production apps tends to make clients a bit
> > uncomfortable.
> >
> > If there is anyway I can help get this out the door please let me
> > know. I have already implemented a fix for the janitor thread problem
> > (see  TAPESTRY-230 <http://issues.apache.org/jira/browse/TAPESTRY-230>)
> 
> I looked at your fix.  You start by saying that interrupt() does nothing
> if the thread is not sleeping.  That is incorrect.
> [See
> http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Thread.html#interrupt()]
> Apart from the other monitor states (i.e. wait, join) that respond to an
> interrupt, the last sentence states, "If none of the previous conditions
> hold then this thread's interrupt status will be set."
> The interrupted status of a thread can be checked via the
> isInterrupted() method.  See my comments just above yours in JIRA.
> 
> > and have packaged Friendly URL support into a standalone jar file for
> > use in my projects. The Friendly URL fix is a modified version of the
> > patches from the wiki that prevents an NPE when the URL suffixes have
> > not been configured in the application specification. This jar could
> > be made available as an add-on in 3.0.3 with only minor tweaks to the
> > core tapestry distribution (ComponentAddressAdaptor and
> > SpecificationParser) if anyone is interested.
> >
> There have been several long discussions about this.  Work on 3.1 is
> well underway (a robust friendly url implementation is already in place
> in 3.1-alpha-1), and new features will target that branch.  Future
> releases from the 3.0 branch (including 3.0.3) will only include
> important bug fixes.
> 
> Paul
> 
> > David
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> 
> 


-- 
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


Mime
View raw message