On 9/15/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I tried to upgrade from myfaces 1.1.1 to myfaces 1.1.4 and tomahawk 1.1.5
(I use the archives from
http://people.apache.org/builds/myfaces/core-1.1.x/myfaces-core-1.1.4-r428254-SNAPSHOT-bin.zip)
and an uptodate tomahawk snapshot)

What is the recommended version of tomahawk?

This is what I'd recommend, although you can now get MyFaces Core
1.1.4 -- I think it's the same code, though.


Now I have some new problems in my application (an apllication which is
already in production usage since several months and works fine).


Problem with styling of h:column with rendered attribute usage
=============================================
I use a dataTable from Tomahawk and there is a t:column in the table
rendered only when a special codition is true.
I style the columns with the columnsClasses attribute of the dataTable.
This attribute is dynamically provided by a backing bean.
When the column rendered attribute is true the UI is o.k.
But when the column isn't rendered the column doesn't get the correct
css-class. (although the columnsClasses attribute has the correct string
value of the css classes of the columns)

The desired behavior worked perfectly in Version 1.1.1.

Sounds like a bug.   It'd be helpful if you gave a specific example
showing how it's broken, though.  It's a little vague.


08:36:34,765 ERROR [MyFacesResourceLoader] Unparsable lastModified :
@lastModified@

You can ignore this one.  It's a problem with the way our Maven build
works.  The error has been reduced to a warning in the latest code.

08:43:56,875 WARN  [ReducedHTMLParser] Invalid tag found: unexpected input
while looking for attr name or '/>' at line 551

This one is serious and you probably better figure out what's
malformed in your page code at line 551.

Reply via email to