StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>The <code><f:ajax></code> can only be attached to a <a href="http://docs.oracle.com/javaee/6/api/javax/faces/component/behavior/ClientBehaviorHolder.html" rel="nofollow noreferrer"><code>ClientBehaviorHolder</code></a> such as <code><h:inputText></code>. A plain HTML <code><div></code> isn't such one component. You basically need to have a HTML <code><input></code> element, not a <code><div></code> element. Even more, how would you otherwise set the submitted value in the bean?</p> <pre><code><cc:interface> ... <cc:clientBehavior name="customEvent" targets="input" event="valueChange" /> </cc:interface> <cc:implementation> ... <h:inputText id="input" value="#{cc.attrs.value}" /> <h:outputScript> jQuery("[id='#{cc.clientId}:input']").ColorPicker({ // ... }); </h:outputScript> </cc:implementation> </code></pre> <p><em>(please note that I fixed the jQuery selector as well; this way the JSF client ID separator <code>:</code> will be taken into account properly instead of malforming the CSS selector)</em></p> <hr> <p><strong>Unrelated</strong> to the concrete problem, your usage of <code><f:ajax onevent></code> is wrong. It should point to a function reference, it should not contain some function calls. The proper usage is</p> <pre><code><f:ajax ... onevent="functionName" /> ... <h:outputScript> function functionName(data) { alert("Event " + data.status + " raised"); } </h:outputScript> </code></pre> <h3>See also:</h3> <ul> <li><a href="https://stackoverflow.com/questions/11350769/ajax-call-in-jsf-2-0-myfaces-the-onevent-javascipt-function-in-the-ajax-tag-g/11351236#11351236">ajax call in jsf 2.0 (myfaces), the onevent Javascript function in the ajax tag gets called before the rendering is complete</a></li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload