Re: Hide page version query parameters

2012-01-01 Thread martin.dilger
Yes, thats right, stateless pages do not have version number,  
but normally it is not so easy to make pages stateless, we always had
problems with that.

But if you change your render strategy to redirect to render, the uri in the
browser does not change and you always have clean uris. Thats how we solved
the problem.

Just try this in your Applications init Method:
getRequestCycleSettings().setRenderStrategy(RenderStrategy.REDIRECT_TO_RENDER);

You should be aware of the side effects of different render strategies, just
look in Javadoc of RenderStrategy.

Regards

MArtin

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Hide-page-version-query-parameters-tp4163099p4251018.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Can't build wicket from updated trunk

2012-01-01 Thread Chris Colman
I have done a recent update on my working copy of the trunk and mvn
clean install yields:
 
Project ID: org.apache.wicket:wicket-ioc
POM Location: C:\dev\libs\wicket\trunk\wicket-ioc\pom.xml
Validation Messages:
 
[0]  'dependencies.dependency.version' is missing for
javax.inject:javax.inject:jar
 
 
Have I done something wrong or do I need to upgrade to a later JDK
(currently 1.6.0_29-b11)?
 
Yours sincerely,
 
Chris Colman
 
Pagebloom Team Leader,
Step Ahead Software

 
pagebloom - your business  your website growing together
 
Sydney: (+61 2) 9656 1278 Canberra: (+61 2) 6100 2120 
Email: chr...@stepahead.com.au mailto://chr...@stepahead.com.au 
Website:
http://www.pagebloom.com blocked::http://www.pagebloom.com/ 
http://develop.stepaheadsoftware.com
blocked::http://develop.stepaheadsoftware.com/ 
 
 


Re: Can't build wicket from updated trunk

2012-01-01 Thread Igor Vaynberg
clone the project from here:
http://git-wip-us.apache.org/repos/asf/wicket

-igor

On Sun, Jan 1, 2012 at 6:09 PM, Chris Colman
chr...@stepaheadsoftware.comwrote:

 ** **

 I have done a recent update on my working copy of the trunk and mvn clean
 install yields:

 ** **

 Project ID: org.apache.wicket:wicket-ioc

 POM Location: C:\dev\libs\wicket\trunk\wicket-ioc\pom.xml

 Validation Messages:

 ** **

 [0]  'dependencies.dependency.version' is missing for
 javax.inject:javax.inject:jar

 ** **

 ** **

 Have I done something wrong or do I need to upgrade to a later JDK
 (currently 1.6.0_29-b11)?

 ** **

 Yours sincerely,

 ** **

 Chris Colman

  

 Pagebloom Team Leader,

 Step Ahead Software

 

 pagebloom - your business  your website growing together

 ** **

 **Sydney**: (+61 2) 9656 1278 Canberra: (+61 2) 6100 2120
 

 Email: chr...@stepahead.com.au //chr...@stepahead.com.au

 Website:

 http://www.pagebloom.com

 http://develop.stepaheadsoftware.com

  

 ** **



RE: Can't build wicket from updated trunk

2012-01-01 Thread Chris Colman
Is Wicket moving to git?

Chris

-Original Message-
From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
Sent: Monday, 2 January 2012 2:24 PM
To: users@wicket.apache.org
Subject: Re: Can't build wicket from updated trunk

clone the project from here:
http://git-wip-us.apache.org/repos/asf/wicket

-igor

On Sun, Jan 1, 2012 at 6:09 PM, Chris Colman
chr...@stepaheadsoftware.comwrote:

 ** **

 I have done a recent update on my working copy of the trunk and mvn
clean
 install yields:

 ** **

 Project ID: org.apache.wicket:wicket-ioc

 POM Location: C:\dev\libs\wicket\trunk\wicket-ioc\pom.xml

 Validation Messages:

 ** **

 [0]  'dependencies.dependency.version' is missing for
 javax.inject:javax.inject:jar

 ** **

 ** **

 Have I done something wrong or do I need to upgrade to a later JDK
 (currently 1.6.0_29-b11)?

 ** **

 Yours sincerely,

 ** **

 Chris Colman

  

 Pagebloom Team Leader,

 Step Ahead Software

 

 pagebloom - your business  your website growing together

 ** **

 **Sydney**: (+61 2) 9656 1278 Canberra: (+61 2) 6100 2120
 

 Email: chr...@stepahead.com.au //chr...@stepahead.com.au

 Website:

 http://www.pagebloom.com

 http://develop.stepaheadsoftware.com

  

 ** **


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Can't build wicket from updated trunk

2012-01-01 Thread Igor Vaynberg
already moved.

-igor

On Sun, Jan 1, 2012 at 7:31 PM, Chris Colman
chr...@stepaheadsoftware.com wrote:
 Is Wicket moving to git?

 Chris

-Original Message-
From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
Sent: Monday, 2 January 2012 2:24 PM
To: users@wicket.apache.org
Subject: Re: Can't build wicket from updated trunk

clone the project from here:
http://git-wip-us.apache.org/repos/asf/wicket

-igor

On Sun, Jan 1, 2012 at 6:09 PM, Chris Colman
chr...@stepaheadsoftware.comwrote:

 ** **

 I have done a recent update on my working copy of the trunk and mvn
 clean
 install yields:

 ** **

 Project ID: org.apache.wicket:wicket-ioc

 POM Location: C:\dev\libs\wicket\trunk\wicket-ioc\pom.xml

 Validation Messages:

 ** **

     [0]  'dependencies.dependency.version' is missing for
 javax.inject:javax.inject:jar

 ** **

 ** **

 Have I done something wrong or do I need to upgrade to a later JDK
 (currently 1.6.0_29-b11)?

 ** **

 Yours sincerely,

 ** **

 Chris Colman

  

 Pagebloom Team Leader,

 Step Ahead Software

 

 pagebloom - your business  your website growing together

 ** **

 **Sydney**: (+61 2) 9656 1278     Canberra: (+61 2) 6100 2120
 

 Email: chr...@stepahead.com.au //chr...@stepahead.com.au

 Website:

 http://www.pagebloom.com

 http://develop.stepaheadsoftware.com

  

 ** **


 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



RE: Can't build wicket from updated trunk

2012-01-01 Thread Chris Colman
I cloned the wicket git repos and then checked out branch wicket-1.5.x branch 
and the build broke in a different place (it got a bit further this time :)  )

The build was done on a Windows XP box with 4GB RAM so I wouldn't have thought 
it would have run out of memory.

[INFO] 1 error
[INFO] -
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] Compilation failure
Failure executing javac, but could not parse the error:


The system is out of resources.
Consult the following stack trace for details.
java.lang.OutOfMemoryError: Java heap space
at com.sun.tools.javac.code.Scope$ImportScope.makeEntry(Scope.java:385)
at com.sun.tools.javac.code.Scope.enter(Scope.java:196)
at com.sun.tools.javac.code.Scope.enter(Scope.java:183)
at com.sun.tools.javac.comp.MemberEnter.importAll(MemberEnter.java:132)
at 
com.sun.tools.javac.comp.MemberEnter.visitTopLevel(MemberEnter.java:509)
at 
com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:446)
at 
com.sun.tools.javac.comp.MemberEnter.memberEnter(MemberEnter.java:387)
at com.sun.tools.javac.comp.MemberEnter.complete(MemberEnter.java:819)
at com.sun.tools.javac.code.Symbol.complete(Symbol.java:386)
at com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:758)
at com.sun.tools.javac.comp.Enter.complete(Enter.java:451)
at com.sun.tools.javac.comp.Enter.main(Enter.java:429)
at 
com.sun.tools.javac.main.JavaCompiler.enterTrees(JavaCompiler.java:819)
at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:727)
at com.sun.tools.javac.main.Main.compile(Main.java:353)
at com.sun.tools.javac.main.Main.compile(Main.java:279)
at com.sun.tools.javac.main.Main.compile(Main.java:270)
at com.sun.tools.javac.Main.compile(Main.java:87)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:554)
at 
org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:161)
at 
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:605)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)

-Original Message-
From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
Sent: Monday, 2 January 2012 2:50 PM
To: users@wicket.apache.org
Subject: Re: Can't build wicket from updated trunk

already moved.

-igor

On Sun, Jan 1, 2012 at 7:31 PM, Chris Colman
chr...@stepaheadsoftware.com wrote:
 Is Wicket moving to git?

 Chris

-Original Message-
From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
Sent: Monday, 2 January 2012 2:24 PM
To: users@wicket.apache.org
Subject: Re: Can't build wicket from updated trunk

clone the project from here:
http://git-wip-us.apache.org/repos/asf/wicket

-igor

On Sun, Jan 1, 2012 at 6:09 PM, Chris Colman
chr...@stepaheadsoftware.comwrote:

 ** **

 I have done a recent update on my working copy of the trunk and mvn
 clean
 install yields:

 ** **

 Project ID: org.apache.wicket:wicket-ioc

 POM Location: C:\dev\libs\wicket\trunk\wicket-ioc\pom.xml

 Validation Messages:

 ** **

     [0]  'dependencies.dependency.version' is missing for
 javax.inject:javax.inject:jar

 ** **

 ** **

 Have I done something wrong or do I need to upgrade to a later JDK
 (currently 1.6.0_29-b11)?

 ** **

 Yours sincerely,

 ** **

 Chris Colman

  

 Pagebloom Team Leader,

 Step Ahead Software

 

 pagebloom - your business  your website growing together

 ** **

 **Sydney**: (+61 2) 9656 1278     Canberra: (+61 2) 6100 2120
 

 Email: chr...@stepahead.com.au //chr...@stepahead.com.au

 Website:

 http://www.pagebloom.com

 

Re: Can't build wicket from updated trunk

2012-01-01 Thread Matthias Gasser
You need to increase the heap space for maven.

Just run the following line prior building:

 snip 
set MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=128m
 snap 

That should bring you through.

-matthias

Am 02.01.2012 um 05:43 schrieb Chris Colman:

 I cloned the wicket git repos and then checked out branch wicket-1.5.x branch 
 and the build broke in a different place (it got a bit further this time :)  )
 
 The build was done on a Windows XP box with 4GB RAM so I wouldn't have 
 thought it would have run out of memory.
 
 [INFO] 1 error
 [INFO] -
 [INFO] 
 
 [ERROR] BUILD FAILURE
 [INFO] 
 
 [INFO] Compilation failure
 Failure executing javac, but could not parse the error:
 
 
 The system is out of resources.
 Consult the following stack trace for details.
 java.lang.OutOfMemoryError: Java heap space
at com.sun.tools.javac.code.Scope$ImportScope.makeEntry(Scope.java:385)
at com.sun.tools.javac.code.Scope.enter(Scope.java:196)
at com.sun.tools.javac.code.Scope.enter(Scope.java:183)
at com.sun.tools.javac.comp.MemberEnter.importAll(MemberEnter.java:132)
at 
 com.sun.tools.javac.comp.MemberEnter.visitTopLevel(MemberEnter.java:509)
at 
 com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:446)
at 
 com.sun.tools.javac.comp.MemberEnter.memberEnter(MemberEnter.java:387)
at com.sun.tools.javac.comp.MemberEnter.complete(MemberEnter.java:819)
at com.sun.tools.javac.code.Symbol.complete(Symbol.java:386)
at 
 com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:758)
at com.sun.tools.javac.comp.Enter.complete(Enter.java:451)
at com.sun.tools.javac.comp.Enter.main(Enter.java:429)
at 
 com.sun.tools.javac.main.JavaCompiler.enterTrees(JavaCompiler.java:819)
at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:727)
at com.sun.tools.javac.main.Main.compile(Main.java:353)
at com.sun.tools.javac.main.Main.compile(Main.java:279)
at com.sun.tools.javac.main.Main.compile(Main.java:270)
at com.sun.tools.javac.Main.compile(Main.java:87)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
 org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:554)
at 
 org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:161)
at 
 org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:605)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
at 
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
 
 -Original Message-
 From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
 Sent: Monday, 2 January 2012 2:50 PM
 To: users@wicket.apache.org
 Subject: Re: Can't build wicket from updated trunk
 
 already moved.
 
 -igor
 
 On Sun, Jan 1, 2012 at 7:31 PM, Chris Colman
 chr...@stepaheadsoftware.com wrote:
 Is Wicket moving to git?
 
 Chris
 
 -Original Message-
 From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
 Sent: Monday, 2 January 2012 2:24 PM
 To: users@wicket.apache.org
 Subject: Re: Can't build wicket from updated trunk
 
 clone the project from here:
 http://git-wip-us.apache.org/repos/asf/wicket
 
 -igor
 
 On Sun, Jan 1, 2012 at 6:09 PM, Chris Colman
 chr...@stepaheadsoftware.comwrote:
 
 ** **
 
 I have done a recent update on my working copy of the trunk and mvn
 clean
 install yields:
 
 ** **
 
 Project ID: org.apache.wicket:wicket-ioc
 
 POM Location: C:\dev\libs\wicket\trunk\wicket-ioc\pom.xml
 
 Validation Messages:
 
 ** **
 
 [0]  'dependencies.dependency.version' is missing for
 javax.inject:javax.inject:jar
 
 ** **
 
 ** **
 
 Have I done something wrong or do I need to upgrade to a later JDK
 (currently 1.6.0_29-b11)?
 
 ** **
 
 Yours sincerely,
 
 ** **
 
 

Re: Hide page version query parameters

2012-01-01 Thread Taneli Korri
On Sat, Dec 31, 2011 at 4:31 PM, Martin Grigorov mgrigo...@apache.org wrote:
 On Sat, Dec 31, 2011 at 2:29 PM, Taneli Korri tko...@gmail.com wrote:
 On Sat, Dec 31, 2011 at 9:09 AM, Martin Grigorov mgrigo...@apache.org 
 wrote:
 On Fri, Dec 30, 2011 at 11:43 PM, martin.dilger
 martin.dil...@googlemail.com wrote:
 hi,
 you could try to change your render strategy to redirect to render, that
 would dismiss the page
 parameters version.

 This is not correct.
 The page id is encoded in the url only for stateful pages. Make your
 page stateless and it wont be there.


 OK, thanks for the info.

 If I remember correctly, in Wicket 1.4 stateful pages had also clean
 urls if the page was mounted to a certain path, i.e. the page version
 number was stored somewhere behind the scenes. I'm guessing this isn't
 possible anymore in Wicket 1.5?

 Everything is possible.
 The new IRequestMapper are easily extensible and you can even use your own 
 one.
 By default this special parameter is set so when the user presses F5
 (Refresh) the page Wicket will deliver the same version of the page.
 Otherwise a new instance will be created without the knowledge of the
 exact version.

 Why do you want to hide this parameter ?


Plain and simple, I like clean urls that can be bookmarked.

Also some of the search engine bots save the crawled urls (with
parameters) and try to access them at a later time. I found this out
when I updated one of my sites and now I'm seeing a lot of 500
Internal error responses in my web server logs.

Regards,
Taneli Korri

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Can't build wicket from updated trunk

2012-01-01 Thread Martin Grigorov
I don't set any JVM settings to be able to build Wicket...

@Chris: do you have some globally exported MAVEN_OPTS which may interfere ?

On Mon, Jan 2, 2012 at 6:52 AM, Matthias Gasser
matthias.gas...@gmail.com wrote:
 You need to increase the heap space for maven.

 Just run the following line prior building:

  snip 
 set MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=128m
  snap 

 That should bring you through.

 -matthias

 Am 02.01.2012 um 05:43 schrieb Chris Colman:

 I cloned the wicket git repos and then checked out branch wicket-1.5.x 
 branch and the build broke in a different place (it got a bit further this 
 time :)  )

 The build was done on a Windows XP box with 4GB RAM so I wouldn't have 
 thought it would have run out of memory.

 [INFO] 1 error
 [INFO] -
 [INFO] 
 
 [ERROR] BUILD FAILURE
 [INFO] 
 
 [INFO] Compilation failure
 Failure executing javac, but could not parse the error:


 The system is out of resources.
 Consult the following stack trace for details.
 java.lang.OutOfMemoryError: Java heap space
        at 
 com.sun.tools.javac.code.Scope$ImportScope.makeEntry(Scope.java:385)
        at com.sun.tools.javac.code.Scope.enter(Scope.java:196)
        at com.sun.tools.javac.code.Scope.enter(Scope.java:183)
        at 
 com.sun.tools.javac.comp.MemberEnter.importAll(MemberEnter.java:132)
        at 
 com.sun.tools.javac.comp.MemberEnter.visitTopLevel(MemberEnter.java:509)
        at 
 com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:446)
        at 
 com.sun.tools.javac.comp.MemberEnter.memberEnter(MemberEnter.java:387)
        at com.sun.tools.javac.comp.MemberEnter.complete(MemberEnter.java:819)
        at com.sun.tools.javac.code.Symbol.complete(Symbol.java:386)
        at 
 com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:758)
        at com.sun.tools.javac.comp.Enter.complete(Enter.java:451)
        at com.sun.tools.javac.comp.Enter.main(Enter.java:429)
        at 
 com.sun.tools.javac.main.JavaCompiler.enterTrees(JavaCompiler.java:819)
        at 
 com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:727)
        at com.sun.tools.javac.main.Main.compile(Main.java:353)
        at com.sun.tools.javac.main.Main.compile(Main.java:279)
        at com.sun.tools.javac.main.Main.compile(Main.java:270)
        at com.sun.tools.javac.Main.compile(Main.java:87)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at 
 org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:554)
        at 
 org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:161)
        at 
 org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:605)
        at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
        at 
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
        at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
        at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
        at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
        at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
        at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)

 -Original Message-
 From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
 Sent: Monday, 2 January 2012 2:50 PM
 To: users@wicket.apache.org
 Subject: Re: Can't build wicket from updated trunk

 already moved.

 -igor

 On Sun, Jan 1, 2012 at 7:31 PM, Chris Colman
 chr...@stepaheadsoftware.com wrote:
 Is Wicket moving to git?

 Chris

 -Original Message-
 From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
 Sent: Monday, 2 January 2012 2:24 PM
 To: users@wicket.apache.org
 Subject: Re: Can't build wicket from updated trunk

 clone the project from here:
 http://git-wip-us.apache.org/repos/asf/wicket

 -igor

 On Sun, Jan 1, 2012 at 6:09 PM, Chris Colman
 chr...@stepaheadsoftware.comwrote:

 ** **

 I have done a recent update on my working copy of the trunk and mvn
 clean
 install yields:

 ** **

 Project ID: org.apache.wicket:wicket-ioc

 POM Location: C:\dev\libs\wicket\trunk\wicket-ioc\pom.xml

 Validation Messages:

 ** **

     [0]  'dependencies.dependency.version' is 

Re: Hide page version query parameters

2012-01-01 Thread Martin Grigorov
On Mon, Jan 2, 2012 at 8:18 AM, Taneli Korri tko...@gmail.com wrote:
 On Sat, Dec 31, 2011 at 4:31 PM, Martin Grigorov mgrigo...@apache.org wrote:
 On Sat, Dec 31, 2011 at 2:29 PM, Taneli Korri tko...@gmail.com wrote:
 On Sat, Dec 31, 2011 at 9:09 AM, Martin Grigorov mgrigo...@apache.org 
 wrote:
 On Fri, Dec 30, 2011 at 11:43 PM, martin.dilger
 martin.dil...@googlemail.com wrote:
 hi,
 you could try to change your render strategy to redirect to render, that
 would dismiss the page
 parameters version.

 This is not correct.
 The page id is encoded in the url only for stateful pages. Make your
 page stateless and it wont be there.


 OK, thanks for the info.

 If I remember correctly, in Wicket 1.4 stateful pages had also clean
 urls if the page was mounted to a certain path, i.e. the page version
 number was stored somewhere behind the scenes. I'm guessing this isn't
 possible anymore in Wicket 1.5?

 Everything is possible.
 The new IRequestMapper are easily extensible and you can even use your own 
 one.
 By default this special parameter is set so when the user presses F5
 (Refresh) the page Wicket will deliver the same version of the page.
 Otherwise a new instance will be created without the knowledge of the
 exact version.

 Why do you want to hide this parameter ?


 Plain and simple, I like clean urls that can be bookmarked.

The urls with the page id can be bookmarked. If the requested version
of the page is not available then a new version is created and
delivered.


 Also some of the search engine bots save the crawled urls (with
 parameters) and try to access them at a later time. I found this out
 when I updated one of my sites and now I'm seeing a lot of 500
 Internal error responses in my web server logs.

Can you paste the stacktrace of an exception caused by such request ?


 Regards,
 Taneli Korri

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org