Hi all,
I am making an autocomplete component based on jquery-autocomplete.
I have currently implemented the data source using a stateless web page
which writes the json response.
What I don't like about this is that it is a separate file/class from my
autocomplete component. But I like that
Has anyone ever encountered this error?
It confuses me because:
1. It doesn't happen often, but happens a few times a day
2. Only happens on production
3. Pretty much all functionality work fine when tested manually
What's weird is the class name is lowercased, i.e.
Hi,
I suggest you to use a resource instead of an adapted stateless page.
Wicketstuff has a module with special Wicket resources to implement REST
api:
https://github.com/wicketstuff/core/tree/master/jdk-1.7-parent/wicketstuff-restannotations-parent.
Here you can find resources that already
There are more filters, besides wicket filter, on the filter chain. Did you
check those?
On 13 Dec 2014 18:12, Hendy Irawan he...@soluvas.com wrote:
Has anyone ever encountered this error?
It confuses me because:
1. It doesn't happen often, but happens a few times a day
2. Only happens on
I wonder how another filter could alter the behavior for this issue..
The call fails at
org.apache.wicket.core.util.lang.WicketObjects.resolveClass(WicketObjects.java:72),
surely the class name to be resolved is solely at Wicket's control?
On Sun, Dec 14, 2014, 01:18 Ernesto Reinaldo Barreiro-4
Hi,
The class name comes from the url, e.g.
/wicket/resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/res/js/wicket-ajax-jquery.js
Something changes the characters to be lower case.
It could be any of the filters but it could be the browser/user too.
Martin Grigorov
Wicket Training and
Hi,
There are few very good integrations between Wicket and JQuery UI.
Check https://github.com/sebfz1/wicket-jquery-ui and
https://github.com/WiQuery/wiquery
Both of them provide autocomplete component.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Dec
Thank you both for your answers.
I have reasons to roll my own autocomplete component. But I did take a look
at the way wiqiery and wicket-jquery are serving the choices.
As far as I can tell neither is using a stateless/lightweight way for
serving the choices. Both serve them with a request to
Hello,
Your issue seems to be related to css and not to Wicket itself.
From the css spec for position: fixed :
The box's position is calculated according to the 'absolute' model, but
in addition, the box is fixed with respect to some reference. [...] the
box is fixed with respect to the
