Re: ModalWindow to ModalDialog // closedCallback

[Johannes Renoth]

Hi Korbinian,

you can overwrite ModalDialog#close and do something like this.

public class MyModalDialog extends ModalDialog {

private SerializableConsumer closeWindowCallback;
...
public void 
setCloseWindowCallback(SerializableConsumer 
closeWindowCallback) { this.closeWindowCallback = closeWindowCallback; }
@Override public ModalDialog close(AjaxRequestTarget target) { 
super.close(target); if (closeWindowCallback != null) { 
closeWindowCallback.accept(target); } return this; }

...
}
I also could not find many of the features the old ModalWindow had in 
ModalDialog. (for example resize, move, header, closebutton).

Hope that helps,
Johannes Renoth

On 20/10/2023 10:31, Korbinian Bachl wrote:

Hi,

when I try to migrate a ModalWindow to ModalDialog i came accross this:

  add(new AjaxLink("edit") {
 @Override
 public void onClick(AjaxRequestTarget target) {
 
getModalWindow().setModel(ReferenceEditorPanel.this.getModel());
 getModalWindow().setWindowClosedCallback(new 
ModalWindow.WindowClosedCallback() {
 public void onClose(AjaxRequestTarget target) {
 target.add(ReferenceEditorPanel.this);
 ReferenceEditorPanel.this.onUpdate(target);
 }
 });
 getModalWindow().show(target);
 }
 });

-> What would a correct way be for the setWindowClosedCallback? Have only see 
some onOk(AjaxRequestTarget) and onCancel(AjaxRequestTarget)?


Best,

KB

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

Re: ModalWindow alert popup that submits form

[Entropy]

Issue Resolved.

Another part of the code was found to be setting it back to false in a way
that evaded my previous searches.  Once that was corrected, the AjaxButton
behaves as expected.  Sorry to waste your time.

--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html

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

Re: ModalWindow alert popup that submits form

[Sven Meier]

Sorry, we seem to speak about different buttons.

Could you create a quickstart? I've used validation in modal dialogs 
plenty of times and it works as expected.


Have fun
Sven


On 14.05.20 19:14, Entropy wrote:

The panel that launches the modal is not inside the form (it's part of a
standard header), so when i remove it from the constructor I get an illegal
state exception saying "form was not specified in the constructor and cannot
be found in the hierarchy of the component this behavior is attached to"

--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html

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



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

Re: ModalWindow alert popup that submits form

[Entropy]

The panel that launches the modal is not inside the form (it's part of a
standard header), so when i remove it from the constructor I get an illegal
state exception saying "form was not specified in the constructor and cannot
be found in the hierarchy of the component this behavior is attached to"

--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html

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

Re: ModalWindow alert popup that submits form

[Sven Meier]

Hi,

form processing should work as usual in the modal window, including validation 
of course.

Does it make a difference when you let the AjaxButton find its form by itself?

Have fun
Sven

Am 13. Mai 2020 22:29:59 MESZ schrieb Entropy :
>We have a custom popup alert box launched from wicket.  It's build
>around
>org.apache.wicket.extensions.ajax.markup.html.modal.ModalWindow.  It
>works
>great in most situations where it's just messaging and doing other
>not-validating things.  But one of the buttons in one scenario needs to
>cause a save (and validate) of the form.  The buttons are based on
>AjaxButton, and the defaultformprocessing flag was set to true on that
>button during initialization.  the button has reference back to the
>form on
>the main page (the form is not INSIDE the modal).
>
>But everytime I submit, the onSubmit() runs instead of the onError()
>despite
>the fact that I deliberately put a validation error in the text that
>DOES
>get trapped on the normal submit process.
>
>Does anyone have an idea of where I should look?  or if this is just
>something you can't do from inside a modalwindow?  
>
>--
>Sent from:
>http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
>
>-
>To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>For additional commands, e-mail: users-h...@wicket.apache.org

Re: ModalWindow cannot trigger setWindowClosedCallback or setCloseButtonCallback problem

[kyc]

Why AjaxButton works inside the modal window ModalEditPanel but Button not
works for the Form submit?

--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html

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

Re: ModalWindow cannot trigger setWindowClosedCallback or setCloseButtonCallback problem

[kyc]

modalEditLog.setContent(new
ModalEditPanel(modalEditLog.getContentId(), modalEditLog, result));


modalEditLog.setWindowClosedCallback(new WindowClosedCallback() 
{
private static final long serialVersionUID = 
7961678233294274184L;

public void onClose(AjaxRequestTarget target) {
doRefresh(target);
}
});


Panel ModalEditPanel is the replacement for the original WebPage
ModalEditPage and it has the close button to close the window

addOrReplace(new AjaxLink("btnClose") {
private static final long serialVersionUID = 
-8174543450190822811L;

@Override
public void onClick(AjaxRequestTarget target) {
window.close(target);
}
});


--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html

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

Re: ModalWindow cannot trigger setWindowClosedCallback or setCloseButtonCallback problem

[Martin Grigorov]

Please share how you solved it.
Someone else may hit the same issue some day and your explicit description
will help him/her.
Just confirming "ModalWindow#setContent() solved it" is also fine.

On Thu, Mar 7, 2019 at 11:52 AM kyc  wrote:

> Solved.  Thank you.
>
> --
> Sent from:
> http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: ModalWindow cannot trigger setWindowClosedCallback or setCloseButtonCallback problem

[kyc]

Solved.  Thank you.

--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html

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

Re: ModalWindow cannot trigger setWindowClosedCallback or setCloseButtonCallback problem

[Martin Grigorov]

Hi,

It seems you use ModalWindow backed by a Page, i.e. you use ModalWindow's
PageCreator.
Try with ModalWindow backed by a Panel (ModalWindow#setContent()).

On Thu, Mar 7, 2019 at 9:57 AM kyc  wrote:

> Hi Bas,
>
> Thanks for your reply.
>
> Since we are saving data in the page of Modal Page itself, it is no
> problem.
> However,  we have problem to close that modalwindow with a separate close
> button.
> Even I change the form to StatelessForm, the close button still have the
> PageExpiredException
>
> addOrReplace(new AjaxLink("btnClose") {
> private static final long serialVersionUID
> = -8174543450190822811L;
>
> @Override
> public void onClick(AjaxRequestTarget target) {
> window.close(target);
> }
> });
>
> KYC
>
>
>
>
>
> --
> Sent from:
> http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: ModalWindow cannot trigger setWindowClosedCallback or setCloseButtonCallback problem

[kyc]

Hi Bas,

Thanks for your reply.

Since we are saving data in the page of Modal Page itself, it is no problem.
However,  we have problem to close that modalwindow with a separate close
button.  
Even I change the form to StatelessForm, the close button still have the
PageExpiredException

addOrReplace(new AjaxLink("btnClose") {
private static final long serialVersionUID = 
-8174543450190822811L;

@Override
public void onClick(AjaxRequestTarget target) {
window.close(target);
}
});

KYC





--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html

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

Re: ModalWindow cannot trigger setWindowClosedCallback or setCloseButtonCallback problem

[Bas Gooren]

Hi,

Since you are not storing pages, how does the form in your modal
window work? I assume you are using a stateless form?

Since your on close callback is stateful, it will not work; you will
either need to use a stateless Ajax behavior or stateless form where
in onsubmit you redirect to a new page with up-to-date information.

// Bas

Verstuurd vanaf mijn iPhone

> Op 7 mrt. 2019 om 07:56 heeft kyc  het volgende geschreven:
>
> Our page open a WindowModal for editing a form, there is an exception throw
> when closed the modal window.
> This problem only happens when our site is using NoPageStore but we have to
> use NoPageStore.
>
> The following exception happen and the setWindowClosedCallback cannot be
> called.
> Page with id '16' has expired.
> org.apache.wicket.protocol.http.PageExpiredException: Page with id '16' has
> expired.
>
>
> The modal window close call back function works on without NoPageStore
> setting:
>
>abcModalWindow.setWindowClosedCallback(new WindowClosedCallback() {
>private static final long serialVersionUID = 
> 7961678233294274184L;
>
>public void onClose(AjaxRequestTarget target) {
>doRefresh(target);
>}
>});
>
> Please help if anyone knows the solution.  Thanks a lot.
>
>
> --
> Sent from: 
> http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>

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

Re: ModalWindow and OnDomReady

[Rob Audenaerde]

The panel is created and added with setContent just before the modal window
is shown.

On Oct 20, 2016 10:40 AM, "Ernesto Reinaldo Barreiro" 
wrote:

> is this panel initially added to the mcdal? When page is created?
>
> On Thu, Oct 20, 2016 at 10:13 AM, Rob Audenaerde  >
> wrote:
>
> > It is the Panel that I put on the ModalWindow.
> >
> > On Wed, Oct 19, 2016 at 7:56 PM, Martin Grigorov 
> > wrote:
> >
> > > Hi,
> > >
> > > It depends on what you add the OnDomReady header item.
> > > Is it the ModalWindow ? Or its content (Panel or Page) ?
> > >
> > > Martin Grigorov
> > > Wicket Training and Consulting
> > > https://twitter.com/mtgrigorov
> > >
> > > On Wed, Oct 19, 2016 at 5:06 PM, Rob Audenaerde <
> > rob.audenae...@gmail.com>
> > > wrote:
> > >
> > > > Hi all,
> > > >
> > > > I have a panel that needs some JavaScript for sizing etc. to run
> after
> > a
> > > > ModalWindow is shown, but as I now see it the Javascript is run
> > *before*
> > > > the modal window is shown.
> > > >
> > > > What is the proper way to run javascript after a ModalWindow is
> shown?
> > It
> > > > seems OnDomReady is not sufficient here?
> > > >
> > > > Thanks,
> > > >
> > > > Rob
> > > >
> > >
> >
>
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>

Re: ModalWindow and OnDomReady

[Ernesto Reinaldo Barreiro]

is this panel initially added to the mcdal? When page is created?

On Thu, Oct 20, 2016 at 10:13 AM, Rob Audenaerde 
wrote:

> It is the Panel that I put on the ModalWindow.
>
> On Wed, Oct 19, 2016 at 7:56 PM, Martin Grigorov 
> wrote:
>
> > Hi,
> >
> > It depends on what you add the OnDomReady header item.
> > Is it the ModalWindow ? Or its content (Panel or Page) ?
> >
> > Martin Grigorov
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
> >
> > On Wed, Oct 19, 2016 at 5:06 PM, Rob Audenaerde <
> rob.audenae...@gmail.com>
> > wrote:
> >
> > > Hi all,
> > >
> > > I have a panel that needs some JavaScript for sizing etc. to run after
> a
> > > ModalWindow is shown, but as I now see it the Javascript is run
> *before*
> > > the modal window is shown.
> > >
> > > What is the proper way to run javascript after a ModalWindow is shown?
> It
> > > seems OnDomReady is not sufficient here?
> > >
> > > Thanks,
> > >
> > > Rob
> > >
> >
>



-- 
Regards - Ernesto Reinaldo Barreiro

Re: ModalWindow and OnDomReady

[Rob Audenaerde]

It is the Panel that I put on the ModalWindow.

On Wed, Oct 19, 2016 at 7:56 PM, Martin Grigorov 
wrote:

> Hi,
>
> It depends on what you add the OnDomReady header item.
> Is it the ModalWindow ? Or its content (Panel or Page) ?
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Wed, Oct 19, 2016 at 5:06 PM, Rob Audenaerde 
> wrote:
>
> > Hi all,
> >
> > I have a panel that needs some JavaScript for sizing etc. to run after a
> > ModalWindow is shown, but as I now see it the Javascript is run *before*
> > the modal window is shown.
> >
> > What is the proper way to run javascript after a ModalWindow is shown? It
> > seems OnDomReady is not sufficient here?
> >
> > Thanks,
> >
> > Rob
> >
>

Re: ModalWindow and OnDomReady

[Martin Grigorov]

Hi,

It depends on what you add the OnDomReady header item.
Is it the ModalWindow ? Or its content (Panel or Page) ?

Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Wed, Oct 19, 2016 at 5:06 PM, Rob Audenaerde 
wrote:

> Hi all,
>
> I have a panel that needs some JavaScript for sizing etc. to run after a
> ModalWindow is shown, but as I now see it the Javascript is run *before*
> the modal window is shown.
>
> What is the proper way to run javascript after a ModalWindow is shown? It
> seems OnDomReady is not sufficient here?
>
> Thanks,
>
> Rob
>

Re: ModalWindow and OnDomReady

[Ernesto Reinaldo Barreiro]

Repainting the panel after the modal is shown? On the same ART That way
JavaScript will be executed again.

On Wed, Oct 19, 2016 at 5:06 PM, Rob Audenaerde 
wrote:

> Hi all,
>
> I have a panel that needs some JavaScript for sizing etc. to run after a
> ModalWindow is shown, but as I now see it the Javascript is run *before*
> the modal window is shown.
>
> What is the proper way to run javascript after a ModalWindow is shown? It
> seems OnDomReady is not sufficient here?
>
> Thanks,
>
> Rob
>



-- 
Regards - Ernesto Reinaldo Barreiro

Re: ModalWindow - full screen

[Martin Grigorov]

Hi,

I see two ways to do it then:
1) ModalWindow#setMarkupId("myFullscreenId"); $("#myFullscreenId")
2) $(".OWN_CLASS_NAME").closest("div)

both gives you a reference to the div.modal-window.
>From there on you can manipulate it to make it fullscreen.





Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Tue, Oct 21, 2014 at 12:18 PM, Marieke Vandamme  wrote:

> Hi,
>
> We've tried your proposal, but it doesn't work, because the setCssClassName
> doesn't apply to the div that needs to be resized.
> In code underneath you can see the structure. The class should be place on
> the div that now has wicket-modal, but this is not possible, or is it?
> - cannot depend on element higher in the html, because the only element
> would be the body, and this modalwindow is used onto multiple pages
> - cannot use "wicket-modal" class, because it the full screen may not
> reflect on all modal windows
>
> 
> 
> style="background-color:transparent;padding:0px;margin:0px;border-width:0px;position:static" id="_wicket_window_1" class="OWN_CLASS_NAME">
>
> Thanks ! Kind Regards, Marieke
>
>
> Met vriendelijke groeten,
>
>
> *MARIEKE VANDAMMECORPORATE SERVICES* • *Domain Coordinator*
> T +32 56 43 42 45 • F +32 56 43 44 46 • marieke.vanda...@tvh.com
>
> *TVH GROUP NV*
> Brabantstraat 15 • BE-8790 WAREGEM
> T +32 56 43 42 11 • F +32 56 43 44 88 • www.tvh.com
> Watch our company movies on www.tvh.tv
>
> 2014-10-14 11:10 GMT+02:00 Martin Grigorov :
>
> > Hi,
> >
> > With #setCssClassName() (
> >
> >
> https://github.com/apache/wicket/blob/master/wicket-extensions/src/main/java/org/apache/wicket/extensions/ajax/markup/html/modal/ModalWindow.java#L513
> > )
> > you can set your custom CSS class that should be applied on the main
> modal
> > window  element.
> > In your own .css file you can define CSS rules to show any element having
> > this custom CSS class as fullscreen.
> > I am not CSS master but I guess you have to play with "position", "top",
> > "left". "width" and "height" properties.
> >
> > Martin Grigorov
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
> >
> > On Tue, Oct 14, 2014 at 11:32 AM, Marieke Vandamme <
> > marieke.vanda...@tvh.com
> > > wrote:
> >
> > > Hi,
> > >
> > > I know you can set initial width and height for a modalwindow,
> > > but we now get the requirement to open it full screen.
> > > Is this something built in already, or has somebody done this before?
> > >
> > > Thanks ! Kind Regards, Marieke Vandamme
> > >
> > > --
> > >
> > >
> > >  DISCLAIMER 
> > >
> > > http://www.tvh.com/glob/en/email-disclaimer
> > >
> > > "This message is delivered to all addressees subject to the conditions
> > > set forth in the attached disclaimer, which is an integral part of this
> > > message."
> > >
> >
>
> --
>
>
>  DISCLAIMER 
>
> http://www.tvh.com/glob/en/email-disclaimer
>
> "This message is delivered to all addressees subject to the conditions
> set forth in the attached disclaimer, which is an integral part of this
> message."
>

Re: ModalWindow - full screen

[Marieke Vandamme]

Hi,

We've tried your proposal, but it doesn't work, because the setCssClassName
doesn't apply to the div that needs to be resized.
In code underneath you can see the structure. The class should be place on
the div that now has wicket-modal, but this is not possible, or is it?
- cannot depend on element higher in the html, because the only element
would be the body, and this modalwindow is used onto multiple pages
- cannot use "wicket-modal" class, because it the full screen may not
reflect on all modal windows




Thanks ! Kind Regards, Marieke


Met vriendelijke groeten,


*MARIEKE VANDAMMECORPORATE SERVICES* • *Domain Coordinator*
T +32 56 43 42 45 • F +32 56 43 44 46 • marieke.vanda...@tvh.com

*TVH GROUP NV*
Brabantstraat 15 • BE-8790 WAREGEM
T +32 56 43 42 11 • F +32 56 43 44 88 • www.tvh.com
Watch our company movies on www.tvh.tv

2014-10-14 11:10 GMT+02:00 Martin Grigorov :

> Hi,
>
> With #setCssClassName() (
>
> https://github.com/apache/wicket/blob/master/wicket-extensions/src/main/java/org/apache/wicket/extensions/ajax/markup/html/modal/ModalWindow.java#L513
> )
> you can set your custom CSS class that should be applied on the main modal
> window  element.
> In your own .css file you can define CSS rules to show any element having
> this custom CSS class as fullscreen.
> I am not CSS master but I guess you have to play with "position", "top",
> "left". "width" and "height" properties.
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Tue, Oct 14, 2014 at 11:32 AM, Marieke Vandamme <
> marieke.vanda...@tvh.com
> > wrote:
>
> > Hi,
> >
> > I know you can set initial width and height for a modalwindow,
> > but we now get the requirement to open it full screen.
> > Is this something built in already, or has somebody done this before?
> >
> > Thanks ! Kind Regards, Marieke Vandamme
> >
> > --
> >
> >
> >  DISCLAIMER 
> >
> > http://www.tvh.com/glob/en/email-disclaimer
> >
> > "This message is delivered to all addressees subject to the conditions
> > set forth in the attached disclaimer, which is an integral part of this
> > message."
> >
>

-- 


 DISCLAIMER 

http://www.tvh.com/glob/en/email-disclaimer

"This message is delivered to all addressees subject to the conditions
set forth in the attached disclaimer, which is an integral part of this
message."

Re: ModalWindow - full screen

[Martin Grigorov]

Hi,

With #setCssClassName() (
https://github.com/apache/wicket/blob/master/wicket-extensions/src/main/java/org/apache/wicket/extensions/ajax/markup/html/modal/ModalWindow.java#L513)
you can set your custom CSS class that should be applied on the main modal
window  element.
In your own .css file you can define CSS rules to show any element having
this custom CSS class as fullscreen.
I am not CSS master but I guess you have to play with "position", "top",
"left". "width" and "height" properties.

Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Tue, Oct 14, 2014 at 11:32 AM, Marieke Vandamme  wrote:

> Hi,
>
> I know you can set initial width and height for a modalwindow,
> but we now get the requirement to open it full screen.
> Is this something built in already, or has somebody done this before?
>
> Thanks ! Kind Regards, Marieke Vandamme
>
> --
>
>
>  DISCLAIMER 
>
> http://www.tvh.com/glob/en/email-disclaimer
>
> "This message is delivered to all addressees subject to the conditions
> set forth in the attached disclaimer, which is an integral part of this
> message."
>

Re: ModalWindow positioning

[Lucio Crusca]

In data mercoledì 25 giugno 2014 18:05:54, Lucio Crusca ha scritto:
> Just in case others need it, my current working code is:
> 
> Wicket.Window.prototype.center = function() {
>   var myWindow = this.window;
>   if (!myWindow)
> myWindow = Wicket.Window.current;
>   if (!myWindow)
> myWindow = Wicket.Window.get();
>   if (myWindow) {
> $(myWindow).css("position", "fixed");
> $(myWindow).css("top", Math.max(0, ((window.innerHeight -
> $(myWindow).outerHeight) / 2)) + "px");
> $(myWindow).css("left", Math.max(0, ((window.innerWidth -
> $(myWindow).outerWidth) / 2)) + "px");
>   }
> };

No, this code works only in my development environment (localhost:8084). Once 
deployed to the real domain, the screen dims but the ModalWindow does not show 
up, even using the same browser I use in development tests (I guess it 
actually shows up but it falls outside the browser window, but I'm not sure).

There's no noticeable difference between development and production 
environments, except the Tomcat and Apache versions, but I fail to see how 
those could interfere with javascript. The only strange thing is that the JS 
console is showing an error in both cases, but in development it seems 
harmless:

Error: Permission denied to access property 'toString'

and this error has no reference to any particular line of code in any 
particular js file, so I don't even know if it is my mistake and where.

Any clues about why my code could behave differently in the same browser 
between development and deployment environments?



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

Re: ModalWindow positioning

[Lucio Crusca]

I always forget I should not change the subject, sorry... I send the message 
again with the unchanged subject so that it remains attached to the rest of 
this thread.

In data mercoledì 25 giugno 2014 14:54:23, Martin Grigorov ha scritto:
> also try: this.window

Ok thanks, "this.window" seems to be the correct one in my case, but I suspect 
other variants are needed to be as much cross browser as possible.

Just in case others need it, my current working code is:

Wicket.Window.prototype.center = function() {
  var myWindow = this.window;
  if (!myWindow)
myWindow = Wicket.Window.current;
  if (!myWindow)
myWindow = Wicket.Window.get();
  if (myWindow) {
$(myWindow).css("position", "fixed");
$(myWindow).css("top", Math.max(0, ((window.innerHeight - 
$(myWindow).outerHeight) / 2)) + "px");
$(myWindow).css("left", Math.max(0, ((window.innerWidth - 
$(myWindow).outerWidth) / 2)) + "px");
  }
};

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

Re: ModalWindow positioning [SOLVED]

[Lucio Crusca]

In data mercoledì 25 giugno 2014 14:54:23, Martin Grigorov ha scritto:
> also try: this.window

Ok thanks, "this.window" seems to be the correct one in my case, but I suspect 
other variants are needed to be as much cross browser as possible.

Just in case others need it, my current working code is:

Wicket.Window.prototype.center = function() {
  var myWindow = this.window;
  if (!myWindow)
myWindow = Wicket.Window.current;
  if (!myWindow)
myWindow = Wicket.Window.get();
  if (myWindow) {
$(myWindow).css("position", "fixed");
$(myWindow).css("top", Math.max(0, ((window.innerHeight - 
$(myWindow).outerHeight) / 2)) + "px");
$(myWindow).css("left", Math.max(0, ((window.innerWidth - 
$(myWindow).outerWidth) / 2)) + "px");
  }
};

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

Re: ModalWindow positioning

[Martin Grigorov]

also try: this.window

Martin Grigorov
Wicket Training and Consulting


On Wed, Jun 25, 2014 at 2:53 PM, Martin Grigorov 
wrote:

> try with Wicket.Window.current
>
> Martin Grigorov
> Wicket Training and Consulting
>
>
> On Wed, Jun 25, 2014 at 2:51 PM, Lucio Crusca  wrote:
>
>> In data mercoledì 25 giugno 2014 11:09:42, Martin Grigorov ha scritto:
>> > Make sure that your code appears *after* the 

Re: ModalWindow positioning

[Martin Grigorov]

try with Wicket.Window.current

Martin Grigorov
Wicket Training and Consulting


On Wed, Jun 25, 2014 at 2:51 PM, Lucio Crusca  wrote:

> In data mercoledì 25 giugno 2014 11:09:42, Martin Grigorov ha scritto:
> > Make sure that your code appears *after* the 

Re: ModalWindow positioning

[Lucio Crusca]

In data mercoledì 25 giugno 2014 11:09:42, Martin Grigorov ha scritto:
> Make sure that your code appears *after* the 

Re: ModalWindow positioning

[Martin Grigorov]

Make sure that your code appears *after* the 

Re: ModalWindow positioning

[Lucio Crusca]

In data mercoledì 25 giugno 2014 09:49:51, Martin Grigorov ha scritto:
> Hi,
> 
> What exactly you tried and it didn't work ?

I added the code below, but please note that I'm no JS wizard, so it's likely 
my code wouldn't work anyway, but the point is I don't even get JS errors and 
the ModalWindow behaves just like my code wasn't there, so either my code is 
being actually skipped or it is the exact equivalent of what the default 
wicket code does (unlikely):

Wicket.Window.prototype.center = function() {
  var myWindow = Wicket.Window.get();
  if (myWindow) {
myWindow.css("position", "fixed");
myWindow.css("top", Math.max(0, (($(window).height() - 
$(myWindow).outerHeight()) / 2)) + "px");
myWindow.css("left", Math.max(0, (($(window).width() - 
$(myWindow).outerWidth()) / 2)) + "px");
  }
}; 

I add this code in by including a js file in renderHead of my page and I 
confirm 
the code is there when I look at page source in the browser.



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

Re: ModalWindow positioning

[Martin Grigorov]

Hi,

What exactly you tried and it didn't work ?

Martin Grigorov
Wicket Training and Consulting


On Tue, Jun 24, 2014 at 10:32 PM, Lucio Crusca  wrote:

> Hi *,
>
> In a long page I need a ModalWindow to position itself at the center of the
> browser window even when the page is scrolled way down, so that the
> ModalWindow always pops up in front of the user.
>
> I've found this [1], but it dates back to 2009, and it refers to an old
> versions of Wicket (1.3.x). I've tried nevertheless (I'm using 1.6.15), but
> the JS code seems to be just ignored and nothing happens, e.g. the
> ModalWindow
> still shows in the usual position near the top of the page, so the user
> has to
> scroll back up to understand why the page stopped processing his input.
>
> Can you please provide up to date hints?
>
> [1]
> http://apache-wicket.1842946.n4.nabble.com/Modal-window-position-always-centred-even-on-long-page-td1889257.html
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: ModalWindow and jQuery mousedown binding

[neilbennett]

Hi Martin,

You are exactly right. The other Wicket.Event.stop(event) does need to be
commented out. I've found that while this does allow pop-up's to be closed,
it also stops fields taking focus. I will submit a JIRA issue with a
quickstart though.

Thanks,

Neil

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-and-jQuery-mousedown-binding-tp4664859p4665250.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: ModalWindow and jQuery mousedown binding

[Martin Grigorov]

Hi,

Thanks for sharing your findings !

On Wed, Apr 2, 2014 at 11:20 PM, neilbennett wrote:

> Hello again. Thanks for your help, I've found what occurs. When removing
> onmousedown="Wicket.Event.stop(event);" from the w_content_1 div, the event
> then propagates. However, the mouseDownHandler function is called in the
> Drag class in wicket-ajax-jquery.js this returns false which then stops
> further event propagation. Commenting out the return false then allows my
> component popup window to close.
>

I am not sure why only commenting out the return statement helps.
At
https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/ajax/res/js/wicket-ajax-jquery.js#L2410there
is another Wicket.Event.stop(event) call that I think also should
mess the things up in your case ...


>
> So that's the cause, I'm not sure of the best way to work around this. I
> can
> crudely remove the bindings/return value, but I'm sure that will break
> things. Thought I'd report back anyway - if anyone has any suggestions to
> work around this or what would break/not break from changing this.
>

I am also not aware why this code needs to stop the propagation of the
event.
Please file a bug in our Jira with a quickstart and I'll try to find out.


>
> Thanks,
>
> Neil
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/ModalWindow-and-jQuery-mousedown-binding-tp4664859p4665236.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: ModalWindow and jQuery mousedown binding

[neilbennett]

Hello again. Thanks for your help, I've found what occurs. When removing
onmousedown="Wicket.Event.stop(event);" from the w_content_1 div, the event
then propagates. However, the mouseDownHandler function is called in the
Drag class in wicket-ajax-jquery.js this returns false which then stops
further event propagation. Commenting out the return false then allows my
component popup window to close.

So that's the cause, I'm not sure of the best way to work around this. I can
crudely remove the bindings/return value, but I'm sure that will break
things. Thought I'd report back anyway - if anyone has any suggestions to
work around this or what would break/not break from changing this.

Thanks,

Neil 

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-and-jQuery-mousedown-binding-tp4664859p4665236.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: ModalWindow and jQuery mousedown binding

[Martin Grigorov]

Hi,

You can use Google Chrome's Event Listener Breakpoints and see where
mousedown is trapped.
Dev Tools -> Sources -> right pane -> Event Listener Breakpoints -> Mouse
->mousedown

Martin Grigorov
Wicket Training and Consulting


On Tue, Mar 11, 2014 at 11:32 PM, neilbennett wrote:

> Thanks for the reply. I actually removed that binding from the html output
> but I don't see any noticeable changes in behavior. Clicks on the
> modalwindow still do not trigger the mousedown binding on the datetime
> component unless it is outside of the modal window.
>
> I have limited javascript knowledge, hence why using Wicket, but I'm
> stumped
> on where to look on why these events aren't being sent to the datetime
> component.
>
> Thanks,
>
> Neil
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/ModalWindow-and-jQuery-mousedown-binding-tp4664859p4664902.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: ModalWindow and jQuery mousedown binding

[neilbennett]

Thanks for the reply. I actually removed that binding from the html output
but I don't see any noticeable changes in behavior. Clicks on the
modalwindow still do not trigger the mousedown binding on the datetime
component unless it is outside of the modal window.

I have limited javascript knowledge, hence why using Wicket, but I'm stumped
on where to look on why these events aren't being sent to the datetime
component.

Thanks,

Neil

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-and-jQuery-mousedown-binding-tp4664859p4664902.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: ModalWindow and jQuery mousedown binding

[Martin Grigorov]

Hi,

I don't know what is the reason to stop the event at
https://github.com/apache/wicket/blob/master/wicket-extensions/src/main/java/org/apache/wicket/extensions/ajax/markup/html/modal/res/modal.js?source=c#L1186

You can remove that binding with:
jQuery('.wicket-modal .w_content_1')[0].onmousedown = null; // or =
function() {};


 Martin Grigorov
Wicket Training and Consulting


On Fri, Mar 7, 2014 at 6:22 PM, neilbennett wrote:

> Hi,
>
> I am experiencing an issue very similar to Andrew Geery here,
>
> http://apache-wicket.1842946.n4.nabble.com/weird-interaction-between-ModalWindow-and-jQuery-mousedown-binding-td4473055.html
>
> I have a ModalWindow open with a datetimepicker
> (http://www.malot.fr/bootstrap-datetimepicker/) component. On
> non-ModalWindow pages this component closes if open when clicked outside of
> it's area, but the ModalWindow consumes the mousedown event and so
> datetimepicker is not closed when clicking outside of it or even when the
> modal window is closed itself.
>
> Are there any ideas on how to have these ModalWindow mousedown events not
> be
> consumed?
>
> Thanks,
>
> Neil
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/ModalWindow-and-jQuery-mousedown-binding-tp4664859.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: ModalWindow and Page expired

[Martin Grigorov]

Hi,

Check your logs when the ModalWindow is opened.
Most probably there are serialization errors. I.e. the page cannot be
stored due to serialization error and later the Ajax call cannot find it to
close the modal window.


On Sat, Sep 21, 2013 at 11:05 PM, Piratenvisier
wrote:

> When I try to close the ModalWindow with window.close(target)
> I get the error Page expired
> How can I solve this ?
>
> --**--**-
> To unsubscribe, e-mail: 
> users-unsubscribe@wicket.**apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

RE: ModalWindow and Form problems

[Michal Wegrzyn]

Anybody?

Best regards,
Michał Węgrzyn

> -Original Message-
> From: Michal Wegrzyn [mailto:michal.wegr...@onior.com]
> Sent: Wednesday, May 08, 2013 11:22
> To: users@wicket.apache.org
> Subject: ModalWindow and Form problems
> 
> Hi,
> 
> We are using modal window with two forms at the moment: FilterForm and
> Form (Wicket 1.5.9) (inside bean edit panel with ajax).
> FilterForm is not used at the moment (hidden filter fields).
> 
> Everything works fine in IE and Firefox but in Chrome  tag is not
> rendered (only body of the form element is rendered) which causes:
> 
> ERROR: Wicket.Ajax.Call.submitFormById: Trying to submit form with id
> 'form27a' that is not in document.
> 
> Wrapping modals in forms doesn't help. If I override isRootForm with
> "false" then submit succeeds, but after that forms doesn't work
> anymore.
> I think that it can be connected with nested forms and Wicket's
> ModalWindow structure. I saw several issues on Jira:
> 
> https://issues.apache.org/jira/browse/WICKET-1826
> https://issues.apache.org/jira/browse/WICKET-2214
> https://issues.apache.org/jira/browse/WICKET-3404
> 
> Are there any improvements in Wicket 6.x.x regarding modal forms? If
> not, are there any plans or other up-to-date issue?
> Regardless priority of old issues, it seems that it's a serious
> problem.
> 
> Best regards,
> Michał Węgrzyn


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

Re: ModalWindow: setWindowClosedCallback has access to old model or change to modal window's model goes away ?

[grazia]

I have tried to detach the model of the modal window in the onclick, and to
reset it, but to no avail. I think that trying to manipulate teh model of
the modal window for my purpose will not work at all. 

So, I have tried in the onClick to redirect to intercept page this way:
 modalPageReference.getPage().redirectToInterceptPage(new
SecondPage(parameters));
window.close(target);
Then, I have modified the windowClosedCallBack this way:
 window.setWindowClosedCallback(new ModalWindow.WindowClosedCallback() {
private static final long serialVersionUID = 1L;

   
@Override
public void onClose(AjaxRequestTarget target) {

   modalPageReference.getPage().continueToOriginalDestination();
   }
});
The only problem is that he SecondPage is rendered within the modal window,
and I would like to close it and use the window of the main page ...
Anyone interested in helping out with this ?




--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-setWindowClosedCallback-has-access-to-old-model-or-change-to-modal-window-s-model-goes-a-tp4657672p4657681.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: ModalWindow: setWindowClosedCallback has access to old model or change to modal window's model goes away ?

[grazia]

It seems that  the model of the modal window is read before his behavior
responds, and it is not re-read after the behavior responds. 

How to get around this ? Nobody has a suggestion ?



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-setWindowClosedCallback-has-access-to-old-model-or-change-to-modal-window-s-model-goes-a-tp4657672p4657680.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: ModalWindow: setWindowClosedCallback has access to old model or change to modal window's model goes away ?

[grazia]

I think that the issue has something to do with the fact that
WindowClosedCallBack is a Behavior, and in the wicket.Behavior I find the
note: 
* 
 * You also cannot modify a components model with a behavior.
 * 

I am not modifying the model of the window through the windowClosedCallBack,
but does this note also mean that I cannot expect the behavior to hold a
reference to an updated model of the component (my modal window) ?



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-setWindowClosedCallback-has-access-to-old-model-or-change-to-modal-window-s-model-goes-a-tp4657672p4657679.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: ModalWindow parameters

[Melinda Dweer]

Have you tried AjaxRequestTarget.get()? If you are in a middle of an AJAX
request cycle it should give you the request target.

Regards,

Melinda.


On Tue, May 1, 2012 at 2:51 PM, Brian Mulholland wrote:

> I am popping up a modal window when an ajax event fires.  The event
> has a parameter of which key the user selected.  I know I can get the
> parameters from the AjaxRequestTarget in the onClick event, but in
> ModalWindow.PageCreator.createPage(), how can I get the parameters so
> that I can load the right record into the popup?
>
> Brian Mulholland
> "For every complex problem, there is an answer that is clear, simple and
> wrong."
> --H.L. Mencken
> "Politics is the art of looking for trouble, finding it everywhere,
> diagnosing it incorrectly, and applying the wrong remedies."
> --Groucho Marx
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: ModalWindow accessibility - DIV placeholder not used

[Martin Grigorov]

On Mon, Mar 26, 2012 at 5:15 PM, lukuperman  wrote:
> Done. Made the requested updates to the ticket.
>
> Lucas
>
> PD: do you think i should create another ticket for the related post I
> mentioned above?

It is similar change - add it to this ticket.

>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/ModalWindow-accessibility-DIV-placeholder-not-used-tp4501891p4506115.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
>



-- 
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: ModalWindow accessibility - DIV placeholder not used

[lukuperman]

Done. Made the requested updates to the ticket.

Lucas

PD: do you think i should create another ticket for the related post I
mentioned above?

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-accessibility-DIV-placeholder-not-used-tp4501891p4506115.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: ModalWindow accessibility - DIV placeholder not used

[Martin Grigorov]

Thanks!

I already commented there ...
Just paste the old and the new (the way it how it should be) html as a comment.

On Mon, Mar 26, 2012 at 4:16 PM, lukuperman  wrote:
> Hi Martin, ticket 4472 created
> (https://issues.apache.org/jira/browse/WICKET-4472)
>
> But since I'm new to OSS contributions, I didn't attach a patch. Due to the
> low complexity of the change I don't think my patch is a blocker for you?
> I'll start setting up my env, to be ready to deliver patches in future
> tickets
>
> Regards
> Lucas
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/ModalWindow-accessibility-DIV-placeholder-not-used-tp4501891p4505952.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
>



-- 
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: ModalWindow accessibility - DIV placeholder not used

[lukuperman]

Hi Martin, ticket 4472 created
(https://issues.apache.org/jira/browse/WICKET-4472)

But since I'm new to OSS contributions, I didn't attach a patch. Due to the
low complexity of the change I don't think my patch is a blocker for you?
I'll start setting up my env, to be ready to deliver patches in future
tickets

Regards
Lucas

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-accessibility-DIV-placeholder-not-used-tp4501891p4505952.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: ModalWindow accessibility - DIV placeholder not used

[Martin Grigorov]

Hi Lucas,

On Mon, Mar 26, 2012 at 2:38 PM, lukuperman  wrote:
> Hi Martin, I took a look at the post you mentioned, but in that patch the div
> node is still being appended to the document.body node, resulting in the
> behavior i'm seeing. However I have to admit that appending the new div node
> to the placeholder is just a nice to have. A more appropriate solution for
> making the modal window more accessible would be the outer div element to
> have a role='dialog' attribute along with an aria-labelledBy=' element id>' attribute, like showed below:
>
> line 1170 of modal.js:
>
> " id=\""+idWindow+"\" role=\"dialog\"
> aria-labelledBy=\""+idCaptionText+""\"
> style=\"top: 10px; left: 10px; width: 100px;\">
>
> This will appropriately alert the screen readers when the modal is shown.
> Following with accessibility findings, i also posted
> http://apache-wicket.1842946.n4.nabble.com/adding-associated-text-to-the-close-anchor-on-modal-windows-tp4504732p4504732.html

Please create a ticket in Jira.
1.4.x wont be developed any more but we can add these improvements in
1.5.x and 6.x branches.

>
> Regards
> Lucas
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/ModalWindow-accessibility-DIV-placeholder-not-used-tp4501891p4505633.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
>



-- 
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: ModalWindow accessibility - DIV placeholder not used

[lukuperman]

Hi Martin, I took a look at the post you mentioned, but in that patch the div
node is still being appended to the document.body node, resulting in the
behavior i'm seeing. However I have to admit that appending the new div node
to the placeholder is just a nice to have. A more appropriate solution for
making the modal window more accessible would be the outer div element to
have a role='dialog' attribute along with an aria-labelledBy='' attribute, like showed below:

line 1170 of modal.js:

"

This will appropriately alert the screen readers when the modal is shown.
Following with accessibility findings, i also posted
http://apache-wicket.1842946.n4.nabble.com/adding-associated-text-to-the-close-anchor-on-modal-windows-tp4504732p4504732.html

Regards
Lucas

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-accessibility-DIV-placeholder-not-used-tp4501891p4505633.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: ModalWindow accessibility - DIV placeholder not used

[Martin Grigorov]

Hi Lucas,

This is how ModalWindow currently works. There is a ticket
(https://issues.apache.org/jira/browse/WICKET-3404) that will make
some changes in the way its html is generated but I'm not sure whether
these changes will help you anyhow.
I'm not an expert in ARIA at all so maybe you can help us making
Wicket components ARIA enabled by default. We can start with
ModalWindow component - explain what should be done, what attributes
should be added, and on which HTML element exactly.


On Sat, Mar 24, 2012 at 8:44 PM, lukuperman  wrote:
> Hello, I inherited an application that uses Apache Wicket 1.4.15. Everything
> works fine, but because of accessibility standards I have to address some
> findings we received from DQA team, which includes missing wai-aria
> attributes around to the modal windows. However I noticed the DIV
> placeholder I define in the markup is not where the modalwindow code ends,
> but rather a new DIV element is created dynamically at the end of the page's
> html. This prevents me from enclosing the modal window's DIV element. I
> would have expected the placeholder to be the place where the modalwindow
> code will reside. Am I getting it wrong? Either way, can anyone suggest me
> how can I enclose a modal window's DIV element?
>
> Thank you!
> Regards.
>
> PS: I do not include source code/error cause im not receiving any. Im just
> wondering about render behavior. Also, I don't think its a code problem
> cause the official modal window example at
> http://www.wicket-library.com/wicket-examples/ajax/modal-window?8 behaves
> the same way.
>
> Lucas
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/ModalWindow-accessibility-DIV-placeholder-not-used-tp4501891p4501891.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
>



-- 
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: ModalWindow and Serialization

[vov]

As I understand - the correct way is change usage PageCreator to setContent:)

Thank you very much for all your answers!!!

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-and-Serialization-tp4484547p4484858.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: ModalWindow and Serialization

[Martin Grigorov]

On Mon, Mar 19, 2012 at 3:31 PM, vov  wrote:
> 1) to as simple asgetSession().getAttribute(key)  -
> getSession().getAttribute(key)
>
> It is not in the topic but:
> What it different between your proposal and
> getApplication().getSessionStore().setAttribute(requst, key, value);

mine calls ISessionStore#setAttribute() if the session is bound. If it
is temporary then it keeps the attribute in a temporary map.

>
> Maybe it's stupid question - how to remove object from session if you use
> getSession().getAttribute(key) ?

org.apache.wicket.Session#removeAttribute
but it is protected ... You will need to override it to make it public.

there is this comment in Wicket code :
// TODO WICKET-NG made public for page manager, used to be protected,
see if there is a way to
// revert
public final Serializable getAttribute(final String name)

so set and get are public but remove is not ...
We will improve this for Wicket 6!


>
> 2) Of course - ModalWindow.setContent(aPanel)  will solve the problem. But
> in case if I have several modal windows on the one page - it's no good for
> performance. But I'm not sure about setting of the content on the fly

This will work. We do this in our app. There is one modal window which
content is dynamically loaded depending on the clicked link.

>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/ModalWindow-and-Serialization-tp4484547p4484792.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
>



-- 
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: ModalWindow and Serialization

[vov]

1) to as simple asgetSession().getAttribute(key)  -
getSession().getAttribute(key) 

It is not in the topic but:
What it different between your proposal and 
getApplication().getSessionStore().setAttribute(requst, key, value);

Maybe it's stupid question - how to remove object from session if you use
getSession().getAttribute(key) ?

2) Of course - ModalWindow.setContent(aPanel)  will solve the problem. But
in case if I have several modal windows on the one page - it's no good for
performance. But I'm not sure about setting of the content on the fly

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-and-Serialization-tp4484547p4484792.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: ModalWindow and Serialization

[Martin Grigorov]

On Mon, Mar 19, 2012 at 3:03 PM, vov  wrote:
> Thanks for your answer,
> of course session is not so simple as local variable - but it one of the
> solution

as simple as getSession().setAttribute(key, value) -
getSession().getAttribute(key)

>
> Maybe in next releases of wicket someone will come up with a simpler
> solution

the solution is already there - ModalWindow.setContent(aPanel)

>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/ModalWindow-and-Serialization-tp4484547p4484708.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
>



-- 
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: ModalWindow and Serialization

[vov]

Thanks for your answer,
of course session is not so simple as local variable - but it one of the
solution

Maybe in next releases of wicket someone will come up with a simpler
solution

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-and-Serialization-tp4484547p4484708.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: ModalWindow and Serialization

[Martin Grigorov]

Hi,

On Mon, Mar 19, 2012 at 2:16 PM, vov  wrote:
> Hi All,
> I have a lot of work with ModalWindows in my project and want to use objects
> which created on the base page and are changed in the modal windows.
> I found that ModalWindow was changed in wicket 1.5 and want to ask about
> solution.
> Please see short example:
> // Base Page
> public class MyPage extends WebPage
> {
>  public MyPage()
>  {
>    final ModalWindow window = new ModalWindow("window");
>    add(new AjaxLink("link")
>    {
>      @Override
>      public void onClick(AjaxRequestTarget target)
>      {
>        final CustomObject object = new CustomObject();
>        window.setPageCreator(new ModalWindow.PageCreator()
>        {
>          @Override
>          public Page createPage()
>          {
>            return new MyModalWindow(object, window);
>          }
>        });
>        window.setWindowClosedCallback(new
> ModalWindow.WindowClosedCallback()
>        {
>          @Override
>          public void onClose(AjaxRequestTarget target)
>          {
>            if (object.isValue())
>            {
>              // This code is never executed {1} in wicket 1.5. But it
> worked in wicket 1.4
>            }
>          }
>        });
>      }
>    });
>  }
> }
>
> // Modal Window
> public class MyModalWindow extends WebPage
> {
>  public MyModalWindow(final CustomObject object, final ModalWindow window)
>  {
>    add(new AjaxLink("link")
>    {
>      @Override
>      public void onClick(AjaxRequestTarget target)
>      {
>        object.setValue(true);
>        window.close(target);
>      }
>    });
>  }
> }
>
> As I understand - the reason of this behavior is serialization of pages.
> I also know one solution - use PageReference(same with example here -
> http://www.wicket-library.com/wicket-examples/ajax/modal-window?0).
> But I want to ask - is there another solution? Use PageReference is not so
> flexible.
> For example I have a lot of modal windows which are opened from the panel.
> In this case I have to search my panel on the page. Moreover I can use one
> panel from different pages.
> Other problem - I don't want to use global variables on the Base Page - I
> want(ant in several cases I should) use local variables.
>
> Can anyone give advice - how to simplify usage of modal windows in such
> cases?

Not sure whether this goes against your rule to keep it "local"
(because it is not really local when you pass a final object to an
inner class) but I think
the safest way is to keep such objects in the session. You can share
objects (or even better models) between components in a page, but as
you already read about it this is not the case when you share between
pages.

So
- solution 1 - put the object in the session
- solution 2 - use ModalWindow with a Panel, instead of a page

>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/ModalWindow-and-Serialization-tp4484547p4484547.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
>



-- 
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: ModalWindow does not close cleanly

[Nelson Segura]

I noticed also that if I add a dummy window closed call back to my page:

1) In the modal window, calling window.close() sets the "shown" flag to false
2) My dummy callback causes ModalWindow.WindowClosedBehavior to
respond. The current value of this shown flag is still true! Then the
behavior sets it to false again.

I believed that calling "window.close()" from inside a window that
uses page does not close the window cleanly.

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

Re: ModalWindow does not close cleanly

[Andrea Del Bene]

On 01/03/2012 12:30 AM, Nelson Segura wrote:

  The "shown" flag is set up to false by window.close(), but it stays as true 
in the
context of the parent page. This prevents the page from being opened a
second time. Maybe something similar to how you cannot pass pages
directly to a modal, but instead should pass a page reference.
I agree with you. Your problem seems very similar to the one of passing 
page to modal.
I think this issue has to do with page serialization: when we try to 
open modal window a second time, Wicket uses the "old" versions of both 
main page and modal window where "shown" flag is true.



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

Re: ModalWindow does not close cleanly

[Nelson Segura]

:) A patch will be nice, but ... I think this has to do with my modal
window using page instead of panel. Could it be?

The window clears up the "shown" flag correctly if I press in the "x"
for the modal window, because the CloseButtonBehavior gets called, but
then the Ajax Target being used is in the context of the parent page.
The "x" icon sits outside the window.

My close/cancel button is calling window.close() directly, but that is
being executed inside the context of the modal page. The "shown" flag
is set up to false by window.close(), but it stays as true in the
context of the parent page. This prevents the page from being opened a
second time. Maybe something similar to how you cannot pass pages
directly to a modal, but instead should pass a page reference.
If I provide a dummy WindowClosedCallback, then the flag gets clear in
the context of the parent page.

I don't know if what I am saying is clear or correct, but I don't
exactly know where to start to fix this :(

-nelson

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

Re: ModalWindow does not close cleanly

[Igor Vaynberg]

a patch is welcome :)

-igor

On Mon, Jan 2, 2012 at 10:24 AM, Nelson Segura  wrote:
> Any hope this can be fixed for 1.5.4? I will hate having to change all
> our modals to have a dummy call back to get it to work :(
> -Nelson
>
> On Wed, Dec 21, 2011 at 2:59 PM, Nelson Segura  wrote:
>> I have created a ticket, and attached a quick start to it
>>
>> https://issues.apache.org/jira/browse/WICKET-4311
>>
>> Notice that if you uncomment the dummy callback code, you will be able
>> to reopen the modal.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>

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

Re: ModalWindow does not close cleanly

[Nelson Segura]

Any hope this can be fixed for 1.5.4? I will hate having to change all
our modals to have a dummy call back to get it to work :(
-Nelson

On Wed, Dec 21, 2011 at 2:59 PM, Nelson Segura  wrote:
> I have created a ticket, and attached a quick start to it
>
> https://issues.apache.org/jira/browse/WICKET-4311
>
> Notice that if you uncomment the dummy callback code, you will be able
> to reopen the modal.

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

Re: ModalWindow does not close cleanly

[Nelson Segura]

I have created a ticket, and attached a quick start to it

https://issues.apache.org/jira/browse/WICKET-4311

Notice that if you uncomment the dummy callback code, you will be able
to reopen the modal.

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

Re: ModalWindow does not close cleanly

[Igor Vaynberg]

i took the window closed callback out of the ModalWindowPage in
wicket-examples and was able to close and reopen the modal...please
create a quickstart and attach it to a jira issue.

-igor

On Mon, Dec 19, 2011 at 12:39 PM, Nelson Segura  wrote:
> Sorry, I meant respond() ...
>
>
> On Mon, Dec 19, 2011 at 11:46 AM, Igor Vaynberg  
> wrote:
>> WindowClosedBehavior does not have render()...?
>>
>> -igor
>>
>> On Mon, Dec 19, 2011 at 11:40 AM, Nelson Segura  wrote:
>>> I found that if you have a modal window, and then you close it, it is
>>> not possible to reopen it anymore unless you have set a
>>> WindowClosedCallback. This is because WindowClosedBehavior.render()
>>> does not get called.
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>

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

Re: ModalWindow does not close cleanly

[Nelson Segura]

Sorry, I meant respond() ...


On Mon, Dec 19, 2011 at 11:46 AM, Igor Vaynberg  wrote:
> WindowClosedBehavior does not have render()...?
>
> -igor
>
> On Mon, Dec 19, 2011 at 11:40 AM, Nelson Segura  wrote:
>> I found that if you have a modal window, and then you close it, it is
>> not possible to reopen it anymore unless you have set a
>> WindowClosedCallback. This is because WindowClosedBehavior.render()
>> does not get called.
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>

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

Re: ModalWindow does not close cleanly

[Igor Vaynberg]

WindowClosedBehavior does not have render()...?

-igor

On Mon, Dec 19, 2011 at 11:40 AM, Nelson Segura  wrote:
> I found that if you have a modal window, and then you close it, it is
> not possible to reopen it anymore unless you have set a
> WindowClosedCallback. This is because WindowClosedBehavior.render()
> does not get called.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>

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

Re: ModalWindow shows Error Page in Opera

[Alex]

Thanks to all. With wicket 1.4.19 it works fine.

2011/10/21 Attila Király 

> It is fixed in 1.4.18 too:
> https://issues.apache.org/jira/browse/WICKET-3615
>
> Attila
>
> 2011/10/21 nhsoft.yhw 
>
> > Wicket 1.5.x have fixed the problem.
> >
> >
> > --
> > View this message in context:
> >
> http://apache-wicket.1842946.n4.nabble.com/ModalWindow-shows-Error-Page-in-Opera-tp3924738p3924885.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: ModalWindow shows Error Page in Opera

[Attila Király]

It is fixed in 1.4.18 too: https://issues.apache.org/jira/browse/WICKET-3615

Attila

2011/10/21 nhsoft.yhw 

> Wicket 1.5.x have fixed the problem.
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/ModalWindow-shows-Error-Page-in-Opera-tp3924738p3924885.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: ModalWindow shows Error Page in Opera

[nhsoft.yhw]

Wicket 1.5.x have fixed the problem.


--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-shows-Error-Page-in-Opera-tp3924738p3924885.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: ModalWindow shows Error Page in Opera

[Martin Grigorov]

On Fri, Oct 21, 2011 at 12:05 PM, Alex  wrote:
> Dear all,
>
> While trying to open a ModalWindow the Opera shows error page. Translated
> from German it says something like “Internal Communication error. Check the
> address or search for web site” In FF, IE, Safari everything works fine.
>
>
>
> Wicket version 1.4.9
Try with a newer version of Wicket.
>
> Opera 11.52
>
>
>
> Thanks a lot in advance
> Alex
>



-- 
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: ModalWindow, IFrame and source

[Nelson Segura]

Hey, thanks. I am planning to upgrade to 1.5.x in our .next release.

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

Re: ModalWindow, IFrame and source

[Martin Grigorov]

This is improved in 1.5.x.
You are recommended to upgrade.

On Wed, Oct 12, 2011 at 8:52 PM, Nelson Segura  wrote:
> Hello everyone:
>
> Looking back at issue:
>
> https://issues.apache.org/jira/browse/WICKET-2207
>
> I noticed that the fix was done against certain version of IE. In
> other cases, like firefox, a request to http://:/ is still performed.
> I have got some complains from users that their proxies are blocking
> that particular call as invalid/suspicious, causing a blocked content
> page to show instead of the modal window. I cannot reproduce this
> myself, by have seen it in at least one of our QA machines.
>
> My question is, is there a reason why this was not changed other than
> certain versions of IE? Having the "src" of the iframe for modal
> windows be "//:" still causes random problem for us in other browsers.
>
> -Nelson Segura
>
> -
> 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: ModalWindow in IE6, IE7, IE8 browser issues

[nhsoft.yhw]

I swith to use modal dialog with panel, it works.

ModalWindow seems to have some strange problems, sometimes it is difficult
to reproduce. For example, some of my applications ModalWindow normal, some
abnormal, but I can not find reason.

-
http://www.517wm.com
外卖订餐分享工具
--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-in-IE6-IE7-IE8-browser-issues-tp3854296p3854857.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: ModalWindow in IE6, IE7, IE8 browser issues

[Martin Grigorov]

This is fixed in 1.5.1

On Thu, Sep 29, 2011 at 8:50 AM, nhsoft.yhw  wrote:
> here is exception stack, but only IE throws the exception
>
>
> ERROR - DefaultExceptionMapper     - Connection lost, give up responding.
> org.apache.wicket.protocol.http.servlet.ResponseIOException:
> ClientAbortException:  java.io.IOException
>        at
> org.apache.wicket.protocol.http.servlet.ServletWebResponse.flush(ServletWebResponse.java:254)
>        at
> org.apache.wicket.protocol.http.HeaderBufferingWebResponse.flush(HeaderBufferingWebResponse.java:92)
>        at
> org.apache.wicket.request.resource.AbstractResource.setResponseHeaders(AbstractResource.java:611)
>        at
> org.apache.wicket.request.resource.AbstractResource.respond(AbstractResource.java:485)
>        at
> org.apache.wicket.request.handler.resource.ResourceRequestHandler.respond(ResourceRequestHandler.java:77)
>        at
> org.apache.wicket.request.handler.resource.ResourceReferenceRequestHandler.respond(ResourceReferenceRequestHandler.java:92)
>        at
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:712)
>        at
> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:63)
>        at
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:208)
>        at
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:251)
>        at
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:162)
>        at
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:218)
>        at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>        at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>        at
> org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:399)
>        at
> org.springframework.security.context.HttpSessionContextIntegrationFilter.doFilterHttp(HttpSessionContextIntegrationFilter.java:235)
>        at
> org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)
>        at
> org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:411)
>        at
> org.springframework.security.util.FilterChainProxy.doFilter(FilterChainProxy.java:188)
>        at
> org.springframework.security.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:99)
>        at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>        at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>        at
> org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:198)
>        at
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
>        at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>        at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>        at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240)
>        at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:164)
>        at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:462)
>        at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164)
>        at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
>        at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:563)
>        at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>        at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:399)
>        at
> org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:306)
>        at
> org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:322)
>        at
> org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:1732)
>        at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>        at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>        at java.lang.Thread.run(Thread.java:619)
> Caused by: ClientAbortException:  java.io.IOException
>        at
> org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:329)
>        at 
> org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:298)
>        at 
> org.apache.catalina.connector.Response.flushBuffer(Response.java:559)
>        at
> org.apache.catalina.connector.ResponseFacade.flushBuffer(ResponseFacade.java:303)
>        at
> javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java

Re: ModalWindow in IE6, IE7, IE8 browser issues

[nhsoft.yhw]

here is exception stack, but only IE throws the exception


ERROR - DefaultExceptionMapper - Connection lost, give up responding.
org.apache.wicket.protocol.http.servlet.ResponseIOException:
ClientAbortException:  java.io.IOException
at
org.apache.wicket.protocol.http.servlet.ServletWebResponse.flush(ServletWebResponse.java:254)
at
org.apache.wicket.protocol.http.HeaderBufferingWebResponse.flush(HeaderBufferingWebResponse.java:92)
at
org.apache.wicket.request.resource.AbstractResource.setResponseHeaders(AbstractResource.java:611)
at
org.apache.wicket.request.resource.AbstractResource.respond(AbstractResource.java:485)
at
org.apache.wicket.request.handler.resource.ResourceRequestHandler.respond(ResourceRequestHandler.java:77)
at
org.apache.wicket.request.handler.resource.ResourceReferenceRequestHandler.respond(ResourceReferenceRequestHandler.java:92)
at
org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:712)
at
org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:63)
at
org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:208)
at
org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:251)
at
org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:162)
at
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:218)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:399)
at
org.springframework.security.context.HttpSessionContextIntegrationFilter.doFilterHttp(HttpSessionContextIntegrationFilter.java:235)
at
org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)
at
org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:411)
at
org.springframework.security.util.FilterChainProxy.doFilter(FilterChainProxy.java:188)
at
org.springframework.security.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:99)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:198)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:164)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:462)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:563)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:399)
at
org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:306)
at
org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:322)
at
org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:1732)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: ClientAbortException:  java.io.IOException
at
org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:329)
at 
org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:298)
at org.apache.catalina.connector.Response.flushBuffer(Response.java:559)
at
org.apache.catalina.connector.ResponseFacade.flushBuffer(ResponseFacade.java:303)
at
javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:161)
at
javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:161)
at
org.apache.wicket.protocol.http.servlet.ServletWebResponse.flush(ServletWebResponse.java:250)
... 39 mor

Re: ModalWindow in IE6, IE7, IE8 browser issues

[Igor Vaynberg]

please create a quickstart that reproduces the issue and attach it to
a jira issue.

-igor


On Wed, Sep 28, 2011 at 8:54 PM, nhsoft.yhw  wrote:
> Q1:
> After the upgrade to 1.5 version , I found that the ModalWindow appear in IE
> "Page Expired" error, but in  Chrome browser to normal.
>
> Same Code for ModalWindow works for Firefox, IE, Chrome with wicket 1.4.18
> version.
>
> My ModalWindow Use WebPage Mode, not Page Mode.
>
> Q2:
> sometimes Modalwindow did not display for Firefox 6, but always works for
> firefox "private browse" mode.
>
> I found an article about wicket1.5's page cache changes
> (https://cwiki.apache.org/WICKET/caching-in-wicket-15.html), whether this
> claim?
>
>
>
>
>
> -
> http://www.517wm.com
> 外卖订餐分享工具
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/ModalWindow-in-IE6-IE7-IE8-browser-issues-tp3854296p3854296.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
>
>

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

RE: ModalWindow and reusable components

[Chris Colman]

We wanted to make ModelWindowS more reusable in Wicket and so we created
the ModalX project that is now part of WicketStuff. Not sure if it's
what you're looking for but it certainly makes the use of ModalWindowS
in our apps much more generic/reusable.

https://github.com/wicketstuff/core/wiki/ModalX

It comes in both 1.4.x and 1.5.x flavors.

Regards,
Chris
Step Ahead Software

>-Original Message-
>From: Chris Merrill [mailto:ch...@webperformance.com]
>Sent: Saturday, 24 September 2011 1:48 AM
>To: users@wicket.apache.org
>Subject: ModalWindow and reusable components
>
>In my short time with Wicket, I've found that whenever something seems
>really
>hard, I'm probably doing it wrong :>  I'm hoping this is such a case.
>
>
>We have a number of components that are used on multiple pages. They
are
>pretty
>simple - typically a couple of form field linked together for data
entry.
>
>Sometimes we want one of those to appear in a ModalWindow, coupled with
>Ok/Cancel
>buttons and then update part of the page when the user accepts a
change.
>I am able to make this work, but it is pretty cumbersome. I first have
to
>put the component into a panel with the ok and cancel buttons.  The
panel
>has to
>know about the part of the page that needs to be refreshed. And it has
to
>know
>about the component embedded within it, in order to pass the selection
back
>to the page. This has to be done for each component we want inside a
modal
>ok/cancel
>window.
>
>I found one article on a reusable ModalWindow pattern:
>http://stuq.nl/weblog/2008-06-05/wicket-how-to-write-a-reusable-modal-
>window-popup
>that helped a bit. My next step was to try to put the ok/cancel buttons
>into
>my ModalWindow subclass, but I failed pretty miserably.  I've done some
>more digging
>and now think I know how to make this work, but it seems like it will
be
>more than
>a little convoluted.
>
>
>Am I going about this all wrong?
>
>
>
>--
>---
- -
>Chris Merrill   |  Web Performance, Inc.
>ch...@webperformance.com|  http://webperformance.com
>919-433-1762|  919-845-7601
>
>Web Performance: Website Load Testing Software & Services
>---
- -
>
>-
>To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>For additional commands, e-mail: users-h...@wicket.apache.org


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

Re: ModalWindow and reusable components

[Igor Vaynberg]

the window has a WindowClosedCallback you can use to refresh the
appropriate part of the page once the window has been closed.

-igor


On Fri, Sep 23, 2011 at 8:48 AM, Chris Merrill  wrote:
> In my short time with Wicket, I've found that whenever something seems really
> hard, I'm probably doing it wrong :>  I'm hoping this is such a case.
>
>
> We have a number of components that are used on multiple pages. They are 
> pretty
> simple - typically a couple of form field linked together for data entry.
>
> Sometimes we want one of those to appear in a ModalWindow, coupled with 
> Ok/Cancel
> buttons and then update part of the page when the user accepts a change.
> I am able to make this work, but it is pretty cumbersome. I first have to
> put the component into a panel with the ok and cancel buttons.  The panel has 
> to
> know about the part of the page that needs to be refreshed. And it has to know
> about the component embedded within it, in order to pass the selection back
> to the page. This has to be done for each component we want inside a modal 
> ok/cancel
> window.
>
> I found one article on a reusable ModalWindow pattern:
> http://stuq.nl/weblog/2008-06-05/wicket-how-to-write-a-reusable-modal-window-popup
> that helped a bit. My next step was to try to put the ok/cancel buttons into
> my ModalWindow subclass, but I failed pretty miserably.  I've done some more 
> digging
> and now think I know how to make this work, but it seems like it will be more 
> than
> a little convoluted.
>
>
> Am I going about this all wrong?
>
>
>
> --
>  -
> Chris Merrill                           |  Web Performance, Inc.
> ch...@webperformance.com                |  http://webperformance.com
> 919-433-1762                            |  919-845-7601
>
> Web Performance: Website Load Testing Software & Services
>  -
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

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

Re: ModalWindow and reusable components

[Dan Retzlaff]

Hi Chris,

I have struggled with this pattern myself. Ultimately I ended up using an
eventing pattern to decouple the modal from the page components that need to
be refreshed. I rolled my own event dispatch mechanism in Wicket 1.4 using
event-specific interfaces and IVisitors that find all components that
implement the interface. Wicket 1.5 has some baked in support for such a
pattern which probably requires less boilerplate [1]. In any case, before
closing the modal your ok button submit handler simply fires off the event.

Hope that helps!

Dan

[1]
https://cwiki.apache.org/WICKET/migration-to-wicket-15.html#MigrationtoWicket1.5-Intercomponentevents

On Fri, Sep 23, 2011 at 8:48 AM, Chris Merrill wrote:

> In my short time with Wicket, I've found that whenever something seems
> really
> hard, I'm probably doing it wrong :>  I'm hoping this is such a case.
>
>
> We have a number of components that are used on multiple pages. They are
> pretty
> simple - typically a couple of form field linked together for data entry.
>
> Sometimes we want one of those to appear in a ModalWindow, coupled with
> Ok/Cancel
> buttons and then update part of the page when the user accepts a change.
> I am able to make this work, but it is pretty cumbersome. I first have to
> put the component into a panel with the ok and cancel buttons.  The panel
> has to
> know about the part of the page that needs to be refreshed. And it has to
> know
> about the component embedded within it, in order to pass the selection back
> to the page. This has to be done for each component we want inside a modal
> ok/cancel
> window.
>
> I found one article on a reusable ModalWindow pattern:
>
> http://stuq.nl/weblog/2008-06-05/wicket-how-to-write-a-reusable-modal-window-popup
> that helped a bit. My next step was to try to put the ok/cancel buttons
> into
> my ModalWindow subclass, but I failed pretty miserably.  I've done some
> more digging
> and now think I know how to make this work, but it seems like it will be
> more than
> a little convoluted.
>
>
> Am I going about this all wrong?
>
>
>
> --
>  -
> Chris Merrill   |  Web Performance, Inc.
> ch...@webperformance.com|  http://webperformance.com
> 919-433-1762|  919-845-7601
>
> Web Performance: Website Load Testing Software & Services
>  -
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

RE: ModalWindow problem

[Sotil Bertanzetti, Matteo]

Thanks for help.

I already tried, but it didn't work.

Matteo Sotil

-Missatge original-
De: Dan Retzlaff [mailto:dretzl...@gmail.com] 
Enviat: miércoles, 21 de septiembre de 2011 17:11
Per a: users@wicket.apache.org
Tema: Re: ModalWindow problem

Try giving your modal page a reference to the outer page object, and not
just a model within it. This way serialization of the modal page will
encounter the outer page and update its pagemap entry. I don't know what's
up with 1.5, but with certain request patterns we found this necessary even
in 1.4.

On Wed, Sep 21, 2011 at 4:44 AM, Sotil Bertanzetti, Matteo <
mso...@gencat.cat> wrote:

> Is there another option?, I would have to do a lot of changes to implement
> Panel backed ModalWindow.
>
> Maybe I stay on wicket 1.4 for a while.
>
> Matteo Sotil
>
> -Missatge original-
> De: Martin Grigorov [mailto:mgrigo...@apache.org]
> Enviat: miércoles, 21 de septiembre de 2011 13:19
> Per a: users@wicket.apache.org
> Tema: Re: ModalWindow problem
>
> On Wed, Sep 21, 2011 at 12:25 PM, Sotil Bertanzetti, Matteo
>  wrote:
> > Thanks for responding.
> >
> > I'm using a dynamic model (PropertyModel) but it doesn't work either.
> > For me it's an important loss of functionality. I use it on modal
> > windows, to show a search page (with TabbedPanel, list with
> > pagination...) and select one register; could you please suggest me some
> > alternative?.
>
> Use ModalWindow backed by a Panel instead of a Page. It is much more
> stable.
> There are many tickets for ModalWindow backed by a Page.
>
> >
> > Thank you.
> >
> > Matteo Sotil
> >
> > -Missatge original-
> > De: Andrea Del Bene [mailto:adelb...@ciseonweb.it]
> > Enviat: martes, 20 de septiembre de 2011 18:16
> > Per a: users@wicket.apache.org
> > Tema: Re: ModalWindow problem
> >
> > Hi,
> >
> > we dealt this topic in this issue:
> >
> > https://issues.apache.org/jira/browse/WICKET-3809
> >
> > Basically starting from Wicket 1.5 you can't share static models between
> >
> > pages.
> >> Hello.
> >>
> >>
> >>
> >> I have a problem with ModalWindow in wicket 1.5.0.
> >>
> >> I create a ModalWindow from a page, and that modal window changes
> >> original page's model; some textfields should change their value
> >> according to model change, but they not; in fact seems as if model had
> >> not really changed. ModalWindow's content is a page, not a component;
> > if
> >> I use a component as content, it works, but I need it to be a page.
> > This
> >> worked correctly on wicket 1.4.18.
> >>
> >>
> >>
> >> Matteo Sotil
> >>
> >> 935526855
> >>
> >> mso...@gencat.cat
> >>
> >>
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
>
>
>
> --
> 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
>
>

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

Re: ModalWindow problem

[Dan Retzlaff]

Try giving your modal page a reference to the outer page object, and not
just a model within it. This way serialization of the modal page will
encounter the outer page and update its pagemap entry. I don't know what's
up with 1.5, but with certain request patterns we found this necessary even
in 1.4.

On Wed, Sep 21, 2011 at 4:44 AM, Sotil Bertanzetti, Matteo <
mso...@gencat.cat> wrote:

> Is there another option?, I would have to do a lot of changes to implement
> Panel backed ModalWindow.
>
> Maybe I stay on wicket 1.4 for a while.
>
> Matteo Sotil
>
> -Missatge original-
> De: Martin Grigorov [mailto:mgrigo...@apache.org]
> Enviat: miércoles, 21 de septiembre de 2011 13:19
> Per a: users@wicket.apache.org
> Tema: Re: ModalWindow problem
>
> On Wed, Sep 21, 2011 at 12:25 PM, Sotil Bertanzetti, Matteo
>  wrote:
> > Thanks for responding.
> >
> > I'm using a dynamic model (PropertyModel) but it doesn't work either.
> > For me it's an important loss of functionality. I use it on modal
> > windows, to show a search page (with TabbedPanel, list with
> > pagination...) and select one register; could you please suggest me some
> > alternative?.
>
> Use ModalWindow backed by a Panel instead of a Page. It is much more
> stable.
> There are many tickets for ModalWindow backed by a Page.
>
> >
> > Thank you.
> >
> > Matteo Sotil
> >
> > -Missatge original-----
> > De: Andrea Del Bene [mailto:adelb...@ciseonweb.it]
> > Enviat: martes, 20 de septiembre de 2011 18:16
> > Per a: users@wicket.apache.org
> > Tema: Re: ModalWindow problem
> >
> > Hi,
> >
> > we dealt this topic in this issue:
> >
> > https://issues.apache.org/jira/browse/WICKET-3809
> >
> > Basically starting from Wicket 1.5 you can't share static models between
> >
> > pages.
> >> Hello.
> >>
> >>
> >>
> >> I have a problem with ModalWindow in wicket 1.5.0.
> >>
> >> I create a ModalWindow from a page, and that modal window changes
> >> original page's model; some textfields should change their value
> >> according to model change, but they not; in fact seems as if model had
> >> not really changed. ModalWindow's content is a page, not a component;
> > if
> >> I use a component as content, it works, but I need it to be a page.
> > This
> >> worked correctly on wicket 1.4.18.
> >>
> >>
> >>
> >> Matteo Sotil
> >>
> >> 935526855
> >>
> >> mso...@gencat.cat
> >>
> >>
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
>
>
>
> --
> 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: ModalWindow problem

[Sotil Bertanzetti, Matteo]

Is there another option?, I would have to do a lot of changes to implement 
Panel backed ModalWindow. 

Maybe I stay on wicket 1.4 for a while.

Matteo Sotil

-Missatge original-
De: Martin Grigorov [mailto:mgrigo...@apache.org] 
Enviat: miércoles, 21 de septiembre de 2011 13:19
Per a: users@wicket.apache.org
Tema: Re: ModalWindow problem

On Wed, Sep 21, 2011 at 12:25 PM, Sotil Bertanzetti, Matteo
 wrote:
> Thanks for responding.
>
> I'm using a dynamic model (PropertyModel) but it doesn't work either.
> For me it's an important loss of functionality. I use it on modal
> windows, to show a search page (with TabbedPanel, list with
> pagination...) and select one register; could you please suggest me some
> alternative?.

Use ModalWindow backed by a Panel instead of a Page. It is much more stable.
There are many tickets for ModalWindow backed by a Page.

>
> Thank you.
>
> Matteo Sotil
>
> -Missatge original-
> De: Andrea Del Bene [mailto:adelb...@ciseonweb.it]
> Enviat: martes, 20 de septiembre de 2011 18:16
> Per a: users@wicket.apache.org
> Tema: Re: ModalWindow problem
>
> Hi,
>
> we dealt this topic in this issue:
>
> https://issues.apache.org/jira/browse/WICKET-3809
>
> Basically starting from Wicket 1.5 you can't share static models between
>
> pages.
>> Hello.
>>
>>
>>
>> I have a problem with ModalWindow in wicket 1.5.0.
>>
>> I create a ModalWindow from a page, and that modal window changes
>> original page's model; some textfields should change their value
>> according to model change, but they not; in fact seems as if model had
>> not really changed. ModalWindow's content is a page, not a component;
> if
>> I use a component as content, it works, but I need it to be a page.
> This
>> worked correctly on wicket 1.4.18.
>>
>>
>>
>> Matteo Sotil
>>
>> 935526855
>>
>> mso...@gencat.cat
>>
>>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>



-- 
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: ModalWindow problem

[Martin Grigorov]

On Wed, Sep 21, 2011 at 12:25 PM, Sotil Bertanzetti, Matteo
 wrote:
> Thanks for responding.
>
> I'm using a dynamic model (PropertyModel) but it doesn't work either.
> For me it's an important loss of functionality. I use it on modal
> windows, to show a search page (with TabbedPanel, list with
> pagination...) and select one register; could you please suggest me some
> alternative?.

Use ModalWindow backed by a Panel instead of a Page. It is much more stable.
There are many tickets for ModalWindow backed by a Page.

>
> Thank you.
>
> Matteo Sotil
>
> -Missatge original-
> De: Andrea Del Bene [mailto:adelb...@ciseonweb.it]
> Enviat: martes, 20 de septiembre de 2011 18:16
> Per a: users@wicket.apache.org
> Tema: Re: ModalWindow problem
>
> Hi,
>
> we dealt this topic in this issue:
>
> https://issues.apache.org/jira/browse/WICKET-3809
>
> Basically starting from Wicket 1.5 you can't share static models between
>
> pages.
>> Hello.
>>
>>
>>
>> I have a problem with ModalWindow in wicket 1.5.0.
>>
>> I create a ModalWindow from a page, and that modal window changes
>> original page's model; some textfields should change their value
>> according to model change, but they not; in fact seems as if model had
>> not really changed. ModalWindow's content is a page, not a component;
> if
>> I use a component as content, it works, but I need it to be a page.
> This
>> worked correctly on wicket 1.4.18.
>>
>>
>>
>> Matteo Sotil
>>
>> 935526855
>>
>> mso...@gencat.cat
>>
>>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>



-- 
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: ModalWindow problem

[Sotil Bertanzetti, Matteo]

Thanks for responding.

I'm using a dynamic model (PropertyModel) but it doesn't work either.
For me it's an important loss of functionality. I use it on modal
windows, to show a search page (with TabbedPanel, list with
pagination...) and select one register; could you please suggest me some
alternative?.

Thank you.

Matteo Sotil

-Missatge original-
De: Andrea Del Bene [mailto:adelb...@ciseonweb.it] 
Enviat: martes, 20 de septiembre de 2011 18:16
Per a: users@wicket.apache.org
Tema: Re: ModalWindow problem

Hi,

we dealt this topic in this issue:

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

Basically starting from Wicket 1.5 you can't share static models between

pages.
> Hello.
>
>
>
> I have a problem with ModalWindow in wicket 1.5.0.
>
> I create a ModalWindow from a page, and that modal window changes
> original page's model; some textfields should change their value
> according to model change, but they not; in fact seems as if model had
> not really changed. ModalWindow's content is a page, not a component;
if
> I use a component as content, it works, but I need it to be a page.
This
> worked correctly on wicket 1.4.18.
>
>
>
> Matteo Sotil
>
> 935526855
>
> mso...@gencat.cat
>
>


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


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

Re: ModalWindow problem

[Andrea Del Bene]

Hi,

we dealt this topic in this issue:

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

Basically starting from Wicket 1.5 you can't share static models between 
pages.

Hello.



I have a problem with ModalWindow in wicket 1.5.0.

I create a ModalWindow from a page, and that modal window changes
original page's model; some textfields should change their value
according to model change, but they not; in fact seems as if model had
not really changed. ModalWindow's content is a page, not a component; if
I use a component as content, it works, but I need it to be a page. This
worked correctly on wicket 1.4.18.



Matteo Sotil

935526855

mso...@gencat.cat





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

Re: ModalWindow - CSS problem in IE

[drf]

Found the problem:

The 

Re: ModalWindow

[Duy Do]

It works after I added "Wicket.Window.unloadConfirmation = false;" into 
the page.


Thanks for your helps.

Cheers,
Duy


On 7/12/2011 3:43 PM, Ernesto Reinaldo Barreiro wrote:

Maybe you are getting an Exception which is redirecting you to an
error page... which can also produce what you describe...

Ernesto


On Tue, Jul 12, 2011 at 10:36 AM, Duy Do  wrote:

Thank you for your quick reply.

I already used AjaxButton but it still show that popup. Do we have other
options?

Duy

On 7/12/2011 3:27 PM, Martijn Dashorst wrote:

Use an AjaxSubmitButton instead of a normal SubmitButton (or
AjaxSubmitLink...).

You submit your form with a normal submit instead of an ajax one. The
modalwindow script captures this and tries to help the user.

Martijn

On Tue, Jul 12, 2011 at 10:15 AM, Duy Dowrote:

Hi all,

When submit a form in modal window, browsers display a popup with
message:
/"Are you sure want  leave this page?"/
How we disable this popup?

Thanks,
Duy







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



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




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

Re: ModalWindow

[Ernesto Reinaldo Barreiro]

Maybe you are getting an Exception which is redirecting you to an
error page... which can also produce what you describe...

Ernesto


On Tue, Jul 12, 2011 at 10:36 AM, Duy Do  wrote:
> Thank you for your quick reply.
>
> I already used AjaxButton but it still show that popup. Do we have other
> options?
>
> Duy
>
> On 7/12/2011 3:27 PM, Martijn Dashorst wrote:
>>
>> Use an AjaxSubmitButton instead of a normal SubmitButton (or
>> AjaxSubmitLink...).
>>
>> You submit your form with a normal submit instead of an ajax one. The
>> modalwindow script captures this and tries to help the user.
>>
>> Martijn
>>
>> On Tue, Jul 12, 2011 at 10:15 AM, Duy Do  wrote:
>>>
>>> Hi all,
>>>
>>> When submit a form in modal window, browsers display a popup with
>>> message:
>>> /"Are you sure want  leave this page?"/
>>> How we disable this popup?
>>>
>>> Thanks,
>>> Duy
>>>
>>>
>>>
>>
>>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

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

RE: ModalWindow

[Wilhelmsen Tor Iver]

> I already used AjaxButton but it still show that popup. Do we have other 
> options?

Do you have an onbeforeunload event handler that returns a value? That will 
trigger such a message as well.

- Tor Iver

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

Re: ModalWindow

[Duy Do]

Thank you for your quick reply.

I already used AjaxButton but it still show that popup. Do we have other 
options?


Duy

On 7/12/2011 3:27 PM, Martijn Dashorst wrote:

Use an AjaxSubmitButton instead of a normal SubmitButton (or AjaxSubmitLink...).

You submit your form with a normal submit instead of an ajax one. The
modalwindow script captures this and tries to help the user.

Martijn

On Tue, Jul 12, 2011 at 10:15 AM, Duy Do  wrote:

Hi all,

When submit a form in modal window, browsers display a popup with message:
/"Are you sure want  leave this page?"/
How we disable this popup?

Thanks,
Duy









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

Re: ModalWindow

[Martijn Dashorst]

Use an AjaxSubmitButton instead of a normal SubmitButton (or AjaxSubmitLink...).

You submit your form with a normal submit instead of an ajax one. The
modalwindow script captures this and tries to help the user.

Martijn

On Tue, Jul 12, 2011 at 10:15 AM, Duy Do  wrote:
> Hi all,
>
> When submit a form in modal window, browsers display a popup with message:
> /"Are you sure want  leave this page?"/
> How we disable this popup?
>
> Thanks,
> Duy
>
>
>



-- 
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: ModalWindow with Panel - HeaderContributor in Panel not called

[Nicklas Johnson]

On a related note, has anyone experienced HeaderContributors being
ineffective in IE8 when added via an ajax event?

The scenario is that a component with an attached Ibehavior which in turn
provides several Javascript HeaderContributors is added to an ajax target
(eg, target.addComponent(fooComponent)).

In Firefox the HeaderContributor seems to be added and evaluated correctly,
and the behavior works as expected.  In IE8, however, the contributed
Javascript appears not to be evaluated.

We are able to work around it by pre-adding the HeaderContributors prior to
the ajax event being fired, but that's kind of a messy solution... Would
rather see IE8 doing the right thing.

(Still need to get up to the latest 1.4, so it's possible that this problem
has already been addressed, though I'm curious if it is or was a known
problem with that dreadful browser.)

   Nick


On 5/12/11 9:51 AM, "Igor Vaynberg"  wrote:

> wicket keeps track of header contributions and doesnt contribute the
> same contribution more then once.
> 
> -igor
> 
> 
> On Thu, May 12, 2011 at 1:24 AM, Marieke Vandamme
>  wrote:
>> Igor,
>> 
>> Thanks for the answer, and you're right indeed.
>> I forgot that I added code in my HeaderContributor that checked if it was an
>> ajax request. Because I found it useless so re-add all the css + js to the
>> page just when you're readding your form after validation or something. But
>> when using the HeaderContributor with the modalwindow, I can never be
>> certain that the css / js is already loaded or not.
>> So I just removed my ajax-check, and now it's working. But can I maybe add
>> some test to check if my HomeMadeReusabel component is inside a ModalWindow?
>> Because now I re-add the js + css every time on an ajax call, and most of
>> the time it's not necessary.
>> 
>> Thanks! Marieke Vandamme
>> 
>> --
>> View this message in context:
>> http://apache-wicket.1842946.n4.nabble.com/ModalWindow-with-Panel-HeaderContr
>> ibutor-in-Panel-not-called-tp3514628p3516743.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
>> 
>> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
> 

-- 
Nicklas Johnson -=- N6OL
TXBU Software Engineer
"Ask" is not a noun.  You mean "request," "requirement," or "question."


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

Re: ModalWindow with Panel - HeaderContributor in Panel not called

[Igor Vaynberg]

wicket keeps track of header contributions and doesnt contribute the
same contribution more then once.

-igor


On Thu, May 12, 2011 at 1:24 AM, Marieke Vandamme
 wrote:
> Igor,
>
> Thanks for the answer, and you're right indeed.
> I forgot that I added code in my HeaderContributor that checked if it was an
> ajax request. Because I found it useless so re-add all the css + js to the
> page just when you're readding your form after validation or something. But
> when using the HeaderContributor with the modalwindow, I can never be
> certain that the css / js is already loaded or not.
> So I just removed my ajax-check, and now it's working. But can I maybe add
> some test to check if my HomeMadeReusabel component is inside a ModalWindow?
> Because now I re-add the js + css every time on an ajax call, and most of
> the time it's not necessary.
>
> Thanks! Marieke Vandamme
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/ModalWindow-with-Panel-HeaderContributor-in-Panel-not-called-tp3514628p3516743.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
>
>

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

Re: ModalWindow with Panel - HeaderContributor in Panel not called

[Marieke Vandamme]

Igor, 

Thanks for the answer, and you're right indeed. 
I forgot that I added code in my HeaderContributor that checked if it was an
ajax request. Because I found it useless so re-add all the css + js to the
page just when you're readding your form after validation or something. But
when using the HeaderContributor with the modalwindow, I can never be
certain that the css / js is already loaded or not. 
So I just removed my ajax-check, and now it's working. But can I maybe add
some test to check if my HomeMadeReusabel component is inside a ModalWindow?
Because now I re-add the js + css every time on an ajax call, and most of
the time it's not necessary. 

Thanks! Marieke Vandamme

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-with-Panel-HeaderContributor-in-Panel-not-called-tp3514628p3516743.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: ModalWindow with Panel - HeaderContributor in Panel not called

[Igor Vaynberg]

it is contributed, but wont be visible using view-source because it is
added dynamically via ajax and is not in the original source of the
page.

-igor

On Wed, May 11, 2011 at 6:02 AM, Marieke Vandamme
 wrote:
> Hello,
>
> This is my situation:
> Page
>  |-> ModalWindow
>           |-> Panel
>                   |-> HomeMadeReusableComponent
>                                   |-> HeaderContributor
>
> In this HeaderContributor I override renderHead(IHeaderResponse response).
> I thought that everything I wrote to the response would end up in my Page,
> but it doesn't...
>
> I know that one option would be to add the HeaderContributor directly to the
> page, but then I have duplicate code that is now needly inside my
> HomeMadeReusableComponent.
>
> I tried to add the HeaderContributer inside my HomeMadeReusableComponent to
> the page instead then adding it to the component, but HeaderContributors are
> defined inside the component constructor and then my page isn't ready yet.
>
> Can anyone help me or give me any hints?
> Thanks in advance ! Marieke vandamme
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/ModalWindow-with-Panel-HeaderContributor-in-Panel-not-called-tp3514628p3514628.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
>
>

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

RE: ModalWindow patch for 1.4.x

[Russell Morrisey]

Martin,

I have attached a quickstart to the JIRA issue which demonstrates an alternate 
implementation of WindowClosedBehavior, using an AjaxFormSubmitBehavior 
extension.



RUSSELL E. MORRISEY
Programmer Analyst Professional
Mission Solutions Engineering, LLC

| russell.morri...@missionse.com | www.missionse.com<http://www.missionse.com/>
304 West Route 38, Moorestown, NJ 08057-3212

From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Thursday, April 21, 2011 10:52 AM
To: Russell Morrisey
Subject: Re: ModalWindow patch for 1.4.x

Thanks!
On Thu, Apr 21, 2011 at 5:26 PM, Russell Morrisey 
mailto:russell.morri...@missionse.com>> wrote:
Martin,

Thanks for your reply.

I created a JIRA issue with the .patch file:
https://issues.apache.org/jira/browse/WICKET-3630

I will work on creating an example.

Thanks,

RUSSELL E. MORRISEY
Programmer Analyst Professional
Mission Solutions Engineering, LLC

| russell.morri...@missionse.com<mailto:russell.morri...@missionse.com> | 
www.missionse.com<http://www.missionse.com>
304 West Route 38, Moorestown, NJ 08057-3212

-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org<mailto:mgrigo...@apache.org>]
Sent: Thursday, April 21, 2011 2:35 AM
To: users@wicket.apache.org<mailto:users@wicket.apache.org>
Subject: Re: ModalWindow patch for 1.4.x

Hi,

I don't see attached file. Maybe .patch files are not allowed.
If you create ticket then please create either tests for the new
functionality or at least a demo application that uses it.
Thanks!

On Thu, Apr 21, 2011 at 2:27 AM, Russell Morrisey <
russell.morri...@missionse.com<mailto:russell.morri...@missionse.com>> wrote:

>  Please consider the following ModalWindow patch for inclusion in
> wicket-extensions 1.4.x
>
>
>
> This change lets me replace the WindowClosedBehavior with a custom
> implementation, and preserves the code in getWindowOpenJavascript() that
> manages the javascript setting by using an interface. The body of the
> behavior’s respond() method is made a member of ModalWindow, so that it can
> be called by custom implementers.
>
>
>
> Use cases:
>
> -Add an IAjaxCallDecorator w/script which disables UI controls on the
> containing page while the window closed behavior is being processed
>
> -Substitute a behavior which submits the form on the containing page after
> the modal window is closed
>
>
>
> I’ve attached the .patch file. Do I need to create a JIRA issue?
>
>
>
> Thanks, guys,
>  --
>
>
> *RUSSELL E. MORRISEY
> Programmer Analyst Professional
> Mission Solutions Engineering, LLC *
>
> | russell.morri...@missionse.com<mailto:russell.morri...@missionse.com> | 
> www.missionse.com<http://www.missionse.com>
> 304 West Route 38, Moorestown, NJ 08057-3212
>
>
>
> --
> This is a PRIVATE message. If you are not the intended recipient, please
> delete without copying and kindly advise us by e-mail of the mistake in
> delivery.
> NOTE: Regardless of content, this e-mail shall not operate to bind MSE to
> any order or other contract unless pursuant to explicit written agreement or
> government initiative expressly permitting the use of e-mail for such
> purpose.
>
>
> -
> To unsubscribe, e-mail: 
> users-unsubscr...@wicket.apache.org<mailto:users-unsubscr...@wicket.apache.org>
> For additional commands, e-mail: 
> users-h...@wicket.apache.org<mailto:users-h...@wicket.apache.org>
>



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

This is a PRIVATE message. If you are not the intended recipient, please delete 
without copying and kindly advise us by e-mail of the mistake in delivery.
NOTE: Regardless of content, this e-mail shall not operate to bind MSE to any 
order or other contract unless pursuant to explicit written agreement or 
government initiative expressly permitting the use of e-mail for such purpose.



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



This is a PRIVATE message. If you are not the intended recipient, please delete 
without copying and kindly advise us by e-mail of the mistake in delivery.
NOTE: Regardless of content, this e-mail shall not operate to bind MSE to any 
order or other contract unless pursuant to explicit written agreement or 
government initiative expressly permitting the use of e-mail for such purpose.

RE: ModalWindow patch for 1.4.x

[Russell Morrisey]

Martin,

Thanks for your reply.

I created a JIRA issue with the .patch file:
https://issues.apache.org/jira/browse/WICKET-3630

I will work on creating an example.

Thanks,

RUSSELL E. MORRISEY
Programmer Analyst Professional
Mission Solutions Engineering, LLC

| russell.morri...@missionse.com | www.missionse.com
304 West Route 38, Moorestown, NJ 08057-3212


-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Thursday, April 21, 2011 2:35 AM
To: users@wicket.apache.org
Subject: Re: ModalWindow patch for 1.4.x

Hi,

I don't see attached file. Maybe .patch files are not allowed.
If you create ticket then please create either tests for the new
functionality or at least a demo application that uses it.
Thanks!

On Thu, Apr 21, 2011 at 2:27 AM, Russell Morrisey <
russell.morri...@missionse.com> wrote:

>  Please consider the following ModalWindow patch for inclusion in
> wicket-extensions 1.4.x
>
>
>
> This change lets me replace the WindowClosedBehavior with a custom
> implementation, and preserves the code in getWindowOpenJavascript() that
> manages the javascript setting by using an interface. The body of the
> behavior’s respond() method is made a member of ModalWindow, so that it can
> be called by custom implementers.
>
>
>
> Use cases:
>
> -Add an IAjaxCallDecorator w/script which disables UI controls on the
> containing page while the window closed behavior is being processed
>
> -Substitute a behavior which submits the form on the containing page after
> the modal window is closed
>
>
>
> I’ve attached the .patch file. Do I need to create a JIRA issue?
>
>
>
> Thanks, guys,
>  --
>
>
> *RUSSELL E. MORRISEY
> Programmer Analyst Professional
> Mission Solutions Engineering, LLC *
>
> | russell.morri...@missionse.com | www.missionse.com
> 304 West Route 38, Moorestown, NJ 08057-3212
>
>
>
> --
> This is a PRIVATE message. If you are not the intended recipient, please
> delete without copying and kindly advise us by e-mail of the mistake in
> delivery.
> NOTE: Regardless of content, this e-mail shall not operate to bind MSE to
> any order or other contract unless pursuant to explicit written agreement or
> government initiative expressly permitting the use of e-mail for such
> purpose.
>
>
> -
> 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 <http://jweekend.com/>

This is a PRIVATE message. If you are not the intended recipient, please delete 
without copying and kindly advise us by e-mail of the mistake in delivery.
NOTE: Regardless of content, this e-mail shall not operate to bind MSE to any 
order or other contract unless pursuant to explicit written agreement or 
government initiative expressly permitting the use of e-mail for such purpose.

Re: ModalWindow patch for 1.4.x

[Martin Grigorov]

Hi,

I don't see attached file. Maybe .patch files are not allowed.
If you create ticket then please create either tests for the new
functionality or at least a demo application that uses it.
Thanks!

On Thu, Apr 21, 2011 at 2:27 AM, Russell Morrisey <
russell.morri...@missionse.com> wrote:

>  Please consider the following ModalWindow patch for inclusion in
> wicket-extensions 1.4.x
>
>
>
> This change lets me replace the WindowClosedBehavior with a custom
> implementation, and preserves the code in getWindowOpenJavascript() that
> manages the javascript setting by using an interface. The body of the
> behavior’s respond() method is made a member of ModalWindow, so that it can
> be called by custom implementers.
>
>
>
> Use cases:
>
> -Add an IAjaxCallDecorator w/script which disables UI controls on the
> containing page while the window closed behavior is being processed
>
> -Substitute a behavior which submits the form on the containing page after
> the modal window is closed
>
>
>
> I’ve attached the .patch file. Do I need to create a JIRA issue?
>
>
>
> Thanks, guys,
>  --
>
>
> *RUSSELL E. MORRISEY
> Programmer Analyst Professional
> Mission Solutions Engineering, LLC *
>
> | russell.morri...@missionse.com | www.missionse.com
> 304 West Route 38, Moorestown, NJ 08057-3212
>
>
>
> --
> This is a PRIVATE message. If you are not the intended recipient, please
> delete without copying and kindly advise us by e-mail of the mistake in
> delivery.
> NOTE: Regardless of content, this e-mail shall not operate to bind MSE to
> any order or other contract unless pursuant to explicit written agreement or
> government initiative expressly permitting the use of e-mail for such
> purpose.
>
>
> -
> 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 

RE: ModalWindow detach/serialize crashes wicket app

[Russell Morrisey]

Clint, Pedro,

Thank you both for your replies. Based on your comments, and from looking at a 
heap dump, I am thinking the problem may stem from an inner class created by 
our app's wicket Session. I have made the inner class static, so that it will 
no longer hold a reference to the Session. The inner class is a model which 
loads a reference to a User object.

Any hints on how to reproduce the problem, so I can prove it? I'm not clear on 
what triggers the serialization process that causes the error to be thrown.


RUSSELL E. MORRISEY
Programmer Analyst Professional
Mission Solutions Engineering, LLC

| russell.morri...@missionse.com | www.missionse.com
304 West Route 38, Moorestown, NJ 08057-3212

-Original Message-
From: Clint Checketts [mailto:checke...@gmail.com]
Sent: Friday, April 01, 2011 7:06 PM
To: users@wicket.apache.org
Subject: Re: ModalWindow detach/serialize crashes wicket app

Do you have a propetymodel with the session as its object?

On Friday, April 1, 2011, Pedro Santos  wrote:
> looks like your page is referencing session or pagemap somehow
>
> On Fri, Apr 1, 2011 at 4:15 PM, Russell Morrisey <
> russell.morri...@missionse.com> wrote:
>
>> Guys,
>>
>> I'm having an intermittent issue in development where use of a ModalWindow
>> on a page completely crashes wicket.
>>
>> I don't know of the ModalWindow is the root cause. I am hoping that someone
>> with intimate knowledge of wicket's page store can help me narrow it down.
>> Hints appreciated. =)
>>
>> The "X" button and other ajax controls within the ModalWindow's content
>> page stop responding to user input. When I try to hit the same bookmarkable
>> URL again for the containing page, wicket seems to have stopped running
>> entirely, and I get a Tomcat HTTP 404 error.
>>
>> The JVM outputs a StackOverflowError which looks like it happens during
>> page serialization.
>> Apr 1, 2011 2:53:14 PM org.apache.catalina.core.StandardWrapperValve invoke
>> SEVERE: Servlet.service() for servlet default threw exception
>> java.lang.StackOverflowError
>> The two blocks below occur multiple times, each, within a single trace:
>> ...
>>   at
>> org.apache.wicket.util.io.IObjectStreamFactory$DefaultObjectStreamFactory$2.writeObjectOverride(IObjectStreamFactory.java:121)
>>   at
>> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:322)
>>   at
>> org.apache.wicket.util.lang.Objects.objectToByteArray(Objects.java:1130)
>>   at
>> org.apache.wicket.protocol.http.pagestore.AbstractPageStore.serializePage(AbstractPageStore.java:203)
>>   at
>> org.apache.wicket.protocol.http.pagestore.DiskPageStore.prepareForSerialization(DiskPageStore.java:1190)
>>   at
>> org.apache.wicket.protocol.http.SecondLevelCacheSessionStore$SecondLevelCachePageMap.writeObject(SecondLevelCacheSessionStore.java:386)
>> ...
>>   at
>> org.apache.wicket.util.io.IObjectStreamFactory$DefaultObjectStreamFactory$2.writeObjectOverride(IObjectStreamFactory.java:121)
>>   at
>> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:322)
>>   at
>> org.apache.wicket.util.lang.Objects.objectToByteArray(Objects.java:1130)
>>   at
>> org.apache.wicket.protocol.http.pagestore.AbstractPageStore$PageSerializer.getPageReplacementObject(AbstractPageStore.java:288)
>>   at org.apache.wicket.Page.writeReplace(Page.java:1383)
>>
>> In our application's init() method, we have this setting:
>>
>> Objects.setObjectStreamFactory(null); // jdk serialization
>>
>> I have tried to reproduce the problem in a quickstart; but, I have not had
>> much luck, so far.
>>
>> We don't really have any custom code in our app that deals with object
>> serialization. Any help would be appreciated. We are currently using wicket
>> 1.4.9; if you guys think this might be fixed in a later version, we'd be
>> happy to upgrade. I searched briefly through the JIRA, and nothing popped
>> out at me.
>>
>> 
>>
>> RUSSELL E. MORRISEY
>> Programmer Analyst Professional
>> Mission Solutions Engineering, LLC
>>
>> | russell.morri...@missionse.com | www.missionse.com<
>> http://www.missionse.com/>
>> 304 West Route 38, Moorestown, NJ 08057-3212
>>
>>
>> 
>> This is a PRIVATE message. If you are not the intended recipient, please
>> delete without copying and kindly advise us by e-mail of the mistake in
>> delivery.
>> NOTE: Regardless of content, this e-mail shall not operate to bind M

Re: ModalWindow detach/serialize crashes wicket app

[Clint Checketts]

Do you have a propetymodel with the session as its object?

On Friday, April 1, 2011, Pedro Santos  wrote:
> looks like your page is referencing session or pagemap somehow
>
> On Fri, Apr 1, 2011 at 4:15 PM, Russell Morrisey <
> russell.morri...@missionse.com> wrote:
>
>> Guys,
>>
>> I'm having an intermittent issue in development where use of a ModalWindow
>> on a page completely crashes wicket.
>>
>> I don't know of the ModalWindow is the root cause. I am hoping that someone
>> with intimate knowledge of wicket's page store can help me narrow it down.
>> Hints appreciated. =)
>>
>> The "X" button and other ajax controls within the ModalWindow's content
>> page stop responding to user input. When I try to hit the same bookmarkable
>> URL again for the containing page, wicket seems to have stopped running
>> entirely, and I get a Tomcat HTTP 404 error.
>>
>> The JVM outputs a StackOverflowError which looks like it happens during
>> page serialization.
>> Apr 1, 2011 2:53:14 PM org.apache.catalina.core.StandardWrapperValve invoke
>> SEVERE: Servlet.service() for servlet default threw exception
>> java.lang.StackOverflowError
>> The two blocks below occur multiple times, each, within a single trace:
>> ...
>>       at
>> org.apache.wicket.util.io.IObjectStreamFactory$DefaultObjectStreamFactory$2.writeObjectOverride(IObjectStreamFactory.java:121)
>>       at
>> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:322)
>>       at
>> org.apache.wicket.util.lang.Objects.objectToByteArray(Objects.java:1130)
>>       at
>> org.apache.wicket.protocol.http.pagestore.AbstractPageStore.serializePage(AbstractPageStore.java:203)
>>       at
>> org.apache.wicket.protocol.http.pagestore.DiskPageStore.prepareForSerialization(DiskPageStore.java:1190)
>>       at
>> org.apache.wicket.protocol.http.SecondLevelCacheSessionStore$SecondLevelCachePageMap.writeObject(SecondLevelCacheSessionStore.java:386)
>> ...
>>       at
>> org.apache.wicket.util.io.IObjectStreamFactory$DefaultObjectStreamFactory$2.writeObjectOverride(IObjectStreamFactory.java:121)
>>       at
>> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:322)
>>       at
>> org.apache.wicket.util.lang.Objects.objectToByteArray(Objects.java:1130)
>>       at
>> org.apache.wicket.protocol.http.pagestore.AbstractPageStore$PageSerializer.getPageReplacementObject(AbstractPageStore.java:288)
>>       at org.apache.wicket.Page.writeReplace(Page.java:1383)
>>
>> In our application's init() method, we have this setting:
>>
>> Objects.setObjectStreamFactory(null); // jdk serialization
>>
>> I have tried to reproduce the problem in a quickstart; but, I have not had
>> much luck, so far.
>>
>> We don't really have any custom code in our app that deals with object
>> serialization. Any help would be appreciated. We are currently using wicket
>> 1.4.9; if you guys think this might be fixed in a later version, we'd be
>> happy to upgrade. I searched briefly through the JIRA, and nothing popped
>> out at me.
>>
>> 
>>
>> RUSSELL E. MORRISEY
>> Programmer Analyst Professional
>> Mission Solutions Engineering, LLC
>>
>> | russell.morri...@missionse.com | www.missionse.com<
>> http://www.missionse.com/>
>> 304 West Route 38, Moorestown, NJ 08057-3212
>>
>>
>> 
>> This is a PRIVATE message. If you are not the intended recipient, please
>> delete without copying and kindly advise us by e-mail of the mistake in
>> delivery.
>> NOTE: Regardless of content, this e-mail shall not operate to bind MSE to
>> any order or other contract unless pursuant to explicit written agreement or
>> government initiative expressly permitting the use of e-mail for such
>> purpose.
>>
>
>
>
> --
> Pedro Henrique Oliveira dos Santos
>

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

Re: ModalWindow detach/serialize crashes wicket app

[Pedro Santos]

looks like your page is referencing session or pagemap somehow

On Fri, Apr 1, 2011 at 4:15 PM, Russell Morrisey <
russell.morri...@missionse.com> wrote:

> Guys,
>
> I'm having an intermittent issue in development where use of a ModalWindow
> on a page completely crashes wicket.
>
> I don't know of the ModalWindow is the root cause. I am hoping that someone
> with intimate knowledge of wicket's page store can help me narrow it down.
> Hints appreciated. =)
>
> The "X" button and other ajax controls within the ModalWindow's content
> page stop responding to user input. When I try to hit the same bookmarkable
> URL again for the containing page, wicket seems to have stopped running
> entirely, and I get a Tomcat HTTP 404 error.
>
> The JVM outputs a StackOverflowError which looks like it happens during
> page serialization.
> Apr 1, 2011 2:53:14 PM org.apache.catalina.core.StandardWrapperValve invoke
> SEVERE: Servlet.service() for servlet default threw exception
> java.lang.StackOverflowError
> The two blocks below occur multiple times, each, within a single trace:
> ...
>   at
> org.apache.wicket.util.io.IObjectStreamFactory$DefaultObjectStreamFactory$2.writeObjectOverride(IObjectStreamFactory.java:121)
>   at
> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:322)
>   at
> org.apache.wicket.util.lang.Objects.objectToByteArray(Objects.java:1130)
>   at
> org.apache.wicket.protocol.http.pagestore.AbstractPageStore.serializePage(AbstractPageStore.java:203)
>   at
> org.apache.wicket.protocol.http.pagestore.DiskPageStore.prepareForSerialization(DiskPageStore.java:1190)
>   at
> org.apache.wicket.protocol.http.SecondLevelCacheSessionStore$SecondLevelCachePageMap.writeObject(SecondLevelCacheSessionStore.java:386)
> ...
>   at
> org.apache.wicket.util.io.IObjectStreamFactory$DefaultObjectStreamFactory$2.writeObjectOverride(IObjectStreamFactory.java:121)
>   at
> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:322)
>   at
> org.apache.wicket.util.lang.Objects.objectToByteArray(Objects.java:1130)
>   at
> org.apache.wicket.protocol.http.pagestore.AbstractPageStore$PageSerializer.getPageReplacementObject(AbstractPageStore.java:288)
>   at org.apache.wicket.Page.writeReplace(Page.java:1383)
>
> In our application's init() method, we have this setting:
>
> Objects.setObjectStreamFactory(null); // jdk serialization
>
> I have tried to reproduce the problem in a quickstart; but, I have not had
> much luck, so far.
>
> We don't really have any custom code in our app that deals with object
> serialization. Any help would be appreciated. We are currently using wicket
> 1.4.9; if you guys think this might be fixed in a later version, we'd be
> happy to upgrade. I searched briefly through the JIRA, and nothing popped
> out at me.
>
> 
>
> RUSSELL E. MORRISEY
> Programmer Analyst Professional
> Mission Solutions Engineering, LLC
>
> | russell.morri...@missionse.com | www.missionse.com<
> http://www.missionse.com/>
> 304 West Route 38, Moorestown, NJ 08057-3212
>
>
> 
> This is a PRIVATE message. If you are not the intended recipient, please
> delete without copying and kindly advise us by e-mail of the mistake in
> delivery.
> NOTE: Regardless of content, this e-mail shall not operate to bind MSE to
> any order or other contract unless pursuant to explicit written agreement or
> government initiative expressly permitting the use of e-mail for such
> purpose.
>



-- 
Pedro Henrique Oliveira dos Santos

Re: Modalwindow showing content from external URL

[Pedro Santos]

ops, u saind external link, yes, just put an iframe is fine

On Tue, Mar 15, 2011 at 12:24 PM, Pedro Santos  wrote:

> You can use an ModalWindow.PageCreator see:
>
> http://wicket.apache.org/apidocs/1.4/org/apache/wicket/extensions/ajax/markup/html/modal/ModalWindow.html#setPageCreator(org.apache.wicket.extensions.ajax.markup.html.modal.ModalWindow.PageCreator)
> 
>
> On Tue, Mar 15, 2011 at 11:48 AM, Marieke Vandamme <
> marieke.vanda...@tvh.be> wrote:
>
>> Hello,
>>
>> Is there a way to open an external page inside a modalwindow?
>> The reason why I ask is to avoid popup-blokkers...
>> Or should i just put an iframe on my modalwindow?
>>
>> Thanks, Marieke Vandamme
>>
>> --
>> View this message in context:
>> http://apache-wicket.1842946.n4.nabble.com/Modalwindow-showing-content-from-external-URL-tp3356798p3356798.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
>>
>>
>
>
> --
> Pedro Henrique Oliveira dos Santos
>



-- 
Pedro Henrique Oliveira dos Santos

Re: Modalwindow showing content from external URL

[Pedro Santos]

You can use an ModalWindow.PageCreator see:
http://wicket.apache.org/apidocs/1.4/org/apache/wicket/extensions/ajax/markup/html/modal/ModalWindow.html#setPageCreator(org.apache.wicket.extensions.ajax.markup.html.modal.ModalWindow.PageCreator)


On Tue, Mar 15, 2011 at 11:48 AM, Marieke Vandamme
wrote:

> Hello,
>
> Is there a way to open an external page inside a modalwindow?
> The reason why I ask is to avoid popup-blokkers...
> Or should i just put an iframe on my modalwindow?
>
> Thanks, Marieke Vandamme
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Modalwindow-showing-content-from-external-URL-tp3356798p3356798.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
>
>


-- 
Pedro Henrique Oliveira dos Santos