The wicket-scriptaculous sample throws the following exception due to a
AbstractAutocompleteBehavior.js that is not present in the
wicket-scriptaculous.
I have svn the last version known. I don't know I'll try with the user list.
WicketMessage: Exception in rendering component: [MarkupContainer [Component
id = -header, page =
test.wicket.autocomplete.pages.ScriptaculousAutocomplete, path = 0:-
header.HtmlHeaderContainer, isVisible = true, isVersioned = true]]
Root cause:
java.lang.IllegalArgumentException: resource
AbstractAutocompleteBehavior.jsnot found for scope class
org.wicketstuff.scriptaculous.autocomplete.AbstractAutocompleteBehavior(path =
org/wicketstuff/scriptaculous/autocomplete/AbstractAutocompleteBehavior.js)
at org.apache.wicket.util.template.PackagedTextTemplate.<init>(
PackagedTextTemplate.java:167)
at org.apache.wicket.util.template.PackagedTextTemplate.<init>(
PackagedTextTemplate.java:135)
at org.apache.wicket.util.template.PackagedTextTemplate.<init>(
PackagedTextTemplate.java:118)
On 7/16/07, Ryan Sonnek <[EMAIL PROTECTED]> wrote:
I'd be interested to know if you had any issues using the
wicket-scriptaculous autocomplete component?
On 7/16/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
>
> On 7/16/07, Francisco Diaz Trepat - gmail <
[EMAIL PROTECTED]>
> wrote:
> >
> > I think a new form of autocomplete is needed. One that could better
> > abstract
> > scenarios in which user don't want to use the UL LI elements.
> >
> > I plan in developing one, if the boss approves, and wanted to know if
I
> > can
> > send it to some of you so you 'll review it and see if I can
contribute
> > some
> > to the cause... ;-)
>
>
> create a jira and attach a patch
> preferably what you do is hack up the existing one instead of starting
> from
> scratch.
>
> -igor
>
>
> f(t)
> >
>
