> > I need to map URLs from our old application to the new URLs in our 5.3
> > app. Yesterday I found this page:
> >
> > http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting-api/
>
> For rewriting incoming requests, but not for rewriting the URLs generated by
>
On Thu, 10 Mar 2016 10:55:41 -0300, Tony Nelson
wrote:
Hi All,
Hello, Tony!
I need to map URLs from our old application to the new URLs in our 5.3
app. Yesterday I found this page:
http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting-api/
For rewriting incoming requests
Hi All,
I need to map URLs from our old application to the new URLs in our 5.3 app.
Yesterday I found this page:
http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting-api/
Following that I wrote my first rewrite rule
/maintenance/agency_required_documents.htm?agencyId=86 to
the two context parameters.
That's where the strangeness of your PageLinks came from. If you actually
implemented it the way it should, all inside the URL rewriting code, you
shouldn't need to write strange, wrong PageLinks.
I'm assuming the total number of pages will
continu
="dealerProfile.profileDomain">Profile
>> About-Us
>>
>> in the end it looks like this
>> https://www.cardaddy.com/blue-marlin-motors
>> https://www.cardaddy.com/blue-marlin-motors/about-us
>>
>
> You can create the PageLinks to the original pa
arlin-motors/about-us
You can create the PageLinks to the original pages as long as you have
outgoing URL rewrite rules covering them. The whole point of URL rewriting
is to keep everything the same, but just have the URLs different.
If all the pages that need URL rewriting are put in the
Hi George,
is there a convincing reason to use the same page for these two URLs? To
get the same end result with tapestry-routing (
http://tynamo.org/tapestry-routing+guide), I'd create two pages and
annotate them like so:
@At("/{0}")
public class Profile {...}
@At("/{0}/{1}")
public class About
I ended up getting it working over the weekend, but boy does it seem like a
hack. I used some of your work to help me get going such as SimpleLink,
however I needed the parameters so I needed to complete the class.
I'll look into a second level cache as that seems to be a better solution
than what
On Sat, 15 Nov 2014 00:56:58 -0200, George Christman
wrote:
Example domain.com/profile/profiledomain
to
domain.com/profile
I do stuff very similar to this in Eloquentia
(https://github.com/thiagohp/eloquentia). See
https://github.com/thiagohp/eloquentia/tree/master/src/main/java/br/com/
Hi guys, so I've managed to find a someone challenging task. I'm creating
profiles and I'd like to create profile domains and do a url rewrite so
those domains appear directly after the baseUrl.
Example domain.com/profile/profiledomain
to
domain.com/profile
now the profiledomain will actually b
On Tue, 09 Sep 2014 10:26:00 -0300, squallmat .
wrote:
Ah ok yes, nothing to see with tapestry. Many of the url are entered by
user and then many of them don't have the http:// appended at beginning.
I need to rewrite them, or is there a way in html to make all
tags
to be read as absolu
gt;
>> - ${url}
>>
>>
>>
>> The value of ${url} in the href attribute is rewrote to concatenate the
>> actual displayed page url. Why is there url rewriting here ? And how can
>> I disable it ?
>>
>
> Tapestry itself doesn't rewrite anyth
layed page url. Why is there url rewriting here ? And how can
I disable it ?
Tapestry itself doesn't rewrite anything you include in the template
through ${} expansions. Have you checked what's really in the generated
HTML for that attribute or you just hovered the mouse over it?
Hi,
I have url stored in DB, like "www.google.com" and I just pass them in my
template to an href attribute, like this :
- ${url}
The value of ${url} in the href attribute is rewrote to concatenate the
actual displayed page url. Why is there url rewriting here ? And how can I
disable it ?
Hm...I see so it basically still uses the 'build' which in returns causes
my circular dependency
Thanks that is a good to know.
Cheers
On Thu, May 30, 2013 at 11:55 AM, Lance Java wrote:
> A "contribute" method builds up a Map, List or Collection prior to invoking
> the constructor of a servic
A "contribute" method builds up a Map, List or Collection prior to invoking
the constructor of a service. The Map, List or Collection is then passed
to the constructor of a service. The service must be annotated with one of
@UsesMappedConfiguration, @UsesOrderedConfiguration or @UsesConfiguration.
I understand the difference between decorator and builder method.
Actually i was using contribute as my weapon of choice and I guess I could
be lacking on the knowledge there. More specifically does contribution of
the method act more like decorator or builder.
Nonetheless I was able to make my de
Hi Boris, I'm not sure you have grasped the concept of an IOC decorator. A
decorator method name is prefixed with "decorate" and gets passed the
default implementation so that it can delegate through to it. It is
different to a "builder" method (prefixed with "build") which I think you
might be usi
Hi Lance,
I hope you see this as I have a question regarding your code (if anyone
else can answer I will be happy with that as well :))
I have created the implementation of the PageRenderLinkTransformer. This is
a simple implementation that checks for a few condition and then adds the
appropriate
I guess I am a bit tiered as I just manage to move the code from one
implementation to the other and it worked. So now PageRenderLinkTransformer
implementation can handle this transformation.
Thanks for the help everyone
On Tue, May 28, 2013 at 12:41 AM, Boris Horvat wrote:
> At first glance (a
At first glance (and small try) this look like something I can use. So here
is my idea.
I can use this interface "ComponentEventLinkEncoder" to contribute my own
logic that will strip the prefixed path from the link. However I am not
sure what should I return if dont want any transformation. Shoul
Not sure if this will help but thought it might be of interest. I've
written a ComponentEventLinkEncoder which looks for "special" URL prefixes.
If a "special" folder is found on the URL, it is removed from the URL and
passed on to the normal tapestry component rendering. The "special" folder
(whic
> >>
> >>
> >>
> >> On Mon, May 27, 2013 at 1:18 AM, Boris Horvat >wrote:
> >>
> >>> I spoke too soon. A bit of testing got me the answer that I can just
> >>> insert the folder as a string.
> >>>
> >>> Cheers
>
; t:page="MyPageThatIsNowInFolder1") and still use pagelink component?
>>
>> Cheers
>>
>>
>>
>> On Mon, May 27, 2013 at 1:18 AM, Boris Horvat
>> wrote:
>>
>>> I spoke too soon. A bit of testing got me the answer that I can just
>
der as a string.
>>
>> Cheers
>>
>>
>> On Mon, May 27, 2013 at 1:05 AM, Boris Horvat
>> wrote:
>>
>>> Hi all,
>>>
>>> I was looking into this example here
>>> http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting
; Hi all,
>>
>> I was looking into this example here
>> http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting-api/ however
>> I am not sure if what I want is possible as I am not really sure how to do
>> it.
>>
>> What I want to do is separate my app
I spoke too soon. A bit of testing got me the answer that I can just insert
the folder as a string.
Cheers
On Mon, May 27, 2013 at 1:05 AM, Boris Horvat wrote:
> Hi all,
>
> I was looking into this example here
> http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting-api/
Hi all,
I was looking into this example here
http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting-api/ however
I am not sure if what I want is possible as I am not really sure how to do
it.
What I want to do is separate my application into 2 folders but I need to
keep my urls as they
Excellent, thanks Thiago.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Basic-question-about-URL-rewriting-and-Tapestry-5-tp5691410p5720444.html
Sent from the Tapestry - User mailing list archive at Nabble.com
done much testing yet, but it passes the unit and integration tests. It's
not an implementation, just an adaption of the old URL rewriting code
present in Tapestry 5.1 so it can work in 5.3.
--
Thiago H. de Paula Figueiredo
-
Hi Thiago, has there been any progress with implementing the old API?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Basic-question-about-URL-rewriting-and-Tapestry-5-tp5691410p5720436.html
Sent from the Tapestry - User mailing list archive at Nabble.com
Yeah, I was quite dismayed when the old URL Rewriter API disappeared
to make way for the LinkTransformer - it'd be great if something
similar was resurrected!
In the mean time, I'm checking out Lance's suggestion.
Steve.
On 10 May 2012 20:40, Thiago H. de Paula Figueiredo wrote:
> On Thu, 10
On Thu, 10 May 2012 08:58:50 -0300, Steve Eynon
wrote:
It's just that implementing a LinkTransformer is lot of work and
constructing / deconstructing PageRenderRequestParameters from a raw
Request is not a simple task.
Whereas the external solutions offer a simple search / replace
functionali
FYI, I was able to do URL rewriting using simple string manipulation by
decorating the ComponentEventLinkEncoder
https://github.com/uklance/tapestry-sandbox/blob/master/src/main/java/com/github/uklance/mode/ModeComponentEventLinkEncoder.java
--
View this message in context:
http://tapestry
H. de Paula Figueiredo wrote:
> May I ask why external solutions to URL rewriting are always suggested when
> Tapestry provides a perfectly good one out-of-the-box and that can take
> advantage of all the Tapestry infrastructure?
>
>
> On Tue, 08 May 2012 07:07:32 -030
Thanks Steve.
I was also considering: http://ocpsoft.org/rewrite/
Julien.
2012/5/8 Steve Eynon
> I find Tuckey's Url Rewrite Filter a good option for simple rewrites:
>
> http://www.tuckey.org/urlrewrite/
>
> Steve.
> --
> Steve Eynon
> ---
> "If at first you don't su
I find Tuckey's Url Rewrite Filter a good option for simple rewrites:
http://www.tuckey.org/urlrewrite/
Steve.
--
Steve Eynon
---
"If at first you don't succeed,
so much for skydiving!"
On 8 May 2012 04:23, Julien Martin wrote:
> Thanks Thiago!
>
>
> 2012/5/7 Ju
Thanks Thiago!
2012/5/7 Julien Martin
> Thanks Thiago!
> I was not aware of that.
> J.
>
> 2012/5/7 Thiago H. de Paula Figueiredo
>
> On Mon, 07 May 2012 14:19:24 -0300, Julien Martin
>> wrote:
>>
>> Hi all!
>>>
>>
>> Hi!
>>
>>
>> @Thiago: My only concern is about SEO optimization. Can you
could directly render as in 3.
>> i.e. avoid the not so pretty URLs such as : (*
>> http://localhost:8080/ume-web/**fr/contactus.actionlink_1/en*<http://localhost:8080/ume-web/fr/contactus.actionlink_1/en*>
>> )
>>
>>
>> Is that possible through URL rewr
://localhost:8080/ume-web/en/contactus*
I am just wondering whether my action links could directly render as in
3.
i.e. avoid the not so pretty URLs such as : (*
http://localhost:8080/ume-web/fr/contactus.actionlink_1/en*)
Is that possible through URL rewriting? Perhaps using Igor Drobiazko&#
In this case you should use PageLink, instead of ActionLink.
Cezary
action links could directly render as in 3.
i.e. avoid the not so pretty URLs such as : (*
http://localhost:8080/ume-web/fr/contactus.actionlink_1/en*)
Is that possible through URL rewriting? Perhaps using Igor Drobiazko's
rewrite module? Can anyone please provide guidelines?
Regards,
J
ly so far.
Thanks for all the other tips!
Mike
From: Mike Dunbar
Sent: Monday, April 09, 2012 11:51 AM
To: 'users@tapestry.apache.org'
Subject: Need Help With Event URL Rewriting
Hi,
We are trying to build an application with RESTful URLs, rather than the
out-of-box Tapestry URLs. We&
On Mon, 09 Apr 2012 15:03:26 -0300, Mike Dunbar
wrote:
Hi Thiago, Thanks for your response. My replies inline below. -Mike
Why aren't the Tapestry URLs RESTful enough for your scenario? Using
PUT, DELETE, etc? Just curious. :)
I may be using the term 'RESTful' incorrectly. What I meant i
Hi Thiago, Thanks for your response. My replies inline below. -Mike
> Why aren't the Tapestry URLs RESTful enough for your scenario? Using PUT,
> DELETE, etc? Just curious. :)
I may be using the term 'RESTful' incorrectly. What I meant is suppose I have a
page that displays the details of an or
On Mon, 09 Apr 2012 12:51:19 -0300, Mike Dunbar
wrote:
Hi,
Hi!
We are trying to build an application with RESTful URLs, rather than the
out-of-box Tapestry URLs.
Why aren't the Tapestry URLs RESTful enough for your scenario? Using PUT,
DELETE, etc? Just curious. :)
We've been able
Hi,
We are trying to build an application with RESTful URLs, rather than the
out-of-box Tapestry URLs. We've been able to do this for our page URLs by using
Tynamo tapestry-routing (http://tynamo.org/tapestry-routing+guide). We would
like to do the same thing for the event link URLs contained on
So I dug through the source code, and the custom link transformation is spliced
in by way of an interceptor pattern (in TapestryModule):
@Match("ComponentEventLinkEncoder")
public ComponentEventLinkEncoder decorateLinkTransformer(LinkTransformer
linkTransformer,
Thanks Thiago!
On Jan 31, 2012, at 10:52 AM, Thiago H. de Paula Figueiredo wrote:
> On Tue, 31 Jan 2012 15:53:29 -0200, Jochen Frey wrote:
>
>> Excellent!
>>
>> But what let's say there's a 2nd link transformer, what happens to the
>> PageRenderRequestParameters that the two transformers retu
On Tue, 31 Jan 2012 15:53:29 -0200, Jochen Frey
wrote:
Excellent!
But what let's say there's a 2nd link transformer, what happens to the
PageRenderRequestParameters that the two transformers return? Would the
second one just inject an EventContext
The PageRenderRequestParameters retur
Excellent!
But what let's say there's a 2nd link transformer, what happens to the
PageRenderRequestParameters that the two transformers return? Would the second
one just inject an EventContext
@Inject
private EventContext eventContext;
and use it to generate the new EventContext? As well, wou
On Tue, 31 Jan 2012 15:35:13 -0200, Jochen Frey
wrote:
Let's say there's a page /SomeAccount/profile/SomeOtherVar, where
"SomeOtherVar" is supposed to go into the activation context as well ...
how would I handle that? Do I have the shot of augmenting the
activation context somewhere o
On Jan 31, 2012, at 2:39 AM, Thiago H. de Paula Figueiredo wrote:
> On Tue, 31 Jan 2012 03:50:49 -0200, Jochen Frey wrote:
>
>> Hi!
>
> Hi!
>
>> I am looking for a clean way to generically rewrite URLs as follows:
>>
>> Publicly we want to have an account name to be the first part of the pat
it in TS 5.1
(http://tapestry.apache.org/url-rewriting.html), but URLRewriterRule is
not supported any more.
Alternatively I could roll my own RequestFilter (like the TimingFilter),
but it seems there'd have to be a better way?
If you don't want to user LinkTransformer, I'd just co
eric rewrite along the lines of "if the path
> doesn't start with /login then rewrite the url". The effect would be that
> what was a path element becomes a variable (whether query variable or context
> I don't really know or care).
>
> I have seen Igor's
er query variable or context I don't
really know or care).
I have seen Igor's blog post
(http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting-api/). I have
two conceptual hurdles that I can't overcome and would love some help with:
After doing the path manipulation
null) {
result.addAll(Arrays.asList(values));
}
// the delegated parameters
values = super.getParameters(name);
if (values != null) {
result.addAll(Arrays.asList(values));
}
return result.isEmpty()?null:result.toArray(new String[0]);
}
}
--
View this
er? I don't want to end
up with /app/mypage/ID but /app/ID/mypage
Stephan
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/URL-rewriting-to-create-bookmarkable-URLs-tp3371226p3371288.html
Sent from the Tapestry - User mailing list archive at
The approach is described here:
http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting-api/
On Fri, Feb 4, 2011 at 4:56 PM, Stephan Schwab wrote:
>
> Unfortunately I've been a bit out of the loop since version 5.2.x came out.
> Hopefully someone can bring me up to
f course I don't want any URLs without the ID to leak out.
Stephan
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/URL-rewriting-to-create-bookmarkable-URLs-tp3371226p3371226.html
Sent from the Tapestry - User mailing list archiv
Hi Angelo
LinkTransformer is ready to use. Here is more info:
http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting-api/
I followed that post to write:
http://svn.tynamo.codehaus.org/browse/tynamo/trunk/tapestry-routing/src/main/java/org/tynamo/routing/services
Hi,
what is the status of url rewriting? 5.2.4 has LinkTransformer and the
urlwriting here :http://tapestry.apache.org/url-rewriting.html still uses
the URLRewriterRule which has been deprecated. is LinkTransformer ready to
use? any tutorial on this? Thanks,
Angelo
--
View this message in
Ok, I see. You want one of your activation methods to be called: either the
one with numeric context or the one with string context. As Thiago
suggested, just create an appropriate event context object and pass it.
BTW this can be implemented without the URL rewriting as well. Just provide
an
(id = "pageTemplate", parameters = { "node=currentNode"})
>> private PageTemplate pageTemplate;
>>
>> <…>
>> }
>>
>> On 08/09/2010, at 02:57, Igor Drobiazko wrote:
>>
>>> Hi,
>>>
>>
need to provide some more details. Are you trying to rewrite incoming
> > URLs?
> >
> > 2010/9/7 Marek Stanisław Wawrzyczny
> >
> >> Hi everyone,
> >>
> >> I hope you can help a Tapestry newbie here :)
> >>
> >> I've been f
Thanks Tiago,
I did see that Contenxt type before but didn't look into it since it's in the
internal package. I'll look into using ArrayEventContext.
Are there plans to make a public API to the EventContext manipulation or to
maybe create a new set of API for that purpose?
I would imagine tha
On Tue, 07 Sep 2010 22:30:58 -0300, Marek Stanisław Wawrzyczny
wrote:
Hi,
Hi!
Yes, I'm working with incoming links. The code I have so far:
I guess you're missing some ready-to-use, non internal EventContext
implementation. All them in Tapestry 5.1.0.5 (haven't had the time to try
5
2010/9/7 Marek Stanisław Wawrzyczny
>
>> Hi everyone,
>>
>> I hope you can help a Tapestry newbie here :)
>>
>> I've been following the blog post on how to use the new API (we're
>> developing a new app in 5.2)
>> http://blog.tapestry5
ing a new app in 5.2)
> http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting-api/ but
> for the life of me I can't figure out how to pass extracted URL parameters
> to the new page.
>
> So, say we have to rewrite //page/123 to //page?id=123, how do I
> pass t
Hi everyone,
I hope you can help a Tapestry newbie here :)
I've been following the blog post on how to use the new API (we're developing a
new app in 5.2)
http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting-api/ but for
the life of me I can't figure out how to pas
now all clear, thx
On Sat, 26 Dec 2009 16:18:23 -0200
"Thiago H. de Paula Figueiredo"
wrote:
Em Thu, 24 Dec 2009 16:03:50 -0200, Sergey Kashin
escreveu:
if i click submit button in form (name frm in page)
rewrite works not correctly:
url looks like /rewrited_tst/testpage but i expect url
Em Thu, 24 Dec 2009 16:03:50 -0200, Sergey Kashin escreveu:
if i click submit button in form (name frm in page)
rewrite works not correctly:
url looks like /rewrited_tst/testpage but i expect url like
/test/testpage
all other processed correctly
/rewrited_tst/testpage and expect /rewrited_ts
-0200
"Thiago H. de Paula Figueiredo"
wrote:
Em Thu, 24 Dec 2009 09:14:10 -0200, Sergey Kashin
escreveu:
Hello.
Hi!
All works fine except submit action. Tapestry redirect
to rewrite page
except original
if submit action occurs.
Example:
rule: rewrite /test to /test
mit action. Tapestry redirect
to rewrite page
except original
if submit action occurs.
Example:
rule: rewrite /test to /testRewrited
Are you rewriting /test.form to /testRewrited.form, for
example? URL rewriting is trickier than it sounds. ;)
Please post your rule implementation here so we ca
example? URL
rewriting is trickier than it sounds. ;)
Please post your rule implementation here so we can take a look at it. :)
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer
Hello.
I have create one simple rule for url rewriting.
as described in manual
http://tapestry.apache.org/tapestry5.1/guide/url-rewriting.html
All works fine except submit action. Tapestry redirect to
rewrite page except original
if submit action occurs.
Example:
rule: rewrite /test to
Em Fri, 16 Oct 2009 04:28:57 -0300, Alexander Reelsen
escreveu:
This is exactly what I want. But why does this not go "in line" with my
url rewriting question? If I have three parameters for the onactivate,
where else instead of the url are those constructed of?
That's what
u are looking for?
This is exactly what I want. But why does this not go "in line" with my
url rewriting question? If I have three parameters for the onactivate,
where else instead of the url are those constructed of? Do I need some
magic number in the url which represents the combina
Hi Alexander,
On Thu, Oct 15, 2009 at 11:11 PM, Alexander Reelsen wrote:
> Hi,
>
> after reading the new german book on Tapestry I am thinking to take a
> closer look at it. It is a very nice and clean structured book, which
> can be read quite easily at a rainy weekend. Very well done.
>
It's
annotation and using expression language like
Tapestry supports URL rewriting out-of-the-box:
http://tapestry.apache.org/tapestry5.1/guide/url-rewriting.html. Of
course, you'll need to provide the rewriting logic, and Tapestry does the
rest.
But what you're describing seems to be mo
Hi,
after reading the new german book on Tapestry I am thinking to take a
closer look at it. It is a very nice and clean structured book, which
can be read quite easily at a rainy weekend. Very well done.
One question I could not figure out from the book is a question
regarding complex url redire
Em Thu, 08 Oct 2009 18:48:40 -0300, Angelo Chen
escreveu:
Hi Thiago,
Hi!
Another question is, how do you rewrite a outgoing link without rewriting
the query parameters?
The URL rewriting itself is nothing more than receiving a Request instance
and returning another. You don't ne
ubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
>
--
View this message in context:
http://www.nabble.com/t5%3A-url-rewriting-and-query-paramete
s, you don't need to worry
> about them.
>
> --
> Thiago
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
>
--
View this message in context:
http://www.nabble.com/t5%
On Thu, Oct 8, 2009 at 11:11 AM, Angelo Chen wrote:
> Hi,
Hi!
> I'm rewriting a incoming url into:
> mypage/look.grid.pager/3?t:ac=0001/ABCD
Unless you're rewriting the query parameters, you don't need to worry
about them.
--
Thiago
-
ew this message in context:
http://www.nabble.com/t5%3A-url-rewriting-and-query-parameter-part-tp25803011p25803011.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail:
gt; done. This is much nicer way of doing things and came at a much lower
> efficiency hit than I first thought it would.
Service decoration rules!
> The URL rewriting code was helpful as an example of creating a new LinkImpl -
> I would not have noticed so quickly that the optimizer was n
efficiency hit than I first thought it would.
The URL rewriting code was helpful as an example of creating a new LinkImpl - I
would not have noticed so quickly that the optimizer was not necessary for the
new Link because it will already have done its job.
> -Original Message-
> Fr
bly needs to come later in
the flow of operations.
Robert
Hi Robert, I don't actually need to know the request type /if/ I can implement
bi-directional URL re-writing, as discussed. However, you may have a point...
the URL Rewriting implementation here is so low level as to be limited
3 [mailto:l...@grokers.net]
> Sent: 31 March 2009 17:19
> To: users@tapestry.apache.org
> Subject: RE: T5.1 URL Rewriting
>
>
>
>
> Hey Levi,
>
> That's almost identical to what I need for my application. Sorry I
> missed your post back in Feb, I had a two wee
is now.
That's why I was looking at URL rewriting to see if it was appropriate for this
task in 5.1 - I wasn't looking at the nightly docs though. Now I am and I can
see what Thiago means but I don't think URL rewriting is the right place to do
this. I'm leaning towards a custo
needs to come later in
the flow of operations.
Robert
Hi Robert, I don't actually need to know the request type /if/ I can implement
bi-directional URL re-writing, as discussed. However, you may have a point...
the URL Rewriting implementation here is so low level as to be limited
e. Perhaps try viewing your email as HTML or using nabble too?
Levi
--
View this message in context:
http://n2.nabble.com/T5.1-URL-Rewriting-tp2557652p2563802.html
Sent from the Tapestry Users mailing list archive at Nabble.com.
On Tue, Mar 31, 2009 at 11:53 AM, Thiago H. de Paula Figueiredo
wrote:
> On Tue, Mar 31, 2009 at 11:40 AM, Howard Lewis Ship wrote:
>> Another option would be to combine the URLRewriterRule with an enum to
>> define when it is in effect (INCOMING, OUTGOING, BOTH).
>
> I still prefer the context p
On Tue, Mar 31, 2009 at 11:40 AM, Howard Lewis Ship wrote:
> Another option would be to combine the URLRewriterRule with an enum to
> define when it is in effect (INCOMING, OUTGOING, BOTH).
I still prefer the context parameter option, so it can differentiate
page links from action links.
--
Thi
xfile80303
>> escreveu:
>>
>>> Okay this sounds like a plausible approach, but I'm confused about how I
>>> would identify the fact that my filter is being called to handle an
>>> incoming request (and remove the SITE) or a link generation request (and
>>
ernando Padilla would point out and I would agree 100% :),
> decorating services is almost always a good option. In this specific
> case, you would need to change the Link instances returned by
> ComponentEventLink methods, something that the URL rewriting support
> already does.
I ca
On Tue, Mar 31, 2009 at 6:26 AM, Blower, Andy
wrote:
> Now I am and I can see what Thiago means but I don't think URL rewriting is
> the right place to do this.
I don't think I said that. :)
> I'm leaning towards a custom implementation of
> ComponentEventLinkEnco
On Tue, Mar 31, 2009 at 1:21 AM, Robert Zeigler wrote:
> As a sort of nitpicky aside... does URLRewriterService have to be called
> that? (Since we're still in new feature api-change mode, here... :).
> What about just URLRewriter? Or URLRewriteHandler? Either of those seem to
> gel a little more
That's why I was looking at URL rewriting to see if it was appropriate for this
task in 5.1 - I wasn't looking at the nightly docs though. Now I am and I can
see what Thiago means but I don't think URL rewriting is the right place to do
this. I'm leaning towards a custo
1 - 100 of 131 matches
Mail list logo
