[jira] Created: (TOMAHAWK-896) asts to HttpServletRequest-Objects
asts to HttpServletRequest-Objects -- Key: TOMAHAWK-896 URL: https://issues.apache.org/jira/browse/TOMAHAWK-896 Project: MyFaces Tomahawk Issue Type: Improvement Components: Portlet_Support Affects Versions: 1.1.5-SNAPSHOT Environment: JSR-168 Portlets Reporter: Stephan Strittmatter In many sources are casts to HttpServletRequest-Objects, which are not available in Portal-Environments. These should be replaced to be more JSR-168 conform. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TOMAHAWK-897) Dojo component code refactoring
Dojo component code refactoring --- Key: TOMAHAWK-897 URL: https://issues.apache.org/jira/browse/TOMAHAWK-897 Project: MyFaces Tomahawk Issue Type: Improvement Reporter: Werner Punz The structure of the dojo component code in the sandbox needs refactoring. A generic DojoInput and DojoOutput component has to be refactored out of the existing components, these should resemble the dojo internal dojoWidget class in its attributes all dojo derived components should be based upon it, and should in the long run follow the dojo inheritance hirarchy in the future. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TOBAGO-284) Spacing between separator and next item in menu is too large
Spacing between separator and next item in menu is too large Key: TOBAGO-284 URL: https://issues.apache.org/jira/browse/TOBAGO-284 Project: MyFaces Tobago Issue Type: Bug Components: Themes Environment: Firefox 2.0.0.1 Reporter: Carsten Dimmek Priority: Trivial Fix For: 1.0.10 Spacing between separator and next item in menu is too large -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TOBAGO-285) Missing bottom line in combobox
Missing bottom line in combobox --- Key: TOBAGO-285 URL: https://issues.apache.org/jira/browse/TOBAGO-285 Project: MyFaces Tobago Issue Type: Bug Environment: Firefox 2.0.0.1 Reporter: Carsten Dimmek Priority: Trivial Fix For: 1.0.10 Attachments: screenshot-1.jpg A Combobox doesn't render correctly in firefox. The bottom line is missing. This seems to be only a firefox problem. IE is ok. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[VOTE] MyFaces Core 1.1.5
Hi all, This is the official vote for MyFaces Core 1.1.5. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.maven v1.0.5 [1] 2. Maven artifact group org.apache.myfaces.shared v2.0.5 [1] 3. Maven artifact group org.apache.myfaces.core v1.1.5 [1] 4. MyFaces Core Assembly [2] 5. Proposed Release Announcement [3] [1] http://people.apache.org/builds/myfaces/m2-staging-repository/ [2] http://people.apache.org/builds/myfaces/core-1.1.5/ [3] http://wiki.apache.org/myfaces/CoreRelease115#releasenotes --Manfred
Re: [VOTE] MyFaces Core 1.1.5
+1 (binding) BTW, this was a lot of work! Good thing is: Once more I learned a lot about maven. ;-) See http://wiki.apache.org/myfaces/CoreRelease115#diary if you are interested. On the basis of my experiences I'm going to revise the Release Procedure and start a Release Cookbook in the next days. --Manfred On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote: Hi all, This is the official vote for MyFaces Core 1.1.5. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.maven v1.0.5 [1] 2. Maven artifact group org.apache.myfaces.shared v2.0.5 [1] 3. Maven artifact group org.apache.myfaces.core v1.1.5 [1] 4. MyFaces Core Assembly [2] 5. Proposed Release Announcement [3] [1] http://people.apache.org/builds/myfaces/m2-staging-repository/ [2] http://people.apache.org/builds/myfaces/core-1.1.5/ [3] http://wiki.apache.org/myfaces/CoreRelease115#releasenotes --Manfred
Re: [VOTE] MyFaces Core 1.1.5
+1 binding Manfred, I know. I am currently doing the same work for Trinidad's plugins :) -Matthias On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote: +1 (binding) BTW, this was a lot of work! Good thing is: Once more I learned a lot about maven. ;-) See http://wiki.apache.org/myfaces/CoreRelease115#diary if you are interested. On the basis of my experiences I'm going to revise the Release Procedure and start a Release Cookbook in the next days. --Manfred On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote: Hi all, This is the official vote for MyFaces Core 1.1.5. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.maven v1.0.5 [1] 2. Maven artifact group org.apache.myfaces.shared v2.0.5 [1] 3. Maven artifact group org.apache.myfaces.core v1.1.5 [1] 4. MyFaces Core Assembly [2] 5. Proposed Release Announcement [3] [1] http://people.apache.org/builds/myfaces/m2-staging-repository/ [2] http://people.apache.org/builds/myfaces/core-1.1.5/ [3] http://wiki.apache.org/myfaces/CoreRelease115#releasenotes --Manfred -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Re: [VOTE] MyFaces Core 1.1.5
cookbook sounds good. need also to document my last maven hacks :) On 2/14/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: +1 binding Manfred, I know. I am currently doing the same work for Trinidad's plugins :) -Matthias On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote: +1 (binding) BTW, this was a lot of work! Good thing is: Once more I learned a lot about maven. ;-) See http://wiki.apache.org/myfaces/CoreRelease115#diary if you are interested. On the basis of my experiences I'm going to revise the Release Procedure and start a Release Cookbook in the next days. --Manfred On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote: Hi all, This is the official vote for MyFaces Core 1.1.5. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.maven v1.0.5 [1] 2. Maven artifact group org.apache.myfaces.shared v2.0.5 [1] 3. Maven artifact group org.apache.myfaces.core v1.1.5 [1] 4. MyFaces Core Assembly [2] 5. Proposed Release Announcement [3] [1] http://people.apache.org/builds/myfaces/m2-staging-repository/ [2] http://people.apache.org/builds/myfaces/core-1.1.5/ [3] http://wiki.apache.org/myfaces/CoreRelease115#releasenotes --Manfred -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
[jira] Created: (MYFACES-1533) CLONE -Custom converter consequently ignored
CLONE -Custom converter consequently ignored
Key: MYFACES-1533
URL: https://issues.apache.org/jira/browse/MYFACES-1533
Project: MyFaces Core
Issue Type: Bug
Components: General
Affects Versions: 1.1.4, 1.1.5, 1.1.6-SNAPSHOT
Environment: MyFaces + Facelet + Ajax4JSF
Reporter: Paul Iov
The way how the custom converters are handled in current code is totally
incosistent!
This issue can be splited into two parts:
1. Initial rendering of component, which provides custom converter don't check
this, but just throws an exception: Expected submitted value of type ... for
Component:..., if the type of bound bean property dosn't match expected type.
(i.e. h:selectBooleanCheckbox can't be bound to a String property, even with a
custom converter, that converts a string value posted from client to
true/false, 1/0, yes/no or whatever, because this converter is just
not called at this stage.)
Usecase
in bean:
private String strBoolean = 1;
public String getStrBoolean() {
return strBoolean;
}
public void setStrBoolean(String strBoolean) {
this.strBoolean = strBoolean;
}
converter:
---
public class BooleanConverter implements Converter {
public Object getAsObject(FacesContext arg0,
UIComponent arg1,
String newValue) throws
ConverterException {
return newValue.equalsIgnoreCase(true) ? 1 : 0;
}
public String getAsString(FacesContext arg0,
UIComponent arg1,
Object myValue) throws
ConverterException {
return myValue.toString().equalsIgnoreCase(1) ? true :
false;
//what should we return here, to make the UIBoolean happy???
//checked/ ? on/ ? nothing works, because this method is
//just not called!
}
}
in xhtml:
h:selectBooleanCheckbox value=#{MyBean.strBoolean}
converter=MyBooleanConverter/
causes:
--
Expected submitted value of type Boolean for Component :...
Side note: if property in bean is initialized to null, all works great without
any warning and the initial state of component's value becomes false!
Well, t:inputCalendar implements own converter handling and it works great, if
some valid string is posted from client, but it's not possible to set initial
value of component in bean, i.e.
private String strDate = 01.01.2006;
The initial 'rendered' state of component is always an empty string.
2. The second one should be probably the JSF Specification issue, but somehow
is also converter related... AJAX compatybility. I've discovered some strange
behaviour by using ajaxSingle feature from A4J. If a component's value is not
present in request (ajaxSingle approach), it becomes null during 'Apply request
values' phase regardless of custom converter (which tries to catch this
situation in getAsObject() method). The warning There should always be a
submitted value... is correct, but why should the framework not try to let
custom converter deal with this situation, if it's provided?
regards,
paul
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TOBAGO-282) No horizontal scrollbar in tc:sheet
[ https://issues.apache.org/jira/browse/TOBAGO-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Schnurpfeil resolved TOBAGO-282. Resolution: Fixed Fix Version/s: 1.0.10 Please test it. No horizontal scrollbar in tc:sheet --- Key: TOBAGO-282 URL: https://issues.apache.org/jira/browse/TOBAGO-282 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.0.10 Environment: All Reporter: Helmut Swaczinna Assigned To: Udo Schnurpfeil Fix For: 1.0.10 I have a tc:sheet with a lot of columns, so not all can be displayed at once on the page. The sum of the pixel widths of the column is greater than the page width. Tobago sets all columns that don't fit on the page to width zero. So they never can be seen or resized. What I expect is a horizontal scrollbar for the sheet or the containing panel or cell. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-1532) Custom converter consequently ignored
[
https://issues.apache.org/jira/browse/MYFACES-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473081
]
Paul Iov commented on MYFACES-1532:
---
Sorry for cloning this issue as MYFACES-1533. Would someone close/delete this
one please?
Custom converter consequently ignored
-
Key: MYFACES-1532
URL: https://issues.apache.org/jira/browse/MYFACES-1532
Project: MyFaces Core
Issue Type: Bug
Components: General
Affects Versions: 1.1.4, 1.1.5-SNAPSHOT, 1.1.5, 1.1.6-SNAPSHOT
Environment: MyFaces + Facelet + Ajax4JSF
Reporter: Paul Iov
The way how the custom converters are handled in current code is totally
incosistent!
This issue can be splited into two parts:
1. Initial rendering of component, which provides custom converter don't
check this, but just throws an exception: Expected submitted value of type
... for Component:..., if the type of bound bean property dosn't match
expected type. (i.e. h:selectBooleanCheckbox can't be bound to a String
property, even with a custom converter, that converts a string value posted
from client to true/false, 1/0, yes/no or whatever, because this
converter is just not called at this stage.)
Usecase
in bean:
private String strBoolean = 1;
public String getStrBoolean() {
return strBoolean;
}
public void setStrBoolean(String strBoolean) {
this.strBoolean = strBoolean;
}
converter:
---
public class BooleanConverter implements Converter {
public Object getAsObject(FacesContext arg0,
UIComponent arg1,
String newValue) throws
ConverterException {
return newValue.equalsIgnoreCase(true) ? 1 : 0;
}
public String getAsString(FacesContext arg0,
UIComponent arg1,
Object myValue) throws
ConverterException {
return myValue.toString().equalsIgnoreCase(1) ? true :
false;
//what should we return here, to make the UIBoolean happy???
//checked/ ? on/ ? nothing works, because this method is
//just not called!
}
}
in xhtml:
h:selectBooleanCheckbox value=#{MyBean.strBoolean}
converter=MyBooleanConverter/
causes:
--
Expected submitted value of type Boolean for Component :...
Side note: if property in bean is initialized to null, all works great
without any warning and the initial state of component's value becomes false!
Well, t:inputCalendar implements own converter handling and it works great,
if some valid string is posted from client, but it's not possible to set
initial value of component in bean, i.e.
private String strDate = 01.01.2006;
The initial 'rendered' state of component is always an empty string.
2. The second one should be probably the JSF Specification issue, but somehow
is also converter related... AJAX compatybility. I've discovered some strange
behaviour by using ajaxSingle feature from A4J. If a component's value is not
present in request (ajaxSingle approach), it becomes null during 'Apply
request values' phase regardless of custom converter (which tries to catch
this situation in getAsObject() method). The warning There should always be
a submitted value... is correct, but why should the framework not try to let
custom converter deal with this situation, if it's provided?
regards,
paul
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [VOTE] MyFaces Core 1.1.5
+1 . Thanks for all the hard work, Bruno On 14/02/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: cookbook sounds good. need also to document my last maven hacks :) On 2/14/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: +1 binding Manfred, I know. I am currently doing the same work for Trinidad's plugins :) -Matthias On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote: +1 (binding) BTW, this was a lot of work! Good thing is: Once more I learned a lot about maven. ;-) See http://wiki.apache.org/myfaces/CoreRelease115#diary if you are interested. On the basis of my experiences I'm going to revise the Release Procedure and start a Release Cookbook in the next days. --Manfred On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote: Hi all, This is the official vote for MyFaces Core 1.1.5. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.maven v1.0.5 [1] 2. Maven artifact group org.apache.myfaces.shared v2.0.5 [1] 3. Maven artifact group org.apache.myfaces.core v1.1.5 [1] 4. MyFaces Core Assembly [2] 5. Proposed Release Announcement [3] [1] http://people.apache.org/builds/myfaces/m2-staging-repository/ [2] http://people.apache.org/builds/myfaces/core-1.1.5/ [3] http://wiki.apache.org/myfaces/CoreRelease115#releasenotes --Manfred -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Re: [VOTE] MyFaces Core 1.1.5
+1 (binding) Cool thing that we have a well documented release process now. Many thanks for all the work to get the release out. cheers, Gerald On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote: +1 (binding) BTW, this was a lot of work! Good thing is: Once more I learned a lot about maven. ;-) See http://wiki.apache.org/myfaces/CoreRelease115#diary if you are interested. On the basis of my experiences I'm going to revise the Release Procedure and start a Release Cookbook in the next days. --Manfred On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote: Hi all, This is the official vote for MyFaces Core 1.1.5. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.maven v1.0.5 [1] 2. Maven artifact group org.apache.myfaces.shared v2.0.5 [1] 3. Maven artifact group org.apache.myfaces.core v1.1.5 [1] 4. MyFaces Core Assembly [2] 5. Proposed Release Announcement [3] [1] http://people.apache.org/builds/myfaces/m2-staging-repository/ [2] http://people.apache.org/builds/myfaces/core-1.1.5/ [3] http://wiki.apache.org/myfaces/CoreRelease115#releasenotes --Manfred -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: [VOTE] MyFaces Core 1.1.5
one side note. For the future, we should add this plugin http://mojo.codehaus.org/rat-maven-plugin/ -Matthias On 2/14/07, Gerald Müllan [EMAIL PROTECTED] wrote: +1 (binding) Cool thing that we have a well documented release process now. Many thanks for all the work to get the release out. cheers, Gerald On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote: +1 (binding) BTW, this was a lot of work! Good thing is: Once more I learned a lot about maven. ;-) See http://wiki.apache.org/myfaces/CoreRelease115#diary if you are interested. On the basis of my experiences I'm going to revise the Release Procedure and start a Release Cookbook in the next days. --Manfred On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote: Hi all, This is the official vote for MyFaces Core 1.1.5. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.maven v1.0.5 [1] 2. Maven artifact group org.apache.myfaces.shared v2.0.5 [1] 3. Maven artifact group org.apache.myfaces.core v1.1.5 [1] 4. MyFaces Core Assembly [2] 5. Proposed Release Announcement [3] [1] http://people.apache.org/builds/myfaces/m2-staging-repository/ [2] http://people.apache.org/builds/myfaces/core-1.1.5/ [3] http://wiki.apache.org/myfaces/CoreRelease115#releasenotes --Manfred -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Re: [VOTE] MyFaces Core 1.1.5
Thanks Matze! Issue created: http://issues.apache.org/jira/browse/MYFACES-1534 --Manfred On 2/14/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: one side note. For the future, we should add this plugin http://mojo.codehaus.org/rat-maven-plugin/ -Matthias On 2/14/07, Gerald Müllan [EMAIL PROTECTED] wrote: +1 (binding) Cool thing that we have a well documented release process now. Many thanks for all the work to get the release out. cheers, Gerald On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote: +1 (binding) BTW, this was a lot of work! Good thing is: Once more I learned a lot about maven. ;-) See http://wiki.apache.org/myfaces/CoreRelease115#diary if you are interested. On the basis of my experiences I'm going to revise the Release Procedure and start a Release Cookbook in the next days. --Manfred On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote: Hi all, This is the official vote for MyFaces Core 1.1.5. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.maven v1.0.5 [1] 2. Maven artifact group org.apache.myfaces.shared v2.0.5 [1] 3. Maven artifact group org.apache.myfaces.core v1.1.5 [1] 4. MyFaces Core Assembly [2] 5. Proposed Release Announcement [3] [1] http://people.apache.org/builds/myfaces/m2-staging-repository/ [2] http://people.apache.org/builds/myfaces/core-1.1.5/ [3] http://wiki.apache.org/myfaces/CoreRelease115#releasenotes --Manfred -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
[jira] Created: (MYFACES-1534) Add rat-maven-plugin to the build process
Add rat-maven-plugin to the build process - Key: MYFACES-1534 URL: https://issues.apache.org/jira/browse/MYFACES-1534 Project: MyFaces Core Issue Type: Improvement Components: build process Affects Versions: 1.1.6-SNAPSHOT Reporter: Manfred Geiler Assigned To: Manfred Geiler http://mojo.codehaus.org/rat-maven-plugin/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] MyFaces Core 1.1.5
+1 (binding) Dennis Byrne On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote: Hi all, This is the official vote for MyFaces Core 1.1.5. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.maven v1.0.5 [1] 2. Maven artifact group org.apache.myfaces.shared v2.0.5 [1] 3. Maven artifact group org.apache.myfaces.core v1.1.5 [1] 4. MyFaces Core Assembly [2] 5. Proposed Release Announcement [3] [1] http://people.apache.org/builds/myfaces/m2-staging-repository/ [2] http://people.apache.org/builds/myfaces/core-1.1.5/ [3] http://wiki.apache.org/myfaces/CoreRelease115#releasenotes --Manfred -- Dennis Byrne
Re: [VOTE] MyFaces Core 1.1.5
Sorry, one important thing I forgot: The release artifacts already passed the TCK! (Thanks Thomas) --Manfred On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote: Hi all, This is the official vote for MyFaces Core 1.1.5. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.maven v1.0.5 [1] 2. Maven artifact group org.apache.myfaces.shared v2.0.5 [1] 3. Maven artifact group org.apache.myfaces.core v1.1.5 [1] 4. MyFaces Core Assembly [2] 5. Proposed Release Announcement [3] [1] http://people.apache.org/builds/myfaces/m2-staging-repository/ [2] http://people.apache.org/builds/myfaces/core-1.1.5/ [3] http://wiki.apache.org/myfaces/CoreRelease115#releasenotes --Manfred
Re: [VOTE] MyFaces Core 1.1.5
+1 binding On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote: Sorry, one important thing I forgot: The release artifacts already passed the TCK! (Thanks Thomas) --Manfred On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote: Hi all, This is the official vote for MyFaces Core 1.1.5. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.maven v1.0.5 [1] 2. Maven artifact group org.apache.myfaces.shared v2.0.5 [1] 3. Maven artifact group org.apache.myfaces.core v1.1.5 [1] 4. MyFaces Core Assembly [2] 5. Proposed Release Announcement [3] [1] http://people.apache.org/builds/myfaces/m2-staging-repository/ [2] http://people.apache.org/builds/myfaces/core-1.1.5/ [3] http://wiki.apache.org/myfaces/CoreRelease115#releasenotes --Manfred -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: [VOTE] MyFaces Core 1.1.5
Hi! +1 Hi all, This is the official vote for MyFaces Core 1.1.5. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.maven v1.0.5 [1] 2. Maven artifact group org.apache.myfaces.shared v2.0.5 [1] 3. Maven artifact group org.apache.myfaces.core v1.1.5 [1] 4. MyFaces Core Assembly [2] 5. Proposed Release Announcement [3] [1] http://people.apache.org/builds/myfaces/m2-staging-repository/ [2] http://people.apache.org/builds/myfaces/core-1.1.5/ [3] http://wiki.apache.org/myfaces/CoreRelease115#releasenotes --Manfred Ciao, Mario
Re: [VOTE] MyFaces Core 1.1.5
I don't vote since only pmc votes count but I'd want to thank everyone involved especially Manfred. Cagatay
Re: svn commit: r507121 - /myfaces/tomahawk/trunk/sandbox/core/src/main/java/org/apache/myfaces/custom/submitOnEvent/SubmitOnEventRenderer.java
This deep scan seems wrong to me. It could pose both an unnecessary
performance burden and potentially unexpected behaviour. The search
algorithm defined by the UIComponent findComponent method [1] should be
sufficient for specifying a target in any known naming container.
Consider this: A user attempts to reference an object in another naming
container, but makes a mistake in the path portion of the id. This
should cause the search to fail, but thanks to the deep scan, it finds
the desired component by the simple id. Everything appears to work. A
bit later, another user on the team adds a component to another naming
container with the same simple id. All of a sudden, the search is
finding the wrong component to submit - and a JIRA issue probably gets
opened if they can't figure it out.
If we really want to encourage this sort of lazy specification of for
attributes, then it needs to be both documented and consistent
throughout the project. My feeling is that findComponent() is sufficient.
[1 tiny] http://tinyurl.com/2k8yzn
[1 long]
http://java.sun.com/javaee/javaserverfaces/1.1_01/docs/api/javax/faces/component/UIComponent.html#findComponent(java.lang.String)
Regards,
Jeff Bischoff
Kenneth L Kurz Associates, Inc.
Martin Marinschek wrote:
Why does the normal findComponent method fail for you?
regards,
Martin
On 2/13/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: imario
Date: Tue Feb 13 09:58:27 2007
New Revision: 507121
URL: http://svn.apache.org/viewvc?view=revrev=507121
Log:
use an aggressive strategy (traverse the whole tree) to search a
component by id if the normal
uiComponent.findComponent failed. Is there a better way?
Modified:
myfaces/tomahawk/trunk/sandbox/core/src/main/java/org/apache/myfaces/custom/submitOnEvent/SubmitOnEventRenderer.java
Modified:
myfaces/tomahawk/trunk/sandbox/core/src/main/java/org/apache/myfaces/custom/submitOnEvent/SubmitOnEventRenderer.java
URL:
http://svn.apache.org/viewvc/myfaces/tomahawk/trunk/sandbox/core/src/main/java/org/apache/myfaces/custom/submitOnEvent/SubmitOnEventRenderer.java?view=diffrev=507121r1=507120r2=507121
==
---
myfaces/tomahawk/trunk/sandbox/core/src/main/java/org/apache/myfaces/custom/submitOnEvent/SubmitOnEventRenderer.java
(original)
+++
myfaces/tomahawk/trunk/sandbox/core/src/main/java/org/apache/myfaces/custom/submitOnEvent/SubmitOnEventRenderer.java
Tue Feb 13 09:58:27 2007
@@ -30,6 +30,7 @@
import javax.faces.component.UIInput;
import javax.faces.component.UICommand;
import java.io.IOException;
+import java.util.Iterator;
/**
* Attach an event handler to an input element or use a global event
handler to
@@ -74,7 +75,11 @@
}
forComponent = uiComponent.findComponent(forComponentId);
-if (forComponent == null)
+ if (forComponent == null)
+ {
+ forComponent =
findComponentAggressive(facesContext.getViewRoot(), forComponentId);
+ }
+ if (forComponent == null)
{
throw new IllegalArgumentException(SubmitOnEvent:
can't find 'for'-component ' + forComponentId + ');
}
@@ -119,4 +124,30 @@
out.writeText(js.toString(), null);
out.endElement(HTML.SCRIPT_ELEM);
}
+
+ /**
+* deep scan the tree and see if ANY naming container has a
component with the
+* given id
+*/
+ private UIComponent findComponentAggressive(UIComponent base,
String id)
+ {
+ if (id.equals(base.getId()))
+ {
+ return base;
+ }
+
+ Iterator iter = base.getFacetsAndChildren();
+ while (iter.hasNext())
+ {
+ UIComponent child = (UIComponent) iter.next();
+
+ UIComponent found =
findComponentAggressive(child, id);
+ if (found != null)
+ {
+ return found;
+ }
+ }
+
+ return null;
+ }
}
Re: [VOTE] MyFaces Core 1.1.5
well... no reason to not vote. Its a community effort and therefore every single member of the community is free to vote (or not ;)) Usually I use something like this: [ ] +1 (Binding) for PPMC members only [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. to make it more transparent On 2/14/07, Cagatay Civici [EMAIL PROTECTED] wrote: I don't vote since only pmc votes count but I'd want to thank everyone involved especially Manfred. Cagatay -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Re: [VOTE] MyFaces Core 1.1.5
[ ] +1 (Binding) for PPMC members only [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Ok, then +1:) Thanks for the info, Cagatay On 2/14/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: well... no reason to not vote. Its a community effort and therefore every single member of the community is free to vote (or not ;)) Usually I use something like this: [ ] +1 (Binding) for PPMC members only [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. to make it more transparent On 2/14/07, Cagatay Civici [EMAIL PROTECTED] wrote: I don't vote since only pmc votes count but I'd want to thank everyone involved especially Manfred. Cagatay -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Re: [VOTE] MyFaces Core 1.1.5
Every community member vote counts! Who is a MyFaces community member? Everybody interested in MyFaces, not only committers! PMC members have the right to veto (with a binding -1). That's the only difference. --Manfred On 2/14/07, Cagatay Civici [EMAIL PROTECTED] wrote: I don't vote since only pmc votes count but I'd want to thank everyone involved especially Manfred. Cagatay
Re: [VOTE] MyFaces Core 1.1.5
+1 I have seen alot of hard work done by you guys while participating in the mail lists. It is an interesting learning experience seeing how this is done. Thanks for the effort. Jay On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote: Every community member vote counts! Who is a MyFaces community member? Everybody interested in MyFaces, not only committers! PMC members have the right to veto (with a binding -1). That's the only difference. --Manfred On 2/14/07, Cagatay Civici [EMAIL PROTECTED] wrote: I don't vote since only pmc votes count but I'd want to thank everyone involved especially Manfred. Cagatay
Re: [VOTE] MyFaces Core 1.1.5
Well, in that case... +1 (non-binding) This looks to be the best MyFaces Core yet! Great job guys. Jeff Bischoff Kenneth L Kurz Associates, Inc. Manfred Geiler wrote: Every community member vote counts! Who is a MyFaces community member? Everybody interested in MyFaces, not only committers! PMC members have the right to veto (with a binding -1). That's the only difference. --Manfred On 2/14/07, Cagatay Civici [EMAIL PROTECTED] wrote: I don't vote since only pmc votes count but I'd want to thank everyone involved especially Manfred. Cagatay
Re: [VOTE] MyFaces Core 1.1.5
+1 Great work! Paul Spencer Manfred Geiler wrote: Hi all, This is the official vote for MyFaces Core 1.1.5. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.maven v1.0.5 [1] 2. Maven artifact group org.apache.myfaces.shared v2.0.5 [1] 3. Maven artifact group org.apache.myfaces.core v1.1.5 [1] 4. MyFaces Core Assembly [2] 5. Proposed Release Announcement [3] [1] http://people.apache.org/builds/myfaces/m2-staging-repository/ [2] http://people.apache.org/builds/myfaces/core-1.1.5/ [3] http://wiki.apache.org/myfaces/CoreRelease115#releasenotes --Manfred
[jira] Created: (TOMAHAWK-898) New tableSuggestAjax is ignoring multiple attribtues
New tableSuggestAjax is ignoring multiple attribtues Key: TOMAHAWK-898 URL: https://issues.apache.org/jira/browse/TOMAHAWK-898 Project: MyFaces Tomahawk Issue Type: Bug Components: New Component Affects Versions: 1.1.5-SNAPSHOT Reporter: Stefan Schuster Fix For: 1.1.5-SNAPSHOT The new version of the tableSuggestAjax changed the input field to be generated by dojo instead of the being rendered by the standard HtmlTextRendererBase. This caused multiple lost attributes like disabled or all the javascript handlers. The attached patch solves this by going one step back. The input field will be generated by the HtmlTextRendererBase again and then be injected into the dojo component. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TOMAHAWK-898) New tableSuggestAjax is ignoring multiple attribtues
[ https://issues.apache.org/jira/browse/TOMAHAWK-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Schuster updated TOMAHAWK-898: - Status: Patch Available (was: Open) New tableSuggestAjax is ignoring multiple attribtues Key: TOMAHAWK-898 URL: https://issues.apache.org/jira/browse/TOMAHAWK-898 Project: MyFaces Tomahawk Issue Type: Bug Components: New Component Affects Versions: 1.1.5-SNAPSHOT Reporter: Stefan Schuster Fix For: 1.1.5-SNAPSHOT Attachments: tableSuggestAjax.patch The new version of the tableSuggestAjax changed the input field to be generated by dojo instead of the being rendered by the standard HtmlTextRendererBase. This caused multiple lost attributes like disabled or all the javascript handlers. The attached patch solves this by going one step back. The input field will be generated by the HtmlTextRendererBase again and then be injected into the dojo component. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] MyFaces Core 1.1.5
+1 Bernd Manfred Geiler wrote: Hi all, This is the official vote for MyFaces Core 1.1.5. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.maven v1.0.5 [1] 2. Maven artifact group org.apache.myfaces.shared v2.0.5 [1] 3. Maven artifact group org.apache.myfaces.core v1.1.5 [1] 4. MyFaces Core Assembly [2] 5. Proposed Release Announcement [3] [1] http://people.apache.org/builds/myfaces/m2-staging-repository/ [2] http://people.apache.org/builds/myfaces/core-1.1.5/ [3] http://wiki.apache.org/myfaces/CoreRelease115#releasenotes --Manfred
RE: [VOTE] MyFaces Core 1.1.5
Hi. Looking at the release notes, I see: Release Notes - MyFaces Core - Version 1.1.5 ** Bug * [long listing of bugs] This phrasing is ambiguous. Are these bugs present in the Release, or bugs fixed in the Release? This might be obvious to developers, but release notes should be more friendly to end users who might otherwise be frightened away. Richard J. Barbalace -Original Message- From: Manfred Geiler [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 14, 2007 7:29 AM To: MyFaces Development Subject: [VOTE] MyFaces Core 1.1.5 Hi all, This is the official vote for MyFaces Core 1.1.5. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.maven v1.0.5 [1] 2. Maven artifact group org.apache.myfaces.shared v2.0.5 [1] 3. Maven artifact group org.apache.myfaces.core v1.1.5 [1] 4. MyFaces Core Assembly [2] 5. Proposed Release Announcement [3] [1] http://people.apache.org/builds/myfaces/m2-staging-repository/ [2] http://people.apache.org/builds/myfaces/core-1.1.5/ [3] http://wiki.apache.org/myfaces/CoreRelease115#releasenotes --Manfred The information transmitted in this electronic communication is intended only for the person or entity to whom it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this information in error, please contact the Compliance HelpLine at 800-856-1983 and properly dispose of this information.
Re: [VOTE] MyFaces Core 1.1.5
+1 (binding) Manfred, good job and thanks for documenting the process... :) -- Grant Smith
[jira] Commented: (TOMAHAWK-463) for attribute not rendered on radio buttons
[ https://issues.apache.org/jira/browse/TOMAHAWK-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473163 ] Skylar Sutton commented on TOMAHAWK-463: I agree. It is essential that labels utilize the for attribute for IE. This is a major complaint by our users whenever we use a SelectOneRadio tag, they are forced to click on the tiny radio button itself, and not the label. Perhaps a boolean switch could be built into the tag? for attribute not rendered on radio buttons --- Key: TOMAHAWK-463 URL: https://issues.apache.org/jira/browse/TOMAHAWK-463 Project: MyFaces Tomahawk Issue Type: Bug Components: selectOneRadio / radio Affects Versions: 1.1.2 Environment: n/a Reporter: Russell Loewen Assigned To: Grant Smith Priority: Minor SelectOneRadio doesn't render the for attribute on the label tag it creates beside the radio button. The net effect is that on Internet Explorer the user is not able to click on the label text to select the radio item. It's arguable that this is IE's problem for not supported the parent-child relationship between the label tag surrounding the radio button, but the for attribute is a clearer association anyhow. I believe that the following could fix the problem. org.apache.myfaces.shared_impl.renderkit.html.HtmlResponseWriterImpl.class after Line 163, insert: _writer.writeAttribute(HTML.FOR_ATTR, uiComponent.getClientId(facesContext), null); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] MyFaces Core 1.1.5
On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote: Every community member vote counts! Who is a MyFaces community member? Everybody interested in MyFaces, not only committers! Absolutely. PMC members have the right to veto (with a binding -1). That's the only difference. To clarify, PMC members can veto code modifications, but no one can actually veto a release. After three +1's from PMC members, it's up to the release manager. Of course if something serious is discovered, the release manager will generally stop the process. http://www.apache.org/foundation/voting.html#ReleaseVotes -- Wendy
Re: [VOTE] MyFaces Core 1.1.5
That's what JIRA automatically generates. But I see your point. Will change Bug to Fixed. Thanks. --Manfred On 2/14/07, Barbalace, Richard [EMAIL PROTECTED] wrote: Hi. Looking at the release notes, I see: Release Notes - MyFaces Core - Version 1.1.5 ** Bug * [long listing of bugs] This phrasing is ambiguous. Are these bugs present in the Release, or bugs fixed in the Release? This might be obvious to developers, but release notes should be more friendly to end users who might otherwise be frightened away. Richard J. Barbalace -Original Message- From: Manfred Geiler [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 14, 2007 7:29 AM To: MyFaces Development Subject: [VOTE] MyFaces Core 1.1.5 Hi all, This is the official vote for MyFaces Core 1.1.5. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.maven v1.0.5 [1] 2. Maven artifact group org.apache.myfaces.shared v2.0.5 [1] 3. Maven artifact group org.apache.myfaces.core v1.1.5 [1] 4. MyFaces Core Assembly [2] 5. Proposed Release Announcement [3] [1] http://people.apache.org/builds/myfaces/m2-staging-repository/ [2] http://people.apache.org/builds/myfaces/core-1.1.5/ [3] http://wiki.apache.org/myfaces/CoreRelease115#releasenotes --Manfred The information transmitted in this electronic communication is intended only for the person or entity to whom it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this information in error, please contact the Compliance HelpLine at 800-856-1983 and properly dispose of this information.
[OT] ping Martin Marinscheck
Hi Martin please contact me... your gmail-account today did not accept direct email sorry for the OT... Alexander Jesse
WAP components issue
Are there mature JSF WAP components in MyFaces or the other JSF implements? Where can I find them?
JSF and Ajax combine issue
Are there mature JSF and Ajax combine technology in MyFaces or the other JSF Implementations.
multimedia components issue
Are there multimedia components in MyFaces or the other implements of JSF? Such as Flash and video components.
Re: WAP components issue
Kevin, Your best bet on getting a discussion going on these questions is to ask them on users@myfaces.apache.org mailing list. Thanks, Dennis Byrne On 2/15/07, kevin wu [EMAIL PROTECTED] wrote: Are there mature JSF WAP components in MyFaces or the other JSF implements? Where can I find them? -- Dennis Byrne
Re: [jira] [VOTE] MyFaces Core 1.1.5
+1 Thanks! -- Michael Manfred Geiler-2 wrote: Hi all, This is the official vote for MyFaces Core 1.1.5. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.maven v1.0.5 [1] 2. Maven artifact group org.apache.myfaces.shared v2.0.5 [1] 3. Maven artifact group org.apache.myfaces.core v1.1.5 [1] 4. MyFaces Core Assembly [2] 5. Proposed Release Announcement [3] [1] http://people.apache.org/builds/myfaces/m2-staging-repository/ [2] http://people.apache.org/builds/myfaces/core-1.1.5/ [3] http://wiki.apache.org/myfaces/CoreRelease115#releasenotes --Manfred -- View this message in context: http://www.nabble.com/-VOTE--MyFaces-Core-1.1.5-tf3227021.html#a8978750 Sent from the My Faces - Dev mailing list archive at Nabble.com.
