You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by cracru <cr...@gmail.com> on 2005/08/18 22:43:19 UTC
AbstractEngine.cleanupAfterRequest AWOL
It seems that cleanupAfterRequest() is no longer being called during
service() processing. I grep'd 4.0 b4 source and there seems to be no
references to the method.
In T4, what is the preferred method for releasing resources at the end
of a request?
Thanks, C.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: AbstractEngine.cleanupAfterRequest AWOL
Posted by cracru <cr...@gmail.com>.
Thanks Howard! (for both answers)
-C.
On 8/18/05, Howard Lewis Ship <hl...@gmail.com> wrote:
> There's two different pipelines that you can easily plug into to
> provide whatever pre- and post-request processing you want. The outer
> pipeline is based on the Servlet API; the inner pipeline is based on
> the WebRequest API (an abstraction around Servlets or Portlets).
>
> There are configuration points to which you can contribute filters.
>
> http://jakarta.apache.org/tapestry/tapestry/hivedocs/config/tapestry.request.ServletRequestServicerPipeline.html
> http://jakarta.apache.org/tapestry/tapestry/hivedocs/config/tapestry.request.WebRequestServicerPipeline.html
>
> On 8/18/05, cracru <cr...@gmail.com> wrote:
> > It seems that cleanupAfterRequest() is no longer being called during
> > service() processing. I grep'd 4.0 b4 source and there seems to be no
> > references to the method.
> >
> > In T4, what is the preferred method for releasing resources at the end
> > of a request?
> >
> > Thanks, C.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-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-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: property-specification should be optional most of the time and uses annotation when need extra info
Posted by Mark Dillon <md...@gmail.com>.
Hey Sebastien. In tap 4, you only need to have the abstact getter in
your class for properties. If you want the property to be persistent,
you do something like this:
@Persist
public abstract int getCounter();
No page specification required...
Cheers,
Mark
On 8/18/05, Sebastien Tardif <at...@freenet.carleton.ca> wrote:
> I was reading section 3.5.3 Specifying properties in the page specification
> of Tapestry in Action and then realized that writing something like:
>
> <property-specification name="item" type="examples.todo1.ToDoItem"/>
>
> Doesn't add anything to:
> (In the page class)
> public abstract ToDoItem getToDoItem()
>
> So the property-specification should be optional here. Reflection should
> understand that if somebody declared a get/set abstract in a page class
> that's very probable that the goal was to have a property with the declared
> type.
>
> To specify persistent attribute and default value, annotation could be used.
> Which annotation in this list
> (http://jakarta.apache.org/tapestry/tapestry-annotations/index.html) is used
> in Tapestry 4.0 for that?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: property-specification should be optional most of the time and uses annotati
Posted by Serge Eby <sd...@hotmail.com>.
Check the link below:
http://jakarta.apache.org/tapestry/tapestry-annotations/index.html#Persist
--
Serge
----Original Message Follows----
From: "Sebastien Tardif" <at...@freenet.carleton.ca>
Reply-To: "Tapestry users" <ta...@jakarta.apache.org>
To: "'Tapestry users'" <ta...@jakarta.apache.org>
Subject: property-specification should be optional most of the time and uses
annotation when need extra info
Date: Thu, 18 Aug 2005 23:34:23 -0400
I was reading section 3.5.3 Specifying properties in the page specification
of Tapestry in Action and then realized that writing something like:
<property-specification name="item" type="examples.todo1.ToDoItem"/>
Doesn't add anything to:
(In the page class)
public abstract ToDoItem getToDoItem()
So the property-specification should be optional here. Reflection should
understand that if somebody declared a get/set abstract in a page class
that's very probable that the goal was to have a property with the declared
type.
To specify persistent attribute and default value, annotation could be used.
Which annotation in this list
(http://jakarta.apache.org/tapestry/tapestry-annotations/index.html) is used
in Tapestry 4.0 for that?
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
property-specification should be optional most of the time and uses annotation when need extra info
Posted by Sebastien Tardif <at...@freenet.carleton.ca>.
I was reading section 3.5.3 Specifying properties in the page specification
of Tapestry in Action and then realized that writing something like:
<property-specification name="item" type="examples.todo1.ToDoItem"/>
Doesn't add anything to:
(In the page class)
public abstract ToDoItem getToDoItem()
So the property-specification should be optional here. Reflection should
understand that if somebody declared a get/set abstract in a page class
that's very probable that the goal was to have a property with the declared
type.
To specify persistent attribute and default value, annotation could be used.
Which annotation in this list
(http://jakarta.apache.org/tapestry/tapestry-annotations/index.html) is used
in Tapestry 4.0 for that?
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: AbstractEngine.cleanupAfterRequest AWOL
Posted by Howard Lewis Ship <hl...@gmail.com>.
There's two different pipelines that you can easily plug into to
provide whatever pre- and post-request processing you want. The outer
pipeline is based on the Servlet API; the inner pipeline is based on
the WebRequest API (an abstraction around Servlets or Portlets).
There are configuration points to which you can contribute filters.
http://jakarta.apache.org/tapestry/tapestry/hivedocs/config/tapestry.request.ServletRequestServicerPipeline.html
http://jakarta.apache.org/tapestry/tapestry/hivedocs/config/tapestry.request.WebRequestServicerPipeline.html
On 8/18/05, cracru <cr...@gmail.com> wrote:
> It seems that cleanupAfterRequest() is no longer being called during
> service() processing. I grep'd 4.0 b4 source and there seems to be no
> references to the method.
>
> In T4, what is the preferred method for releasing resources at the end
> of a request?
>
> Thanks, C.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-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-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org