voyent
Messages posted by: philip.breau  XML
Profile for philip.breau -> Messages posted by philip.breau [2745] Go to Page: Previous  1, 2, 3 , 4, 5 ... 181, 182, 183 Next 
Author Message
I can't reproduce on Tomcat 7.0.42 with the 3.3 trunk (Mojarra 2.1.21). What version of Mojarra are you using? When exactly do you get the error?

Philip
Hi,
I can't reproduce the issue, but I did notice that your URLs are different. Here's mine:

http://localhost:8080/showcase/faces/javax.faces.resource/richtextentry/ckeditor/skins/kama/editor.css?ln=icefaces.ace&v=3_4_0_130812

and yours:

http://localhost:8080/syho/faces/javax.faces.resource/richtextentry/ckeditor/skins/kama/editor.css?t=B1GG4Z6

For some reason yours is missing the library name and version parameters. Try adding those to a manual request in your browser and see if you get the resource. Are you adding any sort of filter that might be stripping those?

Thanks,
Philip
Hi,
Could be an old version of JSF. Double check the server logs to see which version of Mojarra is loading. Make sure that you have the javax.faces.jar from the ICEfaces 3.3 bundle included in your web app lib dir.

Philip
We have a tutorial on how to use a dynamic menu bar.

http://www.icesoft.org/wiki/display/ICE/Dynamic+Menu+Tutorial

Hi,
I think you were seeing this because, as a general rule, IE compatibility modes always override doctypes. The X-UA-Compatible meta tag, if it's placed in head region, has to come before any content to have any effect. Unfortunately JSF usually doesn't respect the tag ordering in the head region, so sometimes manually placed meta tags, like this, become useless as JSF may render them after other content in the head, such as css and javascript. You might also want to include 'chrome=1' to 'edge' to include the Chrome Frame for IE ("IE=edge,chrome=1").

Philip
Glassfish normally bundles mojarra be default as it's the baseline Java EE implementation. You should just be able to include the jsf version you want in your web lib. Or you can update the server libs:

https://wikis.oracle.com/display/GlassFish/JavaServerFacesRI#JavaServerFacesRI-HowdoIupdatetheJSFimplementationintheJavaEESDK%28orglassfish%29withthemostrecentversion%3F
Hi,
Sorry that you ran into some bumps there. We'll try to smooth out that tutorial. As an example, just take the following page. You can just nest the singleSubmit like so:

Code:
 <?xml version='1.0' encoding='UTF-8' ?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml"
     xmlns:ui="http://java.sun.com/jsf/facelets"
     xmlns:f="http://java.sun.com/jsf/core"
     xmlns:h="http://java.sun.com/jsf/html"
     xmlns:icecore="http://www.icefaces.org/icefaces/core"
         xmlns:ace="http://www.icefaces.org/icefaces/components"
         xmlns:ice="http://www.icesoft.com/icefaces/component"
     >
     <h:head>
         <title>ICEfaces 3</title>
         <ice:outputStyle href="./xmlhttp/css/rime/rime.css" />
     </h:head>
     <h:body>
        <h:form id="iceForm">
            <icecore:singleSubmit submitOnBlur="true"/>
 
        </h:form>
     </h:body>
 </html>
 
Hi,
Yes, check out the migration guide.

Philip
Glad it's working for you. You can also use the royale and xp themes for the ice components.

./xmlhttp/css/royale/royale.css
./xmlhttp/css/xp/xp.css

Are you including the ICE stylesheet in your page?

Code:
 <?xml version='1.0' encoding='UTF-8' ?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml"
     xmlns:ui="http://java.sun.com/jsf/facelets"
     xmlns:f="http://java.sun.com/jsf/core"
     xmlns:h="http://java.sun.com/jsf/html"
     xmlns:icecore="http://www.icefaces.org/icefaces/core"
         xmlns:ace="http://www.icefaces.org/icefaces/components"
         xmlns:ice="http://www.icesoft.com/icefaces/component"
     >
     <h:head>
         <title>ICEfaces 3</title>
         <ice:outputStyle href="./xmlhttp/css/rime/rime.css" />
     </h:head>
     <h:body>
        <h:form id="iceForm">
         <ice:panelDivider dividerPosition="30">
             <f:facet name="first">Left</f:facet>
             <f:facet name="second">Right</f:facet>
         </ice:panelDivider>
        </h:form>
     </h:body>
 </html>
 
Yes, you'll just bind the 'for' attribute to the id of the panelSeries. There are examples in the showcase:

Code:
 <ice:panelSeries id="panelSeries" value="#{bean.items}" var="item">
    ....
 </ice:panelSeries>
 <ice:dataPaginator for="panelSeries">...
 
I haven't tested this inside a dataTable, but this works ok for me. The valueChangeListener only fires once for blur or the enter key:

Code:
 <h:inputText value="#{bean.value}" valueChangeListener="#{bean.valueChangeListener}">
     <f:ajax event="blur"/>
     <f:ajax event="keypress" onevent="if(event.keyCode == 13){ return true; } else return false;"/>
 </h:inputText>
 
Sounds like you're mixing jars from different versions. Make sure all your ICEfaces jars are the same version. The EE components work fine on 2 and 3, but there's a differently named jar (icefaces-ee-composite.jar).

Philip
Hi,
This might be due to ICE-8970. Try out 3.3 to see if that helps.
I haven't tested this recently, but in the past I've been able to use an ice:dataPaginator with an ice:panelSeries. The dataPaginator should be able to be bound to any UIData component.
 
Profile for philip.breau -> Messages posted by philip.breau [2745] Go to Page: Previous  1, 2, 3 , 4, 5 ... 181, 182, 183 Next 
Go to:   
Powered by JForum 2.1.7ice © JForum Team