Well i guess the onPassivate-method isn't entirely out of the question since
it gives a central place to handle this on the page-level as well. The
tagging-variant seems nicer though. I thought i read somewhere in the
documentation that a 'client-side persistence strategy' was on the horizon,
which would include 'automagically' inserting persistent fields into the
url. I can't find anymore where i've read it though. 

Since we're talking about updating / changing the url, in a somehwat related
post i asked about possibilities for rewriting the url. (I havn't found time
to try to resolve this) 
http://www.nabble.com/url-rewriting-in-Tapestry-5-tf4496726.html#a12823397

from that post: 

For example I want a Venue bean with name venueX and id=123 to show up as:
http://test.com/venue/countryname/cityname/venux/123

Notice the countryname and cityname, which aren't fields of the Venue-page
but are derived from the association venue-page--> venue--> city -->
country. 

I think adapting the onPassivate-method for inserting these values into the
url and onActivate() for only parsing the necessary fields from this url is
all that is needed to get this to work, is this correct? 
btw: a Url-rwrite filtr for this won't work because i also want to have the
translation the other way around.: not only from nice --> tapestry internal
but also from tapestry internal --> nice. Url-rewrite only gives me the
former. 

Later on i would like to strip the first /venue/  -->
http://test.com/venue/countryname/cityname/venux/123 would become
http://test.com/countryname/cityname/venux/123. 

This becomes harder, because tapestry now doesn't know anymore to which page
to redirect. out-of-the-box it starts searching for a page with
<countryname>. I guess for this I have to dig a little deeper. 

Hmm, in hindsight i believe this isn't at all a coherent post, with almost
no question or conclusion to be found... consider this a kind of braindump
;-)

cheers,
Geert-Jan




  



Josh Canfield-2 wrote:
> 
> Ok, and you want to do this without implementing a passivate method on
> page
> B...
> 
> That doesn't seem like a trivial problem to solve, especially in a safe
> and
> general way. I'm pretty sure nothing like that exists now, but I believe
> all
> the hooks are available to create your own annotations so you could do the
> implementation. If I were going to attempt this I'd start by looking at
> adding new activate/passivate methods via the class transform worker...
> 
> There are a lot of issues to deal with... but you could start by taking a
> look at
> http://tapestry.apache.org/tapestry5/apidocs/org/apache/tapestry/services/ComponentClassTransformWorker.html
> 
> and the source for the @Environmental annotation might help
> http://tapestry.apache.org/tapestry5/apidocs/src-html/org/apache/tapestry/internal/services/EnvironmentalWorker.html
> 
> Good luck,
> Josh
> 
> 
> On 10/18/07, Britske <[EMAIL PROTECTED]> wrote:
>>
>>
>> that would require a lot of manual labor for each and every link.
>>
>> btw: my question relates to T5.
>>
>> Say i had page B injected into page A.
>> I could then initialize page B and return page B from some eventhandler
>> on
>> page A.
>> What I would want to accomplish is that this automatically results in
>> redirecting to page B (as normal) with the difference that the url of
>> page
>> B
>> shows my predefined fields of page B in the url (I know I mentioned
>> querystring in the subjectheader, i mean the path-part of the url)
>>
>> The mechanism could know this because at designtime I could have tagged
>> the
>> fields of page B that I wanted to include in the url. This would enable
>> me
>> to once define these fields at design-time and not having to worry about
>> it
>> later on.
>>
>> is anything like this out there, or planned at all?
>>
>> Thanks in advance,
>> Geert-Jan
>>
>>
>> Josh Canfield-2 wrote:
>> >
>> > If you want to parameters to the query string then you can create a
>> link
>> > and
>> > add parameters to it from within your page.
>> >
>> >
>> http://tapestry.apache.org/tapestry5/apidocs/org/apache/tapestry/Link.html
>> >
>> >
>> > Josh
>> >
>> > On 10/18/07, Britske <[EMAIL PROTECTED]> wrote:
>> >>
>> >>
>> >> okay, I like peristent data very much. On the other hand I want to
>> have
>> >> pages
>> >> in which several persistent properties are encoded into the
>> querystring
>> >> (for
>> >> better bookmarking and other requirements from a user-perspective).
>> >>
>> >> so my question is:
>> >> is there a way to encode / decode certain persistent properties into
>> the
>> >> querystring? The best would be a way without having to change the
>> >> onActivate
>> >> and onPassivate-methods of course...
>> >>
>> >> Thanks in advance,
>> >> Geert-Jan
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/how-to-have-persistent-data-in-querystring--tf4646238.html#a13272192
>> >> Sent from the Tapestry - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>
>> >>
>> >
>> >
>> > --
>> > --
>> > TheDailyTube.com. Sign up and get the best new videos on the internet
>> > delivered fresh to your inbox.
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/how-to-have-persistent-data-in-querystring--tf4646238.html#a13280217
>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 
> -- 
> --
> TheDailyTube.com. Sign up and get the best new videos on the internet
> delivered fresh to your inbox.
> 
> 

-- 
View this message in context: 
http://www.nabble.com/how-to-have-persistent-data-in-querystring--tf4646238.html#a13289335
Sent from the Tapestry - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to