I have solved most of this problem by adding a request filter [1] that
sets the PersistentLocale on every request and thus adding the locale to
every url throughout the application. Though /url and /en/url still have
duplicate content, nothing in my app links to /url anymore so google
won't
Hello Joost,
Have you considered using the:
link rel=canonical href=http://www.yourdomain.com/index.html;/link
Mechanism? Google had a nice post on their webmaster central blog
(http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html).
We had quite similar problems with
Thank you Niclas,
Sounds a lot better than redirecting.
Cheers,
Joost
niclas.me...@scoyo.com wrote:
Hello Joost,
Have you considered using the:
link rel=canonical href=http://www.yourdomain.com/index.html;/link
Mechanism? Google had a nice post on their webmaster central blog
Hi,
if you don't use maven you have to provide yourself also all the required
dependencies. (See http://t5-easy-fckeditor.kenai.com/dependencies.html to
view the list of dependencies.)
The jar must be in the project libraries so that the jar is accessible to T5
during runtime, so adding it to
Hi there,
Ive checked the archive and havent been able to find anything that
answers this so here goes...
Im just discovering T5 and have a query regarding the T5 page object and
how it maintains state (without using the session) from render -
through the user interacting with the browser - to
Depends on where your list gets instantiated and populated. I can only guess, but you are probably
filling it with some values in onActivate(), right? This happens every time that page is used to
handle a specific request, be it a page render or a form submit. That's where your state comes from.
Hi,
Can anyone advise on the preferred way of persisting state between pages
without using HTTP Session? PageActivationContext using Object[] looks
promising but I don't want long urls (from serialized objects) and there is
more data to share than a defined number of keys - I'm looking for
Is anyone doing this? It's listed as a feature on the lead page at
http://tapestry.apache.org/tapestry5/:
... Tapestry Services can now be injected into Spring Beans
Any examples anywhere that could be pointed to? Muchos thanks.
Regards,
Jim.
-Original Message-
From: Jim O'Callaghan
Cookies come to mind, would that be an option?
On Wed, Jan 6, 2010 at 2:16 PM, Jim O'Callaghan jc1000...@yahoo.co.uk wrote:
Hi,
Can anyone advise on the preferred way of persisting state between pages
without using HTTP Session? PageActivationContext using Object[] looks
promising but I
Use setters and the @InjectPage annotation.
@InjectPage private MyPage resultpage;
Object onActionFromSomeComponent()
{
resultpage.setSomething(something);
return resultpage;
}
Uli
On 06.01.2010 14:16 schrieb Jim O'Callaghan:
Hi,
Can anyone advise on the preferred way of persisting
Lutz,
Thanks for the response - Cookies would be a last resort - I don't want to be
managing cookies and also feel it makes the app more breakable (fundamental
state could be broken with browser security settings). What I'm after is
something akin to PageActivationContext but that passes the
Thanks Ulrich. Do you think it is realistic to have an entire application
use this approach as a method for sharing state between pages?, i.e. every
page is injected, or is there a downside to this?
Regards,
Jim.
-Original Message-
From: Ulrich Stärk [mailto:u...@spielviel.de]
Sent: 06
Jim
I have injected spring beans using:
@Inject @Autowired
private Service MyService;
I had problems when i wanted to inject services using @InjectService
for some reason the services were not injected. I had to use
Annotation markers and then the injection worked.
Be sure u r NOT using
Em Wed, 06 Jan 2010 12:13:04 -0200, Angelo Chen
angelochen...@yahoo.com.hk escreveu:
Hi,
Hi!
This might be a little off topic here, sorry.
at Playframework(http://www.playframework.org/), it is simple, and fun to
use as well.
I've read the documentation and I haven't found a word
Em Wed, 06 Jan 2010 11:16:23 -0200, Jim O'Callaghan
jc1000...@yahoo.co.uk escreveu:
Hi,
Hi!
Can anyone advise on the preferred way of persisting state between pages
without using HTTP Session? PageActivationContext using Object[] looks
promising but I don't want long urls (from
Em Wed, 06 Jan 2010 12:04:44 -0200, Jim O'Callaghan
jc1000...@yahoo.co.uk escreveu:
What I'm after is something akin to PageActivationContext but that
passes the relevant object(s) using Request parameters rather than the
querystring / url - thanks.
Take a look at the
I forgot that in order to store the object until the result page is being rendered, you'll need to
somehow persist it. That would happen in the session again. So this is not an option for you.
By the way: why do you want to avoid using the session at all costs?
Uli
On 06.01.2010 15:07 schrieb
I see. There wouldn't be much handling, though, one could probably
implement a cookie persistence strategy, so that you could use the
@Persist annotation. Doesn't that even exist already?
The thing you are in favor of, using post.. there'll be some
disadvantages. I assume you won't be using
Thanks for the responses Thiago. I'll have a look at the
LinkCreationListener you suggested in your other email. Regarding the
response below, does the approach not make an assumption that the objects I
am trying to share between pages are persisted objects with a key(id)/value
relationship?
Ulrich,
This is informative thanks. Regarding avoiding using the session - it's not
something I need to do at all costs - I am in the early stages of an
application design and want to ensure the session usage is kept to a minimum
as there may be a requirement to cluster at some stage - I had
Lutz,
You raise some very interesting points. I've replied to some of the other
posters regarding the reasons I was trying to minimise session use, though
taking their replies on board and your own email I think the best course of
action is to proceed with using the session state and just
You might want to have a look at the Clustering Issues section of [1]. Tapestry already has some
mechanisms built-in to help you with deciding when your session attributes have changed and need to
be propagated to the other cluster nodes. Of course, keeping the amount of information stored
Jim,
You still have some different options to pursue in a cluster..
- sticky sessions, so that requests of the same user will go to the
same server in the cluster. Good for load balancing, but if a server
fails, the users of that server will loose their session.
- session replication in the
I have an issue using the datefield - a similar issue was reported by matt22
on Dec 15, 2009 . When a date is selected from the calendar, I get the
following error:
Communication with the server failed: null
# Ajax failure: Status 400
Could this be caused by the url-pattern of
Ulrich, Lutz,
Thanks for the very informative replies. Hopefully they will be useful to
others also.
Regards,
Jim.
-Original Message-
From: Lutz Hühnken [mailto:lh.tapestry.l...@googlemail.com]
Sent: 06 January 2010 15:56
To: Tapestry users
Subject: Re: Persisting state without HTTP
Hi,
I am facing a problem related to the design of FieldTranslatorSourceImpl
internal class design.
I would like to adivse one of the method to pass my own modified instance of
Translator, but actually the adivor does'nt work for this method because the
public method (from the interface) is
I don't know if this qualifies as a bug, I think not ... having a
service call one of its own methods via its proxy is not unreasonable
(and should be supported) BUT would not be the normal case and would
need to see a use case for it (which is why I really like interfaces
with just one method :-)
Thanks for the details Howard - I'll keep an eye on this one.
Regards,
Jim.
-Original Message-
From: Howard Lewis Ship [mailto:hls...@gmail.com]
Sent: 06 January 2010 18:44
To: Tapestry users
Subject: Re: Persisting state without HTTP Session
Something I'm hoping to put together as
You should add a prefix consisting of the field id (and optionally the form
id). In your example you should try to provide a key:
quantity-integer-format-exception.
Let's say the id of your form is 'myform', then
myform-quantity-integer-format-exception is also going to work.
--
Best regards,
29 matches
Mail list logo
