RE: [jira] Updated: (MYFACES-219) JSCookMenu as child of a form

One concern I see with this. Shouldn't the component try and dynamically find a UIForm component parent and use that instead of the user having to specify what form to use? I believe that is how things like HtmlCommandLink works when they are not inside a form (the render the dummy form if

[jira] Created: (MYFACES-245) Temporary directory for the build

Temporary directory for the build - Key: MYFACES-245 URL: http://issues.apache.org/jira/browse/MYFACES-245 Project: MyFaces Type: Improvement Environment: ALL Reporter: Pino Silvaggio Priority: Trivial The default temp dir

RE: MyFacesGenericPortlet behavior

Hi Sven, Thanks for the great feedback. The reason it is done that way is because section 11.1 of the JSF spec suggests that this is how JSF portlets should work. It may be inefficient, but as I understand the spec it is definitely not wrong. If we did a Restore View on render requests then

[jira] Commented: (MYFACES-230) Support UTF-8 encoded property files, allow caching of properties

[ http://issues.apache.org/jira/browse/MYFACES-230?page=comments#action_65691 ] Kalle Korhonen commented on MYFACES-230: The patch breaks characters represented with full 8-bits in Latin-1 character set for obvious reasons (while the actual

[jira] Commented: (MYFACES-243) ClientId not used, so JSCookMenu fires multiple actions in tables

[ http://issues.apache.org/jira/browse/MYFACES-243?page=comments#action_65694 ] sean schofield commented on MYFACES-243: Does this patch completely fix the problem then? ClientId not used, so JSCookMenu fires multiple actions in tables

[jira] Commented: (MYFACES-243) ClientId not used, so JSCookMenu fires multiple actions in tables

[ http://issues.apache.org/jira/browse/MYFACES-243?page=comments#action_65709 ] Neal Haggard commented on MYFACES-243: -- Yes, the patch solves the problem. ClientId not used, so JSCookMenu fires multiple actions in tables

JIRA maintenance

Manfred, If we're going to use the 1.0.10 version in JIRA here is what I suggest. Find any issue that is currently marked with that version and change to nightly (there shouldn't be many since you just added it.) Then edit the versions and rename nightly to 1.0.10. This way all of the issues

[jira] Closed: (MYFACES-243) ClientId not used, so JSCookMenu fires multiple actions in tables

[ http://issues.apache.org/jira/browse/MYFACES-243?page=all ] sean schofield closed MYFACES-243: -- Resolution: Fixed Fix Version: Nightly Build ClientId not used, so JSCookMenu fires multiple actions in tables

Urgent: We need to some JIRA housekeeping

IMO the JIRA database is getting a little out of hand. We have over 100 open issues. I am sure there are some duplicates and some issues reported that will ultimately be resolved as WON'T FIX but its getting to be a large list. There are several issues where users have been kind enough to

[jira] Reopened: (MYFACES-243) ClientId not used, so JSCookMenu fires multiple actions in tables

[ http://issues.apache.org/jira/browse/MYFACES-243?page=all ] Grant Smith reopened MYFACES-243: - This patch breaks JSCookMenu navigation completely. I had to reverse it to get the faces-examples to work properly again. Unfortunately I don't have the

RE: Sandbox

+1. Kalle -Original Message- From: Sean Schofield [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 18, 2005 3:11 PM To: MyFaces Development Subject: Re: Sandbox I propose that we go ahead and create a sandbox area and at a minimum it can be used by committers (such as myself)

Re: myfaces-examples: problem with navigation in nightly build

Found the problem. - MYFACES-243's patch. I reversed it locally and navigation works again. I reopened the JIRA, but unfortunately dont have the time right now to delve into this. Neal ?! :-) Grant Smith wrote: I just deployed the myfaces-examples from the latest SVN version, and it appears