Re: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-12 Thread Martin Grigorov
The problem was found and fixed in
https://issues.apache.org/jira/browse/WICKET-3040
Wicket 1.4.12 will be build soon and a vote mail will be sent.

On Sun, Sep 12, 2010 at 8:44 PM, Chris Colman
wrote:

> I read in the 1.4.11 changelogs that there was an improvement in the
> retrieval of resources from a package such as .js files. It appears that
> previously it was possible that resources were retrieved with the
> jsessionid as a parameter even though cookies were enabled. I noticed
> this sometime back when reviewing the objects in the browser cache -
> there were multiple copies of certain wicket .js files - differentiated
> by the jesssionid parameter.
>
> This is obviously not performance optimal for visitors returning to your
> site as the wicket-ajax.js would not be retrieved from the cache but
> downloaded from the server again.
>
> It seems liks 1.4.11 fixes that problem via:
>
> https://issues.apache.org/jira/browse/WICKET-2999
>
>
> I'm wondering if the problem some people are seeing with 1.4.11 is a
> result of a caching issue whereby the browser is using an older, cached,
> version of wicket-ajax.js (or some other .js) now that the removal of
> the jsessionid is allowing reuse of the .js rather than downloading a
> fresh copy for each session.
>
> So perhaps this reported problem 'broken ajax' simply requires a cache
> flush.
>
> There certainly doesn't appear to be any further reports of this bug for
> a few days so maybe the caches have sorted themselves out.
>
> If people are still having this problem after a cache flush please
> respond here because we're trying to decide whether to deploy our next
> production release using 1.4.10 or 1.4.11 and would like to know if this
> issue is still occurring or not.
>
>
> >-Original Message-
> >From: vladimir.kovalyuk [mailto:koval...@gmail.com]
> >Sent: Saturday, 11 September 2010 8:35 PM
> >To: users@wicket.apache.org
> >Subject: Re: Wicket 1.4.11 seems to have Ajax support broken under
> Firefox
> >3.6.x
> >
> >
> >You're not alone.
> >I upgraded to wicket 1.4.11  and noticed  that the ajax handling was
> >broked.
> >Rolled back to 1.4.10 and ajax handling was broken. Ctrl+R in FF
> helped.
> >Probably something is wrong in wicket-ajax.js?
> >
> >--
> >View this message in context: http://apache-
> >wicket.1842946.n4.nabble.com/Wicket-1-4-11-seems-to-have-Ajax-support-
> >broken-under-Firefox-3-6-x-tp2534120p2535557.html
> >Sent from the Wicket - User 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: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-12 Thread Chris Colman
I read in the 1.4.11 changelogs that there was an improvement in the
retrieval of resources from a package such as .js files. It appears that
previously it was possible that resources were retrieved with the
jsessionid as a parameter even though cookies were enabled. I noticed
this sometime back when reviewing the objects in the browser cache -
there were multiple copies of certain wicket .js files - differentiated
by the jesssionid parameter.

This is obviously not performance optimal for visitors returning to your
site as the wicket-ajax.js would not be retrieved from the cache but
downloaded from the server again.

It seems liks 1.4.11 fixes that problem via:

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


I'm wondering if the problem some people are seeing with 1.4.11 is a
result of a caching issue whereby the browser is using an older, cached,
version of wicket-ajax.js (or some other .js) now that the removal of
the jsessionid is allowing reuse of the .js rather than downloading a
fresh copy for each session.

So perhaps this reported problem 'broken ajax' simply requires a cache
flush.

There certainly doesn't appear to be any further reports of this bug for
a few days so maybe the caches have sorted themselves out.

If people are still having this problem after a cache flush please
respond here because we're trying to decide whether to deploy our next
production release using 1.4.10 or 1.4.11 and would like to know if this
issue is still occurring or not.


>-Original Message-
>From: vladimir.kovalyuk [mailto:koval...@gmail.com]
>Sent: Saturday, 11 September 2010 8:35 PM
>To: users@wicket.apache.org
>Subject: Re: Wicket 1.4.11 seems to have Ajax support broken under
Firefox
>3.6.x
>
>
>You're not alone.
>I upgraded to wicket 1.4.11  and noticed  that the ajax handling was
>broked.
>Rolled back to 1.4.10 and ajax handling was broken. Ctrl+R in FF
helped.
>Probably something is wrong in wicket-ajax.js?
>
>--
>View this message in context: http://apache-
>wicket.1842946.n4.nabble.com/Wicket-1-4-11-seems-to-have-Ajax-support-
>broken-under-Firefox-3-6-x-tp2534120p2535557.html
>Sent from the Wicket - User 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: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-11 Thread vladimir.kovalyuk

You're not alone.
I upgraded to wicket 1.4.11  and noticed  that the ajax handling was broked.
Rolled back to 1.4.10 and ajax handling was broken. Ctrl+R in FF helped.
Probably something is wrong in wicket-ajax.js?

-- 
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wicket-1-4-11-seems-to-have-Ajax-support-broken-under-Firefox-3-6-x-tp2534120p2535557.html
Sent from the Wicket - User mailing list archive at Nabble.com.

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



Re: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-10 Thread nmetzger

I'm glad I'm not the only one. I had a couple of AJAX components not reacting
with 1.4.11, no error message though. They worked well with all versions
between 1.4.7 and 1.4.10.

Natalie
-- 
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wicket-1-4-11-seems-to-have-Ajax-support-broken-under-Firefox-3-6-x-tp2534120p2534834.html
Sent from the Wicket - User mailing list archive at Nabble.com.

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



Re: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-10 Thread Andrea Del Bene
Martin Grigorov  apache.org> writes:

> 
> Please create a minimal application (quickstart) and attach it to Jira
> ticket.
> 
> On Fri, Sep 10, 2010 at 2:45 PM, Predrag Spasojevic <
> predrag.spasojevic  gmail.com> wrote:
> 
> > I have the same problem with AjaxButton, wicket 1.4.11 and FireFox 3.6.x.
> > It
> > doesn't work. I did some testing and it works for wicket 1.4.10.
> > Also there is some strange behavior with Opera 10.62. Sometimes Ajax works,
> > sometimes not, but it seems that problem existed in wicket versions before
> > 1.4.10.
> >

That's sound very strange. 
I've reproduced this behavior in a brand new Eclipse project with Wicket 1.4.11.
I will attach it to Jira as soon as possible.

I've also noticed that under Firefox AJAX post call returns the following error
message "Failed to load source for:
http://localhost:8080/WicketAjax/?wicket:interface=:2:form::IFormSubmitListener";
But under the other browsers (where it works correctly) AJAX calls for another
Wicket interface, which is ActivePageBehaviorListener:
"wicket:interface=:0:form:name::IActivePageBehaviorListener:0 ..."
 

I hope those informations will be useful.




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



Re: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-10 Thread Martin Grigorov
Please create a minimal application (quickstart) and attach it to Jira
ticket.

On Fri, Sep 10, 2010 at 2:45 PM, Predrag Spasojevic <
predrag.spasoje...@gmail.com> wrote:

> I have the same problem with AjaxButton, wicket 1.4.11 and FireFox 3.6.x.
> It
> doesn't work. I did some testing and it works for wicket 1.4.10.
> Also there is some strange behavior with Opera 10.62. Sometimes Ajax works,
> sometimes not, but it seems that problem existed in wicket versions before
> 1.4.10.
>
> 2010/9/10 MONZON Jose 
>
> > I don't understand what's going on. You say it works? I use 1.4.11. From
> > maven. It is impossible I'm using any other version because it's the
> > only wicket JAR I have in my libraries.
> >
> >
> > -Original Message-
> > From: Andrea Del Bene [mailto:andrea.on@libero.it]
> > Sent: Freitag, 10. September 2010 13:31
> > To: users@wicket.apache.org
> > Subject: Re: Wicket 1.4.11 seems to have Ajax support broken under
> > Firefox 3.6.x
> >
> > >
> > > Hi Jose,
> > >
> > > I can confirm this bug. It works fine with Wicket version 1.4.8. I
> > will open a
> > > bug on Apache JIRA.
> > >
> >
> > Sh**! Sorry, but know it seems to work also version 1.4.11. What jars
> > have you
> > inserted in your classpath to run test code?
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
> >
> >  The EFG Mail Gateway made the following annotation 
> >
> > This message is for the addressee only and may contain confidential or
> > privileged information. You must delete and not use it if you are not
> > the intended recipient. It may not be secure or error-free. All e-mail
> > communications to and from the EFG Financial Products Group may be
> > monitored.
> > Processing of incoming e-mails cannot be guaranteed. Any views expressed
> > in this message are those of the individual sender. This message is for
> > information purposes only. All liability of the EFG Financial Products
> > Group
> > and its entities for any damages resulting from e-mail use is excluded.
> > US persons are kindly requested to read the important legal information
> > presented at following URL: http://www.efgfp.com. If you suspect that
> the
> > message may have been intercepted or amended, please call the sender.
> > Should you require any further information, please contact the Compliance
> > Manager on complia...@efgfp.com.
> > 
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
>
>
> --
> Pozdrav,
> Predrag Spasojevic
>


Re: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-10 Thread Predrag Spasojevic
I have the same problem with AjaxButton, wicket 1.4.11 and FireFox 3.6.x. It
doesn't work. I did some testing and it works for wicket 1.4.10.
Also there is some strange behavior with Opera 10.62. Sometimes Ajax works,
sometimes not, but it seems that problem existed in wicket versions before
1.4.10.

2010/9/10 MONZON Jose 

> I don't understand what's going on. You say it works? I use 1.4.11. From
> maven. It is impossible I'm using any other version because it's the
> only wicket JAR I have in my libraries.
>
>
> -Original Message-
> From: Andrea Del Bene [mailto:andrea.on@libero.it]
> Sent: Freitag, 10. September 2010 13:31
> To: users@wicket.apache.org
> Subject: Re: Wicket 1.4.11 seems to have Ajax support broken under
> Firefox 3.6.x
>
> >
> > Hi Jose,
> >
> > I can confirm this bug. It works fine with Wicket version 1.4.8. I
> will open a
> > bug on Apache JIRA.
> >
>
> Sh**! Sorry, but know it seems to work also version 1.4.11. What jars
> have you
> inserted in your classpath to run test code?
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
>
>  The EFG Mail Gateway made the following annotation 
>
> This message is for the addressee only and may contain confidential or
> privileged information. You must delete and not use it if you are not
> the intended recipient. It may not be secure or error-free. All e-mail
> communications to and from the EFG Financial Products Group may be
> monitored.
> Processing of incoming e-mails cannot be guaranteed. Any views expressed
> in this message are those of the individual sender. This message is for
> information purposes only. All liability of the EFG Financial Products
> Group
> and its entities for any damages resulting from e-mail use is excluded.
> US persons are kindly requested to read the important legal information
> presented at following URL: http://www.efgfp.com. If you suspect that the
> message may have been intercepted or amended, please call the sender.
> Should you require any further information, please contact the Compliance
> Manager on complia...@efgfp.com.
> 
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


-- 
Pozdrav,
Predrag Spasojevic


RE: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-10 Thread MONZON Jose
I don't understand what's going on. You say it works? I use 1.4.11. From
maven. It is impossible I'm using any other version because it's the
only wicket JAR I have in my libraries.


-Original Message-
From: Andrea Del Bene [mailto:andrea.on@libero.it] 
Sent: Freitag, 10. September 2010 13:31
To: users@wicket.apache.org
Subject: Re: Wicket 1.4.11 seems to have Ajax support broken under
Firefox 3.6.x

> 
> Hi Jose,
> 
> I can confirm this bug. It works fine with Wicket version 1.4.8. I
will open a
> bug on Apache JIRA.
>

Sh**! Sorry, but know it seems to work also version 1.4.11. What jars
have you
inserted in your classpath to run test code?


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



 The EFG Mail Gateway made the following annotation 

This message is for the addressee only and may contain confidential or
privileged information. You must delete and not use it if you are not
the intended recipient. It may not be secure or error-free. All e-mail
communications to and from the EFG Financial Products Group may be monitored.
Processing of incoming e-mails cannot be guaranteed. Any views expressed
in this message are those of the individual sender. This message is for
information purposes only. All liability of the EFG Financial Products Group
and its entities for any damages resulting from e-mail use is excluded.
US persons are kindly requested to read the important legal information
presented at following URL: http://www.efgfp.com. If you suspect that the
message may have been intercepted or amended, please call the sender.
Should you require any further information, please contact the Compliance
Manager on complia...@efgfp.com.


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



Re: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-10 Thread Andrea Del Bene
> 
> Hi Jose,
> 
> I can confirm this bug. It works fine with Wicket version 1.4.8. I will open a
> bug on Apache JIRA.
>

Sh**! Sorry, but know it seems to work also version 1.4.11. What jars have you
inserted in your classpath to run test code?


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



Re: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-10 Thread Andrea Del Bene
MONZON Jose  efgfp.com> writes:

> 
> Hi there!
> 
> I've been giving a Try to Wicket framework. But I have to admit that I'm
> starting to get crazy! Some help appreciated.
> 
> I'm using last Wicket distribution 1.4.11
> 
> And I'm trying to implement the Wicket Form (with ajax) example you can
> find here:
> http://wicketstuff.org/wicket14/nested/?wicket:bookmarkablePage=:org.apa
> che.wicket.examples.ajax.builtin.FormPage 
> 
> It just doesn't work for Firefox (chrome behaves correctly). The Ajax is
> ignored and a normal submit is perform (actually, it does the ajax
> first, it fails and then it does the normal submit). I have no way to
> check what is going on, because the server logs nothing and the Ajax
> debug layer is cleaned after the pages reloads.
> 
> 

Hi Jose,

I can confirm this bug. It works fine with Wicket version 1.4.8. I will open a
bug on Apache JIRA.
PS: I know it's quite frustrating finding an issue when you learn a new
framework but be patient and you'll find how useful Wicket is ;) 
  
bye bye.


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



Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-10 Thread MONZON Jose
Hi there!

 

I've been giving a Try to Wicket framework. But I have to admit that I'm
starting to get crazy! Some help appreciated.

 

I'm using last Wicket distribution 1.4.11

 

And I'm trying to implement the Wicket Form (with ajax) example you can
find here:
http://wicketstuff.org/wicket14/nested/?wicket:bookmarkablePage=:org.apa
che.wicket.examples.ajax.builtin.FormPage 

 

It just doesn't work for Firefox (chrome behaves correctly). The Ajax is
ignored and a normal submit is perform (actually, it does the ajax
first, it fails and then it does the normal submit). I have no way to
check what is going on, because the server logs nothing and the Ajax
debug layer is cleaned after the pages reloads.

 

 

I'm copying the example here for your convenience:

 

FormPanel.java

-

 

ublic class FormPanel extends WebPage {

private final Bean bean = new Bean();

 

/**

 * Constructor

 */

public FormPanel() {

// create feedback panel to show errors

final FeedbackPanel feedback = new FeedbackPanel("feedback");

feedback.setOutputMarkupId(true);

add(feedback);

 

// add form with markup id setter so it can be updated via ajax

Form form = new Form("form", new
CompoundPropertyModel(bean));

add(form);

form.setOutputMarkupId(true);

 

FormComponent fc;

 

// add form components to the form as usual

 

fc = new RequiredTextField("name");

fc.add(StringValidator.minimumLength(4));

 

form.add(fc);

 

fc = new RequiredTextField("email");

fc.add(EmailAddressValidator.getInstance());

 

form.add(fc);

 

// attach an ajax validation behavior to all form component's
onkeydown

// event and throttle it down to once per second

 

AjaxFormValidatingBehavior.addToAllFormComponents(form,
"onkeyup", Duration.ONE_SECOND);

 

// add a button that can be used to submit the form via ajax

form.add(new AjaxButton("ajax-button", form) {

@Override

protected void onSubmit(AjaxRequestTarget target, Form
form) {

// repaint the feedback panel so that it is hidden

target.addComponent(feedback);

}

 

@Override

protected void onError(AjaxRequestTarget target, Form
form) {

// repaint the feedback panel so errors are shown

target.addComponent(feedback);

}

});

}

 

/**

 * simple java bean.

 */

public static class Bean implements IClusterable {

private String name, email;

 

/**

 * Gets email.

 *

 * @return email

 */

public String getEmail() {

return email;

}

 

/**

 * Sets email.

 *

 * @param email email

 */

public void setEmail(String email) {

this.email = email;

}

 

/**

 * Gets name.

 *

 * @return name

 */

public String getName() {

return name;

}

 

/**

 * Sets name.

 *

 * @param name name

 */

public void setName(String name) {

this.name = name;

}

}

}

 

 

 

 

FormPanel.html

---

 

 



http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>

http://wicket.apache.org";>





event test







Start typing in the textfields and see the form being validated as you
type. Ajax requests are throttled down to once per second, so they will
not

overload the server.



 

[[ feedback ]]

 





















 

 

 

Could please anyone check?

 

Thank you.

 

 

 

 

 


 The EFG Mail Gateway made the following annotation 

This message is for the addressee only and may contain confidential or
privileged information. You must delete and not use it if you are not
the intended recipient. It may not be secure or error-free. All e-mail
communications to and from the EFG Financial Products Group may be monitored.
Processing of incoming e-mails cannot be guaranteed. Any views expressed
in this message are those of the individual sender. This message is for
information purposes only. All liability of the EFG Financial Products Group
and its entities for any damages resulting from e-mail use is excluded.
US persons are kindly requested to read the important legal information
presented at following URL: http://www.efgfp.com. If you suspect that the
message may have been intercepted or amended, please call the sender.
Should you require any further information, please contact the Compliance
Manager on complia...@efgfp.com.