ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

The first thing I would check is that your project stage is set to development in your web.xml:

<context-param>
<description>
A human readable string describing where this particular JSF application is
in the software development lifecycle.
Valid values are 'Development', 'UnitTest', 'SystemTest' and 'Production'.
Default is 'Production'.
This parameter is not available in JSF 1.x.
</description>
<param-name>javax.faces.PROJECT_STAGE</param-name>
<param-value>Development</param-value>
</context-param>

You could turn page 1 into a composite component and each time it's used pass in a different managed bean name referencing the same model class.

If you are going to use multiple managed bean names for the same class, you will have to register the managed beans with the different names in faces.config.xml (can't do it with annotations).

There is a different api for ICEfaces 2, but this should work for 1.8:


<script>
// called from query button on click event.
var fnShow = function() {
document.getElementById(progressPanel').style.visibility = 'visible';
};

// ice.onSendRecieve call back calls this on submit of form data.
function icesubmittest() {
// alert('ICEfaces submit....');
}

// ice.onSendRecieve call back calls this when receive/response.
function icereceivetest() {
// alert('ICEfaces receive....');
document.getElementById('progressPanel').style.visibility = 'hidden';
}

function showProcessingMessage() {
fnShow(source);
}

function init(){
Ice.onSendReceive('document:body',icesubmittest,icereceivetest);
}

</script>
</head>
<body onload="init();">

You do not need to add an editable boolean. In the RichDataGridExampleBean in the ee-composite-showcase two different RichDataGridBean's are constructed.

For the first, you could pass null in to the constructor for the editableRowProperty, for the second you would not set the editableRowProperty and in both cases, all records would be editable.

Implicit navigation does not require the file extension, remove the .xhtml

At this point, the images are not configurable, they are included in the composite-component jar.

I have used c:forEach successfully.

FYI, we have a component that performs this functionality in our Enterprise Component Library:

http://composite-component-showcase.icefaces.org/icefaces-enterprise-comps-showcase/showcase.iface

Selection Components -> State/Province Selector

It will depend on the implementation you are using.

With ICEfaces, the Direct-to-Dom rendering will happen automatically to send the DOM updates back to the browser. With Wicket, you have to implement the PushPanel method to update your application - take a look at the specific documentation.

I believe there is internationalization built in to the java Calendar and that is where those Strings are coming from.

At this point, there is no property for 24 hr mode, but that is something that could possibly be added in the future.

I would suggest implementing this with a PhaseListener instead of a servlet filter.

The source code for the composite components has .properties files for each of the supported languages. We use standard JSF internationalization techniques.

The currently supported languages are displayed in the showcase application, if anyone requires another language, it is a matter of supplying a .properties file with the translated Strings for that language.

The 24hr checkbox should more accurately be labelled "All Day", it is not meant to change to a 24 hour clock.

The source code for the composite components has .properties files for each of the supported languages. We use standard JSF internationalization techniques.

The currently supported languages are displayed in the showcase application, if anyone requires another language, it is a matter of supplying a .properties file with the translated Strings for that language.

The 24hr checkbox should more accurately be labelled "All Day", it is not meant to change to a 24 hour clock.

The source code for the composite components has .properties files for each of the supported languages. We use standard JSF internationalization techniques.

The currently supported languages are displayed in the showcase application, if anyone requires another language, it is a matter of supplying a .properties file with the translated Strings for that language.

The 24hr checkbox should more accurately be labelled "All Day", it is not meant to change to a 24 hour clock.

The commandbutton has an 'action' attribute. This attribute returns a String fed into the JSF navigation handler.

Create a navigation rule in your faces-config.xml that specifies the same page when it gets the String returned from your action. Most importantly, make sure this navigation rule specifies a redirect. This should result in browser fetching the url again.