[jira] [Created] (TOBAGO-1028) Attribute inline=true doesn't work anymore in tc:selectManyRadio
Attribute inline=true doesn't work anymore in tc:selectManyRadio Key: TOBAGO-1028 URL: https://issues.apache.org/jira/browse/TOBAGO-1028 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.5.0-alpha-2 Environment: Facelets Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Fix For: 1.5.0-beta-2 Attribute inline=true doesn't work anymore in tc:selectOneRadio. I can't test it in demo because Ref. is under construction... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] release of myfaces core 2.0.9
+1 Am 13.09.11 05:46, schrieb Leonardo Uribe: +1 2011/9/12 Leonardo Uribelu4...@gmail.com: Hi, I was running the needed tasks to get the 2.0.9 release of Apache MyFaces core out. This is a quick bug-fix release for the following issues. * [MYFACES-3294] - REGRESSION: 2.0.7-2.0.8: Facets lost after validation error POST-back * [MYFACES-3298] - h:outputText incorectly renders an extraspan * [MYFACES-3291] - jsf.js make the comments and structures jsdoc toolkit friendly * [MYFACES-3295] - Replace RendererUtils.renderChild() by UIComponent.encodeAll() * [MYFACES-3301] - ValidatorExceptions are not properly handled in MethodExpressionValidator.validate() The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.core v2.0.9 [1] The artifacts were deployed on nexus repo [1] and to my private Apache account [3] for binary and source packages. The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.9 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +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.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-054/org/apache/myfaces/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces209binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600version=12317644
Re: [VOTE] release of myfaces core 2.1.3
+1 Am 13.09.11 05:44, schrieb Leonardo Uribe: +1 2011/9/12 Leonardo Uribelu4...@gmail.com: Hi, I was running the needed tasks to get the 2.1.3 release of Apache MyFaces core out. This is a quick bug-fix release for the following issues. * [MYFACES-3294] - REGRESSION: 2.0.7-2.0.8: Facets lost after validation error POST-back * [MYFACES-3298] - h:outputText incorectly renders an extraspan * [MYFACES-3291] - jsf.js make the comments and structures jsdoc toolkit friendly * [MYFACES-3295] - Replace RendererUtils.renderChild() by UIComponent.encodeAll() * [MYFACES-3301] - ValidatorExceptions are not properly handled in MethodExpressionValidator.validate() The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.core v2.1.3 [1] The artifacts were deployed on nexus repo [1] and to my private Apache account [3] for binary and source packages. The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.1.3 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +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.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-055/org/apache/myfaces/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces213binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600version=12317642
[jira] [Created] (TOBAGO-1029) Make some (no longer used) inline attributes deprecated
Make some (no longer used) inline attributes deprecated --- Key: TOBAGO-1029 URL: https://issues.apache.org/jira/browse/TOBAGO-1029 Project: MyFaces Tobago Issue Type: Task Components: Core Affects Versions: 1.5.0-beta-1 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Priority: Minor The old inline attribute was used to make a kind of flow layout. In Tobago for this feature the FlowLayoutManager should be used. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] release of myfaces core 2.1.3
+1 Regards, Jakob 2011/9/13 Werner Punz werner.p...@gmail.com: +1 Am 13.09.11 05:44, schrieb Leonardo Uribe: +1 2011/9/12 Leonardo Uribelu4...@gmail.com: Hi, I was running the needed tasks to get the 2.1.3 release of Apache MyFaces core out. This is a quick bug-fix release for the following issues. * [MYFACES-3294] - REGRESSION: 2.0.7-2.0.8: Facets lost after validation error POST-back * [MYFACES-3298] - h:outputText incorectly renders an extraspan * [MYFACES-3291] - jsf.js make the comments and structures jsdoc toolkit friendly * [MYFACES-3295] - Replace RendererUtils.renderChild() by UIComponent.encodeAll() * [MYFACES-3301] - ValidatorExceptions are not properly handled in MethodExpressionValidator.validate() The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.core v2.1.3 [1] The artifacts were deployed on nexus repo [1] and to my private Apache account [3] for binary and source packages. The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.1.3 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +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.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-055/org/apache/myfaces/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces213binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600version=12317642 -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at
Re: [VOTE] release of myfaces core 2.0.9
+1 Regards, Jakob 2011/9/13 Werner Punz werner.p...@gmail.com: +1 Am 13.09.11 05:46, schrieb Leonardo Uribe: +1 2011/9/12 Leonardo Uribelu4...@gmail.com: Hi, I was running the needed tasks to get the 2.0.9 release of Apache MyFaces core out. This is a quick bug-fix release for the following issues. * [MYFACES-3294] - REGRESSION: 2.0.7-2.0.8: Facets lost after validation error POST-back * [MYFACES-3298] - h:outputText incorectly renders an extraspan * [MYFACES-3291] - jsf.js make the comments and structures jsdoc toolkit friendly * [MYFACES-3295] - Replace RendererUtils.renderChild() by UIComponent.encodeAll() * [MYFACES-3301] - ValidatorExceptions are not properly handled in MethodExpressionValidator.validate() The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.core v2.0.9 [1] The artifacts were deployed on nexus repo [1] and to my private Apache account [3] for binary and source packages. The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.9 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +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.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-054/org/apache/myfaces/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces209binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600version=12317644 -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at
Re: [VOTE] release of myfaces core 2.0.9
+1 Regards, Udo Am 13.09.11 12:09, schrieb Jakob Korherr: +1 Regards, Jakob 2011/9/13 Werner Punzwerner.p...@gmail.com: +1 Am 13.09.11 05:46, schrieb Leonardo Uribe: +1 2011/9/12 Leonardo Uribelu4...@gmail.com: Hi, I was running the needed tasks to get the 2.0.9 release of Apache MyFaces core out. This is a quick bug-fix release for the following issues. * [MYFACES-3294] - REGRESSION: 2.0.7-2.0.8: Facets lost after validation error POST-back * [MYFACES-3298] - h:outputText incorectly renders an extraspan * [MYFACES-3291] - jsf.js make the comments and structures jsdoc toolkit friendly * [MYFACES-3295] - Replace RendererUtils.renderChild() by UIComponent.encodeAll() * [MYFACES-3301] - ValidatorExceptions are not properly handled in MethodExpressionValidator.validate() The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.core v2.0.9 [1] The artifacts were deployed on nexus repo [1] and to my private Apache account [3] for binary and source packages. The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.9 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +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.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-054/org/apache/myfaces/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces209binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600version=12317644
Re: [VOTE] release of myfaces core 2.0.9
+1 On Tue, Sep 13, 2011 at 5:29 AM, Udo Schnurpfeil u...@schnurpfeil.de wrote: +1 Regards, Udo Am 13.09.11 12:09, schrieb Jakob Korherr: +1 Regards, Jakob 2011/9/13 Werner Punzwerner.p...@gmail.com: +1 Am 13.09.11 05:46, schrieb Leonardo Uribe: +1 2011/9/12 Leonardo Uribelu4...@gmail.com: Hi, I was running the needed tasks to get the 2.0.9 release of Apache MyFaces core out. This is a quick bug-fix release for the following issues. * [MYFACES-3294] - REGRESSION: 2.0.7-2.0.8: Facets lost after validation error POST-back * [MYFACES-3298] - h:outputText incorectly renders an extraspan * [MYFACES-3291] - jsf.js make the comments and structures jsdoc toolkit friendly * [MYFACES-3295] - Replace RendererUtils.renderChild() by UIComponent.encodeAll() * [MYFACES-3301] - ValidatorExceptions are not properly handled in MethodExpressionValidator.**validate() The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.core v2.0.9 [1] The artifacts were deployed on nexus repo [1] and to my private Apache account [3] for binary and source packages. The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.9 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). --**-- [ ] +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.. --**-- Thanks, Leonardo Uribe [1] https://repository.apache.org/**content/repositories/** orgapachemyfaces-054/org/**apache/myfaces/https://repository.apache.org/content/repositories/orgapachemyfaces-054/org/apache/myfaces/ [2] http://www.apache.org/**foundation/voting.html#**ReleaseVoteshttp://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~**lu4242/myfaces209binsrchttp://people.apache.org/%7Elu4242/myfaces209binsrc [4] https://issues.apache.org/**jira/secure/ReleaseNote.jspa?** projectId=10600version=**12317644https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600version=12317644 -- Grant Smith - V.P. Information Technology Marathon Computer Systems, LLC.
Re: [VOTE] release of myfaces core 2.1.3
+1 On Tue, Sep 13, 2011 at 3:09 AM, Jakob Korherr jakob.korh...@gmail.comwrote: +1 Regards, Jakob 2011/9/13 Werner Punz werner.p...@gmail.com: +1 Am 13.09.11 05:44, schrieb Leonardo Uribe: +1 2011/9/12 Leonardo Uribelu4...@gmail.com: Hi, I was running the needed tasks to get the 2.1.3 release of Apache MyFaces core out. This is a quick bug-fix release for the following issues. * [MYFACES-3294] - REGRESSION: 2.0.7-2.0.8: Facets lost after validation error POST-back * [MYFACES-3298] - h:outputText incorectly renders an extraspan * [MYFACES-3291] - jsf.js make the comments and structures jsdoc toolkit friendly * [MYFACES-3295] - Replace RendererUtils.renderChild() by UIComponent.encodeAll() * [MYFACES-3301] - ValidatorExceptions are not properly handled in MethodExpressionValidator.validate() The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.core v2.1.3 [1] The artifacts were deployed on nexus repo [1] and to my private Apache account [3] for binary and source packages. The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.1.3 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +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.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-055/org/apache/myfaces/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces213binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600version=12317642 -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at -- Grant Smith - V.P. Information Technology Marathon Computer Systems, LLC.
HostedQA and Autoriginate links now point to undesirable non-related entities
Someone should take a look at updating http://myfaces.apache.org/tomahawk/testing/hostedqa.html HostedQA looks like it now points to a generated parked domain. Autoriginate looks like it points to s3xu al1y expli_cit material. I changed the wiki entry on automated testing to remove the links. If the domain no longer works, I'd be surprised if the HostedQA account works anymore, although I have never tested it.
[jira] [Issue Comment Edited] (TRINIDAD-2116) ResourceBundles Strings containing doubled single quotes are not properly formatted by FastMessageFormat on display...
[
https://issues.apache.org/jira/browse/TRINIDAD-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101425#comment-13101425
]
Pavitra Subramaniam edited comment on TRINIDAD-2116 at 9/13/11 6:00 PM:
Precisely. After a fair bit of testing by the i18n team we realized that the
fix would not be backwards compatible. Unless all strings system-wide, are
translated using the same WPTG rules we could easily break cases where doubled
quotes need to be retained.
There are customers that currently have their bundle strings not just in these
resource files, but in other places like database tables, libraries etc..
Changing the behavior of the formatting as proposed by the fix could break code
that relies on retaining the doubled quotes.
When re-visting this in the future we need a solution, that would not only
maintain backward compatibility but also allow us move away from the fast
message formatting altogether.
was (Author: pasubra):
Precisely. After a fair bit of testing by the i18n team we realized that
the fix would not be backwards compatible. Unless all strings system-wide, are
translated using the same WPTG rules we could easily break cases where doubled
quotes need to be retained.
There are teams that currently have their bundle strings in files, ADF
libraries from other teams and in database tables. Changing the behavior of the
formatting would break backward compatibility. (According to Andrew) who did
the work to see if we could fix af:format and found that we could not. We could
not even fix the problem with a web.xml setting as that would affect ADF
libraries as well. The only fix that was accepted was to create new EL
functions so the existing functions could continue to work untouched.
At this time we need a solution, that would maintain backward compatibility but
allow us to start moving away from the fast message formatting altogether.
ResourceBundles Strings containing doubled single quotes are not properly
formatted by FastMessageFormat on display...
---
Key: TRINIDAD-2116
URL: https://issues.apache.org/jira/browse/TRINIDAD-2116
Project: MyFaces Trinidad
Issue Type: Bug
Affects Versions: 1.2.12-core
Reporter: Pavitra Subramaniam
Assignee: Jeanne Waldman
Fix For: 2.0.1
Attachments: jira-2116-1.2.12.6.0.patch, jira2116-trunk.patch
The translations tool used by the WPTG team that provides translations for
the Strings in the ResourceBundle uses special processing for single
quotation marks, common in languages such as French. In ResourceBundle files,
if a message contains an argument placeholder, e.g. {0} or {1}, it is assumed
to be a format pattern for MessageFormat and the translation tool
automatically doubles all single quotes inside such a message. If the message
contains no arguments, it is expected to be used directly after loading from
the bundle, without processing with MessageFormat. Therefore, no quotes are
doubled automatically in such a message. This code change accounts for the
presence of doubled quotes.
Now FastMessageFormat.java and its counterpart on the client
TrFastMessageFormatUtils object (Locale.js) assumes simple formatting rules
and does not account for the presence of doubled single quotes. So this means
that for some messages French users continue to see doubled quotes when
single quotes are more the norm, For e.g., instead of
Entrez une date avec le même format que l'exemple suivant : 01/02/2011
they see something like
Entrez une date avec le même format que l''exemple suivant : 01/02/2011
(Notice the doubled quotes in l''exemple)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] release of myfaces core 2.0.9
+1 regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/9/13 Grant Smith work.gr...@gmail.com +1 On Tue, Sep 13, 2011 at 5:29 AM, Udo Schnurpfeil u...@schnurpfeil.dewrote: +1 Regards, Udo Am 13.09.11 12:09, schrieb Jakob Korherr: +1 Regards, Jakob 2011/9/13 Werner Punzwerner.p...@gmail.com: +1 Am 13.09.11 05:46, schrieb Leonardo Uribe: +1 2011/9/12 Leonardo Uribelu4...@gmail.com: Hi, I was running the needed tasks to get the 2.0.9 release of Apache MyFaces core out. This is a quick bug-fix release for the following issues. * [MYFACES-3294] - REGRESSION: 2.0.7-2.0.8: Facets lost after validation error POST-back * [MYFACES-3298] - h:outputText incorectly renders an extraspan * [MYFACES-3291] - jsf.js make the comments and structures jsdoc toolkit friendly * [MYFACES-3295] - Replace RendererUtils.renderChild() by UIComponent.encodeAll() * [MYFACES-3301] - ValidatorExceptions are not properly handled in MethodExpressionValidator.**validate() The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.core v2.0.9 [1] The artifacts were deployed on nexus repo [1] and to my private Apache account [3] for binary and source packages. The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.9 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). --**-- [ ] +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.. --**-- Thanks, Leonardo Uribe [1] https://repository.apache.org/**content/repositories/** orgapachemyfaces-054/org/**apache/myfaces/https://repository.apache.org/content/repositories/orgapachemyfaces-054/org/apache/myfaces/ [2] http://www.apache.org/**foundation/voting.html#**ReleaseVoteshttp://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~**lu4242/myfaces209binsrchttp://people.apache.org/%7Elu4242/myfaces209binsrc [4] https://issues.apache.org/**jira/secure/ReleaseNote.jspa?** projectId=10600version=**12317644https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600version=12317644 -- Grant Smith - V.P. Information Technology Marathon Computer Systems, LLC.
Re: [VOTE] release of myfaces core 2.1.3
+1 regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/9/13 Grant Smith work.gr...@gmail.com +1 On Tue, Sep 13, 2011 at 3:09 AM, Jakob Korherr jakob.korh...@gmail.comwrote: +1 Regards, Jakob 2011/9/13 Werner Punz werner.p...@gmail.com: +1 Am 13.09.11 05:44, schrieb Leonardo Uribe: +1 2011/9/12 Leonardo Uribelu4...@gmail.com: Hi, I was running the needed tasks to get the 2.1.3 release of Apache MyFaces core out. This is a quick bug-fix release for the following issues. * [MYFACES-3294] - REGRESSION: 2.0.7-2.0.8: Facets lost after validation error POST-back * [MYFACES-3298] - h:outputText incorectly renders an extraspan * [MYFACES-3291] - jsf.js make the comments and structures jsdoc toolkit friendly * [MYFACES-3295] - Replace RendererUtils.renderChild() by UIComponent.encodeAll() * [MYFACES-3301] - ValidatorExceptions are not properly handled in MethodExpressionValidator.validate() The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.core v2.1.3 [1] The artifacts were deployed on nexus repo [1] and to my private Apache account [3] for binary and source packages. The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.1.3 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +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.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-055/org/apache/myfaces/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces213binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600version=12317642 -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at -- Grant Smith - V.P. Information Technology Marathon Computer Systems, LLC.
Re: HostedQA and Autoriginate links now point to undesirable non-related entities
I doubt they work -- that company was sold to Gomez a long time ago. Patrick has a new company called BrowserMob now, which just got acquired as well. --- Kito D. Mann | twitter: kito99 | Author, JSF in Action Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info | twitter: jsfcentral +1 203-404-4848 x3 * Listen to the latest headlines in the JSF and Java EE newscast: http://blogs.jsfcentral.com/roller/editorsdesk/category/JSF+and+Java+EE+Newscast * Keep up with the aftermath of the Oracle/Sun merger: http://www.mergerspeak.com On Tue, Sep 13, 2011 at 1:53 PM, Mike Kienenberger mkien...@gmail.comwrote: Someone should take a look at updating http://myfaces.apache.org/tomahawk/testing/hostedqa.html HostedQA looks like it now points to a generated parked domain. Autoriginate looks like it points to s3xu al1y expli_cit material. I changed the wiki entry on automated testing to remove the links. If the domain no longer works, I'd be surprised if the HostedQA account works anymore, although I have never tested it.
[jira] [Resolved] (MFCOMMONS-36) MyFaces Commons ResourceHandler should allow configuration /javax.faces.resource or ResourceHandler#RESOURCE_IDENTIFIER through a web config param
[ https://issues.apache.org/jira/browse/MFCOMMONS-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MFCOMMONS-36. - Resolution: Fixed Fix Version/s: 1.0.2-SNAPSHOT Assignee: Leonardo Uribe MyFaces Commons ResourceHandler should allow configuration /javax.faces.resource or ResourceHandler#RESOURCE_IDENTIFIER through a web config param -- Key: MFCOMMONS-36 URL: https://issues.apache.org/jira/browse/MFCOMMONS-36 Project: MyFaces Commons Issue Type: Improvement Reporter: Leonardo Uribe Assignee: Leonardo Uribe Priority: Minor Fix For: 1.0.2-SNAPSHOT See http://stackoverflow.com/questions/7354464/change-javax-faces-resource-prefix-of-resource-urls -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MFCOMMONS-36) MyFaces Commons ResourceHandler should allow configuration /javax.faces.resource or ResourceHandler#RESOURCE_IDENTIFIER through a web config param
[ https://issues.apache.org/jira/browse/MFCOMMONS-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13103908#comment-13103908 ] Leonardo Uribe commented on MFCOMMONS-36: - Added this param: /** * Indicate the prefix that is added to each resource path that is used later to check if the request is a resource request. * * By default is /javax.faces.resource */ @JSFWebConfigParam(defaultValue=/javax.faces.resource) public static final String INIT_PARAM_EXTENDED_RESOURCE_IDENTIFIER = org.apache.myfaces.commons.EXTENDED_RESOURCE_IDENTIFIER; MyFaces Commons ResourceHandler should allow configuration /javax.faces.resource or ResourceHandler#RESOURCE_IDENTIFIER through a web config param -- Key: MFCOMMONS-36 URL: https://issues.apache.org/jira/browse/MFCOMMONS-36 Project: MyFaces Commons Issue Type: Improvement Reporter: Leonardo Uribe Priority: Minor Fix For: 1.0.2-SNAPSHOT See http://stackoverflow.com/questions/7354464/change-javax-faces-resource-prefix-of-resource-urls -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TOBAGO-1027) Update jQuery to 1.6.4
[ https://issues.apache.org/jira/browse/TOBAGO-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Schnurpfeil resolved TOBAGO-1027. - Resolution: Fixed Fix Version/s: 1.5.0-beta-2 Update jQuery to 1.6.4 -- Key: TOBAGO-1027 URL: https://issues.apache.org/jira/browse/TOBAGO-1027 Project: MyFaces Tobago Issue Type: Task Components: Themes Affects Versions: 1.5.0-beta-1 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Fix For: 1.5.0-beta-2 Some new Features: * support for HTML5 data attributes * improved support (specially for attr) * differ between attr and prop -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (EXTCDI-175) introduce @ViewParam annotation for page beans
[
https://issues.apache.org/jira/browse/EXTCDI-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13104122#comment-13104122
]
Gerhard Petracek commented on EXTCDI-175:
-
the only direct approach which works without problems is:
using a request scoped bean and only strings. esp. the restriction to
request-scoped beans might be a problem for users who aren't aware of it or in
case of refactorings (because the behaviour wouldn't be expected in a cdi app).
furthermore, the impl. of such simple cases is very simple (we can include a
description in the wiki)
that means: with a producer method with the return-type string, we would
produce a dependent bean - injection in beans with longer scopes than request
scope won't work correctly/as expected.
with view-controllers it works (already prototyped) in combination with
annotated setter methods. for fields it's possible to add an interceptor
dynamically which can do the injection. but therefore we would have to inject
the values for every method call or a marker method would be needed. since we
would also need something like a RequestParameterContext to query if there was
an error in case of converting to a different type than a string or a
validation violation, we could specify a method which has to be implemented.
but in the end that's also not that nice. (or the RequestParameterContext could
be used for requestParameterContext.update(this) to update the values in beans
with scopes longer than the request scope. however, that isn't nice as well)
- a part of it works without problems, but requires annotated setters and the
real goal - manual (without producers to support custom types) field injection
- won't work without a workaround.
an alternative:
like javax.enterprise.inject.Instance we could provide:
@Inject
private RequestParameterMyCustomType param1;
in this case every use-case (mentioned above) would work and we don't need an
additional context, because we could implement everything as a part of
RequestParameter.
e.g.:
RequestParameter#isValid
RequestParameter#get //converted value
RequestParameter#getSubmittedValue //not converted
RequestParameter#getConstraintViolations
RequestParameter#getConversionError
...
introduce @ViewParam annotation for page beans
--
Key: EXTCDI-175
URL: https://issues.apache.org/jira/browse/EXTCDI-175
Project: MyFaces CODI
Issue Type: New Feature
Reporter: Mark Struberg
When using the ViewConfig in CODI we not only get type safe navigation but
also know the 'connection' between views and their backing beans. We already
support annotations like @PreRenderView and likes for such beans.
We should also support the direct annotation of view parameters directly in
the backing beans.
instead of declaring the view parameters in the xhtml:
f:metadata
f:viewParam id=versionParam name=version
value=#{backingbean.versionString} required=false/
f:viewParam id=searchString name=s value=#{backingbean.searchString}
required=false/
/f:metadata
we can maybe use an annotation directly in the backing bean:
@Named
@RequestScoped
public class Backingbean {
@ViewParam(required=false, name=version)
private String versionString;
@ViewParam(required=false, name=s)
private String searchString;
@PreRenderView
private void dosomeinit() {
...
}
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (EXTCDI-175) introduce @ViewParam annotation for page beans
[
https://issues.apache.org/jira/browse/EXTCDI-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13104123#comment-13104123
]
Gerhard Petracek commented on EXTCDI-175:
-
+1 for the approach of @Inject private RequestParameterMyCustomType param1;
introduce @ViewParam annotation for page beans
--
Key: EXTCDI-175
URL: https://issues.apache.org/jira/browse/EXTCDI-175
Project: MyFaces CODI
Issue Type: New Feature
Reporter: Mark Struberg
When using the ViewConfig in CODI we not only get type safe navigation but
also know the 'connection' between views and their backing beans. We already
support annotations like @PreRenderView and likes for such beans.
We should also support the direct annotation of view parameters directly in
the backing beans.
instead of declaring the view parameters in the xhtml:
f:metadata
f:viewParam id=versionParam name=version
value=#{backingbean.versionString} required=false/
f:viewParam id=searchString name=s value=#{backingbean.searchString}
required=false/
/f:metadata
we can maybe use an annotation directly in the backing bean:
@Named
@RequestScoped
public class Backingbean {
@ViewParam(required=false, name=version)
private String versionString;
@ViewParam(required=false, name=s)
private String searchString;
@PreRenderView
private void dosomeinit() {
...
}
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
