Re: wait indicator not showing with veil for AjaxButton

2014-04-23 Thread msalman
Thanks for your help. I knew that it had some thing to do with the url. I found another way to make it work by extending the IndicatingAjaxButton class. It seems it knows the way to find the right URL. But that made me change the code at a lot of different places where the original button was be

Re: Wicket + CDI, in JBoss EAP / WildFly

2014-04-23 Thread Sande Gilda
Hi Martin, He's referring to the wicket-war and wickeet-ear quickstarts here: https://github.com/jboss-developer/jboss-eap-quickstarts On 04/23/2014 10:20 AM, Martin Grigorov wrote: Hi, Wicket Quickstart (http://wicket.apache.org/start/quickstart.html) doesn't use CDI. Which quickstart do

Re: Wicket + CDI, in JBoss EAP / WildFly

2014-04-23 Thread Martin Grigorov
Hi, Wicket Quickstart (http://wicket.apache.org/start/quickstart.html) doesn't use CDI. Which quickstart do you talk about ? Which version of wicket-cdi - 1.0 or 1.1 ? Martin Grigorov Wicket Training and Consulting On Wed, Apr 23, 2014 at 5:14 PM, Ondrej Zizka wrote: > Hi, > > the Wicket quic

Re: Wicket + CDI, in JBoss EAP / WildFly

2014-04-23 Thread Martijn Dashorst
Which "The Wicket quick start for Wildfly" are you talking about? Martijn On Wed, Apr 23, 2014 at 4:14 PM, Ondrej Zizka wrote: > Hi, > > the Wicket quickstart for WildFly, when deployed, gives a warning - > > WARNING [org.jboss.seam.conversation.spi.SeamConversationContextFactory] > (ServerServ

Wicket + CDI, in JBoss EAP / WildFly

2014-04-23 Thread Ondrej Zizka
Hi, the Wicket quickstart for WildFly, when deployed, gives a warning - WARNING [org.jboss.seam.conversation.spi.SeamConversationContextFactory] (ServerService Thread Pool -- 48) No matching SeamConversationContext for store type interface javax.servlet.http.HttpServletRequest, using NOOP inst

SOLVED / Re: Evaluating wickets ajax-response programatically

2014-04-23 Thread Patrick Davids
Martin, you made my day. Thank you very much! Patrick P.s. concerning your other mail... "self" member... dont really know, but does not lead into any script errors, so I thought it might be correct. Was just a try... ;-) Am 23.04.2014 15:19, schrieb Martin Grigorov: > Hi, > > See > https://gith

Re: Evaluating wickets ajax-response programatically

2014-04-23 Thread Martin Grigorov
On Wed, Apr 23, 2014 at 4:37 PM, Patrick Davids < patrick.dav...@nubologic.com> wrote: > Hi Ernesto, > > I read the url-member by script from an attribute, we prev. added via > AttributeAppender. > > > This is how I execute my ajax call: > $.ajax({ > url : u

Re: Evaluating wickets ajax-response programatically

2014-04-23 Thread Patrick Davids
Hi Ernesto, I read the url-member by script from an attribute, we prev. added via AttributeAppender. This is how I execute my ajax call: $.ajax({ url : url, type : 'POST', . . .

Re: Wicketstuff TimerPushService memory leak?

2014-04-23 Thread Decebal Suiu
Thanks Martin! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicketstuff-TimerPushService-memory-leak-tp4665418p4665548.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubs

Re: Evaluating wickets ajax-response programatically

2014-04-23 Thread Martin Grigorov
Hi, See https://github.com/apache/wicket/blob/master/wicket-experimental/wicket-atmosphere/src/main/java/org/apache/wicket/atmosphere/jquery.wicketatmosphere.js#L31 Martin Grigorov Wicket Training and Consulting On Wed, Apr 23, 2014 at 4:01 PM, Patrick Davids < patrick.dav...@nubologic.com> wro

Re: Wicketstuff TimerPushService memory leak?

2014-04-23 Thread Martin Grigorov
https://issues.apache.org/jira/browse/WICKET-5570 Martin Grigorov Wicket Training and Consulting On Wed, Apr 23, 2014 at 3:40 PM, Martin Grigorov wrote: > Hi, > > It appears to be a memory leak caused by Wicket's ajax timer behavior. > Please create a ticket. > > Martin Grigorov > Wicket Train

Re: Evaluating wickets ajax-response programatically

2014-04-23 Thread Ernesto Reinaldo Barreiro
How do you "call" server side AJAX behavior? On Wed, Apr 23, 2014 at 3:01 PM, Patrick Davids < patrick.dav...@nubologic.com> wrote: > Hi all, > > due to a very complex gui panel with many javascript we are using a > quite pure AbstractAjaxBehavior. > > I print out a callback url, I call it, and

Evaluating wickets ajax-response programatically

2014-04-23 Thread Patrick Davids
Hi all, due to a very complex gui panel with many javascript we are using a quite pure AbstractAjaxBehavior. I print out a callback url, I call it, and so on... and having an onRequest() what nearly does the same as AbstractAjaxDefaultBehaviors (just a bit different). Its copy-paste, but I don

Re: Wicketstuff TimerPushService memory leak?

2014-04-23 Thread Martin Grigorov
Hi, It appears to be a memory leak caused by Wicket's ajax timer behavior. Please create a ticket. Martin Grigorov Wicket Training and Consulting On Wed, Apr 23, 2014 at 2:46 PM, Martin Grigorov wrote: > Hi Decebal, > > Your first message didn't make it to the mailing list and from the second

Re: Wicketstuff TimerPushService memory leak?

2014-04-23 Thread Martin Grigorov
Hi Decebal, Your first message didn't make it to the mailing list and from the second alone I didn't understand that. I'll try to check what goes wrong there when I have some time. Martin Grigorov Wicket Training and Consulting On Wed, Apr 23, 2014 at 2:15 PM, Decebal Suiu wrote: > Hi Martin

Re: Wicketstuff TimerPushService memory leak?

2014-04-23 Thread Decebal Suiu
Hi Martin I don't understand you. I talk about the browser memory and I feel like you're talking about java memory. My problem is the browser (tab process) memory and not the java memory. Best regards, Decebal -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicketst