On Mon, 05 Jan 2015 12:59:16 -0200, George Christman
wrote:
I'm not sure why
I ended up finding an alternative to your simplelink approach that I
seem to like much better. I'd be curious as to your thoughts.
private Link buildLink(String basePath, PageRenderRequestParameters
parameters, St
I was a little confused, but I was able to resolve everything without issue.
On Mon, Jan 5, 2015 at 6:27 AM, Thiago H de Paula Figueiredo
wrote:
> On Mon, 29 Dec 2014 12:47:07 -0200, George Christman
> wrote:
>
>> Hi Thiago, The following approach does indeed work, but I'd like to
>> verify it t
On Mon, 29 Dec 2014 12:47:07 -0200, George Christman
wrote:
Hi Thiago, The following approach does indeed work, but I'd like to
verify it to be the correct approach for handling
ComponentEventLinkTransformer.
Looks good to me. :)
SimpleLink is basically the class you
wrote, I'm just not s
is there a more efficient way of
doing this?
One last thing, I see a Mapper service is being used in the nabble
example below. What does that service do?
Thanks
a couple of example sites I used
https://mail.google.com/mail/u/0/#search/label%3Atapestry+url+rewrite/14a22796d35779f0
http://apach
returns
>> "sell/buildlisting.form". How do I get the page to return
>> "/sell-car.form"?
>>
>
> For almost every incoming URL rewrite, you should write an outgoing
> (Tapestry-generated) URL rewrite too, otherwise the non-rewritten URLs
> still appe
ewriting the URL to
"/sell-car". When a form.error occures and the page reloads, it returns
"sell/buildlisting.form". How do I get the page to return
"/sell-car.form"?
For almost every incoming URL rewrite, you should write an outgoing
(Tapestry-generated) URL rewr
Hi, I'm doing some URL rewriting and I just discovered a new issue. I have
the following page rewritten to a new URL. "/sell/buildlisting/sell-car"
with "sell-car" being the context param and I'm rewriting the URL to
"/sell-car". When a form.error occures and the page reloads, it returns
"sell/buil
On Wed, 11 Jun 2014 12:25:43 -0300, Oliver Pelz
wrote:
Dear group,
Hi!
p.s.: I have also looked into this link here
http://tapestry.machina.com.br/2013/10/1/tapestry-url-rewriter-2-0-0-released
but this seem not to work for me.
I'm the author of it. Please define what "this seem not to
Dear group,
I am facing the problem that I want to rewrite a URL's domain, e.g.:
localhost:8080/Test -> helloworld:8080/Test
I am using T5.3.7 and looked into the new LinkTransformer API because
URLRewriterRule is deprecated (http://tapestry.apache.org/url-rewriting.html
)
Since there is not mu
Sorry, got it. I could use contributePageRenderLinkTransformer and
contributeComponentEventLinkTransformer.
--
Jens Reufsteck
Following Igors blog Ive added a PageRenderLinkTransformer to url
rewriting.
Now, Im trying to add also a ComponentEventLinkTransformer, but the method
@Contribute(PageRenderLinkTransformer.class)
@Primary
public static void provideURLRewriting(
OrderedConfigu
making it easier,, but now I see it wasn't a good idea. It
> > would even be simpler to implement the URL rewrite support with different
> > approaches for incoming and outgoing requests. :( My apologies.
> >
> >
>
>
> --
> View this message in context:
>
coming and
> outgoing URLs, making it easier,, but now I see it wasn't a good idea. It
> would even be simpler to implement the URL rewrite support with different
> approaches for incoming and outgoing requests. :( My apologies.
>
>
--
View this message in context:
http:/
On Fri, 21 Oct 2011 10:52:42 -0200, captain_rhino
wrote:
Thankls for your advice.
I can see how you would capture request information using
ActivationRequestParameter but cannot see how in a page context you
would
add parameters in the same way that addparameter works on a link?
(PolicySignin.class);
link.addParameter("x", "123");
link.addParameter("y", "123");
return link;
Do you have an example?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Page-url-rewrite-tp4924085p4924603.html
Se
Just one advice: adding query strings isn't URL rewrite at all. Instead,
it's when you want some URL to be processed as if it was another. Example:
/page.html?id=1 to be processed by Tapestry as /page/1.
In addition, if you need just one or two query parameters, I'd use the
dParameter("x", "123");
>link.addParameter("y", "123");
>return link;
>
>}
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nab
=
linkSource.createPageRenderLinkWithContext(PolicySignin.class);
link.addParameter("x", "123");
link.addParameter("y", "123");
return link;
}
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Page-url-
transformPageRenderLink methods but do not know how to
pass a parmeter value through to this method.
thx for any assistance.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Page-url-rewrite-tp4924085p4924085.html
Sent from the Tapestry - User mailing list archive at Nabble.com
outgoing
> URLs, making it easier,, but now I see it wasn't a good idea. It would even
> be simpler to implement the URL rewrite support with different approaches
> for incoming and outgoing requests. :( My apologies.
>
> --
> Thiago H. de Paula Figueiredo
> Independent Ja
Hi Thiago,
2010/2/23 Thiago H. de Paula Figueiredo
> My apologies.
>
you should'nt apologize! Your solution is working well for many cases.
Besides: An existing improvable solution is better than the nonexisting
perfect solution. So: Thank you for your engagement.
Felix
le, that adds a Link rewrite(Link link) method. My original plan
> was to provide the user the same way of dealing with incoming and outgoing
> URLs, making it easier,, but now I see it wasn't a good idea. It would even
> be simpler to implement the URL rewrite support with different
g and
outgoing URLs, making it easier,, but now I see it wasn't a good idea. It
would even be simpler to implement the URL rewrite support with different
approaches for incoming and outgoing requests. :( My apologies.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and
I agree that I'm a bit unhappy with the current API, but we now have a
larger issue: backwards compatibility (from 5.1 to 5.2). We may
eventually deprecate the current approach and create an improved
approach and maintain both for one release.
On Mon, Feb 8, 2010 at 12:31 PM, Josh Canfield wrote
Hi, I spent some time recently digging around in the URLRewrite code
to track down the bug with forms. I had used this interface previously
but didn't stop to think about it until I was knee deep in the code.
I'm curious about the inspiration for implementation and interface. It
really makes no se
just a guess - try zoeken
On Tue, Mar 10, 2009 at 11:08 PM, Britske wrote:
>
> I saw a recent post about setting up Tuckey url-rewrite filter to set up some
> url rewriting in conjuction with Tapestry so decided to try it out.
>
> All works fine when using 'redirect
I saw a recent post about setting up Tuckey url-rewrite filter to set up some
url rewriting in conjuction with Tapestry so decided to try it out.
All works fine when using 'redirects':
/test
/zoeken
However the real power (in my opinion) comes with forwardin
27 matches
Mail list logo
