Call Custom AppModule Method

Question

I would like to use an application module custom method to set <TD> and <TR> "class" attributes. The method requires as a parameter, one of the values in the current row of the view object. Is there a sample on the OTN website that does something similar to this that I can follow? I have searched this forum and have not been able to find anything.
Thanks,
Jeff

Answer 1

Shay,
Thanks for the information from Ronald Grant’s blog, I found it helpful but I am not convinced his is the best solution to my problem. In resolving my problem, I need to be careful not to mix the presentation and business logic tiers. I am trying to build a dashboard type application and the various rows of data in the table represent jobs. These jobs can have certain "issues" that may impact their completion date. Depending upon the severity level of these “issues”, I’d like to color the entire row or just individual cells. Grant used EL language constructs to dynamically set inlineStyle attributes. Specifically, he used a [CONDITION] ? [CHOICE1] : [CHOICE2] construct which in my case would be a bit cumbersome because having multiple severity levels (5+), I’d have to nest these statements. What I would like to do would be to separate the styling from the logic and create individual styles to represent various severity levels:
severity1 {   
background: Green;
color: Black;
severity2 {
background: Yellow;
color: Black;
severity3 {
background: Red;
color: Black;
Then based upon the severity level defined in a column of the view, I would like to set the style to be used like in this syntactically incorrect example:
<tr class=”severity#{row[‘severity’]}”>
<td> <c:out value="${Row['Sernr']}"/></td>
<td>more data</td>
</tr>
which would produce the html like this:
<tr class=”severity3”>
<td>5677AB</td>
<td>more data</td>
</tr>
Can I do something like this using JSTL? I was successful doing it in ADF Faces EL like this:
<af:outputText value="#{row. 'Sernr'}"
styleClass="severity#{row.severty}">
but the row visual properties in the browser did not change. I think it had something to do with the default stylesheet referenced in the page header:
adf/styles/cache/oracle-desktop-10_1_3_0_4-en-ie-6-windows-s.css
It seemed to me that it's visual properties were taking precedence over mine. Is there a way of making a copy of that stylesheet, storing it locally in the html_root directory and telling Faces to use it rather than the default? This solution would work for me also.
Am I way off in my logic trying to solve this problem? If so, is there pattern documented on the web for this type of problem? I need to get a prototype up and running quickly butI’ve been dogged by what seems to be a fairly benign problem to solve. I hope my explanation makes sense. Thanks in advance for any insight you may provide.