Re: [Wicket-user] Wicket 2.0: Wicket.Ajax.AutoComplete is not a constructor

2006-09-07 Thread Stefan Lindner
Works well with the current wicket 2.0 trunk. The wicket-extensions-version that is downloadable from http://maven.sateh.com/wicket/wicket/ ist a little bit outdated. With the current trunk (shipping around compile errors in dropdownlist code) everything works well.

Re: [Wicket-user] Wicket 2.0: Wicket.Ajax.AutoComplete is not a constructor

2006-09-04 Thread Stefan Lindner
A little supplement: The other javascript resources are present: script type=text/javascript src=/Visiomedic/app/resources/wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax-debug-drag.js/script script type=text/javascript

Re: [Wicket-user] Wicket 2.0: Wicket.Ajax.AutoComplete is not a constructor

2006-09-04 Thread Igor Vaynberg
this is a known header contribution bug in 1.2.2 we are working on right now. you can either roll back to 1.2.1 or wait for 1.2.3 which should be coming in a week or so.-Igor On 9/4/06, Stefan Lindner [EMAIL PROTECTED] wrote: A little supplement: The other _javascript_ resources are present:

Re: [Wicket-user] Wicket 2.0: Wicket.Ajax.AutoComplete is not a constructor

2006-09-04 Thread Stefan Lindner
Dear Igor, it's a 2.0 error too. But thank you for your response! I hope it will be fixes in 2.0 soon. Stefan winmail.dat- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly

Re: [Wicket-user] Wicket 2.0: Wicket.Ajax.AutoComplete is not a constructor

2006-09-04 Thread Matej Knopp
How is this supposed to work in 1.2.1? I believe the header contribution code is the same. getImplementationId() is the one causing problems here. It should work ok in 2.0, as there is no getImplementationId() anymore. -Matej Igor Vaynberg wrote: this is a known header contribution bug in