Hm..ok i didn`t test the component with ajax4Jsf, maybe their special filter ist the problem.
The issue seems to me that the resources are not served. In the web.xml, does the filter come before other special filters? This is a requirement when using ajax4jsf with myfaces. regards, Gerald On 10/19/06, eXiyenaya <[EMAIL PROTECTED]> wrote:
I am using sandbox 1.1.4 snapshot and server side state saving. I think problem caused from me. Because i am also using ajax4jsf jar . When i removed it from my application s:inputsuggestAjax starts to work. thanks ... Umut On 10/19/06, Gerald Müllan <[EMAIL PROTECTED]> wrote: > Hi, > > which version of sandbox are you using? One of the last weeks? > > Apart from that, are you using client side state saving? > > Have not tested it against this requirement since the last refork, but > maybe the component is broken in this mode. > > cheers, > > Gerald > > On 10/19/06, eXiyenaya < [EMAIL PROTECTED]> wrote: > > Hi > > I am trying to use s:inputSuggestAjax component in my application. I am > > filling my list but i could not see my dropdown list on browser. > > There is no error only one warning. > > WARN [DefaultAddResource] MyFaces special javascript could not be retrieved > > from request-map. > > > > Do you have any idea. > > > > > > > -- > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces >
-- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
