datatable, different cell attribures?

To build a table with a variable number of rows and cols I used a t:datatable with a t:columns child. This works pretty good. Is there a way to use different css-classes or attributes for an individual cell? If the value displayed in the cell exceeds a certain value I want to highlight this

RE: datatable, different cell attribures?

I don't think that there is any direct way you can change the column class for an individual cell without writing your own renderer. You can always have outputText elements in the cells which you can use either EL or a backing bean to set the styleClass. For example using EL h:column

Re: datatable, different cell attribures?

Well, actually there is one: you can use the style class of the t:columns with something similar to the thing pointed by Julian. Something like this: t:column styleClass=#{rowVal.cost 0.0? 'negValueStyle' : 'posValueStyle'} ... /t:column Cheers! Bruno On 6/25/06, Julian Ray [EMAIL PROTECTED]

Re: how i protect my jsf pages from direct access

even though i put it in directory it is not working in tomcat 5.0 ?xml version=1.0 encoding=UTF-8? web-app version=2.4 xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee

Tutorial on how to create a custom JSF components library

Hi there, I have just created a tutorial [1] on how to create your custom JSF components library. It uses the (not released yet) MyFaces JSF Components Archetype to generate the project structure and explains how to implement a new component, by analysing the example component that comes with

Re: datatable, different cell attribures?

That's great. It works perfect. Thanks. Bruno Aranda wrote: Well, actually there is one: you can use the style class of the t:columns with something similar to the thing pointed by Julian. Something like this: t:column styleClass=#{rowVal.cost 0.0? 'negValueStyle' : 'posValueStyle'} ...

Protecting pages from expired sessions

How does one prevent all the (method/variable not found) errors generated to STDERR, when a user leaves a page open (the session expires), and then the user comes back and trys to refresh the page or click on some action? John

RE: Protecting pages from expired sessions

Hi John, How about creating a filter which performs a redirect to a logon page if the session has expired. Here is some code which outlines the basic idea. You need to deal with pages such as logon and password retrieval pages (isAllowedPage() performs this function and figure out the

RE: managed properties

Good to know. Btw what are the semantics of using mixed-scope managed properties inside each other? Example: Backing bean A has request scope Backing bean B has application scope but contains a managed reference to A. What am I obtaining when retrieving B.a? Futhermore, in spring,

Re: managed properties

On 6/25/06, Dhananjay Prasanna [EMAIL PROTECTED] wrote: Good to know. Btw what are the semantics of using mixed-scope managed properties inside each other? Example: Backing bean A has request scope Backing bean B has application scope but contains a managed reference to A.

RE: Protecting pages from expired sessions

Thanks Julian, Will this approach protect from a user clicking on an action within anorphanedpage where the session has expired, or will it only function if the user does a refresh (reloading the page)? John From: Julian Ray [mailto:[EMAIL PROTECTED] Sent: Sunday, June 25, 2006 2:00

RE: managed properties

Thanks Craig. At the risk of straying from the subject a bit--I am curious about the JSF bean lifecycle management and why the current strategy was chosen. In the EJB lifecycle, the container manages a pool of scope-agnostic beans that are brought into session on use. The reason for

RE: Protecting pages from expired sessions

It should protect against any server-sode processing but not against client-side actions such as _javascript_ etc. From: John [mailto:[EMAIL PROTECTED] Sent: Sunday, June 25, 2006 8:42 PMTo: MyFaces DiscussionSubject: RE: Protecting pages from expired sessions Thanks Julian, Will this

Re: managed properties

On 6/25/06, Dhananjay Prasanna [EMAIL PROTECTED] wrote: Thanks Craig. At the risk of straying from the subject a bit--I am curious about the JSF bean lifecycle management and why the current strategy was chosen. In the EJB lifecycle, the container manages a pool of

RE: managed properties

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig McClanahan Sent: Monday, 26 June 2006 11:43 AM To: MyFaces Discussion Subject: Re: managed properties In JSF 1.2, which is part of Java EE 5, you get the benefits of resource injection from the

RE: [OT] JSF and JVM performance

From: Jesse Sightler [mailto:[EMAIL PROTECTED] Sent: Saturday, 24 June 2006 11:36 AM To: MyFaces Discussion Subject: Re: [OT] JSF and JVM performance How many times did you run your performance test? Were you timing the first run, or timing some runs after giving it some

Tobago sheet selections seem to repopulate SheetState after delete

Scenario: - Sheet with 12 rows of data - Select 7 rows - Call backing bean delete function which also calls SheetState.resetSelected() after deletion - 7 rows are gone - The front end (_javascript_?) still thinks 7 rows are selected (if there were 7 rows left, they would all show

[tobago]Expression: #{clientConfigController.locale}. Return value null

Hi, I got the following error message when I try to run a jsp page who include tobago tag : Expression: #{clientConfigController.locale}. Return value null Any idea of what I need ? Regards