/app/page:anyEvent => will fire an event named "anyEvent" on the Page.
This method returns void.
At the end of this event, tapestry issues redirect, and rendering should
happen in that request.
And you are correct that I don't see this URL and I see the final redirected
page URL.
In the abov
See that's the weird part..
1) render page form:
/myapp/page1
2) submit form:
/myapp/page1.form:action
3) form handles submit(fail or success),
then returns redirect to render page:
redirect:/myapp/page1
4) page 1 is rendered once more.
So I'm a little confused.. since you mention another ev
Thanks for the reply!
I see there only two render pipelines in the TapestryModule.java. One is
contributeMarkupRenderer and another one is contributePartialMarkupRenderer.
PartialMarkupRenderer uses "PartialMarkupDocumentLinker" as the Document
Linker. And PartialMarkupDocumentLinker generates
Sorry for the wait. I don't have the final answer for you, but I do
have information to share.. :)
I think it'll be the same technique of overriding tapestry's document
linker, but there are two render pipelines, so you have to find the
correct place to contribute..
Don't forget that Tapes
Can anybody throw some light on this issue? I am stuck and not moving
forward...
Dude.Checkitout wrote:
>
> Fernando, need your expertise help! I thought the following trick
> configuration.add( "CustomDocumentLinker", mydoclinker,
> "after:DocumentLinker,before:RenderSupport" );
> worked.
Fernando, need your expertise help! I thought the following trick
configuration.add( "CustomDocumentLinker", mydoclinker,
"after:DocumentLinker,before:RenderSupport" );
worked.
Looks like it is not working in all conditions. It runs fine for a while,
then out of nowhere I start getting the sa
yah, this is little confusing, since it will place the CustomLinker
first in the list of filters.. :) But they "execute" as they come out
of the list.. :)
CustomLinker -> DocumentLinker -> RenderSupport -> PAGERENDER
So as the page render unfurls, it gives control to RenderSupport to
modify
Fernando fix did the trick.
configuration.add( "CustomDocumentLinker", mydoclinker,
"after:DocumentLinker,before:RenderSupport" );
Thanks a lot! I am missing the "override" option in 5.0.18!
Fernando Padilla wrote:
>
> To be honest, I can't remember exactly when the override came into p
Posted the earlier question before reading your post. Here is the code in my
AppModule:
public void
contributeMarkupRenderer(OrderedConfiguration
configuration,
@Symbol(SymbolConstants.PRODUCTION_MODE)
final boolean productionMode,
@Symbol(SymbolConstants
Em Thu, 29 Jan 2009 15:14:40 -0300, Fernando Padilla
escreveu:
No. DocumentLinker would be run first ( deeper in the markup filter
chain ), it would be the only one that RenderSupport would bind to (
RenderSupport does a environment.peekRequired ). So only that
DocumentLinker would do
To be honest, I can't remember exactly when the override came into play
( so it might be worth double checking with eclipse, though I'm pretty
sure it's 5.1.0.0 ).
The other option is to place your DocumentLinker in between the default
DocumentLinker and RenderSupport. Maybe try this:
confi
No. DocumentLinker would be run first ( deeper in the markup filter
chain ), it would be the only one that RenderSupport would bind to (
RenderSupport does a environment.peekRequired ). So only that
DocumentLinker would do it's stuff. and the default DocumentLinker
throws an exception if the
I am using 5.0.18 version and not ready to move to 5.1 yet. Is there any way
to override the DocumentLinker in the 5.0.18 version?
Fernando Padilla wrote:
>
> Ok cool.
>
> with the latest version of tapestry (5.1.0.0-SNAPSHOT), they did add a
> proper way to override contributions. Below is
Em Thu, 29 Jan 2009 14:42:47 -0300, Dude.Checkitout
escreveu:
I created my own CustomDocumentLinker extending from the tapestry
DocumentLinker and modified the code to fit our needs. But I have no idea
how to make Tapestry to use CustomerDocumentLinker instead of its own
DocumentLinker.
Con
Ok cool.
with the latest version of tapestry (5.1.0.0-SNAPSHOT), they did add a
proper way to override contributions. Below is the code we're using for
us to override our DocumentLinker. Please be aware that the override
works, but it seems to trash all of the previous relative directives (
Thank you for the quick reply. We are using tapestry to generate a section of
a html page. We can enforce the requirement of having an root node.
Basically, the requirement will be to accept the root node to be anything.
(not only html)
I created my own CustomDocumentLinker extending from the ta
I have lots of experience playing with that :) (since we publish to
html, fbml). Here are some questions:
1) do your documents have a root node? what is it?
2) do you want to change the behavior of how it includes javascript and
css? Or just have it work with non-html root nodes?
Dude.
We have a requirement of tml file being delivered without as the root
context. As I read the tapestry source, this validation is done in the
DocumentLinker.
In contributeMarkupRenderer method:
MarkupRendererFilter documentLinker = new MarkupRendererFilter()
{
public v
18 matches
Mail list logo
