[result] [vote] release tobago 1.0.9

72 hours are over now and the vote has passed. 5 binding +1 votes from: dennisbyrne mmarinschek matzew grantsmith tomsp 3 non-binding +1 votes from: lofwyr weber bommel Vote thread: http://mail-archives.apache.org/mod_mbox/myfaces-dev/200612.mbox/[EMAIL PROTECTED] I will create all

[jira] Created: (TOMAHAWK-830) s:selectManyPicklist doesn't show preselected values

s:selectManyPicklist doesn't show preselected values -- Key: TOMAHAWK-830 URL: http://issues.apache.org/jira/browse/TOMAHAWK-830 Project: MyFaces Tomahawk Issue Type: Bug

Re: IDEA: client-side state manager that restores majority of saved state from initial tree state

Seems like the subject nether become obsolete nor irrelevant from the beginning of 2006. I mean it is still important for may (including myself) and not yet resolved. IMHO the statefull nature of JSF is most obvious problem of this technology. I wonder if we can come up with some solution

Re: Reason behind jsf_sequence?

lightbulb, It doesn't sound like you are discussing JSF navigation here at all. Key point to note: by default, JSF navigates with server-side forwards. These *do not* result in the browser URL being updated. :) regards, Jeff Bischoff Kenneth L Kurz Associates, Inc. lightbulb432 wrote:

[jira] Commented: (TOMAHAWK-830) s:selectManyPicklist doesn't show preselected values

[ http://issues.apache.org/jira/browse/TOMAHAWK-830?page=comments#action_12460493 ] Jeff Bischoff commented on TOMAHAWK-830: Chintan, When using selectManyPicklist, the selectItems needs to contain *ALL* the possible selections. Then

Re: MyFaces 1.2 Update

Hi, maven-faces-plugin used for autogeneration in its current form is NOT sufficient to generate whole components (mainly tomahawk's ones) - there's no method to e. g. generate initial values for properties in component's code. What i miss most is possibility to use own implementations of

Re: IDEA: client-side state manager that restores majority of saved state from initial tree state

Yes, my idea was probably partially inspired by things I read over the last year so it's probably not all that original. Glad to see I'm on the right track. It does sound like creating an alternate StateManager (which is within the JSF Spec) can accomplish this when using Facelets. I might

[jira] Commented: (TOMAHAWK-826) Improve outputLabel component to have a different CSS class in case of an error

[ http://issues.apache.org/jira/browse/TOMAHAWK-826?page=comments#action_12460538 ] Alex Savitsky commented on TOMAHAWK-826: Ah, I see - I thought you're one of the project owners :). I'll try to find some time to create the necessary

[jira] Commented: (TOMAHAWK-826) Improve outputLabel component to have a different CSS class in case of an error

[ http://issues.apache.org/jira/browse/TOMAHAWK-826?page=comments#action_12460541 ] Mike Kienenberger commented on TOMAHAWK-826: Just a note that this is an open source project -- anyone who contributes is a project owner. The

Re: MyFaces 1.2 Update

Well, AFAIK all what you mention in your mail IS handled by the maven-faces-plugin (from the trinidad 1.2 branch). It is possible to set the initial values (this is done for some of the html basic renderkit components), I cannot check the code right now but you can define a initial-value tag in

[jira] Reopened: (TOBAGO-107) tc:page should use a reasonable default width+height and state

[ http://issues.apache.org/jira/browse/TOBAGO-107?page=all ] Bernd Bohmann reopened TOBAGO-107: -- Assignee: Bernd Bohmann (was: Udo Schnurpfeil) tc:page should use a reasonable default width+height and state