Upgrade to 6.13.0 Alert popup appears through page navigation after modal window closing

2014-01-15 Thread Marco Di Sabatino Di Diodoro
Hi all,

Upgrade to 6.13.0:

after the closing of a modal window if I click on another page, appear a alert 
popup that asks whether to leave or stay into the modal window.
It seems that something is still hanging after the modal window has been closed.

Can you help me?

Thanks
M


-- 
Dott. Marco Di Sabatino Di Diodoro
Tel. +39 3939065570

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

Apache Syncope PMC Member
http://people.apache.org/~mdisabatino/



Re: Upgrade to 6.13.0 Alert popup appears through page navigation after modal window closing

2014-01-15 Thread Martin Grigorov
There is a ticket about this with a workaround.
Unfortunately Apache Jira doesn't work again.

Martin Grigorov
Wicket Training and Consulting


On Wed, Jan 15, 2014 at 10:54 AM, Marco Di Sabatino Di Diodoro 
marco.disabat...@tirasa.net wrote:

 Hi all,

 Upgrade to 6.13.0:

 after the closing of a modal window if I click on another page, appear a
 alert popup that asks whether to leave or stay into the modal window.
 It seems that something is still hanging after the modal window has been
 closed.

 Can you help me?

 Thanks
 M


 --
 Dott. Marco Di Sabatino Di Diodoro
 Tel. +39 3939065570

 Tirasa S.r.l.
 Viale D'Annunzio 267 - 65127 Pescara
 Tel +39 0859116307 / FAX +39 085973
 http://www.tirasa.net

 Apache Syncope PMC Member
 http://people.apache.org/~mdisabatino/




Re: Upgrade to 6.13.0 Alert popup appears through page navigation after modal window closing

2014-01-15 Thread Marco Di Sabatino Di Diodoro
Thanks Martin,

is 5469 the ticket number?

M

Il giorno 15/gen/2014, alle ore 09:57, Martin Grigorov mgrigo...@apache.org 
ha scritto:

 There is a ticket about this with a workaround.
 Unfortunately Apache Jira doesn't work again.
 
 Martin Grigorov
 Wicket Training and Consulting
 
 
 On Wed, Jan 15, 2014 at 10:54 AM, Marco Di Sabatino Di Diodoro 
 marco.disabat...@tirasa.net wrote:
 
 Hi all,
 
 Upgrade to 6.13.0:
 
 after the closing of a modal window if I click on another page, appear a
 alert popup that asks whether to leave or stay into the modal window.
 It seems that something is still hanging after the modal window has been
 closed.
 
 Can you help me?
 
 Thanks
 M
 
 
 --
 Dott. Marco Di Sabatino Di Diodoro
 Tel. +39 3939065570
 
 Tirasa S.r.l.
 Viale D'Annunzio 267 - 65127 Pescara
 Tel +39 0859116307 / FAX +39 085973
 http://www.tirasa.net
 
 Apache Syncope PMC Member
 http://people.apache.org/~mdisabatino/
 
 

-- 
Dott. Marco Di Sabatino Di Diodoro
Tel. +39 3939065570

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

Apache Syncope PMC Member
http://people.apache.org/~mdisabatino/



Re: Upgrade to 6.13.0 Alert popup appears through page navigation after modal window closing

2014-01-15 Thread Martin Grigorov
Yes, and it is fixed now.

Martin Grigorov
Wicket Training and Consulting


On Wed, Jan 15, 2014 at 11:17 AM, Marco Di Sabatino Di Diodoro 
marco.disabat...@tirasa.net wrote:

 Thanks Martin,

 is 5469 the ticket number?

 M

 Il giorno 15/gen/2014, alle ore 09:57, Martin Grigorov 
 mgrigo...@apache.org ha scritto:

  There is a ticket about this with a workaround.
  Unfortunately Apache Jira doesn't work again.
 
  Martin Grigorov
  Wicket Training and Consulting
 
 
  On Wed, Jan 15, 2014 at 10:54 AM, Marco Di Sabatino Di Diodoro 
  marco.disabat...@tirasa.net wrote:
 
  Hi all,
 
  Upgrade to 6.13.0:
 
  after the closing of a modal window if I click on another page, appear a
  alert popup that asks whether to leave or stay into the modal window.
  It seems that something is still hanging after the modal window has been
  closed.
 
  Can you help me?
 
  Thanks
  M
 
 
  --
  Dott. Marco Di Sabatino Di Diodoro
  Tel. +39 3939065570
 
  Tirasa S.r.l.
  Viale D'Annunzio 267 - 65127 Pescara
  Tel +39 0859116307 / FAX +39 085973
  http://www.tirasa.net
 
  Apache Syncope PMC Member
  http://people.apache.org/~mdisabatino/
 
 

 --
 Dott. Marco Di Sabatino Di Diodoro
 Tel. +39 3939065570

 Tirasa S.r.l.
 Viale D'Annunzio 267 - 65127 Pescara
 Tel +39 0859116307 / FAX +39 085973
 http://www.tirasa.net

 Apache Syncope PMC Member
 http://people.apache.org/~mdisabatino/




Re: Upgrade to 6.13.0 Alert popup appears through page navigation after modal window closing

2014-01-15 Thread Marco Di Sabatino Di Diodoro
Hi Martin,

Il giorno 15/gen/2014, alle ore 10:30, Martin Grigorov mgrigo...@apache.org 
ha scritto:

 Yes, and it is fixed now.
 

Thank you very much.

Regards
M

 Martin Grigorov
 Wicket Training and Consulting
 
 
 On Wed, Jan 15, 2014 at 11:17 AM, Marco Di Sabatino Di Diodoro 
 marco.disabat...@tirasa.net wrote:
 
 Thanks Martin,
 
 is 5469 the ticket number?
 
 M
 
 Il giorno 15/gen/2014, alle ore 09:57, Martin Grigorov 
 mgrigo...@apache.org ha scritto:
 
 There is a ticket about this with a workaround.
 Unfortunately Apache Jira doesn't work again.
 
 Martin Grigorov
 Wicket Training and Consulting
 
 
 On Wed, Jan 15, 2014 at 10:54 AM, Marco Di Sabatino Di Diodoro 
 marco.disabat...@tirasa.net wrote:
 
 Hi all,
 
 Upgrade to 6.13.0:
 
 after the closing of a modal window if I click on another page, appear a
 alert popup that asks whether to leave or stay into the modal window.
 It seems that something is still hanging after the modal window has been
 closed.
 
 Can you help me?
 
 Thanks
 M
 
 
 --
 Dott. Marco Di Sabatino Di Diodoro
 Tel. +39 3939065570
 
 Tirasa S.r.l.
 Viale D'Annunzio 267 - 65127 Pescara
 Tel +39 0859116307 / FAX +39 085973
 http://www.tirasa.net
 
 Apache Syncope PMC Member
 http://people.apache.org/~mdisabatino/
 
 
 
 --
 Dott. Marco Di Sabatino Di Diodoro
 Tel. +39 3939065570
 
 Tirasa S.r.l.
 Viale D'Annunzio 267 - 65127 Pescara
 Tel +39 0859116307 / FAX +39 085973
 http://www.tirasa.net
 
 Apache Syncope PMC Member
 http://people.apache.org/~mdisabatino/
 
 

-- 
Dott. Marco Di Sabatino Di Diodoro
Tel. +39 3939065570

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

Apache Syncope PMC Member
http://people.apache.org/~mdisabatino/



Wicket war file deployment to Heroku

2014-01-15 Thread gerritqf
Hello Forum members,

I am trying to deploy a java webapplication with Wicket to Heroku site.
The war file is build with maven and can run with Jetty-runner on
localhost:8080.
Now after deploying to Heroku the site comes up with a Application error.

Maybe you can help me with how and what i must do. For example the Procfile
and system.properties file.

I found this link:

http://wicketinaction.com/2011/09/git-wicket-running-on-heroku/comment-page-1/

but is this a way to follow?

Thanks a lot for your answer!

Gerrit

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wicket-war-file-deployment-to-Heroku-tp4663737.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



Re: Wicket war file deployment to Heroku

2014-01-15 Thread Martin Grigorov
What is the error ?

Martin Grigorov
Wicket Training and Consulting


On Wed, Jan 15, 2014 at 3:57 PM, gerritqf gerrit.wass...@qfactors.nlwrote:

 Hello Forum members,

 I am trying to deploy a java webapplication with Wicket to Heroku site.
 The war file is build with maven and can run with Jetty-runner on
 localhost:8080.
 Now after deploying to Heroku the site comes up with a Application error.

 Maybe you can help me with how and what i must do. For example the Procfile
 and system.properties file.

 I found this link:


 http://wicketinaction.com/2011/09/git-wicket-running-on-heroku/comment-page-1/

 but is this a way to follow?

 Thanks a lot for your answer!

 Gerrit

 --
 View this message in context:
 http://apache-wicket.1842946.n4.nabble.com/Wicket-war-file-deployment-to-Heroku-tp4663737.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




Re: Wicket war file deployment to Heroku

2014-01-15 Thread Gerrit Wassink
Martin,
This is the error on the Heroku site:
==Application ErrorAn error occurred in the 
application and your page could not be served. Please try again in a few 
moments.
If you are the application owner, check your logs for 
details.
But after deploying to Heroku there are no errors only in the end something 
about the Procfile:
SHOT.pom       [INFO] 
       [INFO] 
BUILD SUCCESS       [INFO] 
       [INFO] 
Total time: 14.688s       [INFO] Finished at: Wed Jan 15 09:36:40 UTC 2014      
 [INFO] Final Memory: 19M/514M       [INFO] 
- 
Discovering process types
 ~     Mis-cased procfile detected; ignoring. ~     Rename it to Procfile to 
have it honored.
       Procfile declares types - (none)
- Compressing... done, 93.4MB- Launching... done, v6       
http://ancient-headland-1117.herokuapp.com deployed to Heroku
To g...@heroku.com:ancient-headland-1117.git * [new branch]      master - 
master
What i did is following the tutorials on the Heroku site.Do you have any 
experience with deploying wicket application on Heroku?
Greetings Gerrit



Martin Grigorov mgrigo...@apache.org , 15-1-2014 15:01:
What is the error ? 
 
Martin Grigorov 
Wicket Training and Consulting 
 
 
On Wed, Jan 15, 2014 at 3:57 PM, gerritqf gerrit.wass...@qfactors.nlwrote: 
 
 Hello Forum members, 
 
 I am trying to deploy a java webapplication with Wicket to Heroku site. 
 The war file is build with maven and can run with Jetty-runner on 
 localhost:8080. 
 Now after deploying to Heroku the site comes up with a Application error. 
 
 Maybe you can help me with how and what i must do. For example the Procfile 
 and system.properties file. 
 
 I found this link: 
 
 
 http://wicketinaction.com/2011/09/git-wicket-running-on-heroku/comment-page-1/
  
 
 but is this a way to follow? 
 
 Thanks a lot for your answer! 
 
 Gerrit 
 
 -- 
 View this message in context: 
 http://apache-wicket.1842946.n4.nabble.com/Wicket-war-file-deployment-to-Heroku-tp4663737.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 
 
 


StartExamples of wicket-examples not running

2014-01-15 Thread Martin Funk
Hi,

looking into the current experimental wicket-cdi-1.1 of the wicket-6.x branch, 
I noticed that the wicket-examples.war runs fine in an Container, here Apache 
Tomcat/7.0.50,
but the StartExamples of the wicket-examples doesn't run.

Weld throws an Deployment Exception

WARN  - Interceptor- WELD-001700: Interceptor annotation class 
javax.ejb.PrePassivate not found, interception based on it is not enabled
WARN  - WebAppContext  - Failed startup of context 
o.e.j.w.WebAppContext{/,file:/Users/mafulafunk/Code/wicket/wicket-examples/src/main/webapp/},src/main/webapp
org.jboss.weld.exceptions.DeploymentException: javax/servlet/DispatcherType

It can't find the DispatcherType class, which is plausible, since it is part of 
Servlet 3.0 spec.

I messed around with the jetty versions, but no success yet.

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



Re: CssBehaviour can't find css files

2014-01-15 Thread Anna Simbirtsev
htmlheadmeta http-equiv=Content-Type content=text/html;
charset=ISO-8859-1/titleError 404
NOT_FOUND/title/headbodyh2HTTP ERROR 404/h2pProblem
accessing 
/wat-application/wicket/resource/CSSLinksInjector/info/css/styles-ver-1389797413000.css.
Reason:preNOT_FOUND/pre/phr /ismallPowered by
Jetty:///small/ibr/
  br/br/
 br/
   br/
 br/br/
br/
  br/
br/br/
   br/
 br/
br/br/
   br/
 br/
br/br/
   br/
 /body/html

This error is shown inside the css file. I moved file in src/main/java/.



On Tue, Jan 14, 2014 at 2:05 PM, Anna Simbirtsev asimbirt...@gmail.comwrote:

 Once I moved the file in src/main/java/ without any package, it does not
 show errors that it cant find it, so it is found, it just does not show any
 css.


 On Tue, Jan 14, 2014 at 10:31 AM, Martin Grigorov mgrigo...@apache.orgwrote:

 The reason is that you use info.afilias.WAT.UI.CSSLinksInjector as a scope
 and the resources are looked up relative to it in the package structure.
 In 1.4 it worked because you use '/info/...' - the leading slash resolved
 to the root package.
 This has been changed because of security problems and the leading slash
 is
 removed.
 I think latest 1.4.x also have this fix but I'm not 100% certain.

 If you want to keep the resources there you have to use a class in the
 root
 package as a scope.
 I.e. create a new class in src/main/java/ folder and use it at:
 CssReferenceHeaderItem.forReference(new CssResourceReference(HERE, ..

 Martin Grigorov
 Wicket Training and Consulting


 On Tue, Jan 14, 2014 at 5:22 PM, Anna Simbirtsev asimbirt...@gmail.com
 wrote:

  The file structure is
 
  myApplication/src/main/java
  myApplication/src/main/resources/info/css/ that has all css files
  myApplication/src/main/resources/info/images has all the images
 
 
 
 
  On Tue, Jan 14, 2014 at 10:04 AM, Martin Grigorov mgrigo...@apache.org
  wrote:
 
   What is the file structure ?
   What packages and files you have in UI package ?
  
   Martin Grigorov
   Wicket Training and Consulting
  
  
   On Tue, Jan 14, 2014 at 4:56 PM, Anna Simbirtsev 
 asimbirt...@gmail.com
   wrote:
  
Do you have any other suggestions why it may not be able to find the
  css
file?
   
   
On Tue, Jan 14, 2014 at 9:49 AM, Anna Simbirtsev 
  asimbirt...@gmail.com
wrote:
   
 this is a dynamic parameter, is changes based on settings, it
 should
   work
 either way


 On Tue, Jan 14, 2014 at 9:45 AM, Martin Grigorov 
  mgrigo...@apache.org
wrote:

 The only difference is that the resolved theme is 'info' instead
 of
'root'

 Martin Grigorov
 Wicket Training and Consulting


 On Tue, Jan 14, 2014 at 4:43 PM, Anna Simbirtsev 
   asimbirt...@gmail.com
 wrote:

  The name of the file is different and it cant find it
 
 
  On Tue, Jan 14, 2014 at 9:41 AM, Martin Grigorov 
mgrigo...@apache.org
  wrote:
 
   It looks perfect!
  
   Martin Grigorov
   Wicket Training and Consulting
  
  
   On Tue, Jan 14, 2014 at 4:39 PM, Anna Simbirtsev 
 asimbirt...@gmail.com
   wrote:
  
if I get rid of the CryptoMapper
new link looks like
   
link rel=stylesheet type=text/css
   
   
  
 

   
  
 
 href=./wicket/resource/info.afilias.WAT.UI.CSSLinksInjector/info/css/tooltip-ver-1389710287000.css
view-source:
   
  
 

   
  
 
 http://localhost:8080/wat-application/wicket/resource/info.afilias.WAT.UI.CSSLinksInjector/info/css/tooltip-ver-1389710287000.css

/
   
   
   
On Tue, Jan 14, 2014 at 9:35 AM, Martin Grigorov 
 mgrigo...@apache.org
wrote:
   
 Because you use CryptoMapper in your app.

 Martin Grigorov
 Wicket Training and Consulting


 On Tue, Jan 14, 2014 at 4:32 PM, Anna Simbirtsev 
   asimbirt...@gmail.com
 wrote:

  NEW: href=../X5EA-RpmG5-
 
 

   
  
 

   
  
 
 t7GSByiSpogTj4bvW9MKMW4vn832-xprwEXT2RkaeV8fX_4jkKsv1CB554pAX0u87jm6UPI3w_ihTiZY3tftZ8jJqrrURxUxvKsFXCdT_2G6JYzRb5crh/X5E87/URx2a/zRb59/sFXb4/URx2a/zRb59
  /
 
  why is the new link looks like this?
 
 
  On Tue, Jan 14, 2014 at 9:29 AM, Martin Grigorov 
   mgrigo...@apache.org
  wrote:
 
   I am not sure what you mean.
  
   Martin 

Re: CssBehaviour can't find css files

2014-01-15 Thread Martin Grigorov
Please create a quickstart application showing the problem.

Martin Grigorov
Wicket Training and Consulting


On Wed, Jan 15, 2014 at 5:13 PM, Anna Simbirtsev asimbirt...@gmail.comwrote:

 htmlheadmeta http-equiv=Content-Type content=text/html;
 charset=ISO-8859-1/titleError 404
 NOT_FOUND/title/headbodyh2HTTP ERROR 404/h2pProblem
 accessing
 /wat-application/wicket/resource/CSSLinksInjector/info/css/styles-ver-1389797413000.css.
 Reason:preNOT_FOUND/pre/phr /ismallPowered by
 Jetty:///small/ibr/
   br/br/
  br/
br/
  br/br/
 br/
   br/
 br/br/
br/
  br/
 br/br/
br/
  br/
 br/br/
br/
  /body/html

 This error is shown inside the css file. I moved file in src/main/java/.



 On Tue, Jan 14, 2014 at 2:05 PM, Anna Simbirtsev asimbirt...@gmail.com
 wrote:

  Once I moved the file in src/main/java/ without any package, it does not
  show errors that it cant find it, so it is found, it just does not show
 any
  css.
 
 
  On Tue, Jan 14, 2014 at 10:31 AM, Martin Grigorov mgrigo...@apache.org
 wrote:
 
  The reason is that you use info.afilias.WAT.UI.CSSLinksInjector as a
 scope
  and the resources are looked up relative to it in the package structure.
  In 1.4 it worked because you use '/info/...' - the leading slash
 resolved
  to the root package.
  This has been changed because of security problems and the leading slash
  is
  removed.
  I think latest 1.4.x also have this fix but I'm not 100% certain.
 
  If you want to keep the resources there you have to use a class in the
  root
  package as a scope.
  I.e. create a new class in src/main/java/ folder and use it at:
  CssReferenceHeaderItem.forReference(new CssResourceReference(HERE, ..
 
  Martin Grigorov
  Wicket Training and Consulting
 
 
  On Tue, Jan 14, 2014 at 5:22 PM, Anna Simbirtsev asimbirt...@gmail.com
  wrote:
 
   The file structure is
  
   myApplication/src/main/java
   myApplication/src/main/resources/info/css/ that has all css files
   myApplication/src/main/resources/info/images has all the images
  
  
  
  
   On Tue, Jan 14, 2014 at 10:04 AM, Martin Grigorov 
 mgrigo...@apache.org
   wrote:
  
What is the file structure ?
What packages and files you have in UI package ?
   
Martin Grigorov
Wicket Training and Consulting
   
   
On Tue, Jan 14, 2014 at 4:56 PM, Anna Simbirtsev 
  asimbirt...@gmail.com
wrote:
   
 Do you have any other suggestions why it may not be able to find
 the
   css
 file?


 On Tue, Jan 14, 2014 at 9:49 AM, Anna Simbirtsev 
   asimbirt...@gmail.com
 wrote:

  this is a dynamic parameter, is changes based on settings, it
  should
work
  either way
 
 
  On Tue, Jan 14, 2014 at 9:45 AM, Martin Grigorov 
   mgrigo...@apache.org
 wrote:
 
  The only difference is that the resolved theme is 'info'
 instead
  of
 'root'
 
  Martin Grigorov
  Wicket Training and Consulting
 
 
  On Tue, Jan 14, 2014 at 4:43 PM, Anna Simbirtsev 
asimbirt...@gmail.com
  wrote:
 
   The name of the file is different and it cant find it
  
  
   On Tue, Jan 14, 2014 at 9:41 AM, Martin Grigorov 
 mgrigo...@apache.org
   wrote:
  
It looks perfect!
   
Martin Grigorov
Wicket Training and Consulting
   
   
On Tue, Jan 14, 2014 at 4:39 PM, Anna Simbirtsev 
  asimbirt...@gmail.com
wrote:
   
 if I get rid of the CryptoMapper
 new link looks like

 link rel=stylesheet type=text/css


   
  
 

   
  
 
 href=./wicket/resource/info.afilias.WAT.UI.CSSLinksInjector/info/css/tooltip-ver-1389710287000.css
 view-source:

   
  
 

   
  
 
 http://localhost:8080/wat-application/wicket/resource/info.afilias.WAT.UI.CSSLinksInjector/info/css/tooltip-ver-1389710287000.css
 
 /



 On Tue, Jan 14, 2014 at 9:35 AM, Martin Grigorov 
  mgrigo...@apache.org
 wrote:

  Because you use CryptoMapper in your app.
 
  Martin Grigorov
  Wicket Training and Consulting
 
 
  On Tue, Jan 14, 2014 at 4:32 PM, Anna Simbirtsev 
asimbirt...@gmail.com
  wrote:
 
   NEW: href=../X5EA-RpmG5-
  
  
 

   
  
 

   
  
 
 

Re: StartExamples of wicket-examples not running

2014-01-15 Thread Martin Grigorov
I am able to run StartExamples.java from Intellij IDEA without problems
both with wicket-6.x and master branches.
Do you have any local changes ?

Martin Grigorov
Wicket Training and Consulting


On Wed, Jan 15, 2014 at 4:47 PM, Martin Funk mafulaf...@gmail.com wrote:

 Hi,

 looking into the current experimental wicket-cdi-1.1 of the wicket-6.x
 branch, I noticed that the wicket-examples.war runs fine in an Container,
 here Apache Tomcat/7.0.50,
 but the StartExamples of the wicket-examples doesn't run.

 Weld throws an Deployment Exception

 WARN  - Interceptor- WELD-001700: Interceptor annotation
 class javax.ejb.PrePassivate not found, interception based on it is not
 enabled
 WARN  - WebAppContext  - Failed startup of context
 o.e.j.w.WebAppContext{/,file:/Users/mafulafunk/Code/wicket/wicket-examples/src/main/webapp/},src/main/webapp
 org.jboss.weld.exceptions.DeploymentException: javax/servlet/DispatcherType

 It can't find the DispatcherType class, which is plausible, since it is
 part of Servlet 3.0 spec.

 I messed around with the jetty versions, but no success yet.

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




Re: Wicket war file deployment to Heroku

2014-01-15 Thread Martijn Dashorst
Change the case of your procfile to Procfile.

That is what the error says.

Martijn

On Wed, Jan 15, 2014 at 3:36 PM, Gerrit Wassink
gerrit.wass...@qfactors.nl wrote:
 Martin,
 This is the error on the Heroku site:
 ==Application ErrorAn error occurred in the 
 application and your page could not be served. Please try again in a few 
 moments.
 If you are the application owner, check your logs for 
 details.
 But after deploying to Heroku there are no errors only in the end something 
 about the Procfile:
 SHOT.pom   [INFO] 
    [INFO] 
 BUILD SUCCESS   [INFO] 
    [INFO] 
 Total time: 14.688s   [INFO] Finished at: Wed Jan 15 09:36:40 UTC 2014
[INFO] Final Memory: 19M/514M   [INFO] 
 - 
 Discovering process types
  ~ Mis-cased procfile detected; ignoring. ~ Rename it to Procfile to 
 have it honored.
Procfile declares types - (none)
 - Compressing... done, 93.4MB- Launching... done, v6   
 http://ancient-headland-1117.herokuapp.com deployed to Heroku
 To g...@heroku.com:ancient-headland-1117.git * [new branch]  master - 
 master
 What i did is following the tutorials on the Heroku site.Do you have any 
 experience with deploying wicket application on Heroku?
 Greetings Gerrit



 Martin Grigorov mgrigo...@apache.org , 15-1-2014 15:01:
 What is the error ?

 Martin Grigorov
 Wicket Training and Consulting


 On Wed, Jan 15, 2014 at 3:57 PM, gerritqf gerrit.wass...@qfactors.nlwrote:

 Hello Forum members,

 I am trying to deploy a java webapplication with Wicket to Heroku site.
 The war file is build with maven and can run with Jetty-runner on
 localhost:8080.
 Now after deploying to Heroku the site comes up with a Application error.

 Maybe you can help me with how and what i must do. For example the Procfile
 and system.properties file.

 I found this link:


 http://wicketinaction.com/2011/09/git-wicket-running-on-heroku/comment-page-1/

 but is this a way to follow?

 Thanks a lot for your answer!

 Gerrit

 --
 View this message in context:
 http://apache-wicket.1842946.n4.nabble.com/Wicket-war-file-deployment-to-Heroku-tp4663737.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





-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

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



Re: Models and page serialization

2014-01-15 Thread gmparker2000
Thanks for the tip.  I'm a little unclear on what this is telling me though. 
Wouldn't this just tell me if the detach method of all my LDMs was called? 
What I'm interested in determining is where my LDMs are directly referencing
objects that will inadvertantly get serialized with the LDM.   For example,
if an LDM has a member variable pointing to an object or the LDM accesses a
final variable from its parent class.  I want to be sure I'm not serializing
business objects or references to business objects along with the page.  

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Models-and-page-serialization-tp4663668p4663746.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



Re: [ANNOUNCE] Apache Wicket 6.13.0 adds free online user guide

2014-01-15 Thread Paul Bors
I think this release broke the quick start at:
http://wicket.apache.org/start/quickstart.html

When the page loads at first the Command Line is empty at first. Null
initial model object?
Selecting a different version from the drop down and then back to 6.13.0
will fill in the form field.


On Mon, Jan 13, 2014 at 11:00 AM, Martijn Dashorst dasho...@apache.orgwrote:

 The Apache Wicket PMC is proud to announce Apache Wicket 6.13.0!

 This release marks the thirteenth minor release of Wicket 6. Starting
 with Wicket 6 we use semantic versioning for the future development of
 Wicket, and as such no API breaks are present in this release compared
 to 6.0.0.

 New and noteworthy
 --

 This release fixes 25 bugs and adds the following improvements:

  * Online Wicket User guide (see below)
  * CDI 1.1 support (see below)
  * JQuery upgraded from 1.10.1 to 1.10.2
  * Implemented BigIntegerConverter
  * Migrate Wicket-Atmosphere to Atmosphere 2

 New Wicket User guide
 -

 After many years of people asking for a reference guide for Apache
 Wicket we finally were able to add one to our site thanks to Andrea del
 Bene and comSysto for writing the guide and providing the hours of
 converting it to our site.

 You can read the manual in 3 forms: multi page HTML, single page HTML
 and PDF.

 The contents:
  - Introduction
  - How to use the example code
  - Why should I learn Wicket?
  - Wicket says Hello, World!
  - Wicket as page layout manager
  - Keeping control over HTML
  - Component Lifecycle
  - Page versioning and caching
  - Under the hood of request processing
  - Wicket Links and URL generation
  - Wicket models and forms
  - Wicket forms in detail
  - Displaying multiple items with repeaters
  - Internationalization with Wicket
  - Resource management with Wicket
  - An example of integration with JavaScript
  - Wicket advanced topics
  - Working with AJAX
  - Integration with enterprise containers
  - Security with Wicket
  - Test Driven Development with Wicket
  - Test Driven Development with Wicket and Spring
  - Wicket Best Practices
  - Working with Maven (Appendix)
  - Project WicketStuff (Appendix)
  - Lost in redirection with Apache Wicket (Appendix)
  - Contributing to this guide (Appendix)

 Read more in the User guide by following this link:

 http://wicket.apache.org/start/userguide.html

 New CDI-1.1 integration project
 ---

 A new (experimental) module for CDI integration was added to support
 CDI 1.1 with Wicket. As CDI 1.0 and 1.1 are different beasts and not
 compatible, we had to craft a new module with specific support for the
 new CDI standard. The module is still experimental, but we expect to
 make it a default module in a couple of releases.

 You can use the new Wicket CDI module by including the following
 dependency in your POM:

 dependency
groupIdorg.apache.wicket/groupId
 artifactIdwicket-cdi-1.1/artifactId
 version0.2/version
 /dependency

 Note that you have to remove the old wicket-cdi module and the Seam
 conversation dependency: org.jboss.seam.conversation:seam-conversation-weld

 For more information about what is new in CDI 1.1 read this blog post
 by Pete Muir: http://s.apache.org/newincdi11

 JQuery update in 6.9.0
 --

 As of Wicket 6.9 we ship JQuery 1.10.1. The JQuery project has
 decided to remove deprecated APIs from their codebase from JQuery 1.9
 and up. This means that JQuery plugins using these deprecated APIs no
 longer work. See the JQuery migration guide for more information,
 available from http://jquery.com/upgrade-guide/1.9/

 If your application depends on these deprecated APIs you can easily
 downgrade to JQuery 1.8.3-the previously provided JQuery that still
 contains these APIs. Download the 1.8.3 release of jquery and add it
 to your project in its application's init method:

 @Override
 protected void init() {
 getJavaScriptLibrarySettings()
 .setJQueryReference(yourJquery183ResourceReference);
 }

 CDI injection issue
 ---

 In the CDI releases of Weld 2.0.1 and prior, it was assumed that
 injection in anonymous inner classes was not legal and when
 attempted, it resulted in an exception:

 Caused by: org.jboss.weld.exceptions.DefinitionException:
 WELD-70 Simple bean [EnhancedAnnotatedTypeImpl] private class
 com.example.HomePage$AForm cannot be a non-static inner class

 This was reported as
 https://issues.apache.org/jira/browse/WICKET-5226, as it became an
 issue in Glassfish 4, which ships with Weld 2.0.1 (or earlier). We
 implemented a fix for this particular issue by not injecting into
 anonymous inner classes.

 Unfortunately this was not a bug that needed fixing on our part, but
 rather in the Weld framework (see
 https://issues.jboss.org/browse/WELD-1441)

 Therefore we reverted the commits done for WICKET-5226 and hope that
 Glassfish will upgrade their Weld 

Re: [ANNOUNCE] Apache Wicket 6.13.0 adds free online user guide

2014-01-15 Thread Paul Bors
Also, the quick start has this in its HTML:
Please mention the correct Wicket version: wicket:container
wicket:id=version1.5-SNAPSHOT/wicket:container.

Maybe we should change it with:
Please mention the correct Wicket version: wicket:container
wicket:id=version[version will be inserted here]/wicket:container.

or similar so that newbies don't get confused.


On Wed, Jan 15, 2014 at 12:14 PM, Paul Bors p...@bors.ws wrote:

 I think this release broke the quick start at:
 http://wicket.apache.org/start/quickstart.html

 When the page loads at first the Command Line is empty at first. Null
 initial model object?
 Selecting a different version from the drop down and then back to 6.13.0
 will fill in the form field.


 On Mon, Jan 13, 2014 at 11:00 AM, Martijn Dashorst dasho...@apache.orgwrote:

 The Apache Wicket PMC is proud to announce Apache Wicket 6.13.0!

 This release marks the thirteenth minor release of Wicket 6. Starting
 with Wicket 6 we use semantic versioning for the future development of
 Wicket, and as such no API breaks are present in this release compared
 to 6.0.0.

 New and noteworthy
 --

 This release fixes 25 bugs and adds the following improvements:

  * Online Wicket User guide (see below)
  * CDI 1.1 support (see below)
  * JQuery upgraded from 1.10.1 to 1.10.2
  * Implemented BigIntegerConverter
  * Migrate Wicket-Atmosphere to Atmosphere 2

 New Wicket User guide
 -

 After many years of people asking for a reference guide for Apache
 Wicket we finally were able to add one to our site thanks to Andrea del
 Bene and comSysto for writing the guide and providing the hours of
 converting it to our site.

 You can read the manual in 3 forms: multi page HTML, single page HTML
 and PDF.

 The contents:
  - Introduction
  - How to use the example code
  - Why should I learn Wicket?
  - Wicket says Hello, World!
  - Wicket as page layout manager
  - Keeping control over HTML
  - Component Lifecycle
  - Page versioning and caching
  - Under the hood of request processing
  - Wicket Links and URL generation
  - Wicket models and forms
  - Wicket forms in detail
  - Displaying multiple items with repeaters
  - Internationalization with Wicket
  - Resource management with Wicket
  - An example of integration with JavaScript
  - Wicket advanced topics
  - Working with AJAX
  - Integration with enterprise containers
  - Security with Wicket
  - Test Driven Development with Wicket
  - Test Driven Development with Wicket and Spring
  - Wicket Best Practices
  - Working with Maven (Appendix)
  - Project WicketStuff (Appendix)
  - Lost in redirection with Apache Wicket (Appendix)
  - Contributing to this guide (Appendix)

 Read more in the User guide by following this link:

 http://wicket.apache.org/start/userguide.html

 New CDI-1.1 integration project
 ---

 A new (experimental) module for CDI integration was added to support
 CDI 1.1 with Wicket. As CDI 1.0 and 1.1 are different beasts and not
 compatible, we had to craft a new module with specific support for the
 new CDI standard. The module is still experimental, but we expect to
 make it a default module in a couple of releases.

 You can use the new Wicket CDI module by including the following
 dependency in your POM:

 dependency
groupIdorg.apache.wicket/groupId
 artifactIdwicket-cdi-1.1/artifactId
 version0.2/version
 /dependency

 Note that you have to remove the old wicket-cdi module and the Seam
 conversation dependency:
 org.jboss.seam.conversation:seam-conversation-weld

 For more information about what is new in CDI 1.1 read this blog post
 by Pete Muir: http://s.apache.org/newincdi11

 JQuery update in 6.9.0
 --

 As of Wicket 6.9 we ship JQuery 1.10.1. The JQuery project has
 decided to remove deprecated APIs from their codebase from JQuery 1.9
 and up. This means that JQuery plugins using these deprecated APIs no
 longer work. See the JQuery migration guide for more information,
 available from http://jquery.com/upgrade-guide/1.9/

 If your application depends on these deprecated APIs you can easily
 downgrade to JQuery 1.8.3-the previously provided JQuery that still
 contains these APIs. Download the 1.8.3 release of jquery and add it
 to your project in its application's init method:

 @Override
 protected void init() {
 getJavaScriptLibrarySettings()
 .setJQueryReference(yourJquery183ResourceReference);
 }

 CDI injection issue
 ---

 In the CDI releases of Weld 2.0.1 and prior, it was assumed that
 injection in anonymous inner classes was not legal and when
 attempted, it resulted in an exception:

 Caused by: org.jboss.weld.exceptions.DefinitionException:
 WELD-70 Simple bean [EnhancedAnnotatedTypeImpl] private class
 com.example.HomePage$AForm cannot be a non-static inner class

 This was reported as
 https://issues.apache.org/jira/browse/WICKET-5226, as it 

Re: [ANNOUNCE] Apache Wicket 6.13.0 adds free online user guide

2014-01-15 Thread Duane Searsmith
This guide is a FANTASTIC addition to the project.

Many, many thanks to everyone that helped to create this resource.


On Wed, Jan 15, 2014 at 11:27 AM, Paul Bors p...@bors.ws wrote:

 Also, the quick start has this in its HTML:
 Please mention the correct Wicket version: wicket:container
 wicket:id=version1.5-SNAPSHOT/wicket:container.

 Maybe we should change it with:
 Please mention the correct Wicket version: wicket:container
 wicket:id=version[version will be inserted here]/wicket:container.

 or similar so that newbies don't get confused.


 On Wed, Jan 15, 2014 at 12:14 PM, Paul Bors p...@bors.ws wrote:

  I think this release broke the quick start at:
  http://wicket.apache.org/start/quickstart.html
 
  When the page loads at first the Command Line is empty at first. Null
  initial model object?
  Selecting a different version from the drop down and then back to 6.13.0
  will fill in the form field.
 
 
  On Mon, Jan 13, 2014 at 11:00 AM, Martijn Dashorst dasho...@apache.org
 wrote:
 
  The Apache Wicket PMC is proud to announce Apache Wicket 6.13.0!
 
  This release marks the thirteenth minor release of Wicket 6. Starting
  with Wicket 6 we use semantic versioning for the future development of
  Wicket, and as such no API breaks are present in this release compared
  to 6.0.0.
 
  New and noteworthy
  --
 
  This release fixes 25 bugs and adds the following improvements:
 
   * Online Wicket User guide (see below)
   * CDI 1.1 support (see below)
   * JQuery upgraded from 1.10.1 to 1.10.2
   * Implemented BigIntegerConverter
   * Migrate Wicket-Atmosphere to Atmosphere 2
 
  New Wicket User guide
  -
 
  After many years of people asking for a reference guide for Apache
  Wicket we finally were able to add one to our site thanks to Andrea del
  Bene and comSysto for writing the guide and providing the hours of
  converting it to our site.
 
  You can read the manual in 3 forms: multi page HTML, single page HTML
  and PDF.
 
  The contents:
   - Introduction
   - How to use the example code
   - Why should I learn Wicket?
   - Wicket says Hello, World!
   - Wicket as page layout manager
   - Keeping control over HTML
   - Component Lifecycle
   - Page versioning and caching
   - Under the hood of request processing
   - Wicket Links and URL generation
   - Wicket models and forms
   - Wicket forms in detail
   - Displaying multiple items with repeaters
   - Internationalization with Wicket
   - Resource management with Wicket
   - An example of integration with JavaScript
   - Wicket advanced topics
   - Working with AJAX
   - Integration with enterprise containers
   - Security with Wicket
   - Test Driven Development with Wicket
   - Test Driven Development with Wicket and Spring
   - Wicket Best Practices
   - Working with Maven (Appendix)
   - Project WicketStuff (Appendix)
   - Lost in redirection with Apache Wicket (Appendix)
   - Contributing to this guide (Appendix)
 
  Read more in the User guide by following this link:
 
  http://wicket.apache.org/start/userguide.html
 
  New CDI-1.1 integration project
  ---
 
  A new (experimental) module for CDI integration was added to support
  CDI 1.1 with Wicket. As CDI 1.0 and 1.1 are different beasts and not
  compatible, we had to craft a new module with specific support for the
  new CDI standard. The module is still experimental, but we expect to
  make it a default module in a couple of releases.
 
  You can use the new Wicket CDI module by including the following
  dependency in your POM:
 
  dependency
 groupIdorg.apache.wicket/groupId
  artifactIdwicket-cdi-1.1/artifactId
  version0.2/version
  /dependency
 
  Note that you have to remove the old wicket-cdi module and the Seam
  conversation dependency:
  org.jboss.seam.conversation:seam-conversation-weld
 
  For more information about what is new in CDI 1.1 read this blog post
  by Pete Muir: http://s.apache.org/newincdi11
 
  JQuery update in 6.9.0
  --
 
  As of Wicket 6.9 we ship JQuery 1.10.1. The JQuery project has
  decided to remove deprecated APIs from their codebase from JQuery 1.9
  and up. This means that JQuery plugins using these deprecated APIs no
  longer work. See the JQuery migration guide for more information,
  available from http://jquery.com/upgrade-guide/1.9/
 
  If your application depends on these deprecated APIs you can easily
  downgrade to JQuery 1.8.3-the previously provided JQuery that still
  contains these APIs. Download the 1.8.3 release of jquery and add it
  to your project in its application's init method:
 
  @Override
  protected void init() {
  getJavaScriptLibrarySettings()
  .setJQueryReference(yourJquery183ResourceReference);
  }
 
  CDI injection issue
  ---
 
  In the CDI releases of Weld 2.0.1 and prior, it was assumed that
  injection in anonymous inner classes was not legal and when
  

Re: [ANNOUNCE] Apache Wicket 6.13.0 adds free online user guide

2014-01-15 Thread Andrea Del Bene

Thank you Paul, I've fixed the quickstart

I think this release broke the quick start at:
http://wicket.apache.org/start/quickstart.html

When the page loads at first the Command Line is empty at first. Null
initial model object?
Selecting a different version from the drop down and then back to 6.13.0
will fill in the form field.


On Mon, Jan 13, 2014 at 11:00 AM, Martijn Dashorst dasho...@apache.orgwrote:




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



Re: CssBehaviour can't find css files

2014-01-15 Thread Anna Simbirtsev
http://www.freeuploadsite.com/do.php?id=31499

Here is a link to sample application. I t may not run.


On Wed, Jan 15, 2014 at 10:23 AM, Martin Grigorov mgrigo...@apache.orgwrote:

 Please create a quickstart application showing the problem.

 Martin Grigorov
 Wicket Training and Consulting


 On Wed, Jan 15, 2014 at 5:13 PM, Anna Simbirtsev asimbirt...@gmail.com
 wrote:

  htmlheadmeta http-equiv=Content-Type content=text/html;
  charset=ISO-8859-1/titleError 404
  NOT_FOUND/title/headbodyh2HTTP ERROR 404/h2pProblem
  accessing
 
 /wat-application/wicket/resource/CSSLinksInjector/info/css/styles-ver-1389797413000.css.
  Reason:preNOT_FOUND/pre/phr /ismallPowered by
  Jetty:///small/ibr/
br/br/
   br/
 br/
   br/br/
  br/
br/
  br/br/
 br/
   br/
  br/br/
 br/
   br/
  br/br/
 br/
   /body/html
 
  This error is shown inside the css file. I moved file in src/main/java/.
 
 
 
  On Tue, Jan 14, 2014 at 2:05 PM, Anna Simbirtsev asimbirt...@gmail.com
  wrote:
 
   Once I moved the file in src/main/java/ without any package, it does
 not
   show errors that it cant find it, so it is found, it just does not show
  any
   css.
  
  
   On Tue, Jan 14, 2014 at 10:31 AM, Martin Grigorov 
 mgrigo...@apache.org
  wrote:
  
   The reason is that you use info.afilias.WAT.UI.CSSLinksInjector as a
  scope
   and the resources are looked up relative to it in the package
 structure.
   In 1.4 it worked because you use '/info/...' - the leading slash
  resolved
   to the root package.
   This has been changed because of security problems and the leading
 slash
   is
   removed.
   I think latest 1.4.x also have this fix but I'm not 100% certain.
  
   If you want to keep the resources there you have to use a class in the
   root
   package as a scope.
   I.e. create a new class in src/main/java/ folder and use it at:
   CssReferenceHeaderItem.forReference(new CssResourceReference(HERE, ..
  
   Martin Grigorov
   Wicket Training and Consulting
  
  
   On Tue, Jan 14, 2014 at 5:22 PM, Anna Simbirtsev 
 asimbirt...@gmail.com
   wrote:
  
The file structure is
   
myApplication/src/main/java
myApplication/src/main/resources/info/css/ that has all css files
myApplication/src/main/resources/info/images has all the images
   
   
   
   
On Tue, Jan 14, 2014 at 10:04 AM, Martin Grigorov 
  mgrigo...@apache.org
wrote:
   
 What is the file structure ?
 What packages and files you have in UI package ?

 Martin Grigorov
 Wicket Training and Consulting


 On Tue, Jan 14, 2014 at 4:56 PM, Anna Simbirtsev 
   asimbirt...@gmail.com
 wrote:

  Do you have any other suggestions why it may not be able to find
  the
css
  file?
 
 
  On Tue, Jan 14, 2014 at 9:49 AM, Anna Simbirtsev 
asimbirt...@gmail.com
  wrote:
 
   this is a dynamic parameter, is changes based on settings, it
   should
 work
   either way
  
  
   On Tue, Jan 14, 2014 at 9:45 AM, Martin Grigorov 
mgrigo...@apache.org
  wrote:
  
   The only difference is that the resolved theme is 'info'
  instead
   of
  'root'
  
   Martin Grigorov
   Wicket Training and Consulting
  
  
   On Tue, Jan 14, 2014 at 4:43 PM, Anna Simbirtsev 
 asimbirt...@gmail.com
   wrote:
  
The name of the file is different and it cant find it
   
   
On Tue, Jan 14, 2014 at 9:41 AM, Martin Grigorov 
  mgrigo...@apache.org
wrote:
   
 It looks perfect!

 Martin Grigorov
 Wicket Training and Consulting


 On Tue, Jan 14, 2014 at 4:39 PM, Anna Simbirtsev 
   asimbirt...@gmail.com
 wrote:

  if I get rid of the CryptoMapper
  new link looks like
 
  link rel=stylesheet type=text/css
 
 

   
  
 

   
  
 
 href=./wicket/resource/info.afilias.WAT.UI.CSSLinksInjector/info/css/tooltip-ver-1389710287000.css
  view-source:
 

   
  
 

   
  
 
 http://localhost:8080/wat-application/wicket/resource/info.afilias.WAT.UI.CSSLinksInjector/info/css/tooltip-ver-1389710287000.css
  
  /
 
 
 
  On Tue, Jan 14, 2014 at 9:35 AM, Martin Grigorov 
   mgrigo...@apache.org
  wrote:
 
   Because you use CryptoMapper in your app.
 

Should we expect empty PageParameters for pages that have such a constructor yet no parameters are available?

2014-01-15 Thread Paul Bors
Suppose I have a page with the default constructor and with the page
parameter constructor.

Should my page parameter constructor be called with an empty not null
PageParameter instance when no parameters are provided? Shouldn't the
default constructor be used instead?

What about in unit tests?
I've seen the tester use the page parameter constructor and pass it a
reference to an empty PageParameters when I invoke
tester.startPage(MyPage.class, null).


Re: Should we expect empty PageParameters for pages that have such a constructor yet no parameters are available?

2014-01-15 Thread Paul Bors
Btw, I just noticed that adding this constructor eliminates the problem:
public MyPage() {
this(null);
}

So I take it Wicket tries to build the page via the Page(PageParameters)
but instead of using a null reference to the PageParameters it builds an
object without any parameters in it.

If the default constructor is added, then it can invoke the custom
PageParameters constructor with the null reference.
I don't recall this behavior. Has this changed recently?


On Wed, Jan 15, 2014 at 1:45 PM, Paul Bors p...@bors.ws wrote:

 Suppose I have a page with the default constructor and with the page
 parameter constructor.

 Should my page parameter constructor be called with an empty not null
 PageParameter instance when no parameters are provided? Shouldn't the
 default constructor be used instead?

 What about in unit tests?
 I've seen the tester use the page parameter constructor and pass it a
 reference to an empty PageParameters when I invoke
 tester.startPage(MyPage.class, null).



Re: Wicket war file deployment to Heroku

2014-01-15 Thread Gerrit Wassink
Hello Martijn,
Thank you for your reply, but that is what i already did.I even deleted this 
file and made a new one with capital P but after deploying again the same 
error came back.
Is it possible that the solution is in this link:
http://apache-wicket.1842946.n4.nabble.com/Wicket-war-file-deployment-to-Heroku-tp4663737.html
 
because i followed one of the manuals of Heroku site according to deploy with 
Jetty runner and the approach in above link is somewhat different.This works 
locally but i maybe some start.class must be in this Procfile??
Greetings Gerrit



Martijn Dashorst martijn.dasho...@gmail.com , 15-1-2014 16:40:
Change the case of your procfile to Procfile. 
 
That is what the error says. 
 
Martijn 
 
On Wed, Jan 15, 2014 at 3:36 PM, Gerrit Wassink 
gerrit.wass...@qfactors.nl wrote: 
 Martin, 
 This is the error on the Heroku site: 
 ==Application ErrorAn error occurred in the 
 application and your page could not be served. Please try again in a few 
 moments. 
 If you are the application owner, check your logs for 
 details. 
 But after deploying to Heroku there are no errors only in the end something 
 about the Procfile: 
 SHOT.pom       [INFO] 
        [INFO] 
 BUILD SUCCESS       [INFO] 
        [INFO] 
 Total time: 14.688s       [INFO] Finished at: Wed Jan 15 09:36:40 UTC 2014    
    [INFO] Final Memory: 19M/514M       [INFO] 
 - 
 Discovering process types 
  ~     Mis-cased procfile detected; ignoring. ~     Rename it to Procfile to 
 have it honored. 
        Procfile declares types - (none) 
 - Compressing... done, 93.4MB- Launching... done, v6       
 http://ancient-headland-1117.herokuapp.com deployed to Heroku 
 To g...@heroku.com:ancient-headland-1117.git * [new branch]      master - 
 master 
 What i did is following the tutorials on the Heroku site.Do you have any 
 experience with deploying wicket application on Heroku? 
 Greetings Gerrit 
 
 
 
 Martin Grigorov mgrigo...@apache.org , 15-1-2014 15:01: 
 What is the error ? 
 
 Martin Grigorov 
 Wicket Training and Consulting 
 
 
 On Wed, Jan 15, 2014 at 3:57 PM, gerritqf gerrit.wass...@qfactors.nlwrote: 
 
 Hello Forum members, 
 
 I am trying to deploy a java webapplication with Wicket to Heroku site. 
 The war file is build with maven and can run with Jetty-runner on 
 localhost:8080. 
 Now after deploying to Heroku the site comes up with a Application error. 
 
 Maybe you can help me with how and what i must do. For example the Procfile 
 and system.properties file. 
 
 I found this link: 
 
 
 http://wicketinaction.com/2011/09/git-wicket-running-on-heroku/comment-page-1/
  
 
 but is this a way to follow? 
 
 Thanks a lot for your answer! 
 
 Gerrit 
 
 -- 
 View this message in context: 
 http://apache-wicket.1842946.n4.nabble.com/Wicket-war-file-deployment-to-Heroku-tp4663737.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 
 
 
 
 
 
--  
Become a Wicket expert, learn from the best: http://wicketinaction.com 
 
- 
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org 
For additional commands, e-mail: users-h...@wicket.apache.org 
 


Re: Wicket war file deployment to Heroku

2014-01-15 Thread Martin Grigorov
Without the error it will be hard to find out what is wrong.
Try harder to find the error logs.

Martin Grigorov
Wicket Training and Consulting


On Wed, Jan 15, 2014 at 9:16 PM, Gerrit Wassink
gerrit.wass...@qfactors.nlwrote:

 Hello Martijn,
 Thank you for your reply, but that is what i already did.I even deleted
 this file and made a new one with capital P but after deploying again the
 same error came back.
 Is it possible that the solution is in this link:

 http://apache-wicket.1842946.n4.nabble.com/Wicket-war-file-deployment-to-Heroku-tp4663737.html

 because i followed one of the manuals of Heroku site according to deploy
 with Jetty runner and the approach in above link is somewhat different.This
 works locally but i maybe some start.class must be in this Procfile??
 Greetings Gerrit



 Martijn Dashorst martijn.dasho...@gmail.com , 15-1-2014 16:40:
 Change the case of your procfile to Procfile.

 That is what the error says.

 Martijn

 On Wed, Jan 15, 2014 at 3:36 PM, Gerrit Wassink
 gerrit.wass...@qfactors.nl wrote:
  Martin,
  This is the error on the Heroku site:
  ==Application ErrorAn error occurred in
 the application and your page could not be served. Please try again in a
 few moments.
  If you are the application owner, check your logs for
 details.
  But after deploying to Heroku there are no errors only in the end
 something about the Procfile:
  SHOT.pom
 [INFO] 
   [INFO] BUILD SUCCESS   [INFO]
 
 [INFO] Total time: 14.688s   [INFO] Finished at: Wed Jan 15 09:36:40
 UTC 2014   [INFO] Final Memory: 19M/514M   [INFO]
 -
 Discovering process types
   ~ Mis-cased procfile detected; ignoring. ~ Rename it to
 Procfile to have it honored.
 Procfile declares types - (none)
  - Compressing... done, 93.4MB- Launching... done, v6
 http://ancient-headland-1117.herokuapp.com deployed to Heroku
  To g...@heroku.com:ancient-headland-1117.git * [new branch]  master
 - master
  What i did is following the tutorials on the Heroku site.Do you have any
 experience with deploying wicket application on Heroku?
  Greetings Gerrit
 
 
 
  Martin Grigorov mgrigo...@apache.org , 15-1-2014 15:01:
  What is the error ?
 
  Martin Grigorov
  Wicket Training and Consulting
 
 
  On Wed, Jan 15, 2014 at 3:57 PM, gerritqf gerrit.wass...@qfactors.nl
 wrote:
 
  Hello Forum members,
 
  I am trying to deploy a java webapplication with Wicket to Heroku site.
  The war file is build with maven and can run with Jetty-runner on
  localhost:8080.
  Now after deploying to Heroku the site comes up with a Application
 error.
 
  Maybe you can help me with how and what i must do. For example the
 Procfile
  and system.properties file.
 
  I found this link:
 
 
 
 http://wicketinaction.com/2011/09/git-wicket-running-on-heroku/comment-page-1/
 
  but is this a way to follow?
 
  Thanks a lot for your answer!
 
  Gerrit
 
  --
  View this message in context:
 
 http://apache-wicket.1842946.n4.nabble.com/Wicket-war-file-deployment-to-Heroku-tp4663737.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
 
 



 --
 Become a Wicket expert, learn from the best: http://wicketinaction.com

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




Re: Should we expect empty PageParameters for pages that have such a constructor yet no parameters are available?

2014-01-15 Thread Martin Grigorov
AFAIR if there are no request parameters then Wicket first uses the Java
default constructor (no parameters) if available.
If there is no such constructor then Wicket constructs an empty
PageParameters and uses it for the constructor with PageParameters.
If none are available then an error is thrown.

Consult with DefaultPageFactory.java

Martin Grigorov
Wicket Training and Consulting


On Wed, Jan 15, 2014 at 8:50 PM, Paul Bors p...@bors.ws wrote:

 Btw, I just noticed that adding this constructor eliminates the problem:
 public MyPage() {
 this(null);
 }

 So I take it Wicket tries to build the page via the Page(PageParameters)
 but instead of using a null reference to the PageParameters it builds an
 object without any parameters in it.

 If the default constructor is added, then it can invoke the custom
 PageParameters constructor with the null reference.
 I don't recall this behavior. Has this changed recently?


 On Wed, Jan 15, 2014 at 1:45 PM, Paul Bors p...@bors.ws wrote:

  Suppose I have a page with the default constructor and with the page
  parameter constructor.
 
  Should my page parameter constructor be called with an empty not null
  PageParameter instance when no parameters are provided? Shouldn't the
  default constructor be used instead?
 
  What about in unit tests?
  I've seen the tester use the page parameter constructor and pass it a
  reference to an empty PageParameters when I invoke
  tester.startPage(MyPage.class, null).
 



Re: Models and page serialization

2014-01-15 Thread Martin Grigorov
See for example SerializableChecker.
It does the same - checks that a serialized object implements
java.io.Serializable.
If it doesn't then it prints a nice message explaining where this object is
used.

Martin Grigorov
Wicket Training and Consulting


On Wed, Jan 15, 2014 at 6:29 PM, gmparker2000 greg.par...@brovada.comwrote:

 Thanks for the tip.  I'm a little unclear on what this is telling me
 though.
 Wouldn't this just tell me if the detach method of all my LDMs was called?
 What I'm interested in determining is where my LDMs are directly
 referencing
 objects that will inadvertantly get serialized with the LDM.   For example,
 if an LDM has a member variable pointing to an object or the LDM accesses a
 final variable from its parent class.  I want to be sure I'm not
 serializing
 business objects or references to business objects along with the page.

 --
 View this message in context:
 http://apache-wicket.1842946.n4.nabble.com/Models-and-page-serialization-tp4663668p4663746.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




Re: Models and page serialization

2014-01-15 Thread gmparker2000
The problem is that my business objects do implement serializable for another
reason.  However, I don't want Wicket to serialize them.  So I could remove
Serializable and see what happens but I was hoping for a way to just look at
what is getting serialized.

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Models-and-page-serialization-tp4663668p4663758.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



Re: Models and page serialization

2014-01-15 Thread Martin Grigorov
Do your business objects have common property ?
base class/interface, annotation, ... ?
If YES then you can check for it and write the nice error message when you
see such.

Martin Grigorov
Wicket Training and Consulting


On Wed, Jan 15, 2014 at 10:29 PM, gmparker2000 greg.par...@brovada.comwrote:

 The problem is that my business objects do implement serializable for
 another
 reason.  However, I don't want Wicket to serialize them.  So I could remove
 Serializable and see what happens but I was hoping for a way to just look
 at
 what is getting serialized.

 --
 View this message in context:
 http://apache-wicket.1842946.n4.nabble.com/Models-and-page-serialization-tp4663668p4663758.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




Re: Should we expect empty PageParameters for pages that have such a constructor yet no parameters are available?

2014-01-15 Thread Paul Bors
Awsome, thanks!

One last question, in my tests I keep a collection of page parameters for
my pages.
I've noticed at some point wicket tester (or deeper in the framework, prob.
in the page factory) that the PageParameter instance used had the
parameters combined from different instances. That scared me a bit.

ie: I have
customConstructors = new HashMapClass? extends AdminPage,
PageParameters();
customConstructors.put(PageA.class, new PageParameters().set(pageID,
-1));
customConstructors.put(PageB.class, new PageParameters().set(sessionID,
-2));

and then later when running the test:
PageParameters pageParameters = customConstructors.get(pageClass);
if(pageParameters != null) {
log.info(Running  + pageTest.getTestName() +  for  +
pageClass.getName() +  with pageParameters of  + pageParameters);
pageTest.runTest(getTester(), pageClass,
customConstructors.get(pageClass));
}

Above log stamenent would print correct, but when in the page constructor
both pageID AND sessionID are present althrough those are 2 different
instances of PageParameters.

Should I dig more into that?
To me that sounds like a bug :(




On Wed, Jan 15, 2014 at 2:24 PM, Martin Grigorov mgrigo...@apache.orgwrote:

 AFAIR if there are no request parameters then Wicket first uses the Java
 default constructor (no parameters) if available.
 If there is no such constructor then Wicket constructs an empty
 PageParameters and uses it for the constructor with PageParameters.
 If none are available then an error is thrown.

 Consult with DefaultPageFactory.java

 Martin Grigorov
 Wicket Training and Consulting


 On Wed, Jan 15, 2014 at 8:50 PM, Paul Bors p...@bors.ws wrote:

  Btw, I just noticed that adding this constructor eliminates the problem:
  public MyPage() {
  this(null);
  }
 
  So I take it Wicket tries to build the page via the Page(PageParameters)
  but instead of using a null reference to the PageParameters it builds an
  object without any parameters in it.
 
  If the default constructor is added, then it can invoke the custom
  PageParameters constructor with the null reference.
  I don't recall this behavior. Has this changed recently?
 
 
  On Wed, Jan 15, 2014 at 1:45 PM, Paul Bors p...@bors.ws wrote:
 
   Suppose I have a page with the default constructor and with the page
   parameter constructor.
  
   Should my page parameter constructor be called with an empty not null
   PageParameter instance when no parameters are provided? Shouldn't the
   default constructor be used instead?
  
   What about in unit tests?
   I've seen the tester use the page parameter constructor and pass it a
   reference to an empty PageParameters when I invoke
   tester.startPage(MyPage.class, null).
  
 



Re: [ANNOUNCE] Apache Wicket 6.13.0 adds free online user guide

2014-01-15 Thread Paul Bors
Thanks Andres, and also as per the rest of the community...

Thank you for the guide :)


On Wed, Jan 15, 2014 at 1:17 PM, Andrea Del Bene an.delb...@gmail.comwrote:

 Thank you Paul, I've fixed the quickstart

  I think this release broke the quick start at:
 http://wicket.apache.org/start/quickstart.html

 When the page loads at first the Command Line is empty at first. Null
 initial model object?
 Selecting a different version from the drop down and then back to 6.13.0
 will fill in the form field.


 On Mon, Jan 13, 2014 at 11:00 AM, Martijn Dashorst dasho...@apache.org
 wrote:



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




Re: Should we expect empty PageParameters for pages that have such a constructor yet no parameters are available?

2014-01-15 Thread Martin Grigorov
On Thu, Jan 16, 2014 at 12:07 AM, Paul Bors p...@bors.ws wrote:

 Awsome, thanks!

 One last question, in my tests I keep a collection of page parameters for
 my pages.
 I've noticed at some point wicket tester (or deeper in the framework, prob.
 in the page factory) that the PageParameter instance used had the
 parameters combined from different instances. That scared me a bit.

 ie: I have
 customConstructors = new HashMapClass? extends AdminPage,
 PageParameters();
 customConstructors.put(PageA.class, new PageParameters().set(pageID,
 -1));
 customConstructors.put(PageB.class, new PageParameters().set(sessionID,
 -2));

 and then later when running the test:
 PageParameters pageParameters = customConstructors.get(pageClass);
 if(pageParameters != null) {
 log.info(Running  + pageTest.getTestName() +  for  +
 pageClass.getName() +  with pageParameters of  + pageParameters);
 pageTest.runTest(getTester(), pageClass,
 customConstructors.get(pageClass));
 }

 Above log stamenent would print correct, but when in the page constructor
 both pageID AND sessionID are present althrough those are 2 different
 instances of PageParameters.

 Should I dig more into that?
 To me that sounds like a bug :(


Yes, it is not correct behavior if you use tester.startPage(clazz,
parameters).
Make a quickstart and attach it to Jira.






 On Wed, Jan 15, 2014 at 2:24 PM, Martin Grigorov mgrigo...@apache.org
 wrote:

  AFAIR if there are no request parameters then Wicket first uses the Java
  default constructor (no parameters) if available.
  If there is no such constructor then Wicket constructs an empty
  PageParameters and uses it for the constructor with PageParameters.
  If none are available then an error is thrown.
 
  Consult with DefaultPageFactory.java
 
  Martin Grigorov
  Wicket Training and Consulting
 
 
  On Wed, Jan 15, 2014 at 8:50 PM, Paul Bors p...@bors.ws wrote:
 
   Btw, I just noticed that adding this constructor eliminates the
 problem:
   public MyPage() {
   this(null);
   }
  
   So I take it Wicket tries to build the page via the
 Page(PageParameters)
   but instead of using a null reference to the PageParameters it builds
 an
   object without any parameters in it.
  
   If the default constructor is added, then it can invoke the custom
   PageParameters constructor with the null reference.
   I don't recall this behavior. Has this changed recently?
  
  
   On Wed, Jan 15, 2014 at 1:45 PM, Paul Bors p...@bors.ws wrote:
  
Suppose I have a page with the default constructor and with the page
parameter constructor.
   
Should my page parameter constructor be called with an empty not null
PageParameter instance when no parameters are provided? Shouldn't the
default constructor be used instead?
   
What about in unit tests?
I've seen the tester use the page parameter constructor and pass it a
reference to an empty PageParameters when I invoke
tester.startPage(MyPage.class, null).
   
  
 



Best way to do authentication in external system

2014-01-15 Thread Илья Нарыжный
Guys,

Please advice me. What's the best way to implement authentication in
external system(support of Single Sign On)? I know 3 variants, but all of
them have different pros and cons.

1) Implement your own IRequestCycleListener. You are intercepting all
requests, finding out those that should be authenticated externally and
proceeed with proper operations (commonly redirect to external system).
2) Implement of IREquestMapper. HttpsMapper can be taken as some kind of
example.
3) Override restartResponseAtSignInPage() and redirect to external system
if required.

So, what is the best one? May be you know more variants?

Thanks,

Ilia


Wicket browser autocomplete

2014-01-15 Thread MikeDundee
Hello,

I'm trying to figure out how to make html autocomplete work (browser offers
values previously entered).

The problem is that I have dynamically generated complex form hierarchy with
variant number of fields. Wicket uses html attribute name and fills it
with path of the component in component hierarchy.

Browsers store previous values for autocompletion based on name attribute.

However my names look like:
formList:udajForm144:wrapForm:value ...
formList:udajForm145:wrapForm:nestedForm:value ...

Across all forms on the page there are fields like email, city, street,
name, surname etc. which should share autocompletion values.
However they are not shared because they have different name. Moreover,
autocompletion works poorly even with single field, because when page is
rendered next time, the field can get absolutely different name (because
there are repeating panels which give components another index).

Is there any way to overcome this limitation?
I found out that IE permits html attribute vcard_name (which overrides name
for autocompletion purposes), but this does not work in FF or Chrome.

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wicket-browser-autocomplete-tp4663766.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



Re: CssBehaviour can't find css files

2014-01-15 Thread Martin Grigorov
Yes.
It doesn't (build):

mvn clean
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project - [Help 1]
[ERROR]
[ERROR]   The project sampleApp:sampleApp:1.1
(/home/martin/tmp/debug/sampleApp/pom.xml) has 11 errors
[ERROR] 'dependencies.dependency.version' for
org.apache.wicket:wicket-core:jar must be a valid version but is
'${wicket.version}'. @ line 15, column 16
[ERROR] 'dependencies.dependency.version' for
org.apache.wicket:wicket-extensions:jar must be a valid version but is
'${wicket.version}'. @ line 19, column 16
[ERROR] 'dependencies.dependency.version' for
org.apache.wicket:wicket-datetime:jar must be a valid version but is
'${wicket.version}'. @ line 23, column 16
[ERROR] 'dependencies.dependency.version' for
org.apache.wicket:wicket-devutils:jar must be a valid version but is
'${wicket.version}'. @ line 27, column 16
[ERROR] 'dependencies.dependency.version' for
org.apache.wicket:wicket-jmx:jar must be a valid version but is
'${wicket.version}'. @ line 31, column 16
[ERROR] 'dependencies.dependency.version' for
org.springframework:spring-core:jar must be a valid version but is
'${spring.version}'. @ line 36, column 16
[ERROR] 'dependencies.dependency.version' for
org.springframework:spring-context:jar must be a valid version but is
'${spring.version}'. @ line 41, column 16
[ERROR] 'dependencies.dependency.version' for
org.springframework:spring-web:jar must be a valid version but is
'${spring.version}'. @ line 46, column 16
[ERROR] 'dependencies.dependency.version' for
org.apache.wicket:wicket-spring:jar must be a valid version but is
'${wicket.version}'. @ line 64, column 16
[ERROR] 'dependencies.dependency.version' for
org.mortbay.jetty:jetty:jar must be a valid version but is
'${jetty.version}'. @ line 130, column 16
[ERROR] 'dependencies.dependency.version' for
org.mortbay.jetty:jetty-util:jar must be a valid version but is
'${jetty.version}'. @ line 136, column 16
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException


You should respect more our time.
We want to help but you must make an effort yourself!


Martin Grigorov
Wicket Training and Consulting


On Wed, Jan 15, 2014 at 8:24 PM, Anna Simbirtsev asimbirt...@gmail.comwrote:

 http://www.freeuploadsite.com/do.php?id=31499

 Here is a link to sample application. I t may not run.


 On Wed, Jan 15, 2014 at 10:23 AM, Martin Grigorov mgrigo...@apache.org
 wrote:

  Please create a quickstart application showing the problem.
 
  Martin Grigorov
  Wicket Training and Consulting
 
 
  On Wed, Jan 15, 2014 at 5:13 PM, Anna Simbirtsev asimbirt...@gmail.com
  wrote:
 
   htmlheadmeta http-equiv=Content-Type content=text/html;
   charset=ISO-8859-1/titleError 404
   NOT_FOUND/title/headbodyh2HTTP ERROR 404/h2pProblem
   accessing
  
 
 /wat-application/wicket/resource/CSSLinksInjector/info/css/styles-ver-1389797413000.css.
   Reason:preNOT_FOUND/pre/phr /ismallPowered by
   Jetty:///small/ibr/
 br/br/
br/
  br/
br/br/
   br/
 br/
   br/br/
  br/
br/
   br/br/
  br/
br/
   br/br/
  br/
/body/html
  
   This error is shown inside the css file. I moved file in
 src/main/java/.
  
  
  
   On Tue, Jan 14, 2014 at 2:05 PM, Anna Simbirtsev 
 asimbirt...@gmail.com
   wrote:
  
Once I moved the file in src/main/java/ without any package, it does
  not
show errors that it cant find it, so it is found, it just does not
 show
   any
css.
   
   
On Tue, Jan 14, 2014 at 10:31 AM, Martin Grigorov 
  mgrigo...@apache.org
   wrote:
   
The reason is that you use info.afilias.WAT.UI.CSSLinksInjector as a
   scope
and the resources are looked up relative to it in the package
  structure.
In 1.4 it worked because you use '/info/...' - the leading slash
   resolved
to the root package.
This has been changed because of security problems and the leading
  slash
is
removed.
I think latest 1.4.x also have this fix but I'm not 100% certain.
   
If you want to keep the resources there you have to use a class in
 the
root
package as a scope.
I.e. create a new class in src/main/java/ folder and use it at:

Re: Wicket browser autocomplete

2014-01-15 Thread Martin Grigorov
Hi,

Try by overriding FormComponent#getInputName().

Martin Grigorov
Wicket Training and Consulting


On Thu, Jan 16, 2014 at 9:40 AM, MikeDundee mikedun...@centrum.cz wrote:

 Hello,

 I'm trying to figure out how to make html autocomplete work (browser offers
 values previously entered).

 The problem is that I have dynamically generated complex form hierarchy
 with
 variant number of fields. Wicket uses html attribute name and fills it
 with path of the component in component hierarchy.

 Browsers store previous values for autocompletion based on name
 attribute.

 However my names look like:
 formList:udajForm144:wrapForm:value ...
 formList:udajForm145:wrapForm:nestedForm:value ...

 Across all forms on the page there are fields like email, city, street,
 name, surname etc. which should share autocompletion values.
 However they are not shared because they have different name. Moreover,
 autocompletion works poorly even with single field, because when page is
 rendered next time, the field can get absolutely different name (because
 there are repeating panels which give components another index).

 Is there any way to overcome this limitation?
 I found out that IE permits html attribute vcard_name (which overrides name
 for autocompletion purposes), but this does not work in FF or Chrome.

 --
 View this message in context:
 http://apache-wicket.1842946.n4.nabble.com/Wicket-browser-autocomplete-tp4663766.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




Re: Best way to do authentication in external system

2014-01-15 Thread Martin Grigorov
Hi,

4) Add a Servlet Filter *before* WicketFilter in web.xml
The new filter will check whether there is an authenticated user or not and
do whatever is needed

Martin Grigorov
Wicket Training and Consulting


On Thu, Jan 16, 2014 at 9:29 AM, Илья Нарыжный phan...@ydn.ru wrote:

 Guys,

 Please advice me. What's the best way to implement authentication in
 external system(support of Single Sign On)? I know 3 variants, but all of
 them have different pros and cons.

 1) Implement your own IRequestCycleListener. You are intercepting all
 requests, finding out those that should be authenticated externally and
 proceeed with proper operations (commonly redirect to external system).
 2) Implement of IREquestMapper. HttpsMapper can be taken as some kind of
 example.
 3) Override restartResponseAtSignInPage() and redirect to external system
 if required.

 So, what is the best one? May be you know more variants?

 Thanks,

 Ilia