scottbentley

I had the same problem you did, thought I'd post my solution even if it's too late to help you. In the Pattern Expression you should not be returning a pattern, but rather a string from which a pattern will be made. For example, in my report I wanted numbers formatted as "#,##0.00;(#,##0.00)" but when the field label was "Net Invoiced" i wanted the output to be bold. So, in Pattern Exp. I put: $F{label}.matches("Net Invoiced")? "<b>#,##0.00;(#,##0.00)</b>":"#,##0.00;(#,##0.00)" Hope that helps someone!

Seems this is never going to be fixed despite the obvious need.

It would be really really nice to see lists get some love. This same issue has been a thorn in Jasper's side since at least 2005 given that's the first time I reported it myself. The HTML Component unfortunately is not a viable alternative to enhancing the basic html support of the textfield as it renders an image that cannot break across pages.

I should note that when I create the HTML component I set the Scale Type to Real Height. Without this setting the contents gets scaled so it can fit on a page but the result is barely readable. Not to mention, any other scaling setting results in text sizes that vary with content size which is absolutely not ok on a report that needs all text to be rendered in fixed font size.