I am playing Wicket now and came across this strange behavior.
I have a page with two LDM-based DropDownChoice (Country and State). The
Country DDC ajax-controls the State DDC. The Ajax works well.
Here is something I dont understand.
When the page is diplayed first time, both
After using CSS for layout things for two years my summary is:
Use tables for layout, CSS for the rest
It it simple, it works, and it doesn't break in each new version of IE
Am 18.03.2010 um 08:39 schrieb nino martinez wael:
CSS are the way to do stuff, but usually IE smashes it somehow. My
I checked in jwicket 0.5.2 into wicketstuff/trunk. This fiexes an Ajax
update problem for input fields with DatePicker with button as trigger.
Looks like Ajax redraws of wicket components with jQuery behavior is
always a problem.
What's the difference between jwicket and wiQuery?
Is it necessary to have 2 separate projects?
Just curious, because I'll soon be looking into better jQuery
On Mar 20, 2010, at 8:50 PM, Stefan Lindner wrote:
I checked in jwicket 0.5.2 into
take a look at both amd make your own decision. I can only speek for jWicket.
- At the moment it's main focus is drag/drop/resize. That's why I started this
- It trys to implement mostly all callback functions
- It trys to implement mostly all options
- It's part of
I'm out of town right now but when I get back to my computer I will
send you our ntlm page code. We have an AuthorizationStrategy that
redirects the user to NTLMPage and it handles all the header stuff
like you are talking about. If I don't send it to you Sunday then
email me to
I'm having problems with deployment/undeployment of Wicket apps on
Tomcat (and also JBoss, though I think it's related to the fact that it
embeds Tomcat). Basically, in both cases undeployment comes back with an
Exception, leaving the server in a dirty state and I have to restart
I have implemented a data table with cells having components as TextFields,
Currently,I have been able to achieve this by enclosing them inside panels.
But with large data set to be displayed I think it might consume lot of UI
resources or rendering time.
Is there any other
state's model is only loaded if the dropdown is rerendered (thats when
the model is needed)
see here http://wicketstuff.org/wicket14/ajax/choice
On Fri, Mar 19, 2010 at 11:21 PM, David Chang david_q_zh...@yahoo.com wrote:
I am playing Wicket now and came across this strange
I often have the same problem and symptom in my dev Tomcat, forcing me te
On Sat, Mar 20, 2010 at 5:06 PM, Alexandros Karypidis akary...@yahoo.grwrote:
I'm having problems with deployment/undeployment of Wicket apps on Tomcat
(and also JBoss, though I think it's related to
I wonder if this is a serialization problem:
the following request:
10.242.46.21 - - [20/Mar/2010:13:04:19 -0400] POST
HTTP/1.1 200 161
jWicket 0.5.4 is released in wicketstuff/trunk and
I recomend to upgrade to this versioin as it fixes a serious bug in
drag/drop/resize. If someone needs pre-built jar files please let me
Thanks for sharing!
Regarding the issue with drag-drop I just added  and . I locally
patched my jquery to get it working but this is something I do not like.
I'll keep you informed if someone provides an official fix.
interesting, wonder why the class would be unloaded *before* the
try this, add a field private PropertyClassResolver resolver=null; to
your application subclass, see if the field is enough to stop the
class from unloading.
On Sat, Mar 20, 2010 at 9:06 AM,
i doubt its the diskstore since you are the only one seeing this problem.
is this happening on multiple pages or just a particular one?
On Sat, Mar 20, 2010 at 10:34 AM, Nikita Tovstoles
I wonder if this is a serialization problem:
View this message in context:
Sent from the Wicket - User mailing list archive at Nabble.com.
OK, here's what I can surmise thus far:
- Only 'wicket:interface' JS requests - from 'onchange' Ajax validator or
from a SubmitLink-initiated form submission trigger the exception
- the form being submitted or validated is in a couple of pages but *never
What about using the @StatelessComponent (moving it from devutils into
wicket) as an indicator, that pages are intended to be stateless (_must_
be stateless)? Or introduce a new annotation @StatelessPage?
When a page that is intented to be stateless turns to be stateful, it's
always an issue
I may have found something - but first another question: under which
conditions would an ajax wicket:interface request omit a 'version'? (I see
request processor then assumes that the version is 0).
I may have found a race condition:
- check out
Forgive me about this meaningless subject, but I cannot think of a better one.
I have been learning Wicket through the WIA book. I just found out something
interesting to me. Not sure it is a bug, design, or something I did wrong.
I have a page with three Wicket elements:
1. Locale selector
Mail list logo