Sorry that I am new to Wicket and may not know what the greatest values of
wicket are supposed to be.
We are evaluating different web frameworks right now and Wicket is one of
them.
One good and attracting point of Wicket to us is that it can separate
html/design and logic at a good way.
The
1.3 is what i would look at, the current trunk in our svn. we just had a
1.3.0-beta release in apache incubator. 1.2.x doesnt have stateless support.
there are numerous threads on this list that try to disprove the session is
evil myth. so i would search the list for those first, before i made
in 1.3 you still can use getSession() and set the locale
But then you need to set it everytime because the session is created
everytime
if the pages are all stateless. So then you still can work with the normal
Wicket session object
Creating a wicket session object doesn't mean you create a http
in 1.3 you still can use getSession() and set the locale
But then you need to set it everytime because the session is created
everytime
if the pages are all stateless. So then you still can work with the normal
Wicket session object
Creating a wicket session object doesn't mean you create a
Dear all,
I have read the wicket examples, wiki, mail lists, etc and it seems that if
I need to expliclity change the locale, i need to write codes like:
getSession().setLocale(my locale);
Now, I can determine the explicity language/locale need to use from the
incoming URL.
I want to use
Can I ask why you don't want to store the locale in the session? It
seems that the locale is unarguably session-specific.
Cheers,
Scott
On 5/3/07, ywtsang [EMAIL PROTECTED] wrote:
Dear all,
I have read the wicket examples, wiki, mail lists, etc and it seems that if
I need to expliclity
you can override page.getlocale() and return something based on page
parameters. havent tried it but sounds like it should work.
-igor
On 5/3/07, ywtsang [EMAIL PROTECTED] wrote:
Dear all,
I have read the wicket examples, wiki, mail lists, etc and it seems that
if
I need to expliclity
One of the requirements of my project is not to use session, that's why my
question is so :)
Our website will have different language. Customers can choose for different
languages by clicking links like:
e.g.
/en/... (show english content)
/jp/... (show japanese content)
/kr/... (show korean
tbh i see little value of using wicket in a completely stateless
application. the big advantage of wicket is the programming model it offers,
which you give up when using stateless only components.
-igor
On 5/3/07, ywtsang [EMAIL PROTECTED] wrote:
One of the requirements of my project is
