I totally agree. I have also started a release wiki page where I try to
collect the information about the legals we have been going through and
solved.
http://cwiki.apache.org/confluence/display/WICKET/Wicket+1.3.0+incubating+checkpoint+1
Frank
On 3/15/07, Igor Vaynberg [EMAIL PROTECTED]
sure, i'll resolve it just after anyone confirm that the thing finally works :)
-Matej
On 3/14/07, Jean-Baptiste Quenot [EMAIL PROTECTED] wrote:
* [EMAIL PROTECTED]:
Author: knopp
Date: Wed Mar 14 09:45:14 2007
New Revision: 518211
URL: http://svn.apache.org/viewvc?view=revrev=518211
Hi,
as I see it
Wicket.Ajax.getTransport
sometimes returns XMLHttpRequest objects that are in readyState == 4
so they still might be processed by the stateChangeCallback.
Once stateChangeCallback reaches t.onreadystatechange =
Wicket.emptyFunction;
the freshly created XMLHttpRequest never
But the channel is only dead if the xmlhtprequest wasn't processed
properly. And that should never happen. If the xmlhttprequest is in
pol with readyState == 4, then new xmlhttprequest should be created.
Can you demonstrate the behavior you're describing on a quick start project?
-Matej
On
Without being 100% sure about what you're aiming for, this is what I'm
doing in one of my projects, which might help?
pom.xml:
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
outputDirectorytarget/release/outputDirectory
+1
/Gwyn
On 14/03/07, Al Maw [EMAIL PROTECTED] wrote:
There's been a lot of comment and discussion lately about the future
direction of Wicket, and the trunk/2.0 branch in particular.
We've done some hard thinking and we now have a roadmap for the future.
When What
Okay, i've fixed it. Thanks for pointing out the problem. Can you
please confirm that the fix solves it for you?
On 3/15/07, Martin Funk [EMAIL PROTECTED] wrote:
Here ist is:
https://issues.apache.org/jira/browse/WICKET-392
The chocking happens even on the same channel.
Martin
Matej
it does,
thnx,
Martin
Matej Knopp schrieb:
Okay, i've fixed it. Thanks for pointing out the problem. Can you
please confirm that the fix solves it for you?
On 3/15/07, Martin Funk [EMAIL PROTECTED] wrote:
Here ist is:
https://issues.apache.org/jira/browse/WICKET-392
The chocking happens
