You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Lance Java <la...@googlemail.com> on 2012/05/09 17:03:42 UTC
tapestry-push - proof of concept
Hi guys, I've been thinking about a "push" component for a while and I
thought I might make a start when I got some free time. I will be using an
abstraction on top of DWR's reverse ajax to achieve this.
Basically, it will look something like this:
ItemsComponent.tml
<div>
<t:zone t:id="zone" t:mixins="push" t:pushId="items-${user.id}"
t:pushEvent="doPush">
<t:loop source="items" item="item">${item.name}</t:loop>
</t:zone>
</div>
public class ItemsComponent {
@Property
private List<Item> items;
@Property
private Item item;
@SessionState
@Property
private User user;
@InjectComponent
private Zone zone;
public Block doPush(List<Item> context) {
this.items = context;
return zone.getBody();
}
}
And at some point, an asynchronous process will call
PushService.doPush(Object pushId, Object pushContext) which will fire
"doPush" and update the zone.
As part of this, I will need to do the following FROM A NON WEB THREAD
1. Get a component / page instance (using a path/id I stored earlier)
2. Execute an event on the component / page instance
3. Get the resultant block and run it through tapestry's template engine
4. Use DWR's reverse ajax to update the zone with the html fragment.
A couple of questions:
5. The push mixin will be storing the pushId and pushEvent in DWR's
http://directwebremoting.org/dwr/javadoc/org/directwebremoting/ScriptSession.html
ScriptSession . I will also need a String which will allow me to lookup a
component / page at a later stage. Is there a component path that will
uniquely identify the component page / instance?
6. I *think* that DWR has a HTTPServletRequest and HTTPServletResponse that
I *might* be able to get a handle on for the push. Any ideas on how I would
lookup the page / component / component resources?
Cheers,
Lance.
--
View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: tapestry-push - proof of concept
Posted by Lance Java <la...@googlemail.com>.
Thanks for the link Giulio, I'm sure I could achieve something quite similar
using DWR and Tapestry side by side. I'm hoping for a far more integrated
approach using tapestry's templating for html and zero javascript.
Cheers,
Lance.
--
View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644p5699403.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: tapestry-push - proof of concept
Posted by Giulio Micali <gi...@gmail.com>.
I don't know if it's what you are looking for, but some time ago I found
this article:
http://spreadthesource.com/2010/11/bringing-realtime-to-your-java-applications-with-websockets-nodejs-redis-tapestry-5/
Hope can be useful.
Cheers,
Giulio
Re: tapestry-push - proof of concept
Posted by Lance Java <la...@googlemail.com>.
The tapestry request processing pipeline is quite complicated and as you get
further down, it becomes less of a "black box" and you must know more of
it's internals ("white box"). There is a great diagram at the bottom of
http://tapestry.apache.org/request-processing.html this page. One thing to
keep in mind is that as you go down the request processing pipeline, objects
can be pushed onto the Environment thread local.
I recommend that you download the tapestry source code and follow the flow
through from the TapestryFilter. If you were to get down to the low level
RenderCommand and PageRenderQueue code, I think you would find that you will
be copy/pasting quite a lot of the internal tapestry code. Keep in mind that
any class in an "internal" package is considered private, should be avoided
and can change between releases.
I'm happier to not involve myself with the internal code, by invoking the
ComponentEventRequestHandler and reading the response into a JSONObject. I
will be able to access the HTML and javascript for an AJAX event without
needing to involve myself with too much of the tapestry internals.
If you'd like to go further, feel free to dive in ;)
--
View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644p5709831.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: tapestry-push - proof of concept
Posted by xieweiguo <xi...@139.com>.
Yes ,that's the real question.the block/zone/component dependents on the
environment (page or parent component ),so we can't just render it like call
a function
--
View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644p5710470.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: tapestry-push - proof of concept
Posted by Lance Java <la...@googlemail.com>.
No matter what you do, you will need a fake request and probably a fake
response. Tapestry converts components to RenderCommands but they still
point to their resources. For example, if you have an EventLink on in your
block, it requires a Request object for it to render.
--
View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644p5709908.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: tapestry-push - proof of concept
Posted by xieweiguo <xi...@139.com>.
Yes , you are right ,maybe using ComponentEventRequestHandler is the best
way now . But I wish that the next version of tapestry will provide some
service to render html more easily.^_^
The AjaxComponentEventRequestHandler is the key of partial-rendering , maybe
I should spend much more time to study it someday.
Here somebody named mindhawk provides another option:
//--------------------------------------------------------------
如果直接用renderqueue比较简单,不过可能有一些副作用,比如框架提供的安全检查和错误报告等都跳过啦。
If use renderqueue directly , it will be more simple , but has some negative
effect , such as security checks and error reporting provided by the
framework will be skiped .
下面给你一个简单的实现供你参考。
Here comes a simple implement for your reference
我定义了一个Tapestry的服务,负责渲染block或者rendercommand。
I define a tapestry services, for rendering the Block and Rendercommand
AppModule
=================
public static void bind(ServiceBinder binder) {
binder.bind(RenderFacade.class, RenderFacade.class); //注册服务
}
=================
RenderFacade
=================
package com.once.tapestry.services;
import java.io.PrintWriter;
import java.io.StringWriter;
import org.apache.tapestry5.Block;
import org.apache.tapestry5.ContentType;
import org.apache.tapestry5.MarkupWriter;
import org.apache.tapestry5.internal.services.RenderQueueImpl;
import org.apache.tapestry5.ioc.LoggerSource;
import org.apache.tapestry5.ioc.services.TypeCoercer;
import org.apache.tapestry5.runtime.RenderCommand;
import org.apache.tapestry5.services.MarkupWriterFactory;
import org.slf4j.Logger;
/**
* @author mindhawk
*
*/
public class RenderFacade {
private final MarkupWriterFactory markupWriterFactory;
private final LoggerSource loggerSource;
private final TypeCoercer typeCoercer;
public RenderFacade(MarkupWriterFactory markupWriterFactory,
LoggerSource loggerSource, TypeCoercer typeCoercer) {
super();
this.markupWriterFactory = markupWriterFactory;
this.loggerSource = loggerSource;
this.typeCoercer = typeCoercer;
}
public String render(Block block) {
RenderCommand command = typeCoercer.coerce(block,
RenderCommand.class);
return render(command);
}
public String render(RenderCommand command) {
MarkupWriter writer = markupWriterFactory.newMarkupWriter(new
ContentType("text/html;charset=UTF-8"));
String name = "tapestry.render.CommandRender";
Logger logger = loggerSource.getLogger(name);
RenderQueueImpl queue = new RenderQueueImpl(logger);
queue.push(command);
// Run the queue until empty.
queue.run(writer);
StringWriter stringWriter = new StringWriter();
PrintWriter pw = new PrintWriter(stringWriter);
writer.toMarkup(pw);
return stringWriter.toString();
}
}
==============
下面给出测试页面
Now comes the test page
RenderCommands (TML):
======================
<html title="About test"
xmlns:t="http://tapestry.apache.org/schema/tapestry_5_1_0.xsd"
xmlns:p="tapestry:parameter">
<body>
<t:block t:id="b1">
<div>Hello world!</div>
</t:block>
<t:block t:id="b2">
<div>World peace!</div>
</t:block>
${renderB1}<br/>
${renderB2}
</body>
</html>
======================
RenderCommands (Page):
======================
package com.once.tapestry.pages;
import org.apache.tapestry5.Block;
import org.apache.tapestry5.ioc.annotations.Inject;
import com.once.tapestry.services.RenderFacade;
public class RenderCommands {
@Inject
private Block b1;
@Inject
private Block b2;
@Inject
private RenderFacade renderFacade;
public String getRenderB1() {
return renderFacade.render(b1);
}
public String getRenderB2() {
return renderFacade.render(b2);
}
}
=======================
--
View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644p5709898.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: tapestry-push - proof of concept
Posted by Lance Java <la...@googlemail.com>.
You might find
http://tapestry.apache.org/5.3/apidocs/src-html/org/apache/tapestry5/internal/services/AjaxComponentEventRequestHandler.html
this code interesting
--
View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644p5709846.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: tapestry-push - proof of concept
Posted by xieweiguo <xi...@139.com>.
Yes,I believe if we use the tapestry's existing event processing chain,we
will get the rendered html we want.
The question is:in the back of tapestry's existing event processing
chain,tapestry use PageRenderQueue(or something else) and RenderCommand to
render blocks/zones/components. So , why don't we just use
PageRenderQueue(or something else) and RenderCommand ? it looks more
natural.
Thank you for your guidance,now I have got more clearly on tapestry's
architecture.
--
View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644p5709684.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: tapestry-push - proof of concept
Posted by Lance Java <la...@googlemail.com>.
Another option is call ComponentRequestHandler instead of
HttpServletRequestHandler which might be easier to pass an event context.
You will need to store a fake request and response in the RequestGlobals if
you want to use the ComponentRequestHandler but the request URL will not be
important.
http://tapestry.apache.org/tapestry5/apidocs/org/apache/tapestry5/services/ComponentRequestHandler.html
--
View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644p5709069.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: tapestry-push - proof of concept
Posted by Lance Java <la...@googlemail.com>.
Unfortunately I think howard's right in that you will need a fake request and
response. It's perfectly legal for a component to @Inject Request or @Inject
Response so you will need these.
It's probably easiest to take a very simple ajax zone update and try to fake
it from a non-web thread.
As an example:
1. Open firebug to the "net" tab
2. Go to
http://jumpstart.doublenegative.com.au/jumpstart/examples/ajax/eventlink
3. Click on the ajax link
4. Look at the request and response in firebug
In the net tab you will see
1. The request that you are trying to fake (important bits are the URL and
X-Requested-With header)
2. The response json
If you want a good place to start, create a simple ajax event on your site
and then try to fake it. You will need to call
HttpServletRequestHandler.service(request, response). The
HttpServletRequestHandler is a service which can be looked up from the
tapestry registry.
--
View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644p5708997.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: tapestry-push - proof of concept
Posted by xieweiguo <xi...@139.com>.
How about just render a block(or zone,component,etc) in a non-web-thead ?
Think about this:no event on the component will be execute,the
non-web-thread just prepare PageRenderQueue (or something else,I'm not
sure),RenderCommand and render the html of the block.and then,the
non-web-thread push the html to the clients.
That's my ideal way , and I think it's very important for comet/reverse ajax
developers,because they could push any part of page/component to client as
they want.
I have tried to implement this way,but unfortunately failed,because there
are many things I don't know about tapestry.But this way is feasible,isn't
it?
Thanks!
Howard Lewis Ship wrote
>
> On Wed, May 9, 2012 at 9:01 AM, Lance Java <lance.java@> wrote:
>> I see... I might keep going with the DWR approach then. So If I
>> understand
>> your proposal.
>>
>> 1. Use the incoming page request (& component resources) to generate a
>> URL.
>> Should this URL be to "activate" to component or to do the actual work
>> (eg
>> "doPush" in my example)?
>>
>> 2. In the asynchronous event (non web thread), I construct a fake request
>> with the URL and spoof it into the RequestGlobals. I'm still not entirely
>> sure how I would fire the "doPush" event from here (passing it a context)
>> and get the resultant block back. Is there a service in the registry I
>> should be calling?
>
> Yes ... start with TapestryFilter and work down; with luck, you can
> set things up so that you can pass your spoofed Request and Response
> into the RequestHandler service and everything will just happen from
> there. The normal Tapestry code will decompose the URL in the Request
> and do all the page activation, component invocation, and response
> rendering.
>
>>
>> Thanks,
>> Lance.
>>
>> --
>> View this message in context:
>> http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644p5697808.html
>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@.apache
>> For additional commands, e-mail: users-help@.apache
>>
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@.apache
> For additional commands, e-mail: users-help@.apache
>
--
View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644p5708909.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: tapestry-push - proof of concept
Posted by Lance Java <la...@googlemail.com>.
Ok, thanks for this. The only problem that I can see is that I don't have the
event context at the time I am constructing the URL. I will only have the
context in my asynchronous push event.
I'll take a look at how tapestry adds the context to the URL in
ComponentResources.createEventLink(String eventType, Object... context) and
see if I can mimmic the behaviour in my asynchronous thread.
Cheers,
Lance.
--
View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644p5699369.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: tapestry-push - proof of concept
Posted by Howard Lewis Ship <hl...@gmail.com>.
On Wed, May 9, 2012 at 9:01 AM, Lance Java <la...@googlemail.com> wrote:
> I see... I might keep going with the DWR approach then. So If I understand
> your proposal.
>
> 1. Use the incoming page request (& component resources) to generate a URL.
> Should this URL be to "activate" to component or to do the actual work (eg
> "doPush" in my example)?
>
> 2. In the asynchronous event (non web thread), I construct a fake request
> with the URL and spoof it into the RequestGlobals. I'm still not entirely
> sure how I would fire the "doPush" event from here (passing it a context)
> and get the resultant block back. Is there a service in the registry I
> should be calling?
Yes ... start with TapestryFilter and work down; with luck, you can
set things up so that you can pass your spoofed Request and Response
into the RequestHandler service and everything will just happen from
there. The normal Tapestry code will decompose the URL in the Request
and do all the page activation, component invocation, and response
rendering.
>
> Thanks,
> Lance.
>
> --
> View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644p5697808.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: tapestry-push - proof of concept
Posted by Lance Java <la...@googlemail.com>.
I see... I might keep going with the DWR approach then. So If I understand
your proposal.
1. Use the incoming page request (& component resources) to generate a URL.
Should this URL be to "activate" to component or to do the actual work (eg
"doPush" in my example)?
2. In the asynchronous event (non web thread), I construct a fake request
with the URL and spoof it into the RequestGlobals. I'm still not entirely
sure how I would fire the "doPush" event from here (passing it a context)
and get the resultant block back. Is there a service in the registry I
should be calling?
Thanks,
Lance.
--
View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644p5697808.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: tapestry-push - proof of concept
Posted by Howard Lewis Ship <hl...@gmail.com>.
On Wed, May 9, 2012 at 8:42 AM, Lance Java <la...@googlemail.com> wrote:
> Interesting to know you are thinking about push for tapestry. I know that DWR
> have done quite a bit of work to abstract the underlying mechanism for push
> (comet / polling / piggyback), do you think that you would roll-your-own
> push mechanism or do you have a library in mind?
>
I've really done zero research, so I wouldn't want to talk about solutions yet.
> --
> View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644p5697749.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: tapestry-push - proof of concept
Posted by Lance Java <la...@googlemail.com>.
Interesting to know you are thinking about push for tapestry. I know that DWR
have done quite a bit of work to abstract the underlying mechanism for push
(comet / polling / piggyback), do you think that you would roll-your-own
push mechanism or do you have a library in mind?
--
View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644p5697749.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: tapestry-push - proof of concept
Posted by Howard Lewis Ship <hl...@gmail.com>.
You might need to put a fake Request object into RequestGlobals for
Tapestry to be happy.
You can use existing (public) Tapestry services, and the component's
ComponentResources, to generate a Link object; plugging that link's
URL into the fake Request's path property and using the normal
Tapestry code paths should get you MOST of the way there.
My thinking for push in 5.4 may incorporate similar use cases to this
... but I'm mostly thinking in terms of leveraging client-side pubsub
when server-side events happen. Maybe part of that pubsub is delivery
of updated compone-t-rendered content.
On Wed, May 9, 2012 at 8:03 AM, Lance Java <la...@googlemail.com> wrote:
> Hi guys, I've been thinking about a "push" component for a while and I
> thought I might make a start when I got some free time. I will be using an
> abstraction on top of DWR's reverse ajax to achieve this.
>
> Basically, it will look something like this:
>
> ItemsComponent.tml
> <div>
> <t:zone t:id="zone" t:mixins="push" t:pushId="items-${user.id}"
> t:pushEvent="doPush">
> <t:loop source="items" item="item">${item.name}</t:loop>
> </t:zone>
> </div>
>
> public class ItemsComponent {
> @Property
> private List<Item> items;
>
> @Property
> private Item item;
>
> @SessionState
> @Property
> private User user;
>
> @InjectComponent
> private Zone zone;
>
> public Block doPush(List<Item> context) {
> this.items = context;
> return zone.getBody();
> }
> }
>
> And at some point, an asynchronous process will call
> PushService.doPush(Object pushId, Object pushContext) which will fire
> "doPush" and update the zone.
>
> As part of this, I will need to do the following FROM A NON WEB THREAD
> 1. Get a component / page instance (using a path/id I stored earlier)
> 2. Execute an event on the component / page instance
> 3. Get the resultant block and run it through tapestry's template engine
> 4. Use DWR's reverse ajax to update the zone with the html fragment.
>
> A couple of questions:
> 5. The push mixin will be storing the pushId and pushEvent in DWR's
> http://directwebremoting.org/dwr/javadoc/org/directwebremoting/ScriptSession.html
> ScriptSession . I will also need a String which will allow me to lookup a
> component / page at a later stage. Is there a component path that will
> uniquely identify the component page / instance?
> 6. I *think* that DWR has a HTTPServletRequest and HTTPServletResponse that
> I *might* be able to get a handle on for the push. Any ideas on how I would
> lookup the page / component / component resources?
>
> Cheers,
> Lance.
>
>
>
> --
> View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org