[Vote] Sponsoring Entity of RCF (was Re: [Proposal] RCF, a rich component library for JSF)
Hello, last week I sent out the proposal for the donation of RCF from Oracle to the ASF. The proposal mentioned, that we need to do a vote on the MyFaces PMC of being the Sponsoring Entity of that *podling*. After finding the sponsor, we move this *discussion* to the incubator general list. The proposal has been posted to the MyFaces wiki: http://wiki.apache.org/myfaces/RCF_Proposal Please vote here, on the MyFaces DEV mailing list. Thanks, Matthias On 3/14/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: Hi, This is a proposal to donate a rich component library for JSF to the Apache Software Foundation. The live version of the proposal is available at http://wiki.apache.org/myfaces/RCF_Proposal. Omar Tazi (Chief Open Source Evangelist at Oracle) and I have been working on that proposal over the past days. Comments and questions are welcome. There is also a vacant place for two more mentors. Once people are satisfied with the proposal I will first call a vote on the MyFaces PMC to sponsor the proposal and Omar will resend this proposal to the General Incubator List. PS. Based on quick Google and USPTO searches there doesn't seem to be anything that would cause trouble with the RCF name. Thx, Matthias Wessendorf RCF, a rich component library for JSF Abstract RCF is a rich (Ajax-style) component set for the JavaServer Faces(tm) 1.2 technology. . Proposal RCF is an Ajax-based component library for the JavaServer Faces technology. RCF comes with very high quality components, and skinning (CSS-based) capabilities. RCF features include: file upload support, client-side conversion and validation, a complete Ajax-integration, data tables, hierarchical tables, color/date pickers, menu tabs/buttons, wizards, popups, toolbars, toolboxes, internationalization and accessibility. This project starts with more than 100 components which have already been documented and thoroughly tested. RCF stands for Rich Client Framework and it means that web applications, using this component set look very similar to a real, native desktop application. The name for this project can be a subject to change. RCF depends on some artifacts, provided by the Apache Trinidad project, such as framework features or Apache Maven plug-ins. Background The development of RCF started in 2005 at Oracle Corporation. With the advent of Ajax and the higher requirements for a very rich user experience, Oracle decided to implement a rich/Ajax-style JSF component set. The goal was to advance the already existing ADF Faces product, donated to the ASF in early 2006 (Apache Trinidad). When the development of RCF started, there wasn't any JSF component set that provides similar richness to the user. The RCF components run on any JSF 1.2 compliant implementation. RCF is based on some internal features of the Apache Trinidad project. The JavaServer Faces technology is a very important technology for the RCF component set, since RCF requires JSF as its runtime environment. Oracle has a large commitment to both open source and open standards. This proposal illustrates Oracle's commitment to the success of the JSF standard and supporting the open source community by providing a rich component set under a liberal license, the Apache 2.0 license. Rationale The project is interested in moving to Apache for the following reasons: To provide Apache-licensed implementation of a full-blown Ajax-based JSF component set, to become better integrated with the MyFaces and Shale initiatives, and to build a strong vendor-neutral community that will outlast any one person's or company's participation. Initial Goals The initial goals of the proposed project are: * Viable community around the RCF code base * Active relationships and possible cooperation with related projects and communities, such as Apache MyFaces (and it's subprojects) or Apache Trinidad. Current Status == Meritocracy All the initial committers are familiar with the meritocracy principles of Apache, and have already worked on the various source code bases. Some of the initial committers also have experience, undergoing the Apache incubation process. We will follow the normal meritocracy rules also with other potential contributors. Community The Apache MyFaces project, the Apache Trinidad podling and the JavaServer Faces standard hold great promise. A fully Ajax-based set of user interface components will significantly accelerate their adoption. We strongly believe that RCF will gather significant momentum and enough developers to build a vibrant community of users and contributors. Core Developers Four of the initial committers are Oracle employees and all are committers on the Apache Trinidad podling. One of them is a committer at Apache MyFaces and Apache Shale. Four of the initial committers are committers on the Apache
Re: [Vote] Sponsoring Entity of RCF (was Re: [Proposal] RCF, a rich component library for JSF)
+1 for MyFaces being the sponsoring entity for RCF On 3/19/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: Hello, last week I sent out the proposal for the donation of RCF from Oracle to the ASF. The proposal mentioned, that we need to do a vote on the MyFaces PMC of being the Sponsoring Entity of that *podling*. After finding the sponsor, we move this *discussion* to the incubator general list. The proposal has been posted to the MyFaces wiki: http://wiki.apache.org/myfaces/RCF_Proposal Please vote here, on the MyFaces DEV mailing list. Thanks, Matthias
Re: [Vote] Sponsoring Entity of RCF (was Re: [Proposal] RCF, a rich component library for JSF)
Matthias Wessendorf schrieb: +1 for MyFaces being the sponsoring entity for RCF +1
Re: [Vote] Sponsoring Entity of RCF (was Re: [Proposal] RCF, a rich component library for JSF)
Matthias Wessendorf schrieb: +1 for MyFaces being the sponsoring entity for RCF +1 Ciao, Mario
Re: [Vote] Sponsoring Entity of RCF (was Re: [Proposal] RCF, a rich component library for JSF)
+1 (non-binding) Cagatay On 3/19/07, Mario Ivankovits [EMAIL PROTECTED] wrote: Matthias Wessendorf schrieb: +1 for MyFaces being the sponsoring entity for RCF +1 Ciao, Mario
Re: [Vote] Sponsoring Entity of RCF (was Re: [Proposal] RCF, a rich component library for JSF)
+1 On 3/19/07, Cagatay Civici [EMAIL PROTECTED] wrote: +1 (non-binding) Cagatay On 3/19/07, Mario Ivankovits [EMAIL PROTECTED] wrote: Matthias Wessendorf schrieb: +1 for MyFaces being the sponsoring entity for RCF +1 Ciao, Mario -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
JSF 1.2 Issues
Hy, most of the open JSF 1.2 Issues seams to be implemented already. I have taken a look to the following Issues: MYFACES-1221 MYFACES-1269 MYFACES-1226 MYFACES-1235 MYFACES-1381 Should i comment them that this issues seams to be implemented and some takes also a closer look to these, or should i set them to the resolved status? regards, Martin Haimberger
Re: JSF 1.2 Issues
Martin, please do a comment on each of them https://issues.apache.org/jira/browse/MYFACES-1269 That isn't complete, I added it only to abstract UIComponent, not UIData yet thx, M On 3/19/07, Martin Haimberger [EMAIL PROTECTED] wrote: Hy, most of the open JSF 1.2 Issues seams to be implemented already. I have taken a look to the following Issues: MYFACES-1221 MYFACES-1269 MYFACES-1226 MYFACES-1235 MYFACES-1381 Should i comment them that this issues seams to be implemented and some takes also a closer look to these, or should i set them to the resolved status? regards, Martin Haimberger -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Re: JSF 1.2 Issues
Hi, MYFACES-1235 is done for English locale. Cagatay On 3/19/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: Martin, please do a comment on each of them https://issues.apache.org/jira/browse/MYFACES-1269 That isn't complete, I added it only to abstract UIComponent, not UIData yet thx, M On 3/19/07, Martin Haimberger [EMAIL PROTECTED] wrote: Hy, most of the open JSF 1.2 Issues seams to be implemented already. I have taken a look to the following Issues: MYFACES-1221 MYFACES-1269 MYFACES-1226 MYFACES-1235 MYFACES-1381 Should i comment them that this issues seams to be implemented and some takes also a closer look to these, or should i set them to the resolved status? regards, Martin Haimberger -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
[jira] Commented: (MYFACES-1235) JSR-252 Issue #78: Added a more user-friendly default error message for UIInput update model.
[ https://issues.apache.org/jira/browse/MYFACES-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482072 ] Martin Haimberger commented on MYFACES-1235: done for English locale JSR-252 Issue #78: Added a more user-friendly default error message for UIInput update model. - Key: MYFACES-1235 URL: https://issues.apache.org/jira/browse/MYFACES-1235 Project: MyFaces Core Issue Type: Improvement Components: JSR-252 Reporter: Stan Silvert Assigned To: Martin Haimberger Added a more user-friendly default error message for UIInput update model. Please see Section 2.5.2.4 Localized Application Messages for more details. Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=78 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-1221) JSR-252 Issue #50: Allow an application to specify multiple render kits by introducing an optional renderKitId attribute on f:view.
[ https://issues.apache.org/jira/browse/MYFACES-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482073 ] Martin Haimberger commented on MYFACES-1221: it seams that this is implemented yet. Can anyone take also a closer look to this issue? regards, Martin Haimberger JSR-252 Issue #50: Allow an application to specify multiple render kits by introducing an optional renderKitId attribute on f:view. - Key: MYFACES-1221 URL: https://issues.apache.org/jira/browse/MYFACES-1221 Project: MyFaces Core Issue Type: New Feature Components: JSR-252 Reporter: Stan Silvert Allow an application to specify multiple render kits by introducing an optional renderKitId attribute on f:view. It is no longer required to write a customer ViewHandler to incorporate a different render kit. Please refer to Section 8.3 ResponseStateManager and Section 9.4.20 f:view for more details. Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=50 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MYFACES-1235) JSR-252 Issue #78: Added a more user-friendly default error message for UIInput update model.
[ https://issues.apache.org/jira/browse/MYFACES-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated MYFACES-1235: --- Status: Patch Available (was: Open) JSR-252 Issue #78: Added a more user-friendly default error message for UIInput update model. - Key: MYFACES-1235 URL: https://issues.apache.org/jira/browse/MYFACES-1235 Project: MyFaces Core Issue Type: Improvement Components: JSR-252 Reporter: Stan Silvert Assigned To: Martin Haimberger Added a more user-friendly default error message for UIInput update model. Please see Section 2.5.2.4 Localized Application Messages for more details. Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=78 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MYFACES-1235) JSR-252 Issue #78: Added a more user-friendly default error message for UIInput update model.
[ https://issues.apache.org/jira/browse/MYFACES-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated MYFACES-1235: --- Status: Open (was: Patch Available) JSR-252 Issue #78: Added a more user-friendly default error message for UIInput update model. - Key: MYFACES-1235 URL: https://issues.apache.org/jira/browse/MYFACES-1235 Project: MyFaces Core Issue Type: Improvement Components: JSR-252 Reporter: Stan Silvert Assigned To: Martin Haimberger Added a more user-friendly default error message for UIInput update model. Please see Section 2.5.2.4 Localized Application Messages for more details. Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=78 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-1381) JSR-252 Issue #303: Clarified the use of encodeChildren with no renderer: render not no-op
[ https://issues.apache.org/jira/browse/MYFACES-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482105 ] Martin Haimberger commented on MYFACES-1381: Regarding to the jsf 1.2 spezification section 3.1.12 there should nothing be done if not rendertype is set. The resolution of the corresponding jsf ri issue was set to later (jsf 2.0). I think this is no bug. JSR-252 Issue #303: Clarified the use of encodeChildren with no renderer: render not no-op -- Key: MYFACES-1381 URL: https://issues.apache.org/jira/browse/MYFACES-1381 Project: MyFaces Core Issue Type: Bug Components: JSR-252 Affects Versions: 1.2.0-SNAPSHOT Reporter: Mike Kienenberger Assigned To: Martin Haimberger JSR-252 Issue #303: Clarified the use of encodeChildren with no renderer: render not no-op https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=303 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MYFACES-1381) JSR-252 Issue #303: Clarified the use of encodeChildren with no renderer: render not no-op
[ https://issues.apache.org/jira/browse/MYFACES-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf resolved MYFACES-1381. - Resolution: Later Fix Version/s: 1.2.0-SNAPSHOT JSF EG targeted this as LATER. JSR-252 Issue #303: Clarified the use of encodeChildren with no renderer: render not no-op -- Key: MYFACES-1381 URL: https://issues.apache.org/jira/browse/MYFACES-1381 Project: MyFaces Core Issue Type: Bug Components: JSR-252 Affects Versions: 1.2.0-SNAPSHOT Reporter: Mike Kienenberger Assigned To: Martin Haimberger Fix For: 1.2.0-SNAPSHOT JSR-252 Issue #303: Clarified the use of encodeChildren with no renderer: render not no-op https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=303 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TOMAHAWK-936) TableSuggestAjax aborts page load in IE
TableSuggestAjax aborts page load in IE --- Key: TOMAHAWK-936 URL: https://issues.apache.org/jira/browse/TOMAHAWK-936 Project: MyFaces Tomahawk Issue Type: Bug Affects Versions: 1.1.5-SNAPSHOT Reporter: Stefan Schuster Fix For: 1.1.5-SNAPSHOT Every use of the tableSuggestComponent in a page aborts the page load in IE with an error message (even in the sandbox example pages). This happens due to a bug that the javascript gets rendered before the DIV it works with gets closed. The attached patch moves the DIV-close to the correct position. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TOMAHAWK-936) TableSuggestAjax aborts page load in IE
[ https://issues.apache.org/jira/browse/TOMAHAWK-936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Schuster updated TOMAHAWK-936: - Status: Patch Available (was: Open) TableSuggestAjax aborts page load in IE --- Key: TOMAHAWK-936 URL: https://issues.apache.org/jira/browse/TOMAHAWK-936 Project: MyFaces Tomahawk Issue Type: Bug Affects Versions: 1.1.5-SNAPSHOT Reporter: Stefan Schuster Fix For: 1.1.5-SNAPSHOT Attachments: TableSuggestAjax_IEPatch.patch Every use of the tableSuggestComponent in a page aborts the page load in IE with an error message (even in the sandbox example pages). This happens due to a bug that the javascript gets rendered before the DIV it works with gets closed. The attached patch moves the DIV-close to the correct position. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [Vote] Sponsoring Entity of RCF (was Re: [Proposal] RCF, a rich component library for JSF)
+1 On 3/19/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: Hello, last week I sent out the proposal for the donation of RCF from Oracle to the ASF. The proposal mentioned, that we need to do a vote on the MyFaces PMC of being the Sponsoring Entity of that *podling*. After finding the sponsor, we move this *discussion* to the incubator general list. The proposal has been posted to the MyFaces wiki: http://wiki.apache.org/myfaces/RCF_Proposal Please vote here, on the MyFaces DEV mailing list. Thanks, Matthias On 3/14/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: Hi, This is a proposal to donate a rich component library for JSF to the Apache Software Foundation. The live version of the proposal is available at http://wiki.apache.org/myfaces/RCF_Proposal. Omar Tazi (Chief Open Source Evangelist at Oracle) and I have been working on that proposal over the past days. Comments and questions are welcome. There is also a vacant place for two more mentors. Once people are satisfied with the proposal I will first call a vote on the MyFaces PMC to sponsor the proposal and Omar will resend this proposal to the General Incubator List. PS. Based on quick Google and USPTO searches there doesn't seem to be anything that would cause trouble with the RCF name. Thx, Matthias Wessendorf RCF, a rich component library for JSF Abstract RCF is a rich (Ajax-style) component set for the JavaServer Faces(tm) 1.2 technology. . Proposal RCF is an Ajax-based component library for the JavaServer Faces technology. RCF comes with very high quality components, and skinning (CSS-based) capabilities. RCF features include: file upload support, client-side conversion and validation, a complete Ajax-integration, data tables, hierarchical tables, color/date pickers, menu tabs/buttons, wizards, popups, toolbars, toolboxes, internationalization and accessibility. This project starts with more than 100 components which have already been documented and thoroughly tested. RCF stands for Rich Client Framework and it means that web applications, using this component set look very similar to a real, native desktop application. The name for this project can be a subject to change. RCF depends on some artifacts, provided by the Apache Trinidad project, such as framework features or Apache Maven plug-ins. Background The development of RCF started in 2005 at Oracle Corporation. With the advent of Ajax and the higher requirements for a very rich user experience, Oracle decided to implement a rich/Ajax-style JSF component set. The goal was to advance the already existing ADF Faces product, donated to the ASF in early 2006 (Apache Trinidad). When the development of RCF started, there wasn't any JSF component set that provides similar richness to the user. The RCF components run on any JSF 1.2 compliant implementation. RCF is based on some internal features of the Apache Trinidad project. The JavaServer Faces technology is a very important technology for the RCF component set, since RCF requires JSF as its runtime environment. Oracle has a large commitment to both open source and open standards. This proposal illustrates Oracle's commitment to the success of the JSF standard and supporting the open source community by providing a rich component set under a liberal license, the Apache 2.0 license. Rationale The project is interested in moving to Apache for the following reasons: To provide Apache-licensed implementation of a full-blown Ajax-based JSF component set, to become better integrated with the MyFaces and Shale initiatives, and to build a strong vendor-neutral community that will outlast any one person's or company's participation. Initial Goals The initial goals of the proposed project are: * Viable community around the RCF code base * Active relationships and possible cooperation with related projects and communities, such as Apache MyFaces (and it's subprojects) or Apache Trinidad. Current Status == Meritocracy All the initial committers are familiar with the meritocracy principles of Apache, and have already worked on the various source code bases. Some of the initial committers also have experience, undergoing the Apache incubation process. We will follow the normal meritocracy rules also with other potential contributors. Community The Apache MyFaces project, the Apache Trinidad podling and the JavaServer Faces standard hold great promise. A fully Ajax-based set of user interface components will significantly accelerate their adoption. We strongly believe that RCF will gather significant momentum and enough developers to build a vibrant community of users and contributors. Core Developers Four of the initial committers are Oracle employees and all are committers on the
[jira] Commented: (MYFACES-1226) JSR-252 Issue #59: Avoid EL expression evaluation for value attribute on AttributeTag. AttributeTag now passes the expression to UIComponent for evaluation.
[ https://issues.apache.org/jira/browse/MYFACES-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482113 ] Martin Haimberger commented on MYFACES-1226: it seams that this is implemented yet. See org.apache.myfaces.taglib.core.AttributeTag. Can anyone take also a closer look to this issue? regards, Martin Haimberger JSR-252 Issue #59: Avoid EL expression evaluation for value attribute on AttributeTag. AttributeTag now passes the expression to UIComponent for evaluation. --- Key: MYFACES-1226 URL: https://issues.apache.org/jira/browse/MYFACES-1226 Project: MyFaces Core Issue Type: Improvement Components: JSR-252 Reporter: Stan Silvert Avoid EL expression evaluation for value attribute on AttributeTag. AttributeTag now passes the expression to UIComponent for evaluation. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=59 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: JSF 1.2 Issues
Hy, provided patch for German locale. On 3/19/07, Cagatay Civici [EMAIL PROTECTED] wrote: Hi, MYFACES-1235 is done for English locale. Cagatay On 3/19/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: Martin, please do a comment on each of them https://issues.apache.org/jira/browse/MYFACES-1269 That isn't complete, I added it only to abstract UIComponent, not UIData yet thx, M On 3/19/07, Martin Haimberger [EMAIL PROTECTED] wrote: Hy, most of the open JSF 1.2 Issues seams to be implemented already. I have taken a look to the following Issues: MYFACES-1221 MYFACES-1269 MYFACES-1226 MYFACES-1235 MYFACES-1381 Should i comment them that this issues seams to be implemented and some takes also a closer look to these, or should i set them to the resolved status? regards, Martin Haimberger -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Re: [Vote] Sponsoring Entity of RCF (was Re: [Proposal] RCF, a rich component library for JSF)
+1 On 3/19/07, Mike Kienenberger [EMAIL PROTECTED] wrote: +1 On 3/19/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: Hello, last week I sent out the proposal for the donation of RCF from Oracle to the ASF. The proposal mentioned, that we need to do a vote on the MyFaces PMC of being the Sponsoring Entity of that *podling*. After finding the sponsor, we move this *discussion* to the incubator general list. The proposal has been posted to the MyFaces wiki: http://wiki.apache.org/myfaces/RCF_Proposal Please vote here, on the MyFaces DEV mailing list. Thanks, Matthias On 3/14/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: Hi, This is a proposal to donate a rich component library for JSF to the Apache Software Foundation. The live version of the proposal is available at http://wiki.apache.org/myfaces/RCF_Proposal. Omar Tazi (Chief Open Source Evangelist at Oracle) and I have been working on that proposal over the past days. Comments and questions are welcome. There is also a vacant place for two more mentors. Once people are satisfied with the proposal I will first call a vote on the MyFaces PMC to sponsor the proposal and Omar will resend this proposal to the General Incubator List. PS. Based on quick Google and USPTO searches there doesn't seem to be anything that would cause trouble with the RCF name. Thx, Matthias Wessendorf RCF, a rich component library for JSF Abstract RCF is a rich (Ajax-style) component set for the JavaServer Faces(tm) 1.2 technology. . Proposal RCF is an Ajax-based component library for the JavaServer Faces technology. RCF comes with very high quality components, and skinning (CSS-based) capabilities. RCF features include: file upload support, client-side conversion and validation, a complete Ajax-integration, data tables, hierarchical tables, color/date pickers, menu tabs/buttons, wizards, popups, toolbars, toolboxes, internationalization and accessibility. This project starts with more than 100 components which have already been documented and thoroughly tested. RCF stands for Rich Client Framework and it means that web applications, using this component set look very similar to a real, native desktop application. The name for this project can be a subject to change. RCF depends on some artifacts, provided by the Apache Trinidad project, such as framework features or Apache Maven plug-ins. Background The development of RCF started in 2005 at Oracle Corporation. With the advent of Ajax and the higher requirements for a very rich user experience, Oracle decided to implement a rich/Ajax-style JSF component set. The goal was to advance the already existing ADF Faces product, donated to the ASF in early 2006 (Apache Trinidad). When the development of RCF started, there wasn't any JSF component set that provides similar richness to the user. The RCF components run on any JSF 1.2 compliant implementation. RCF is based on some internal features of the Apache Trinidad project. The JavaServer Faces technology is a very important technology for the RCF component set, since RCF requires JSF as its runtime environment. Oracle has a large commitment to both open source and open standards. This proposal illustrates Oracle's commitment to the success of the JSF standard and supporting the open source community by providing a rich component set under a liberal license, the Apache 2.0 license. Rationale The project is interested in moving to Apache for the following reasons: To provide Apache-licensed implementation of a full-blown Ajax-based JSF component set, to become better integrated with the MyFaces and Shale initiatives, and to build a strong vendor-neutral community that will outlast any one person's or company's participation. Initial Goals The initial goals of the proposed project are: * Viable community around the RCF code base * Active relationships and possible cooperation with related projects and communities, such as Apache MyFaces (and it's subprojects) or Apache Trinidad. Current Status == Meritocracy All the initial committers are familiar with the meritocracy principles of Apache, and have already worked on the various source code bases. Some of the initial committers also have experience, undergoing the Apache incubation process. We will follow the normal meritocracy rules also with other potential contributors. Community The Apache MyFaces project, the Apache Trinidad podling and the JavaServer Faces standard hold great promise. A fully Ajax-based set of user interface components will significantly accelerate their adoption. We strongly believe that RCF will gather significant momentum and
[jira] Resolved: (MYFACES-1226) JSR-252 Issue #59: Avoid EL expression evaluation for value attribute on AttributeTag. AttributeTag now passes the expression to UIComponent for evaluation.
[ https://issues.apache.org/jira/browse/MYFACES-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf resolved MYFACES-1226. - Resolution: Fixed Fix Version/s: 1.2.0-SNAPSHOT JSR-252 Issue #59: Avoid EL expression evaluation for value attribute on AttributeTag. AttributeTag now passes the expression to UIComponent for evaluation. --- Key: MYFACES-1226 URL: https://issues.apache.org/jira/browse/MYFACES-1226 Project: MyFaces Core Issue Type: Improvement Components: JSR-252 Affects Versions: 1.2.0-SNAPSHOT Reporter: Stan Silvert Fix For: 1.2.0-SNAPSHOT Avoid EL expression evaluation for value attribute on AttributeTag. AttributeTag now passes the expression to UIComponent for evaluation. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=59 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-1202) JSR-252 Issue #5: Clarified the use of a string literal for the action attribute on ActionSource components.
[ https://issues.apache.org/jira/browse/MYFACES-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482121 ] Martin Haimberger commented on MYFACES-1202: Hy, this was a bug in the JSF RI 1.1 and worked in myfaces 1.1 and 1.2. In the UIComponent.setValueExpression the expression is checked if it is literal and if it is, the literal navigation outcome will be added. So i think this issue was never a new feature in myfaces, or i have missunderstood samething. Regards, Martin Haimberger JSR-252 Issue #5: Clarified the use of a string literal for the action attribute on ActionSource components. -- Key: MYFACES-1202 URL: https://issues.apache.org/jira/browse/MYFACES-1202 Project: MyFaces Core Issue Type: New Feature Components: JSR-252 Reporter: Stan Silvert Clarified the use of a string literal for the action attribute on ActionSource components. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=5 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (TOMAHAWK-934) Email validator allows whitespace
[ https://issues.apache.org/jira/browse/TOMAHAWK-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger reopened TOMAHAWK-934: After reading this more carefully, the problem is on the MyFaces side. commons-validator commons-validator 1.2.0 - jar We need to update the dependency to be 1.3.0 or higher to close this issue. Email validator allows whitespace - Key: TOMAHAWK-934 URL: https://issues.apache.org/jira/browse/TOMAHAWK-934 Project: MyFaces Tomahawk Issue Type: Bug Components: Validators Affects Versions: 1.1.5-SNAPSHOT Environment: Windows XP JBoss 4.0.5 Reporter: Daniel Ray Fix For: 1.1.5-SNAPSHOT Email validator allows white space in an email address i.e. test(space)@email.com is considered valid. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-1569) Error message when input text is disabled or readOnly
Error message when input text is disabled or readOnly - Key: MYFACES-1569 URL: https://issues.apache.org/jira/browse/MYFACES-1569 Project: MyFaces Core Issue Type: Improvement Components: General Reporter: Oliver Pfau Priority: Minor Submit of a from with input text is disabled == true leads to the following message: WARNING: There should always be a submitted value for an input if it is rendered, its form is submitted, and it is not disabled or read-only . Component : ...inputText The warning does not appear when readOnly == true. Please remove the part or read-only from the message. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [Vote] Sponsoring Entity of RCF (was Re: [Proposal] RCF, a rich component library for JSF)
From: Matthias Wessendorf [EMAIL PROTECTED] Hello, last week I sent out the proposal for the donation of RCF from Oracle to the ASF. The proposal mentioned, that we need to do a vote on the MyFaces PMC of being the Sponsoring Entity of that *podling*. After finding the sponsor, we move this *discussion* to the incubator general list. The proposal has been posted to the MyFaces wiki: http://wiki.apache.org/myfaces/RCF_Proposal Please vote here, on the MyFaces DEV mailing list. +1 (non-binding) Thanks, Matthias Gary VanMatre On 3/14/07, Matthias Wessendorf wrote: Hi, This is a proposal to donate a rich component library for JSF to the Apache Software Foundation. The live version of the proposal is available at http://wiki.apache.org/myfaces/RCF_Proposal. Omar Tazi (Chief Open Source Evangelist at Oracle) and I have been working on that proposal over the past days. Comments and questions are welcome. There is also a vacant place for two more mentors. Once people are satisfied with the proposal I will first call a vote on the MyFaces PMC to sponsor the proposal and Omar will resend this proposal to the General Incubator List. PS. Based on quick Google and USPTO searches there doesn't seem to be anything that would cause trouble with the RCF name. Thx, Matthias Wessendorf RCF, a rich component library for JSF Abstract RCF is a rich (Ajax-style) component set for the JavaServer Faces(tm) 1.2 technology. . Proposal RCF is an Ajax-based component library for the JavaServer Faces technology. RCF comes with very high quality components, and skinning (CSS-based) capabilities. RCF features include: file upload support, client-side conversion and validation, a complete Ajax-integration, data tables, hierarchical tables, color/date pickers, menu tabs/buttons, wizards, popups, toolbars, toolboxes, internationalization and accessibility. This project starts with more than 100 components which have already been documented and thoroughly tested. RCF stands for Rich Client Framework and it means that web applications, using this component set look very similar to a real, native desktop application. The name for this project can be a subject to change. RCF depends on some artifacts, provided by the Apache Trinidad project, such as framework features or Apache Maven plug-ins. Background The development of RCF started in 2005 at Oracle Corporation. With the advent of Ajax and the higher requirements for a very rich user experience, Oracle decided to implement a rich/Ajax-style JSF component set. The goal was to advance the already existing ADF Faces product, donated to the ASF in early 2006 (Apache Trinidad). When the development of RCF started, there wasn't any JSF component set that provides similar richness to the user. The RCF components run on any JSF 1.2 compliant implementation. RCF is based on some internal features of the Apache Trinidad project. The JavaServer Faces technology is a very important technology for the RCF component set, since RCF requires JSF as its runtime environment. Oracle has a large commitment to both open source and open standards. This proposal illustrates Oracle's commitment to the success of the JSF standard and supporting the open source community by providing a rich component set under a liberal license, the Apache 2.0 license. Rationale The project is interested in moving to Apache for the following reasons: To provide Apache-licensed implementation of a full-blown Ajax-based JSF component set, to become better integrated with the MyFaces and Shale initiatives, and to build a strong vendor-neutral community that will outlast any one person's or company's participation. Initial Goals The initial goals of the proposed project are: * Viable community around the RCF code base * Active relationships and possible cooperation with related projects and communities, such as Apache MyFaces (and it's subprojects) or Apache Trinidad. Current Status == Meritocracy All the initial committers are familiar with the meritocracy principles of Apache, and have already worked on the various source code bases. Some of the initial committers also have experience, undergoing the Apache incubation process. We will follow the normal meritocracy rules also with other potential contributors. Community The Apache MyFaces project, the Apache Trinidad podling and the JavaServer Faces standard hold great promise. A fully Ajax-based set of user interface components will significantly accelerate their
[jira] Commented: (MYFACES-1224) JSR-252 Issue #55: For postback requests, in the RestoreViewPhase, during ValueExpression examination for each component, specify that calling setValue() on each Val
[ https://issues.apache.org/jira/browse/MYFACES-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482139 ] Martin Haimberger commented on MYFACES-1224: Hy, this improvement is already implemented, because the JSF RI took the myfaces approach to call the setValue() methode parent first and then traversing the children. Regards, Martin Haimberger JSR-252 Issue #55: For postback requests, in the RestoreViewPhase, during ValueExpression examination for each component, specify that calling setValue() on each ValueExpression should be done parent-first - Key: MYFACES-1224 URL: https://issues.apache.org/jira/browse/MYFACES-1224 Project: MyFaces Core Issue Type: Improvement Components: JSR-252 Reporter: Stan Silvert For postback requests, in the RestoreViewPhase, during ValueExpression examination for each component in the component tree, specify that calling the setValue() method on each ValueExpression, should be done in a parent-first fashion, calling the setValue() method and then traversing the children. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=55 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-1230) JSR-252 Issue #68: Specify that the component tree may be manipulated throughout the request processing lifecycle, except during render.
[ https://issues.apache.org/jira/browse/MYFACES-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482143 ] Martin Haimberger commented on MYFACES-1230: Hy, is this really an issue or only a clearification request to the jsf spec? Regards, Martin Haimberger JSR-252 Issue #68: Specify that the component tree may be manipulated throughout the request processing lifecycle, except during render. Key: MYFACES-1230 URL: https://issues.apache.org/jira/browse/MYFACES-1230 Project: MyFaces Core Issue Type: Improvement Components: JSR-252 Reporter: Stan Silvert Specify that the component tree may be manipulated throughout the request processing lifecycle, except during render. Please see Section 2.2.6 Render Response for more details. Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=68 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [Vote] Sponsoring Entity of RCF (was Re: [Proposal] RCF, a rich component library for JSF)
+1 On 19/03/07, Gary VanMatre [EMAIL PROTECTED] wrote: From: Matthias Wessendorf [EMAIL PROTECTED] Hello, last week I sent out the proposal for the donation of RCF from Oracle to the ASF. The proposal mentioned, that we need to do a vote on the MyFaces PMC of being the Sponsoring Entity of that *podling*. After finding the sponsor, we move this *discussion* to the incubator general list. The proposal has been posted to the MyFaces wiki: http://wiki.apache.org/myfaces/RCF_Proposal Please vote here, on the MyFaces DEV mailing list. +1 (non-binding) Thanks, Matthias Gary VanMatre On 3/14/07, Matthias Wessendorf wrote: Hi, This is a proposal to donate a rich component library for JSF to the Apache Software Foundation. The live version of the proposal is available at http://wiki.apache.org/myfaces/RCF_Proposal. Omar Tazi (Chief Open Source Evangelist at Oracle) and I have been working on that proposal over the past days. Comments and questions are welcome. There is also a vacant place for two more mentors. Once people are satisfied with the proposal I will first call a vote on the MyFaces PMC to sponsor the proposal and Omar will resend this proposal to the General Incubator List. PS. Based on quick Google and USPTO searches there doesn't seem to be anything that would cause trouble with the RCF name. Thx, Matthias Wessendorf RCF, a rich component library for JSF Abstract RCF is a rich (Ajax-style) component set for the JavaServer Faces(tm) 1.2 technology. . Proposal RCF is an Ajax-based component library for the JavaServer Faces technology. RCF comes with very high quality components, and skinning (CSS-based) capabilities. RCF features include: file upload support, client-side conversion and validation, a complete Ajax-integration, data tables, hierarchical tables, color/date pickers, menu tabs/buttons, wizards, popups, toolbars, toolboxes, internat ionali zation and accessibility. This project starts with more than 100 components which have already been documented and thoroughly tested. RCF stands for Rich Client Framework and it means that web applications, using this component set look very similar to a real, native desktop application. The name for this project can be a subject to change. RCF depends on some artifacts, provided by the Apache Trinidad project, such as framework features or Apache Maven plug-ins. Background The development of RCF started in 2005 at Oracle Corporation. With the advent of Ajax and the higher requirements for a very rich user experience, Oracle decided to implement a rich/Ajax-style JSF component set. The goal was to advance the al ready existing ADF Faces product, donated to the ASF in early 2006 (Apache Trinidad). When the development of RCF started, there wasn't any JSF component set that provides similar richness to the user. The RCF components run on any JSF 1.2 compliant implementation. RCF is based on some internal features of the Apache Trinidad project. The JavaServer Faces technology is a very important technology for the RCF component set, since RCF requires JSF as its runtime environment. Oracle has a large commitment to both open source and open standards. This proposal illustrates Oracle's commitment to the success of the JSF standard and supporting the open source community by providing a rich component set under a liberal license, the Apache 2.0 license. Rationale The project is interested in moving to Apache for the following reasons: To provide Apache-licensed implementation of a full-blown Ajax-based JSF component set, to become better integrated with the MyFaces and Shale initiatives, and to build a strong vendor-neutral community that will outlast any one person's or company's participation. Initial Goals The initial goals of the proposed project are: * Viable community around the RCF code base * Active relationships and possible cooperation with related projects and communities, such as Apache MyFaces (and it's subprojects) or Apache Trinidad. Current Status == Meritocracy g t; All the initial committers are familiar with the meritocracy principles of Apache, and have already worked on the various source code bases. Some of the initial committers also have experience, undergoing the Apache incubation process. We will follow the normal meritocracy rules also with other potential contributors. Community The Apache MyFaces project, the Apache Trinidad podling and the JavaServer Faces standard hold great promise. A fully Ajax-based set of user interface components will significantly accelerate their adoption. We strongly believe that RCF will gather significant momentum
[jira] Updated: (TOMAHAWK-936) TableSuggestAjax aborts page load in IE
[ https://issues.apache.org/jira/browse/TOMAHAWK-936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Punz updated TOMAHAWK-936: - Resolution: Fixed Status: Resolved (was: Patch Available) Applied on Revision: 520031 Thanks for the patch... TableSuggestAjax aborts page load in IE --- Key: TOMAHAWK-936 URL: https://issues.apache.org/jira/browse/TOMAHAWK-936 Project: MyFaces Tomahawk Issue Type: Bug Affects Versions: 1.1.5-SNAPSHOT Reporter: Stefan Schuster Fix For: 1.1.5-SNAPSHOT Attachments: TableSuggestAjax_IEPatch.patch Every use of the tableSuggestComponent in a page aborts the page load in IE with an error message (even in the sandbox example pages). This happens due to a bug that the javascript gets rendered before the DIV it works with gets closed. The attached patch moves the DIV-close to the correct position. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[RESULT][VOTE] New Apache MyFaces Fusion Name
Hi! The vote for the new name for the Apache MyFaces Fusion name is finished now. The result: Apache MyFaces Orchestra 10 votes Apache MyFaces Aurora 2 votes Apache MyFaces Connections nothing Please find the voting thread here [1] From now on the new name is Apache MyFaces Orchestra. Thanks to everyone who participated in this process . and - also to everyone who did not, you didn't introduce the one-thousand-and-first name ;-) hehe - well - and thanks that Kleber didn't make it :-D Ciao, Mario [1] http://www.nabble.com/-VOTE--New-Apache-MyFaces-Fusion-Name-t3371648.html
[jira] Resolved: (MYFACES-1202) JSR-252 Issue #5: Clarified the use of a string literal for the action attribute on ActionSource components.
[ https://issues.apache.org/jira/browse/MYFACES-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf resolved MYFACES-1202. - Resolution: Invalid Fix Version/s: 1.2.0-SNAPSHOT was wrong inside of the impl details of the JSF RI; not really a bug JSR-252 Issue #5: Clarified the use of a string literal for the action attribute on ActionSource components. -- Key: MYFACES-1202 URL: https://issues.apache.org/jira/browse/MYFACES-1202 Project: MyFaces Core Issue Type: New Feature Components: JSR-252 Reporter: Stan Silvert Fix For: 1.2.0-SNAPSHOT Clarified the use of a string literal for the action attribute on ActionSource components. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=5 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [Vote] Sponsoring Entity of RCF (was Re: [Proposal] RCF, a rich component library for JSF)
+1 regards, Martin On 3/19/07, Bruno Aranda [EMAIL PROTECTED] wrote: +1 On 19/03/07, Gary VanMatre [EMAIL PROTECTED] wrote: From: Matthias Wessendorf [EMAIL PROTECTED] Hello, last week I sent out the proposal for the donation of RCF from Oracle to the ASF. The proposal mentioned, that we need to do a vote on the MyFaces PMC of being the Sponsoring Entity of that *podling*. After finding the sponsor, we move this *discussion* to the incubator general list. The proposal has been posted to the MyFaces wiki: http://wiki.apache.org/myfaces/RCF_Proposal Please vote here, on the MyFaces DEV mailing list. +1 (non-binding) Thanks, Matthias Gary VanMatre On 3/14/07, Matthias Wessendorf wrote: Hi, This is a proposal to donate a rich component library for JSF to the Apache Software Foundation. The live version of the proposal is available at http://wiki.apache.org/myfaces/RCF_Proposal. Omar Tazi (Chief Open Source Evangelist at Oracle) and I have been working on that proposal over the past days. Comments and questions are welcome. There is also a vacant place for two more mentors. Once people are satisfied with the proposal I will first call a vote on the MyFaces PMC to sponsor the proposal and Omar will resend this proposal to the General Incubator List. PS. Based on quick Google and USPTO searches there doesn't seem to be anything that would cause trouble with the RCF name. Thx, Matthias Wessendorf RCF, a rich component library for JSF Abstract RCF is a rich (Ajax-style) component set for the JavaServer Faces(tm) 1.2 technology. . Proposal RCF is an Ajax-based component library for the JavaServer Faces technology. RCF comes with very high quality components, and skinning (CSS-based) capabilities. RCF features include: file upload support, client-side conversion and validation, a complete Ajax-integration, data tables, hierarchical tables, color/date pickers, menu tabs/buttons, wizards, popups, toolbars, toolboxes, internat ionali zation and accessibility. This project starts with more than 100 components which have already been documented and thoroughly tested. RCF stands for Rich Client Framework and it means that web applications, using this component set look very similar to a real, native desktop application. The name for this project can be a subject to change. RCF depends on some artifacts, provided by the Apache Trinidad project, such as framework features or Apache Maven plug-ins. Background The development of RCF started in 2005 at Oracle Corporation. With the advent of Ajax and the higher requirements for a very rich user experience, Oracle decided to implement a rich/Ajax-style JSF component set. The goal was to advance the al ready existing ADF Faces product, donated to the ASF in early 2006 (Apache Trinidad). When the development of RCF started, there wasn't any JSF component set that provides similar richness to the user. The RCF components run on any JSF 1.2 compliant implementation. RCF is based on some internal features of the Apache Trinidad project. The JavaServer Faces technology is a very important technology for the RCF component set, since RCF requires JSF as its runtime environment. Oracle has a large commitment to both open source and open standards. This proposal illustrates Oracle's commitment to the success of the JSF standard and supporting the open source community by providing a rich component set under a liberal license, the Apache 2.0 license. Rationale The project is interested in moving to Apache for the following reasons: To provide Apache-licensed implementation of a full-blown Ajax-based JSF component set, to become better integrated with the MyFaces and Shale initiatives, and to build a strong vendor-neutral community that will outlast any one person's or company's participation. Initial Goals The initial goals of the proposed project are: * Viable community around the RCF code base * Active relationships and possible cooperation with related projects and communities, such as Apache MyFaces (and it's subprojects) or Apache Trinidad. Current Status == Meritocracy g t; All the initial committers are familiar with the meritocracy principles of Apache, and have already worked on the various source code bases. Some of the initial committers also have experience, undergoing the Apache incubation process. We will follow the normal meritocracy rules also with other potential contributors. Community The Apache MyFaces project, the Apache Trinidad podling and the
Re: [Vote] Sponsoring Entity of RCF (was Re: [Proposal] RCF, a rich component library for JSF)
+1 Regards, Volker 2007/3/19, Matthias Wessendorf [EMAIL PROTECTED]: Hello, last week I sent out the proposal for the donation of RCF from Oracle to the ASF. The proposal mentioned, that we need to do a vote on the MyFaces PMC of being the Sponsoring Entity of that *podling*. After finding the sponsor, we move this *discussion* to the incubator general list. The proposal has been posted to the MyFaces wiki: http://wiki.apache.org/myfaces/RCF_Proposal Please vote here, on the MyFaces DEV mailing list. Thanks, Matthias
Re: [Vote] Sponsoring Entity of RCF (was Re: [Proposal] RCF, a rich component library for JSF)
+1 Volker Weber wrote: +1 Regards, Volker 2007/3/19, Matthias Wessendorf [EMAIL PROTECTED]: Hello, last week I sent out the proposal for the donation of RCF from Oracle to the ASF. The proposal mentioned, that we need to do a vote on the MyFaces PMC of being the Sponsoring Entity of that *podling*. After finding the sponsor, we move this *discussion* to the incubator general list. The proposal has been posted to the MyFaces wiki: http://wiki.apache.org/myfaces/RCF_Proposal Please vote here, on the MyFaces DEV mailing list. Thanks, Matthias
Re: [Vote] Sponsoring Entity of RCF (was Re: [Proposal] RCF, a rich component library for JSF)
+1 On 3/19/07, Bernd Bohmann [EMAIL PROTECTED] wrote: +1 Volker Weber wrote: +1 Regards, Volker 2007/3/19, Matthias Wessendorf [EMAIL PROTECTED]: Hello, last week I sent out the proposal for the donation of RCF from Oracle to the ASF. The proposal mentioned, that we need to do a vote on the MyFaces PMC of being the Sponsoring Entity of that *podling*. After finding the sponsor, we move this *discussion* to the incubator general list. The proposal has been posted to the MyFaces wiki: http://wiki.apache.org/myfaces/RCF_Proposal Please vote here, on the MyFaces DEV mailing list. Thanks, Matthias -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: Hello
El lun, 19-03-2007 a las 10:38 +0100, Zdeněk Sochor escribió: Hi, comments in-line. Josué Alcalde González napsal(a): Hello. My name is Josué Alcalde and I am new to this list. I started four months ago to use myfaces in my projects and I would like to contribute, perhaps with new components. Anyone is welcomed to contribute in apache projects ;) I have read the wiki and now, I have a workspace for myfaces in eclipse. Don't forget that MyFaces projects use Maven2 for building and Myfaces 1.1 must be compiled under J2SE 1.4. Don't worry. There is a good page in the wiki which explain all the process. Maven is good for build, but I can't life without Eclipse. :) One thing I would like to have in myfaces is a clean way to render messages in differents divs for each level, to be able to have a box for every kind of messages. Now, the only workaround to do this is four t:messages and add a LevelStyle=display:none; for the three unwanted messages but it will render the messages four times. I would like to make a patch adding four new boolean attributes: - fatalRendered - errorRendered - warnRendered - infoRendered It would be easy to do overwriting renderSingleFacesMessage and check the level there. t:messages has already styleClasses attributes for each level of importance (from JSF spec). If you want to render each level messages together, add sorting attribute for specifying order of rendering messages. Rendering divs around each level of importance could be implemented as another layout (t:messages has already support for rendering as list or table). I'm against using multiple t:messages tags in one page - hard to read and it would save/restore the same messages in view. Yes, four t:messages is not a good idea. Perhaps a div layout would be a better approach, but there should be divInfoStyle and divInfoClass for the style, or the actual infoStyle and infoClass could be used for it. I have been playing with it and I have some questions: - Is there a Code Formatter Profile for Apache Code coventions? - There is a code generation. I have been browsing the wiki and the lists and I haven't found how it works. There are some old messages which said it didn't work. Code auto-generation was dropped in 1.1.1 release, i was playing with making it work again, but auto-generating won't be re-enabled in its former form. MyFaces 1.2 uses new apt plugin for autogeneration from trinidad, so it doesn't make sense to support old and new forms. Is it working now? If it works, how can I generate the new attributes? if it doesn't work, should I edit the tag definition, the tag class and the component class manually? Manual editing is only way to altering components in MyFaces 1.1. Submitting changes for contributers is done through JIRA issues and providing unified diff patches. Only PMC and commiters have direct wrtite access to svn repository, so it's up to them if your patches are accepted. Thanks, I think I will develop a div Layout for t:messages. It could be usefull at least for me :) Regards, Zdenek
Re: [continuum] BUILD ERROR: Tobago Gendoc
Does anyone know why this keeps repeating? On 3/19/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Online report : http://myfaces.zones.apache.org:8080/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/203/buildId/9596 Build statistics: State: Error Previous State: Error Started at: Mon, 19 Mar 2007 23:06:24 + Finished at: Mon, 19 Mar 2007 23:06:26 + Total time: 1s Build Trigger: Schedule Exit code: 0 Building machine hostname: myfaces.zones.apache.org Operating system : SunOS(unknown) Java version : 1.5.0_10(Sun Microsystems Inc.) Changes No files changed Build Error: Provider message: The svn command failed. Command output: --- svn: REPORT request failed on '/repos/asf/!svn/vcc/default' svn: Target path does not exist --- -- Dennis Byrne
