Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to get JSF composite components to work in WebView
    primarykey
    data
    text
    <p>I have JSF 2.1 web application with Spring and Hibernate. I need to create an Android vesion of that web application. I did it with help of WebView. Everything is OK. Enabling JavaScript and navigating web page history. However, JSF composite components are not working. They work fine in regular browsers.</p> <p>How to get JSF composite components to work in Android application using WebView?</p> <p><strong>EDIT</strong> : I use composite component in many places in my application for example I had one component for see more "list items with see more link" </p> <p>here's the code for the component</p> <p></p> <pre><code>&lt;!-- INTERFACE --&gt; &lt;cc:interface&gt; &lt;cc:attribute name="from" required="true"/&gt; &lt;cc:attribute name="to" required="true" shortDescription="First time limit before clicking see more link"/&gt; &lt;cc:attribute name="moreSize" required="true" shortDescription="Limit when clicking see more link"/&gt; &lt;cc:attribute name="totalCount" required="false" shortDescription="Total counts that helps is displaying see more link or not"/&gt; &lt;/cc:interface&gt; &lt;!-- IMPLEMENTATION --&gt; &lt;cc:implementation&gt; &lt;div class="SeeMore" from="#{cc.attrs.from}" to="#{cc.attrs.to}" moresize="#{cc.attrs.moreSize}" totalcount="#{cc.attrs.totalCount}"&gt;&lt;/div&gt; &lt;/cc:implementation&gt; </code></pre> <p></p> <p>and I used it by </p> <pre><code>&lt;core:seeMore moreSize="10" totalcount="20" from="0" to="10"/&gt; </code></pre> <p>when I view any page that had core:seeMore using android webView it doesn't list anything at all.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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