You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Massimo Lusetti <ml...@gmail.com> on 2007/01/26 10:04:57 UTC
Re: svn commit: r500081 - in /tapestry/tapestry5/tapestry-core/trunk/src: main/java/org/apache/tapestry/annotations/ main/java/org/apache/tapestry/internal/services/ main/java/org/apache/tapestry/services/ main/java/org/apache/tapestry/test/ main/res
On 1/26/07, hlship@apache.org <hl...@apache.org> wrote:
> Author: hlship
> Date: Thu Jan 25 17:29:41 2007
> New Revision: 500081
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=500081
> Log:
> Add support for Application State Objects.
There's a small typo[1] in the link to javadocs for
ApplicationStateCreator and ApplicationStateContribution.
BTW, Do you plan to bring EngineSerivce-like feature to tapestry5 and
do you have ideas on when they it be back?
[1]
Index: appstate.apt
===================================================================
--- appstate.apt (revision 500171)
+++ appstate.apt (working copy)
@@ -53,7 +53,7 @@
Alternately, you will configure an ASO so that you can control how
it is instantiated. You may need to inject some values into the ASO
when it is first created, or otherwise initialize it. In this
second case, you may provide an
- {{{../org/apache/tapestry/services/ApplicationStateCreator.html}ApplicationStateCreator}}
object, which will be called upon to create the ASO
+ {{{../apidocs/org/apache/tapestry/services/ApplicationStateCreator.html}ApplicationStateCreator}}
object, which will be called upon to create the ASO
as necessary. This is also the technique to use when you want your
ASO to be represented by an <interface> rather than a <class>: you
need to provide
a creator that knows about the class that implements the interface.
@@ -83,5 +83,5 @@
example.
Finally, we create an
- {{{../org/apache/tapestry/services/ApplicationStateContribution.html}ApplicationStateContribution}}
- identifying the strategy name and the creator, and give that to the
configuration.
\ No newline at end of file
+ {{{../apidocs/org/apache/tapestry/services/ApplicationStateContribution.html}ApplicationStateContribution}}
+ identifying the strategy name and the creator, and give that to the
configuration.
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: svn commit: r500081 - in /tapestry/tapestry5/tapestry-core/trunk/src: main/java/org/apache/tapestry/annotations/ main/java/org/apache/tapestry/internal/services/ main/java/org/apache/tapestry/services/ main/java/org/apache/tapestry/test/ main/res
Posted by Massimo Lusetti <ml...@gmail.com>.
On 2/3/07, Howard Lewis Ship <hl...@gmail.com> wrote:
> and an InputStream that can be pushed to the client. Details soon ...
> I'm writing a tutorial right now and I hope it will be ready before we
> start promoting 5.0.1 on monday.
Glad to ear that Howard!
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: svn commit: r500081 - in /tapestry/tapestry5/tapestry-core/trunk/src: main/java/org/apache/tapestry/annotations/ main/java/org/apache/tapestry/internal/services/ main/java/org/apache/tapestry/services/ main/java/org/apache/tapestry/test/ main/res
Posted by Howard Lewis Ship <hl...@gmail.com>.
Nope, different stuff in T5. But this isn't implemented yet.
The ComponentEventDispatcher is pretty much ready for the job; it
triggers and event on a component and captures the result object.
There's a set of types that are supported for the return type ...
currently Strings are considred Page Names (a redirect is sent), or
Components are expected to be a page root component (a redirect is
sent) but extending this list will allow for some additional types,
such as some kind of MIMEByteStream type that represents a MIME type
and an InputStream that can be pushed to the client. Details soon ...
I'm writing a tutorial right now and I hope it will be ready before we
start promoting 5.0.1 on monday.
On 2/3/07, Massimo Lusetti <ml...@gmail.com> wrote:
> On 1/26/07, Howard Lewis Ship <hl...@gmail.com> wrote:
>
> > What I intend is to make it easy for components to generate links to
> > themselves, and allow an event handler method to return a bytestream
> > directly. None of this engine service complexity ... if a component
> > wishes to handle requests by generating a bytestream, I'll let it.
>
> Doesn't it need to interact with a Dispatcher?
> Like the AssetDispatcher which recognize the request asset prefix, or
> something like that?
>
> I was able to stream bytes to the client from wihtin a component and a
> page event handler method but always got some IllegalStateException
> when the container tried to manage the output via its own PrintWriter.
>
> I mean the whole process succeed but i fill the log with some nasty
> stack trace output, but probably i'm missing something...
>
> --
> Massimo
> http://meridio.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: svn commit: r500081 - in /tapestry/tapestry5/tapestry-core/trunk/src: main/java/org/apache/tapestry/annotations/ main/java/org/apache/tapestry/internal/services/ main/java/org/apache/tapestry/services/ main/java/org/apache/tapestry/test/ main/res
Posted by Massimo Lusetti <ml...@gmail.com>.
On 1/26/07, Howard Lewis Ship <hl...@gmail.com> wrote:
> What I intend is to make it easy for components to generate links to
> themselves, and allow an event handler method to return a bytestream
> directly. None of this engine service complexity ... if a component
> wishes to handle requests by generating a bytestream, I'll let it.
Doesn't it need to interact with a Dispatcher?
Like the AssetDispatcher which recognize the request asset prefix, or
something like that?
I was able to stream bytes to the client from wihtin a component and a
page event handler method but always got some IllegalStateException
when the container tried to manage the output via its own PrintWriter.
I mean the whole process succeed but i fill the log with some nasty
stack trace output, but probably i'm missing something...
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: svn commit: r500081 - in /tapestry/tapestry5/tapestry-core/trunk/src: main/java/org/apache/tapestry/annotations/ main/java/org/apache/tapestry/internal/services/ main/java/org/apache/tapestry/services/ main/java/org/apache/tapestry/test/ main/res
Posted by Howard Lewis Ship <hl...@gmail.com>.
What I intend is to make it easy for components to generate links to
themselves, and allow an event handler method to return a bytestream
directly. None of this engine service complexity ... if a component
wishes to handle requests by generating a bytestream, I'll let it.
On 1/26/07, Massimo Lusetti <ml...@gmail.com> wrote:
> On 1/26/07, Massimo Lusetti <ml...@gmail.com> wrote:
>
> > BTW, Do you plan to bring EngineSerivce-like feature to tapestry5 and
> > do you have ideas on when they it be back?
>
> I mean, maybe the HttpServletRequestHandler pipeline is enough?
>
> --
> Massimo
> http://meridio.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: svn commit: r500081 - in /tapestry/tapestry5/tapestry-core/trunk/src: main/java/org/apache/tapestry/annotations/ main/java/org/apache/tapestry/internal/services/ main/java/org/apache/tapestry/services/ main/java/org/apache/tapestry/test/ main/res
Posted by Massimo Lusetti <ml...@gmail.com>.
On 1/26/07, Massimo Lusetti <ml...@gmail.com> wrote:
> BTW, Do you plan to bring EngineSerivce-like feature to tapestry5 and
> do you have ideas on when they it be back?
I mean, maybe the HttpServletRequestHandler pipeline is enough?
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org