Re: Apache Wicket 1.5.8 is released

[Martin Grigorov]

Thanks!

I've missed a step in our post-release process.
Fixed.

On Wed, Sep 5, 2012 at 8:56 AM, Maarten Bosteels
mbosteels@gmail.com wrote:
 Congratulations with the new release.

 I guess it would be best if 1.5.8 was added to the dropdown box (and become
 the default option) on http://wicket.apache.org/start/quickstart.html

 regards
 Maarten

 On Fri, Aug 24, 2012 at 5:02 PM, Martin Grigorov mgrigo...@apache.orgwrote:

 This is the eighth maintenance release of the Wicket 1.5.x series. This
 release brings over 45 bug fixes and improvements.

 Git tag:
 release/wicket-1.5.8

 Changelog:

 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310561version=12321662

 Maven:
 dependency
  groupIdorg.apache.wicket/groupId
  artifactIdwicket-core/artifactId
  version1.5.8/version
 /dependency


 Download the full distribution (including source):
 http://www.apache.org/dyn/closer.cgi/wicket/1.5.8

 The Wicket team

 -
 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

Re: Migration to 1.5: 'X' is not a valid Serializable

[dpmihai]

see this:
http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-ListMultipleChoice-add-Serializable-values-td4585991.html#a4586026



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Migration-to-1-5-X-is-not-a-valid-Serializable-tp4651757p4651764.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: Question about unit testing

[Martin Makundi]

https://cwiki.apache.org/WICKET/type-safe-testing-in-wicket.html

=)

2012/9/5 Markward Schubert markward.schub...@gmail.com:
 Hi folks!

 I am sure this is a trivial question, but i am simply too dumb to figure
 this out.
 We have a DopDownChoice, which is prefilled by some modelvalue, given to
 the page.
 Until now i was doing some testing about the model-state before and after
 submitting, which then was correct.
 The problem in the browser was, that the rendered DropDownChoice did  not
 show the preselected value correctly. It could not recognize the equality
 between some member of the available choices and the model's choice.

 Actually it turned out that it was a problem with the model object's
 equals.

 Now my question is:

 What is the most elegant way to unit test the correct rendering of the
 preselection of the DropDownChoice or similar components?
 As said, simply dealing with sumbmit and stuff worked correctly.


 Regards,

 Markward

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

Re: Question about unit testing

[Markward Schubert]

Thanks for the link!

This is really interesting and I think I will adapt this.
Unfortunately I am not sure if this addresses my original Problem.

What I need is a kind of code, like this:

// start page...
tester.startComponentInPage(MyFormPanel.)

// verify that after initial page rendering, the selected item in the
DropDown equals the pageModel's
assertEquals(pageModel.myChoice.getLabel(),getDropDownChoice().currentlyRenderedSelectedChoiceItem());

As described before, I had a problem in the equals. This resulted in
myChoice being let's say red and the DropDown containing red black
blue, but please select was rendered in the DDC, because myChoice(red)
was not equal to dropChoice(red).

Sorry for the pseudo code :-)

So the DDC could not find out that the red of my model was the same as the
red in the choices list.
Of course this would be a stupid bug, but i would like to protect my code
against fellows changing the equals behavior.





--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Question-about-unit-testing-tp4651766p4651768.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

Error ESC key press event

[Marco Di Sabatino Di Diodoro]

Hi all,

I configure into Apache Syncope the possibility to close ModalWindow with ESC 
key press event.

public class CloseOnESCBehavior extends AbstractDefaultAjaxBehavior {

private static final long serialVersionUID = 5826308247642534260L;
private ModalWindow modalWindow;

public CloseOnESCBehavior(ModalWindow modalWindow) {
this.modalWindow = modalWindow;
}

private static final String PRE_JS = $(document).ready(function() {\n
+ $(document).bind('keyup', function(evt) {\n
+ if (evt.keyCode == 27){\n;

private static final String POST_JS = \n evt.preventDefault();\n
+ evt.stopImmediatePropagation();\n
+ }\n
+   });\n
+ });;

@Override
protected void respond(final AjaxRequestTarget target) {
modalWindow.close(target);
}

@Override
protected String findIndicatorId() {
return null;
}

@Override
public void renderHead(final Component component, final IHeaderResponse 
response) {
response.renderJavaScript(new 
StringBuilder(PRE_JS).append(getCallbackScript())
.append(POST_JS).toString(),
closeModalOnEsc);
}

In the modal page:

add(new CloseOnESCBehavior(window));

It work correctly with Chrome and Safari. With Firefox, if I press the ESC key 
twice quickly before the window closes the console return an error:

ERROR: Wicket.Ajax.Call.failure: Error while parsing response: Could not find 
root ajax-response element

Regards
Marco


--

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 PPMC Member
http://people.apache.org/~mdisabatino

Re: Error ESC key press event

[Martin Grigorov]

Hi Marco,

I see a quite simple solution with Wicket 6 for this. I think you just
start with your project (or even this is just a prototype?) so you
better use the latest and greatest :-)

What I mean is to use the new AjaxChannel.Type.Active. The active type
prevents a second Ajax call in the same channel while there is a still
running Ajax call in this channel.

The code is as simple as:

@Override
protected void updateAjaxAttributes(AjaxRequestAttributes attrs) {
   super.updateAjaxAttributes(attrs);

   attrs.setAjaxChannel(new AjaxChannel(modalClose, Type.Active));
}

For more about the goodies in Wicket 6 read:
http://wicketinaction.com/2012/07/wicket-6-javascript-improvements/

In Wicket 1.5 you will have to add some custom JavaScript to prevent
the second request. You can unbind the event, or add a flag for
example.

On Wed, Sep 5, 2012 at 12:04 PM, Marco Di Sabatino Di Diodoro
marco.disabat...@tirasa.net wrote:
 Hi all,

 I configure into Apache Syncope the possibility to close ModalWindow with ESC 
 key press event.

 public class CloseOnESCBehavior extends AbstractDefaultAjaxBehavior {

 private static final long serialVersionUID = 5826308247642534260L;
 private ModalWindow modalWindow;

 public CloseOnESCBehavior(ModalWindow modalWindow) {
 this.modalWindow = modalWindow;
 }

 private static final String PRE_JS = $(document).ready(function() {\n
 + $(document).bind('keyup', function(evt) {\n
 + if (evt.keyCode == 27){\n;

 private static final String POST_JS = \n evt.preventDefault();\n
 + evt.stopImmediatePropagation();\n
 + }\n
 +   });\n
 + });;

 @Override
 protected void respond(final AjaxRequestTarget target) {
 modalWindow.close(target);
 }

 @Override
 protected String findIndicatorId() {
 return null;
 }

 @Override
 public void renderHead(final Component component, final IHeaderResponse 
 response) {
 response.renderJavaScript(new 
 StringBuilder(PRE_JS).append(getCallbackScript())
 .append(POST_JS).toString(),
 closeModalOnEsc);
 }

 In the modal page:

 add(new CloseOnESCBehavior(window));

 It work correctly with Chrome and Safari. With Firefox, if I press the ESC 
 key twice quickly before the window closes the console return an error:

 ERROR: Wicket.Ajax.Call.failure: Error while parsing response: Could not find 
 root ajax-response element

 Regards
 Marco


 --

 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 PPMC Member
 http://people.apache.org/~mdisabatino







-- 
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

Re: Jqwicket

[Pierre Goupil]

Excellent! Thank you, everybody!



On Tue, Sep 4, 2012 at 11:17 PM, mk bigpur...@gmail.com wrote:

 I've started Wicket 6 migration, check the SCM. Plan to release next
 JQWicket
 version after Wicket 6 final is available.



 --
 View this message in context:
 http://apache-wicket.1842946.n4.nabble.com/Jqwicket-tp4651665p4651754.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




-- 
Le bonheur n'est pas une destination, mais une façon de voyager.

Papa d'une petite Lou-Ann depuis le 30 juin.

Re: Error ESC key press event

[Marco Di Sabatino Di Diodoro]

Hi Martin,

On Sep 5, 2012, at 12:20 PM, Martin Grigorov wrote:

 Hi Marco,
 
 I see a quite simple solution with Wicket 6 for this. I think you just
 start with your project (or even this is just a prototype?) so you
 better use the latest and greatest :-)

We can not upgrade to Wicket 6 in this moment.

 
 What I mean is to use the new AjaxChannel.Type.Active. The active type
 prevents a second Ajax call in the same channel while there is a still
 running Ajax call in this channel.
 
 The code is as simple as:
 
 @Override
 protected void updateAjaxAttributes(AjaxRequestAttributes attrs) {
   super.updateAjaxAttributes(attrs);
 
   attrs.setAjaxChannel(new AjaxChannel(modalClose, Type.Active));
 }
 
 For more about the goodies in Wicket 6 read:
 http://wicketinaction.com/2012/07/wicket-6-javascript-improvements/
 
 In Wicket 1.5 you will have to add some custom JavaScript to prevent
 the second request. You can unbind the event, or add a flag for
 example.

I tried to use unbind() and flag but always return me the same error. How can I 
prevent the second request?

Thanks
Marco

 
 On Wed, Sep 5, 2012 at 12:04 PM, Marco Di Sabatino Di Diodoro
 marco.disabat...@tirasa.net wrote:
 Hi all,
 
 I configure into Apache Syncope the possibility to close ModalWindow with 
 ESC key press event.
 
 public class CloseOnESCBehavior extends AbstractDefaultAjaxBehavior {
 
private static final long serialVersionUID = 5826308247642534260L;
private ModalWindow modalWindow;
 
public CloseOnESCBehavior(ModalWindow modalWindow) {
this.modalWindow = modalWindow;
}
 
private static final String PRE_JS = $(document).ready(function() {\n
+ $(document).bind('keyup', function(evt) {\n
+ if (evt.keyCode == 27){\n;
 
private static final String POST_JS = \n evt.preventDefault();\n
+ evt.stopImmediatePropagation();\n
+ }\n
+   });\n
+ });;
 
@Override
protected void respond(final AjaxRequestTarget target) {
modalWindow.close(target);
}
 
@Override
protected String findIndicatorId() {
return null;
}
 
@Override
public void renderHead(final Component component, final IHeaderResponse 
 response) {
response.renderJavaScript(new 
 StringBuilder(PRE_JS).append(getCallbackScript())
.append(POST_JS).toString(),
closeModalOnEsc);
}
 
 In the modal page:
 
 add(new CloseOnESCBehavior(window));
 
 It work correctly with Chrome and Safari. With Firefox, if I press the ESC 
 key twice quickly before the window closes the console return an error:
 
 ERROR: Wicket.Ajax.Call.failure: Error while parsing response: Could not 
 find root ajax-response element
 
 Regards
 Marco
 
 
 --
 
 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 PPMC Member
 http://people.apache.org/~mdisabatino
 
 
 
 
 
 
 
 -- 
 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
 

--

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 PPMC Member
http://people.apache.org/~mdisabatino

Re: Error ESC key press event

[Martin Grigorov]

Hi,

You already wrap the call to wicketAjaxXXX() method in if statement.
Just raise a flag that you entered in this code and set it back to
false in the success/failure handler.

On Wed, Sep 5, 2012 at 3:40 PM, Marco Di Sabatino Di Diodoro
marco.disabat...@tirasa.net wrote:
 Hi Martin,

 On Sep 5, 2012, at 12:20 PM, Martin Grigorov wrote:

 Hi Marco,

 I see a quite simple solution with Wicket 6 for this. I think you just
 start with your project (or even this is just a prototype?) so you
 better use the latest and greatest :-)

 We can not upgrade to Wicket 6 in this moment.


 What I mean is to use the new AjaxChannel.Type.Active. The active type
 prevents a second Ajax call in the same channel while there is a still
 running Ajax call in this channel.

 The code is as simple as:

 @Override
 protected void updateAjaxAttributes(AjaxRequestAttributes attrs) {
   super.updateAjaxAttributes(attrs);

   attrs.setAjaxChannel(new AjaxChannel(modalClose, Type.Active));
 }

 For more about the goodies in Wicket 6 read:
 http://wicketinaction.com/2012/07/wicket-6-javascript-improvements/

 In Wicket 1.5 you will have to add some custom JavaScript to prevent
 the second request. You can unbind the event, or add a flag for
 example.

 I tried to use unbind() and flag but always return me the same error. How can 
 I prevent the second request?

 Thanks
 Marco


 On Wed, Sep 5, 2012 at 12:04 PM, Marco Di Sabatino Di Diodoro
 marco.disabat...@tirasa.net wrote:
 Hi all,

 I configure into Apache Syncope the possibility to close ModalWindow with 
 ESC key press event.

 public class CloseOnESCBehavior extends AbstractDefaultAjaxBehavior {

private static final long serialVersionUID = 5826308247642534260L;
private ModalWindow modalWindow;

public CloseOnESCBehavior(ModalWindow modalWindow) {
this.modalWindow = modalWindow;
}

private static final String PRE_JS = $(document).ready(function() {\n
+ $(document).bind('keyup', function(evt) {\n
+ if (evt.keyCode == 27){\n;

private static final String POST_JS = \n evt.preventDefault();\n
+ evt.stopImmediatePropagation();\n
+ }\n
+   });\n
+ });;

@Override
protected void respond(final AjaxRequestTarget target) {
modalWindow.close(target);
}

@Override
protected String findIndicatorId() {
return null;
}

@Override
public void renderHead(final Component component, final IHeaderResponse 
 response) {
response.renderJavaScript(new 
 StringBuilder(PRE_JS).append(getCallbackScript())
.append(POST_JS).toString(),
closeModalOnEsc);
}

 In the modal page:

 add(new CloseOnESCBehavior(window));

 It work correctly with Chrome and Safari. With Firefox, if I press the ESC 
 key twice quickly before the window closes the console return an error:

 ERROR: Wicket.Ajax.Call.failure: Error while parsing response: Could not 
 find root ajax-response element

 Regards
 Marco


 --

 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 PPMC Member
 http://people.apache.org/~mdisabatino







 --
 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


 --

 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 PPMC Member
 http://people.apache.org/~mdisabatino







-- 
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

Apache Wicket 1.4.21 is released

[Carl-Eric Menzel]

This is 21st release of the Wicket 1.4.x series. This is also the last
release of the 1.4.x series, rounding up the remaining bugfixes. No
further releases will happen in this branch.

Git tag:
release/wicket-1.4.21

Changelog:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310561version=12320171

Maven:
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket/artifactId
version1.4.21/version
/dependency

Download the full distribution (including source):
http://www.apache.org/dyn/closer.cgi/wicket/1.4.21

The Wicke

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

Re: Error ESC key press event

[Marco Di Sabatino Di Diodoro]

On Sep 5, 2012, at 3:49 PM, Martin Grigorov wrote:

 Hi,
 
 You already wrap the call to wicketAjaxXXX() method in if statement.
 Just raise a flag that you entered in this code and set it back to
 false in the success/failure handler.

Do you mean this?

private static final String PRE_JS = 
var flag = false;
+ $(window).ready(function() {\n
+ $(window).bind('keyup', function(evt) {\n
+ if (!flag  evt.keyCode == 27){\n
+ flag = true;;
   ...
   ...

always the same error.

Regards
Marco

 
 On Wed, Sep 5, 2012 at 3:40 PM, Marco Di Sabatino Di Diodoro
 marco.disabat...@tirasa.net wrote:
 Hi Martin,
 
 On Sep 5, 2012, at 12:20 PM, Martin Grigorov wrote:
 
 Hi Marco,
 
 I see a quite simple solution with Wicket 6 for this. I think you just
 start with your project (or even this is just a prototype?) so you
 better use the latest and greatest :-)
 
 We can not upgrade to Wicket 6 in this moment.
 
 
 What I mean is to use the new AjaxChannel.Type.Active. The active type
 prevents a second Ajax call in the same channel while there is a still
 running Ajax call in this channel.
 
 The code is as simple as:
 
 @Override
 protected void updateAjaxAttributes(AjaxRequestAttributes attrs) {
  super.updateAjaxAttributes(attrs);
 
  attrs.setAjaxChannel(new AjaxChannel(modalClose, Type.Active));
 }
 
 For more about the goodies in Wicket 6 read:
 http://wicketinaction.com/2012/07/wicket-6-javascript-improvements/
 
 In Wicket 1.5 you will have to add some custom JavaScript to prevent
 the second request. You can unbind the event, or add a flag for
 example.
 
 I tried to use unbind() and flag but always return me the same error. How 
 can I prevent the second request?
 
 Thanks
 Marco
 
 
 On Wed, Sep 5, 2012 at 12:04 PM, Marco Di Sabatino Di Diodoro
 marco.disabat...@tirasa.net wrote:
 Hi all,
 
 I configure into Apache Syncope the possibility to close ModalWindow with 
 ESC key press event.
 
 public class CloseOnESCBehavior extends AbstractDefaultAjaxBehavior {
 
   private static final long serialVersionUID = 5826308247642534260L;
   private ModalWindow modalWindow;
 
   public CloseOnESCBehavior(ModalWindow modalWindow) {
   this.modalWindow = modalWindow;
   }
 
   private static final String PRE_JS = $(document).ready(function() {\n
   + $(document).bind('keyup', function(evt) {\n
   + if (evt.keyCode == 27){\n;
 
   private static final String POST_JS = \n evt.preventDefault();\n
   + evt.stopImmediatePropagation();\n
   + }\n
   +   });\n
   + });;
 
   @Override
   protected void respond(final AjaxRequestTarget target) {
   modalWindow.close(target);
   }
 
   @Override
   protected String findIndicatorId() {
   return null;
   }
 
   @Override
   public void renderHead(final Component component, final IHeaderResponse 
 response) {
   response.renderJavaScript(new 
 StringBuilder(PRE_JS).append(getCallbackScript())
   .append(POST_JS).toString(),
   closeModalOnEsc);
   }
 
 In the modal page:
 
 add(new CloseOnESCBehavior(window));
 
 It work correctly with Chrome and Safari. With Firefox, if I press the ESC 
 key twice quickly before the window closes the console return an error:
 
 ERROR: Wicket.Ajax.Call.failure: Error while parsing response: Could not 
 find root ajax-response element
 
 Regards
 Marco
 
 
 --
 
 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 PPMC Member
 http://people.apache.org/~mdisabatino
 
 
 
 
 
 
 
 --
 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
 
 
 --
 
 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 PPMC Member
 http://people.apache.org/~mdisabatino
 
 
 
 
 
 
 
 -- 
 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
 

--

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 PPMC Member
http://people.apache.org/~mdisabatino

Re: Error ESC key press event

[Martin Grigorov]

Try with bigger scope: window.Flag

On Wed, Sep 5, 2012 at 5:25 PM, Marco Di Sabatino Di Diodoro
marco.disabat...@tirasa.net wrote:

 On Sep 5, 2012, at 3:49 PM, Martin Grigorov wrote:

 Hi,

 You already wrap the call to wicketAjaxXXX() method in if statement.
 Just raise a flag that you entered in this code and set it back to
 false in the success/failure handler.

 Do you mean this?

 private static final String PRE_JS =
 var flag = false;
 + $(window).ready(function() {\n
 + $(window).bind('keyup', function(evt) {\n
 + if (!flag  evt.keyCode == 27){\n
 + flag = true;;
...
...

 always the same error.

 Regards
 Marco


 On Wed, Sep 5, 2012 at 3:40 PM, Marco Di Sabatino Di Diodoro
 marco.disabat...@tirasa.net wrote:
 Hi Martin,

 On Sep 5, 2012, at 12:20 PM, Martin Grigorov wrote:

 Hi Marco,

 I see a quite simple solution with Wicket 6 for this. I think you just
 start with your project (or even this is just a prototype?) so you
 better use the latest and greatest :-)

 We can not upgrade to Wicket 6 in this moment.


 What I mean is to use the new AjaxChannel.Type.Active. The active type
 prevents a second Ajax call in the same channel while there is a still
 running Ajax call in this channel.

 The code is as simple as:

 @Override
 protected void updateAjaxAttributes(AjaxRequestAttributes attrs) {
  super.updateAjaxAttributes(attrs);

  attrs.setAjaxChannel(new AjaxChannel(modalClose, Type.Active));
 }

 For more about the goodies in Wicket 6 read:
 http://wicketinaction.com/2012/07/wicket-6-javascript-improvements/

 In Wicket 1.5 you will have to add some custom JavaScript to prevent
 the second request. You can unbind the event, or add a flag for
 example.

 I tried to use unbind() and flag but always return me the same error. How 
 can I prevent the second request?

 Thanks
 Marco


 On Wed, Sep 5, 2012 at 12:04 PM, Marco Di Sabatino Di Diodoro
 marco.disabat...@tirasa.net wrote:
 Hi all,

 I configure into Apache Syncope the possibility to close ModalWindow with 
 ESC key press event.

 public class CloseOnESCBehavior extends AbstractDefaultAjaxBehavior {

   private static final long serialVersionUID = 5826308247642534260L;
   private ModalWindow modalWindow;

   public CloseOnESCBehavior(ModalWindow modalWindow) {
   this.modalWindow = modalWindow;
   }

   private static final String PRE_JS = $(document).ready(function() {\n
   + $(document).bind('keyup', function(evt) {\n
   + if (evt.keyCode == 27){\n;

   private static final String POST_JS = \n evt.preventDefault();\n
   + evt.stopImmediatePropagation();\n
   + }\n
   +   });\n
   + });;

   @Override
   protected void respond(final AjaxRequestTarget target) {
   modalWindow.close(target);
   }

   @Override
   protected String findIndicatorId() {
   return null;
   }

   @Override
   public void renderHead(final Component component, final IHeaderResponse 
 response) {
   response.renderJavaScript(new 
 StringBuilder(PRE_JS).append(getCallbackScript())
   .append(POST_JS).toString(),
   closeModalOnEsc);
   }

 In the modal page:

 add(new CloseOnESCBehavior(window));

 It work correctly with Chrome and Safari. With Firefox, if I press the 
 ESC key twice quickly before the window closes the console return an 
 error:

 ERROR: Wicket.Ajax.Call.failure: Error while parsing response: Could not 
 find root ajax-response element

 Regards
 Marco


 --

 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 PPMC Member
 http://people.apache.org/~mdisabatino







 --
 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


 --

 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 PPMC Member
 http://people.apache.org/~mdisabatino







 --
 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


 --

 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 PPMC Member
 http://people.apache.org/~mdisabatino







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

The Apache Software Foundation Announces Apache Wicket™ 6.0.0

[Martijn Dashorst]

With great pleasure we announce the availability of Apache Wicket 6.0.0
-- Martijn Dashorst, Vice President, Apache Wicket

Apache Wicket v6.0.0 is the 6th major release of the popular open
source Java web framework. Numerous enhancements make Apache Wicket
v6.0.0 a solid choice for web development:

- Out-of-the box JQuery integration
- Complete control over AJAX requests
- Improved event registration in browsers
- Support for large datasets in components
- Dependency management for client side javascript libraries
- Experimental support for websockets

Additional features include a customizable client-side API, improved
feedback messages, correct packaging for OSGi compatibility and
improved initialization of plugins. Highlights include:

Java 6 required -This release moves the minimum required Java version
to Java 6. This means that Wicket applications running on earlier Java
versions meaning to upgrade, also need to upgrade their Java runtime.

Revamped Wicket AJAX now leverages JQuery - Wicket's custom AJAX
JavaScript library has been re-implemented using JQuery. This makes it
easier to integrate JQuery plugins into Wicket applications. With the
new AJAX implementation it is possible to provide your own version of
JQuery should the need arise, or even to replace the whole Wicket
client side AJAX implementation.

AJAX Attributes - With the new and improved AJAX implementation, you
can alter any aspect of an AJAX request through AjaxRequestAttributes.
For example you can specify that the request should be executed using
POST instead of GET, or that the AJAX request should be multi-part,
etc. See the migration guide or the JavaDoc of AjaxRequestAttributes
for all possible options.

Browser event registration replaces inline events - Wicket now uses
JavaScript event registration instead of inline attributes for AJAX
components. This enables multiple event listeners to be attached to a
markup tag, cleans up the rendered markup considerably and reduces the
amount of generated markup.

IDataProvider now uses long instead of int - The IDataProviderT
interface and implementations now use long instead of int for index
and size parameters to better line up with the Java Persistence API
and other persistency frameworks. Big data is now possible with
Wicket!

${label} replaces ${input} in feedback messages - Previous Wicket
versions used the input that was provided by users in error messages
when validations failed. This led to error messages like 1234a is not
a valid number. In Wicket 6 the feedback messages use the label of
the invalid form component instead. You can set the label by calling
setLabel() on the form component. If no label is provided, Wicket
defaults to displaying the component identifier. This changes the
error message to Phonenumber is not a valid number.

Resources can declare dependencies - It is now much easier to create
resource contributions with dependencies, for example a JQuery plugin
can declare a dependency on JQuery and other resources such as
embedded style sheets. Users of such resources don’t have to provide
these dependencies themselves, and the dependencies are linked in the
appropriate order.

Packaged resources will use minimized version automatically - When a
minimized JavaScript resource is available (filename.min.js – add the
.min part to the filename before the extension), Wicket will
automatically use the minimized version when running in deployment
mode, while using the non-minimized version for development mode.

OSGi compatible packaging - Wicket's packaging has been made
compatible with OSGi bundles by moving some classes to different
packages. The full list can be found in our migration guide. This
makes it much easier to deploy Wicket applications in an OSGi
environment.

Experimental websocket implementations - This release also includes
two experimental websocket implementations: one using Atmosphere as a
bridge for browsers and containers that don't support websockets
natively and one for containers and browsers that have native
websocket support.

The complete set of changes is available in the migration guide at
http://s.apache.org/wicket-6.0-migration

Availability and Oversight

As with all Apache products, Apache Wicket v6.0.0 is released under
the Apache License v2.0, and is overseen by a self-selected team of
active contributors to the project. A Project Management Committee
(PMC) guides the Project's day-to-day operations, including community
development and product releases. Apache Wicket source code,
documentation, and related resources are available at
http://wicket.apache.org/

Apache, Wicket, Apache Wicket, and ApacheCon are trademarks of
The Apache Software Foundation. All other brands and trademarks are
the property of their respective owners.

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

Re: The Apache Software Foundation Announces Apache Wicket™ 6.0.0

[Michael M]

Congratulations, and thank you!

2012/9/5 Martijn Dashorst martijn.dasho...@gmail.com

 With great pleasure we announce the availability of Apache Wicket 6.0.0
 -- Martijn Dashorst, Vice President, Apache Wicket

 Apache Wicket v6.0.0 is the 6th major release of the popular open
 source Java web framework. Numerous enhancements make Apache Wicket
 v6.0.0 a solid choice for web development:

 - Out-of-the box JQuery integration
 - Complete control over AJAX requests
 - Improved event registration in browsers
 - Support for large datasets in components
 - Dependency management for client side javascript libraries
 - Experimental support for websockets

 Additional features include a customizable client-side API, improved
 feedback messages, correct packaging for OSGi compatibility and
 improved initialization of plugins. Highlights include:

 Java 6 required -This release moves the minimum required Java version
 to Java 6. This means that Wicket applications running on earlier Java
 versions meaning to upgrade, also need to upgrade their Java runtime.

 Revamped Wicket AJAX now leverages JQuery - Wicket's custom AJAX
 JavaScript library has been re-implemented using JQuery. This makes it
 easier to integrate JQuery plugins into Wicket applications. With the
 new AJAX implementation it is possible to provide your own version of
 JQuery should the need arise, or even to replace the whole Wicket
 client side AJAX implementation.

 AJAX Attributes - With the new and improved AJAX implementation, you
 can alter any aspect of an AJAX request through AjaxRequestAttributes.
 For example you can specify that the request should be executed using
 POST instead of GET, or that the AJAX request should be multi-part,
 etc. See the migration guide or the JavaDoc of AjaxRequestAttributes
 for all possible options.

 Browser event registration replaces inline events - Wicket now uses
 JavaScript event registration instead of inline attributes for AJAX
 components. This enables multiple event listeners to be attached to a
 markup tag, cleans up the rendered markup considerably and reduces the
 amount of generated markup.

 IDataProvider now uses long instead of int - The IDataProviderT
 interface and implementations now use long instead of int for index
 and size parameters to better line up with the Java Persistence API
 and other persistency frameworks. Big data is now possible with
 Wicket!

 ${label} replaces ${input} in feedback messages - Previous Wicket
 versions used the input that was provided by users in error messages
 when validations failed. This led to error messages like 1234a is not
 a valid number. In Wicket 6 the feedback messages use the label of
 the invalid form component instead. You can set the label by calling
 setLabel() on the form component. If no label is provided, Wicket
 defaults to displaying the component identifier. This changes the
 error message to Phonenumber is not a valid number.

 Resources can declare dependencies - It is now much easier to create
 resource contributions with dependencies, for example a JQuery plugin
 can declare a dependency on JQuery and other resources such as
 embedded style sheets. Users of such resources don’t have to provide
 these dependencies themselves, and the dependencies are linked in the
 appropriate order.

 Packaged resources will use minimized version automatically - When a
 minimized JavaScript resource is available (filename.min.js – add the
 .min part to the filename before the extension), Wicket will
 automatically use the minimized version when running in deployment
 mode, while using the non-minimized version for development mode.

 OSGi compatible packaging - Wicket's packaging has been made
 compatible with OSGi bundles by moving some classes to different
 packages. The full list can be found in our migration guide. This
 makes it much easier to deploy Wicket applications in an OSGi
 environment.

 Experimental websocket implementations - This release also includes
 two experimental websocket implementations: one using Atmosphere as a
 bridge for browsers and containers that don't support websockets
 natively and one for containers and browsers that have native
 websocket support.

 The complete set of changes is available in the migration guide at
 http://s.apache.org/wicket-6.0-migration

 Availability and Oversight

 As with all Apache products, Apache Wicket v6.0.0 is released under
 the Apache License v2.0, and is overseen by a self-selected team of
 active contributors to the project. A Project Management Committee
 (PMC) guides the Project's day-to-day operations, including community
 development and product releases. Apache Wicket source code,
 documentation, and related resources are available at
 http://wicket.apache.org/

 Apache, Wicket, Apache Wicket, and ApacheCon are trademarks of
 The Apache Software Foundation. All other brands and trademarks are
 the property of their respective owners.

 

Debug messages

[Anna Simbirtsev]

Hi

I am seeing the following debug messages, how do I turn them off?

15:51:07.816 [1945207123@qtp-636450175-3] DEBUG
org.apache.wicket.MarkupContainer - Rendering raw markup
15:51:07.816 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Page -
Rendered [MarkupContainer [Component id = 7]]
15:51:07.816 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Component
- End render [MarkupContainer [Component id = 7]]
15:51:07.816 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Page -
Rendered [MarkupContainer [Component id = linkContainer]]
15:51:07.816 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Component
- End render [MarkupContainer [Component id = linkContainer]]
15:51:07.816 [1945207123@qtp-636450175-3] DEBUG
org.apache.wicket.MarkupContainer - Rendering raw markup
15:51:07.816 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Page -
Rendered [Page class = info.afilias.WAT.UI.Pages.SubMenuContents, id = 2,
version = 0]
15:51:07.816 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Component
- End render [Page class = info.afilias.WAT.UI.Pages.SubMenuContents, id =
2, version = 0]
15:51:07.817 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Page -
ending request for page [Page class =
info.afilias.WAT.UI.Pages.SubMenuContents, id = 2, version = 0], request
[method = GET, protocol = HTTP/1.1, requestURL =
http://localhost:8080/application/home, contentType = null, contentLength =
-1, contextPath = /application, pathInfo = null, requestURI =
/application/home, servletPath = /home, pathTranslated = null]
15:51:07.817 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Session -
update: Session not dirty.

Re: Debug messages

[vineet semwal]

change the log setting to INFO from DEBUG

On Thu, Sep 6, 2012 at 1:24 AM, Anna Simbirtsev asimbirt...@gmail.com wrote:
 Hi

 I am seeing the following debug messages, how do I turn them off?

 15:51:07.816 [1945207123@qtp-636450175-3] DEBUG
 org.apache.wicket.MarkupContainer - Rendering raw markup
 15:51:07.816 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Page -
 Rendered [MarkupContainer [Component id = 7]]
 15:51:07.816 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Component
 - End render [MarkupContainer [Component id = 7]]
 15:51:07.816 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Page -
 Rendered [MarkupContainer [Component id = linkContainer]]
 15:51:07.816 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Component
 - End render [MarkupContainer [Component id = linkContainer]]
 15:51:07.816 [1945207123@qtp-636450175-3] DEBUG
 org.apache.wicket.MarkupContainer - Rendering raw markup
 15:51:07.816 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Page -
 Rendered [Page class = info.afilias.WAT.UI.Pages.SubMenuContents, id = 2,
 version = 0]
 15:51:07.816 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Component
 - End render [Page class = info.afilias.WAT.UI.Pages.SubMenuContents, id =
 2, version = 0]
 15:51:07.817 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Page -
 ending request for page [Page class =
 info.afilias.WAT.UI.Pages.SubMenuContents, id = 2, version = 0], request
 [method = GET, protocol = HTTP/1.1, requestURL =
 http://localhost:8080/application/home, contentType = null, contentLength =
 -1, contextPath = /application, pathInfo = null, requestURI =
 /application/home, servletPath = /home, pathTranslated = null]
 15:51:07.817 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Session -
 update: Session not dirty.



-- 
thank you,

regards,
Vineet Semwal

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

inmethod grid 6.0-SNAPSHOT doesn't work in IE8

[Dan Simko]

Hi,

online example (http://www.wicket-library.com/inmethod-grid) is working
great in my IE8, but when I run latest version from
https://github.com/wicketstuff/core/tree/master/jdk-1.6-parent/inmethod-grid-parentgrid
is not initialized correctly in IE8 (see attachment). The problem is
probably in script.js on line 1545:

window.setInterval(this.update.bind(this), interval);

Unfortunately I do not have so strong JS knowledge in order to fix it.
In FF and Chrome grid works great.


Thanks in advance!

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

Re: Debug messages

[Anna Simbirtsev]

This log setting? I tried changing log4j.rootLogger=INFO,Stdout, it still
prints.

Thank you for you answer.

log4j.rootLogger=DEBUG,Stdout

log4j.appender.Stdout=org.apache.log4j.ConsoleAppender
log4j.appender.Stdout.layout=org.apache.log4j.TTCCLayout
log4j.appender.Stdout.layout.ThreadPrinting=true
log4j.appender.Stdout.layout.ContextPrinting=true
log4j.appender.Stdout.layout.DateFormat=ISO8601
log4j.appender.Stdout.layout.TimeZone=GMT

log4j.logger.org.springframework=INFO
log4j.logger.org.springframework.beans.factory=DEBUG
log4j.logger.org.apache.wicket=INFO
log4j.logger.org.apache.wicket.protocol.http.HttpSessionStore=INFO
log4j.logger.org.apache.wicket.version=INFO
log4j.logger.org.apache.wicket.RequestCycle=INFO

On Wed, Sep 5, 2012 at 4:23 PM, vineet semwal vineetsemwal1...@gmail.comwrote:

 change the log setting to INFO from DEBUG

 On Thu, Sep 6, 2012 at 1:24 AM, Anna Simbirtsev asimbirt...@gmail.com
 wrote:
  Hi
 
  I am seeing the following debug messages, how do I turn them off?
 
  15:51:07.816 [1945207123@qtp-636450175-3] DEBUG
  org.apache.wicket.MarkupContainer - Rendering raw markup
  15:51:07.816 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Page -
  Rendered [MarkupContainer [Component id = 7]]
  15:51:07.816 [1945207123@qtp-636450175-3] DEBUG
 org.apache.wicket.Component
  - End render [MarkupContainer [Component id = 7]]
  15:51:07.816 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Page -
  Rendered [MarkupContainer [Component id = linkContainer]]
  15:51:07.816 [1945207123@qtp-636450175-3] DEBUG
 org.apache.wicket.Component
  - End render [MarkupContainer [Component id = linkContainer]]
  15:51:07.816 [1945207123@qtp-636450175-3] DEBUG
  org.apache.wicket.MarkupContainer - Rendering raw markup
  15:51:07.816 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Page -
  Rendered [Page class = info.afilias.WAT.UI.Pages.SubMenuContents, id = 2,
  version = 0]
  15:51:07.816 [1945207123@qtp-636450175-3] DEBUG
 org.apache.wicket.Component
  - End render [Page class = info.afilias.WAT.UI.Pages.SubMenuContents, id
 =
  2, version = 0]
  15:51:07.817 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Page -
  ending request for page [Page class =
  info.afilias.WAT.UI.Pages.SubMenuContents, id = 2, version = 0], request
  [method = GET, protocol = HTTP/1.1, requestURL =
  http://localhost:8080/application/home, contentType = null,
 contentLength =
  -1, contextPath = /application, pathInfo = null, requestURI =
  /application/home, servletPath = /home, pathTranslated = null]
  15:51:07.817 [1945207123@qtp-636450175-3] DEBUG
 org.apache.wicket.Session -
  update: Session not dirty.



 --
 thank you,

 regards,
 Vineet Semwal

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

Re: inmethod grid 6.0-SNAPSHOT doesn't work in IE8

[Dan Simko]

sorry, attachment is here http://wickeria.com/screenshot.png

On Wed, Sep 5, 2012 at 10:27 PM, Dan Simko wicke...@gmail.com wrote:

 Hi,

 online example (http://www.wicket-library.com/inmethod-grid) is working
 great in my IE8, but when I run latest version from
 https://github.com/wicketstuff/core/tree/master/jdk-1.6-parent/inmethod-grid-parentgrid
  is not initialized correctly in IE8 (see attachment). The problem is
 probably in script.js on line 1545:

 window.setInterval(this.update.bind(this), interval);

 Unfortunately I do not have so strong JS knowledge in order to fix it.
 In FF and Chrome grid works great.


 Thanks in advance!

Re: Debug messages

[vineet semwal]

looks ok to me ..

On Thu, Sep 6, 2012 at 1:59 AM, Anna Simbirtsev asimbirt...@gmail.com wrote:
 This log setting? I tried changing log4j.rootLogger=INFO,Stdout, it still
 prints.

 Thank you for you answer.

 log4j.rootLogger=DEBUG,Stdout

 log4j.appender.Stdout=org.apache.log4j.ConsoleAppender
 log4j.appender.Stdout.layout=org.apache.log4j.TTCCLayout
 log4j.appender.Stdout.layout.ThreadPrinting=true
 log4j.appender.Stdout.layout.ContextPrinting=true
 log4j.appender.Stdout.layout.DateFormat=ISO8601
 log4j.appender.Stdout.layout.TimeZone=GMT

 log4j.logger.org.springframework=INFO
 log4j.logger.org.springframework.beans.factory=DEBUG
 log4j.logger.org.apache.wicket=INFO
 log4j.logger.org.apache.wicket.protocol.http.HttpSessionStore=INFO
 log4j.logger.org.apache.wicket.version=INFO
 log4j.logger.org.apache.wicket.RequestCycle=INFO

 On Wed, Sep 5, 2012 at 4:23 PM, vineet semwal 
 vineetsemwal1...@gmail.comwrote:

 change the log setting to INFO from DEBUG

 On Thu, Sep 6, 2012 at 1:24 AM, Anna Simbirtsev asimbirt...@gmail.com
 wrote:
  Hi
 
  I am seeing the following debug messages, how do I turn them off?
 
  15:51:07.816 [1945207123@qtp-636450175-3] DEBUG
  org.apache.wicket.MarkupContainer - Rendering raw markup
  15:51:07.816 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Page -
  Rendered [MarkupContainer [Component id = 7]]
  15:51:07.816 [1945207123@qtp-636450175-3] DEBUG
 org.apache.wicket.Component
  - End render [MarkupContainer [Component id = 7]]
  15:51:07.816 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Page -
  Rendered [MarkupContainer [Component id = linkContainer]]
  15:51:07.816 [1945207123@qtp-636450175-3] DEBUG
 org.apache.wicket.Component
  - End render [MarkupContainer [Component id = linkContainer]]
  15:51:07.816 [1945207123@qtp-636450175-3] DEBUG
  org.apache.wicket.MarkupContainer - Rendering raw markup
  15:51:07.816 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Page -
  Rendered [Page class = info.afilias.WAT.UI.Pages.SubMenuContents, id = 2,
  version = 0]
  15:51:07.816 [1945207123@qtp-636450175-3] DEBUG
 org.apache.wicket.Component
  - End render [Page class = info.afilias.WAT.UI.Pages.SubMenuContents, id
 =
  2, version = 0]
  15:51:07.817 [1945207123@qtp-636450175-3] DEBUG org.apache.wicket.Page -
  ending request for page [Page class =
  info.afilias.WAT.UI.Pages.SubMenuContents, id = 2, version = 0], request
  [method = GET, protocol = HTTP/1.1, requestURL =
  http://localhost:8080/application/home, contentType = null,
 contentLength =
  -1, contextPath = /application, pathInfo = null, requestURI =
  /application/home, servletPath = /home, pathTranslated = null]
  15:51:07.817 [1945207123@qtp-636450175-3] DEBUG
 org.apache.wicket.Session -
  update: Session not dirty.



 --
 thank you,

 regards,
 Vineet Semwal

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





-- 
regards,

Vineet Semwal

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

AjaxFallbackLabel Component

[Abid K]

I've created a simple component called 'AjaxFallbackLabel', which might be
useful to have as part of the Ajax components.

I particularly found it useful when explaining to the user that Ajaxified
components would automatically refresh, otherwise when JavaScript is
disabled it would revert to the default message which could say 'Manually
refresh the page to update the component'. If you wanted to see it in
action then just checkout the wicket example and run it.

Anyway, if you'd like to include it into Wicket, you're more than welcome...
https://code.google.com/p/mutable-password/source/browse/trunk/mutable-password-wicket-example/src/main/java/abid/password/wicket/components/AjaxFallbackLabel.java

Thanks

Problems with ModalWindows during upgrade from 1.4 to 1.5

[Greg Wogan-Browne]

Hello,

I am new to Wicket and have recently inherited a moderately large Wicket
application. I have been asked to upgrade the application from version 1.4
to 1.5, and have run into a problem with the way this application handles
ModalWindows, and the receiving of values therefrom.

I have attached two Wicket Quickstarts (one for 1.4 and one for 1.5) which
show the nature of my problem. Both quickstarts have much the same code, and
I will explain the expected behaviour.

On launching the application, click on the link in Show Window to show the
modal window. Enter any value (eg, test) into the input element on the
form and click Go. Then close the modal window. The value that you entered
should appear after the text Value is:  on the home page.

This works in the 1.4 quickstart, but not in the 1.5.

Obviously the quickstarts are significantly cut down from the actual
application I have inherited, so I would value advice on how to fix this in
1.5 without significant refactoring, if possible.

Any advice is much appreciated!

Cheers,

Greg

http://apache-wicket.1842946.n4.nabble.com/file/n4651794/testmodals.tar.gz
testmodals.tar.gz 



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Problems-with-ModalWindows-during-upgrade-from-1-4-to-1-5-tp4651794.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: Problems with ModalWindows during upgrade from 1.4 to 1.5

[Gabriel Landon]

Hi Greg,

I think this is related to the problem I had last year :
http://apache-wicket.1842946.n4.nabble.com/Page-serialization-problem-with-wicket-1-5-td4097909.html

See 
https://issues.apache.org/jira/browse/WICKET-3751
https://issues.apache.org/jira/browse/WICKET-3809

Regards,

Gabriel.





--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Problems-with-ModalWindows-during-upgrade-from-1-4-to-1-5-tp4651794p4651795.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: Problems with ModalWindows during upgrade from 1.4 to 1.5

[Greg Wogan-Browne]

Thanks Gabriel, it does seem like the same issue. I will investigate 
whether changing the modal window contents into panels is feasible for 
my application.





--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Problems-with-ModalWindows-during-upgrade-from-1-4-to-1-5-tp4651794p4651796.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