Re: Modal closed callback
Hi Gabriel,
thanks for your help.
Regards
Marco
Il 27/08/2015 20:27, Gabriel Landon ha scritto:
You mean something like this :
public class PanelContentModal extends ModalVoid {
/** close callback. */
private WindowClosedCallback windowClosedCallback = null;
public PanelContentModal(final String varMarkupId) {
super(varMarkupId);
setUseCloseHandler(true);
}
@Override
protected void onClose(final AjaxRequestTarget paramTarget) {
if (windowClosedCallback != null) {
windowClosedCallback.onClose(paramTarget);
}
}
public PanelContentModal setWindowClosedCallback(final
WindowClosedCallback callback) {
windowClosedCallback = callback;
return this;
}
}
And then use it like a ModalWindow :
PanelContentModal modal = new PanelContentModal(yourId);
modal.setWindowClosedCallback(new WindowClosedCallback() {
@Override
public void onClose(final AjaxRequestTarget paramTarget) {
// Do your refresh
}
});
regards,
Gabriel.
});
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Modal-closed-callback-tp4671861p4671862.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
--
Dott. Marco Di Sabatino Di Diodoro
Tel. +39 3939065570
Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net
Apache Syncope PMC Member
http://people.apache.org/~mdisabatino/
Re: New Community page
On 24/08/15 17:29, Mihir Chhaya wrote: Thanks, Andrea. Very helpful links for developers like me and, everybody else looking into Wicket site for any other reason. My humble observation though; there is 'CONTRIBUTE' link before 'COMMUNITY'. Would it be helpful in 'linking' those two or having reference of COMMUNITY on the other one? Or, Contribute section mentioning other projects (WicketStuff and Wicket-Bootstrap - with reference to COMMUNITY page) Hi and thank you for your feedback. I think your observation is right. I will try to insert a reference to 'community' at then end of 'contribute' page. I hope I have not confused with mention of my observation above. Thanks again to you and the wicket team, -Mihir. On Mon, Aug 24, 2015, 5:25 AM Andrea Del Bene an.delb...@gmail.com wrote: Hi folks, I've uploaded a new page on our site called 'Community' where anyone can find the different community-driven resources for Wicket. https://wicket.apache.org/community/ I hope you will like it! Andrea - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Has anybody used WebSockets with an embedded Jetty instance?
Hi, You can use : ServerContainer serverContainer = WebSocketServerContainerInitializer.configureContext(bb); serverContainer.addEndpoint(new WicketServerEndpointConfig()); bb is: WebAppContext bb = new WebAppContext(); Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Fri, Aug 28, 2015 at 6:05 PM, Don Ferguson don.fergu...@gmail.com wrote: I have an app built on Wicket 7.0,0 and Jetty 9.2.6 to which I am attempting to add WebSockets (wicket-native-websocket-javax). The app functions properly when running from the IDE, however I have not been able to get web sockets to work when running from an executable WAR file. The main issue appears to be classloader related. I’m struggling to figure out precisely what classes need to be alongside Jetty in the system classloader, and what needs to be part of the WAR. Before introducing WebSockets, all of the wicket jars were in the WebApp classloader (WEB-INF/lib). However now some classes (such as WicketServerEndpointConfig) need to be in Jetty’s classloader. But if I put all of wicket in the Jetty's classloader, I get other problems. Anyway, I would really appreciate some guidance if anyone has sorted this out. -Don - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Has anybody used WebSockets with an embedded Jetty instance?
Hi Martin, I'm already doing that (I encountered your earlier post which got me this far). This means that WebServerEndpointConfig must be in Jetty's classpath, along with its dependencies. I'm ending up with the bulk of wicket in Jetty's classpath (and duplicated in WEB-INF/lib) which leads to having two versions of Application.class loaded by two different classloaders. The upshot is that, when trying to upgrade the connection, WicketEndPoint.onOpen() tries to get the Application object via: WebApplication app = (WebApplication) WebApplication.get(appName); which returns null, due to the classloader confusion (appName was registered using the Application.class loaded in the webapp classloader). The obvious solution would be to remove wicket from WEB-INF/lib, so that there would only be the copy in jetty's classloader, but that lead to other problems. Anyway, was just wondering how to structure the executable WAR to avoid this nightmare. -Don On Fri, Aug 28, 2015 at 9:19 AM, Martin Grigorov mgrigo...@apache.org wrote: Hi, You can use : ServerContainer serverContainer = WebSocketServerContainerInitializer.configureContext(bb); serverContainer.addEndpoint(new WicketServerEndpointConfig()); bb is: WebAppContext bb = new WebAppContext(); Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Fri, Aug 28, 2015 at 6:05 PM, Don Ferguson don.fergu...@gmail.com wrote: I have an app built on Wicket 7.0,0 and Jetty 9.2.6 to which I am attempting to add WebSockets (wicket-native-websocket-javax). The app functions properly when running from the IDE, however I have not been able to get web sockets to work when running from an executable WAR file. The main issue appears to be classloader related. I’m struggling to figure out precisely what classes need to be alongside Jetty in the system classloader, and what needs to be part of the WAR. Before introducing WebSockets, all of the wicket jars were in the WebApp classloader (WEB-INF/lib). However now some classes (such as WicketServerEndpointConfig) need to be in Jetty’s classloader. But if I put all of wicket in the Jetty's classloader, I get other problems. Anyway, I would really appreciate some guidance if anyone has sorted this out. -Don - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Has anybody used WebSockets with an embedded Jetty instance?
I have an app built on Wicket 7.0,0 and Jetty 9.2.6 to which I am attempting to add WebSockets (wicket-native-websocket-javax). The app functions properly when running from the IDE, however I have not been able to get web sockets to work when running from an executable WAR file. The main issue appears to be classloader related. I’m struggling to figure out precisely what classes need to be alongside Jetty in the system classloader, and what needs to be part of the WAR. Before introducing WebSockets, all of the wicket jars were in the WebApp classloader (WEB-INF/lib). However now some classes (such as WicketServerEndpointConfig) need to be in Jetty’s classloader. But if I put all of wicket in the Jetty's classloader, I get other problems. Anyway, I would really appreciate some guidance if anyone has sorted this out. -Don - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
OAuth2 on google app engine - Same httpsession - new wicket sessions
Hi all, I have built a rather crude OAuth2 authentication / authorization of google apis mechanism. I am using wicketstuff.gae (and a customized wicket-auth-roles for internal app authorization). On the gae side, I am using the REST api for the shake of clarity and traceability. The problem, which I am facing is that during the flow wicket page - google authentication - redirection servlet(filter) - wicket page new wicket sessions are created at every step. So far I have discovered the following: 1. Everything works fine on the local development server. The problem only happens on the deployed application. 2. The httpsession remains the same, so I think it is a problem with the combination wicket / app engine (maybe wicket session does not get stored in the httpsession?) Has anyone faced something similar / any suggestions ? Thank you, Elias. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
