Result (was: Re: [VOTE] Trinidad core: 1.0.13)
Hi, thanks for voting. We got 5 votes, all were +1: -Blake Sullivan -Matthias Wessendorf -Mark Struberg -Grant Smith -Jakob Korherr I will follow up with the required steps to get the last Trinidad 1.0.x release (for JSF 1.1) out. Thanks! Matthias On Tue, Dec 21, 2010 at 1:44 PM, Matthias Wessendorf mat...@apache.org wrote: Hi, as discussed in the past, the 1.0.13 release will be the last one of our JSF 1.1 supported version. JSF 2 (Trinidad 2) will be the one line where the most efforts go into, in terms of developing Trinidad I was running the needed tasks to get the next release of the Apache MyFaces Trinidad 1.0.x CORE out. The artifacts are deployed to a staging repo ([1]). Please take a look at the 1.0.13 artifacts and vote. [ ] +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, Matthias [1] https://repository.apache.org/content/repositories/orgapachemyfaces-055/ -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [Trinidad] Future of Apache MyFaces Trinidad for 1.x and 2.x
HEllo Manuel, Trinidad 1.0.x will have one last release (see current vote result on dev@). After that there is most likely no new release of Trinidad 1.0.x (optimized for JSF 1.1) Trinidad 1.2.x will have a very few releases, basically for maintenance reasons. Trinidad 2.0.x (for JSF2) is the most 'active' development, and releases are planed. Once we (Trinidad's pom file) move to the new nexus/release infrastructure, releases are cheap and easy to do. Actually I am currently looking into this. HTH, Matthias On Wed, Jan 5, 2011 at 8:04 PM, Manuel Hartl ha...@flexsecure.de wrote: Hi Trinidad Developers, What are the future plans (if there are any) for upcoming releases for Trinidad for JSF 1.2 and JSF2 ? I am wondering, whether there will be more releases, escecially stable releases of Trinidad 2.x for JSF2!? Greetings, Manuel Hartl. -- Dipl. Inform. Manuel Hartl FlexSecure GmbH Industriestr. 12 64297 Darmstadt Tel. +49 6151 50123 18 E-Mail: ha...@flexsecure.de www.flexsecure.de -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[VOTE] Trinidad plugins: 2.0.3 release
Hi, I've created a 2.0.3 release candidate, with the following artifacts up for a vote: SVN source tag (r1057187): http://svn.apache.org/repos/asf/myfaces/trinidad-maven/tags/maven-plugin-parent-2.0.3/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachemyfaces-012/ Source release: https://repository.apache.org/content/repositories/orgapachemyfaces-012/org/apache/myfaces/trinidadbuild/maven-plugin-parent/2.0.3/maven-plugin-parent-2.0.3-source-release.zip Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[Trinidad] Beta release of Trinidad 2.0.0
Hi, there were some questions regarding the state of Trinidad 2.0; We will have a beta1 release within January. Currently we are voting on the plugins: http://markmail.org/message/tzkhsmzq3owmy6dp Once that is done, we can vote on the framework/components. By end of this week I do expect a vote for Trinidad 2.0-beta1. Sorry for the delay, please stay tuned. -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] Trinidad plugins: 2.0.3 release
+1 On Mon, Jan 10, 2011 at 2:46 PM, Matthias Wessendorf mat...@apache.org wrote: Hi, I've created a 2.0.3 release candidate, with the following artifacts up for a vote: SVN source tag (r1057187): http://svn.apache.org/repos/asf/myfaces/trinidad-maven/tags/maven-plugin-parent-2.0.3/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachemyfaces-012/ Source release: https://repository.apache.org/content/repositories/orgapachemyfaces-012/org/apache/myfaces/trinidadbuild/maven-plugin-parent/2.0.3/maven-plugin-parent-2.0.3-source-release.zip Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] Trinidad plugins: 2.0.3 release
+1 On 1/10/2011 8:46 AM, Matthias Wessendorf wrote: Hi, I've created a 2.0.3 release candidate, with the following artifacts up for a vote: SVN source tag (r1057187): http://svn.apache.org/repos/asf/myfaces/trinidad-maven/tags/maven-plugin-parent-2.0.3/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachemyfaces-012/ Source release: https://repository.apache.org/content/repositories/orgapachemyfaces-012/org/apache/myfaces/trinidadbuild/maven-plugin-parent/2.0.3/maven-plugin-parent-2.0.3-source-release.zip Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Matthias
Re: [VOTE] Trinidad plugins: 2.0.3 release
+1 -- Blake On 1/10/11 7:46 AM, MAX STARETS wrote: +1 On 1/10/2011 8:46 AM, Matthias Wessendorf wrote: Hi, I've created a 2.0.3 release candidate, with the following artifacts up for a vote: SVN source tag (r1057187): http://svn.apache.org/repos/asf/myfaces/trinidad-maven/tags/maven-plugin-parent-2.0.3/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachemyfaces-012/ Source release: https://repository.apache.org/content/repositories/orgapachemyfaces-012/org/apache/myfaces/trinidadbuild/maven-plugin-parent/2.0.3/maven-plugin-parent-2.0.3-source-release.zip Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Matthias
[VOTE] Apache MyFaces Trinidad 1.2.14
Hi, I've created a Trinidad 1.2.14 release candidate, with the following artifacts up for a vote: SVN source tag (r1057250): http://svn.apache.org/repos/asf/myfaces/trinidad/tags/trinidad-1.2.14/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachemyfaces-013/ Source release: https://repository.apache.org/content/repositories/orgapachemyfaces-013/org/apache/myfaces/trinidad/trinidad/1.2.14/trinidad-1.2.14-source-release.zip Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] Trinidad plugins: 2.0.3 release
+1 On Mon, Jan 10, 2011 at 8:27 AM, Blake Sullivan blake.sulli...@oracle.comwrote: +1 -- Blake On 1/10/11 7:46 AM, MAX STARETS wrote: +1 On 1/10/2011 8:46 AM, Matthias Wessendorf wrote: Hi, I've created a 2.0.3 release candidate, with the following artifacts up for a vote: SVN source tag (r1057187): http://svn.apache.org/repos/asf/myfaces/trinidad-maven/tags/maven-plugin-parent-2.0.3/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachemyfaces-012/ Source release: https://repository.apache.org/content/repositories/orgapachemyfaces-012/org/apache/myfaces/trinidadbuild/maven-plugin-parent/2.0.3/maven-plugin-parent-2.0.3-source-release.zip Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Matthias -- Grant Smith - V.P. Information Technology Marathon Computer Systems, LLC.
Re: [VOTE] Apache MyFaces Trinidad 1.2.14
+1 On Monday, January 10, 2011, Matthias Wessendorf mat...@apache.org wrote: Hi, I've created a Trinidad 1.2.14 release candidate, with the following artifacts up for a vote: SVN source tag (r1057250): http://svn.apache.org/repos/asf/myfaces/trinidad/tags/trinidad-1.2.14/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachemyfaces-013/ Source release: https://repository.apache.org/content/repositories/orgapachemyfaces-013/org/apache/myfaces/trinidad/trinidad/1.2.14/trinidad-1.2.14-source-release.zip Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] Apache MyFaces Trinidad 1.2.14
Hey Matthias, Although not being a team member I would like to add a comment on this. I recently had major problems deploying some of the MyFaces artifacts to the just released JBoss AS 6.0.0.Final. The problems were caused by invalid TLD descriptors generated by the MyFaces Builder Plugin. As far as I can tell the current trunk of Trinidad for JSF 1.2 is also affected by this. Perhaps it would be a good idea if somebody of the Trinidad team takes a look at this before starting the release. Please refer to the following Tomahawk issue for details: https://issues.apache.org/jira/browse/TOMAHAWK-1560 Kind regards Christian https://issues.apache.org/jira/browse/TOMAHAWK-1560 2011/1/10, Matthias Wessendorf mat...@apache.org: Hi, I've created a Trinidad 1.2.14 release candidate, with the following artifacts up for a vote: SVN source tag (r1057250): http://svn.apache.org/repos/asf/myfaces/trinidad/tags/trinidad-1.2.14/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachemyfaces-013/ Source release: https://repository.apache.org/content/repositories/orgapachemyfaces-013/org/apache/myfaces/trinidad/trinidad/1.2.14/trinidad-1.2.14-source-release.zip Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Christian Kaltepoth Blog: http://chkal.blogspot.com/ Twitter: http://twitter.com/chkal
Re: [VOTE] Apache MyFaces Trinidad 1.2.14
+1 On 1/10/11 8:28 AM, Matthias Wessendorf wrote: Hi, I've created a Trinidad 1.2.14 release candidate, with the following artifacts up for a vote: SVN source tag (r1057250): http://svn.apache.org/repos/asf/myfaces/trinidad/tags/trinidad-1.2.14/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachemyfaces-013/ Source release: https://repository.apache.org/content/repositories/orgapachemyfaces-013/org/apache/myfaces/trinidad/trinidad/1.2.14/trinidad-1.2.14-source-release.zip Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Matthias
Re: [VOTE] Trinidad plugins: 2.0.3 release
+1 On 1/10/2011 8:34 AM, Grant Smith wrote: +1 On Mon, Jan 10, 2011 at 8:27 AM, Blake Sullivan blake.sulli...@oracle.com mailto:blake.sulli...@oracle.com wrote: +1 -- Blake On 1/10/11 7:46 AM, MAX STARETS wrote: +1 On 1/10/2011 8:46 AM, Matthias Wessendorf wrote: Hi, I've created a 2.0.3 release candidate, with the following artifacts up for a vote: SVN source tag (r1057187): http://svn.apache.org/repos/asf/myfaces/trinidad-maven/tags/maven-plugin-parent-2.0.3/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachemyfaces-012/ Source release: https://repository.apache.org/content/repositories/orgapachemyfaces-012/org/apache/myfaces/trinidadbuild/maven-plugin-parent/2.0.3/maven-plugin-parent-2.0.3-source-release.zip Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Matthias -- Grant Smith - V.P. Information Technology Marathon Computer Systems, LLC.
Re: [VOTE] Apache MyFaces Trinidad 1.2.14
So basically JBoss' JavaEE 6 container is not backwards compatible to EE5. Why are the URLs and elements outdated? Aren't say valid for JavaEE 5 ? -Matthias On Mon, Jan 10, 2011 at 6:09 PM, Christian Kaltepoth christ...@kaltepoth.de wrote: Hey Matthias, Although not being a team member I would like to add a comment on this. I recently had major problems deploying some of the MyFaces artifacts to the just released JBoss AS 6.0.0.Final. The problems were caused by invalid TLD descriptors generated by the MyFaces Builder Plugin. As far as I can tell the current trunk of Trinidad for JSF 1.2 is also affected by this. Perhaps it would be a good idea if somebody of the Trinidad team takes a look at this before starting the release. Please refer to the following Tomahawk issue for details: https://issues.apache.org/jira/browse/TOMAHAWK-1560 Kind regards Christian https://issues.apache.org/jira/browse/TOMAHAWK-1560 2011/1/10, Matthias Wessendorf mat...@apache.org: Hi, I've created a Trinidad 1.2.14 release candidate, with the following artifacts up for a vote: SVN source tag (r1057250): http://svn.apache.org/repos/asf/myfaces/trinidad/tags/trinidad-1.2.14/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachemyfaces-013/ Source release: https://repository.apache.org/content/repositories/orgapachemyfaces-013/org/apache/myfaces/trinidad/trinidad/1.2.14/trinidad-1.2.14-source-release.zip Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Christian Kaltepoth Blog: http://chkal.blogspot.com/ Twitter: http://twitter.com/chkal -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] Apache MyFaces Trinidad 1.2.14
It looks like the TLD starts with the correct namespaces taglib xmlns=http://java.sun.com/xml/ns/javaee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd; version=2.1 display-nameApache Trinidad Core/display-name ... ... -Matthias On Mon, Jan 10, 2011 at 7:04 PM, Matthias Wessendorf mat...@apache.org wrote: So basically JBoss' JavaEE 6 container is not backwards compatible to EE5. Why are the URLs and elements outdated? Aren't say valid for JavaEE 5 ? -Matthias On Mon, Jan 10, 2011 at 6:09 PM, Christian Kaltepoth christ...@kaltepoth.de wrote: Hey Matthias, Although not being a team member I would like to add a comment on this. I recently had major problems deploying some of the MyFaces artifacts to the just released JBoss AS 6.0.0.Final. The problems were caused by invalid TLD descriptors generated by the MyFaces Builder Plugin. As far as I can tell the current trunk of Trinidad for JSF 1.2 is also affected by this. Perhaps it would be a good idea if somebody of the Trinidad team takes a look at this before starting the release. Please refer to the following Tomahawk issue for details: https://issues.apache.org/jira/browse/TOMAHAWK-1560 Kind regards Christian https://issues.apache.org/jira/browse/TOMAHAWK-1560 2011/1/10, Matthias Wessendorf mat...@apache.org: Hi, I've created a Trinidad 1.2.14 release candidate, with the following artifacts up for a vote: SVN source tag (r1057250): http://svn.apache.org/repos/asf/myfaces/trinidad/tags/trinidad-1.2.14/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachemyfaces-013/ Source release: https://repository.apache.org/content/repositories/orgapachemyfaces-013/org/apache/myfaces/trinidad/trinidad/1.2.14/trinidad-1.2.14-source-release.zip Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Christian Kaltepoth Blog: http://chkal.blogspot.com/ Twitter: http://twitter.com/chkal -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] Apache MyFaces Trinidad 1.2.14
looks like we are OK here. (currently downloading JBoss to check details early 2morrow) -M On Mon, Jan 10, 2011 at 7:06 PM, Matthias Wessendorf mat...@apache.org wrote: It looks like the TLD starts with the correct namespaces taglib xmlns=http://java.sun.com/xml/ns/javaee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd; version=2.1 display-nameApache Trinidad Core/display-name ... ... -Matthias On Mon, Jan 10, 2011 at 7:04 PM, Matthias Wessendorf mat...@apache.org wrote: So basically JBoss' JavaEE 6 container is not backwards compatible to EE5. Why are the URLs and elements outdated? Aren't say valid for JavaEE 5 ? -Matthias On Mon, Jan 10, 2011 at 6:09 PM, Christian Kaltepoth christ...@kaltepoth.de wrote: Hey Matthias, Although not being a team member I would like to add a comment on this. I recently had major problems deploying some of the MyFaces artifacts to the just released JBoss AS 6.0.0.Final. The problems were caused by invalid TLD descriptors generated by the MyFaces Builder Plugin. As far as I can tell the current trunk of Trinidad for JSF 1.2 is also affected by this. Perhaps it would be a good idea if somebody of the Trinidad team takes a look at this before starting the release. Please refer to the following Tomahawk issue for details: https://issues.apache.org/jira/browse/TOMAHAWK-1560 Kind regards Christian https://issues.apache.org/jira/browse/TOMAHAWK-1560 2011/1/10, Matthias Wessendorf mat...@apache.org: Hi, I've created a Trinidad 1.2.14 release candidate, with the following artifacts up for a vote: SVN source tag (r1057250): http://svn.apache.org/repos/asf/myfaces/trinidad/tags/trinidad-1.2.14/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachemyfaces-013/ Source release: https://repository.apache.org/content/repositories/orgapachemyfaces-013/org/apache/myfaces/trinidad/trinidad/1.2.14/trinidad-1.2.14-source-release.zip Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Christian Kaltepoth Blog: http://chkal.blogspot.com/ Twitter: http://twitter.com/chkal -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] Apache MyFaces Trinidad 1.2.14
meh... 19:22:49,086 WARN [SaxJBossXBParser] SchemaLocation: schemaLocation value = 'http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd' must have even number of URI's. @ vfs:///home/matzew/JBoss6/jboss-6.0.0.Final/server/default/deploy/trinidad-demo-1.2.14.war/WEB-INF/lib/trinidad-impl-1.2.14.jar/META-INF/tr.tld[1,238] 19:22:49,102 WARN [JBossEntityResolver] Trying to resolve systemId as a non-file URL: http://java.sun.com/xml/ns/javaee this sucks :) Question is... should the container resolve it, or is the current behavior OK... -Matthias On Mon, Jan 10, 2011 at 7:08 PM, Matthias Wessendorf mat...@apache.org wrote: looks like we are OK here. (currently downloading JBoss to check details early 2morrow) -M On Mon, Jan 10, 2011 at 7:06 PM, Matthias Wessendorf mat...@apache.org wrote: It looks like the TLD starts with the correct namespaces taglib xmlns=http://java.sun.com/xml/ns/javaee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd; version=2.1 display-nameApache Trinidad Core/display-name ... ... -Matthias On Mon, Jan 10, 2011 at 7:04 PM, Matthias Wessendorf mat...@apache.org wrote: So basically JBoss' JavaEE 6 container is not backwards compatible to EE5. Why are the URLs and elements outdated? Aren't say valid for JavaEE 5 ? -Matthias On Mon, Jan 10, 2011 at 6:09 PM, Christian Kaltepoth christ...@kaltepoth.de wrote: Hey Matthias, Although not being a team member I would like to add a comment on this. I recently had major problems deploying some of the MyFaces artifacts to the just released JBoss AS 6.0.0.Final. The problems were caused by invalid TLD descriptors generated by the MyFaces Builder Plugin. As far as I can tell the current trunk of Trinidad for JSF 1.2 is also affected by this. Perhaps it would be a good idea if somebody of the Trinidad team takes a look at this before starting the release. Please refer to the following Tomahawk issue for details: https://issues.apache.org/jira/browse/TOMAHAWK-1560 Kind regards Christian https://issues.apache.org/jira/browse/TOMAHAWK-1560 2011/1/10, Matthias Wessendorf mat...@apache.org: Hi, I've created a Trinidad 1.2.14 release candidate, with the following artifacts up for a vote: SVN source tag (r1057250): http://svn.apache.org/repos/asf/myfaces/trinidad/tags/trinidad-1.2.14/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachemyfaces-013/ Source release: https://repository.apache.org/content/repositories/orgapachemyfaces-013/org/apache/myfaces/trinidad/trinidad/1.2.14/trinidad-1.2.14-source-release.zip Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Christian Kaltepoth Blog: http://chkal.blogspot.com/ Twitter: http://twitter.com/chkal -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] Apache MyFaces Trinidad 1.2.14
I think JBoss is expecting a full schemaLocation attribute including the namespace AND the physical location of the XSD file separated by a space character. Something like: xsi:schemaLocation=http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd; Christian 2011/1/10 Matthias Wessendorf mat...@apache.org: It looks like the TLD starts with the correct namespaces taglib xmlns=http://java.sun.com/xml/ns/javaee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd; version=2.1 display-nameApache Trinidad Core/display-name ... ... -Matthias On Mon, Jan 10, 2011 at 7:04 PM, Matthias Wessendorf mat...@apache.org wrote: So basically JBoss' JavaEE 6 container is not backwards compatible to EE5. Why are the URLs and elements outdated? Aren't say valid for JavaEE 5 ? -Matthias On Mon, Jan 10, 2011 at 6:09 PM, Christian Kaltepoth christ...@kaltepoth.de wrote: Hey Matthias, Although not being a team member I would like to add a comment on this. I recently had major problems deploying some of the MyFaces artifacts to the just released JBoss AS 6.0.0.Final. The problems were caused by invalid TLD descriptors generated by the MyFaces Builder Plugin. As far as I can tell the current trunk of Trinidad for JSF 1.2 is also affected by this. Perhaps it would be a good idea if somebody of the Trinidad team takes a look at this before starting the release. Please refer to the following Tomahawk issue for details: https://issues.apache.org/jira/browse/TOMAHAWK-1560 Kind regards Christian https://issues.apache.org/jira/browse/TOMAHAWK-1560 2011/1/10, Matthias Wessendorf mat...@apache.org: Hi, I've created a Trinidad 1.2.14 release candidate, with the following artifacts up for a vote: SVN source tag (r1057250): http://svn.apache.org/repos/asf/myfaces/trinidad/tags/trinidad-1.2.14/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachemyfaces-013/ Source release: https://repository.apache.org/content/repositories/orgapachemyfaces-013/org/apache/myfaces/trinidad/trinidad/1.2.14/trinidad-1.2.14-source-release.zip Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Christian Kaltepoth Blog: http://chkal.blogspot.com/ Twitter: http://twitter.com/chkal -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Christian Kaltepoth Blog: http://chkal.blogspot.com/ Twitter: http://twitter.com/chkal
Re: [VOTE] Apache MyFaces Trinidad 1.2.14
As far as I know the schemaLocation attribute must always contain the namespace and the location of the XSD file. Specifying only the location of the XSD is wrong in my option as it is not clear for which namespace the XSD is (without downloading it of cause). But I might be wrong. I didn't find the correct section in the spec yet! :-) Christian 2011/1/10 Matthias Wessendorf mat...@apache.org: meh... 19:22:49,086 WARN [SaxJBossXBParser] SchemaLocation: schemaLocation value = 'http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd' must have even number of URI's. @ vfs:///home/matzew/JBoss6/jboss-6.0.0.Final/server/default/deploy/trinidad-demo-1.2.14.war/WEB-INF/lib/trinidad-impl-1.2.14.jar/META-INF/tr.tld[1,238] 19:22:49,102 WARN [JBossEntityResolver] Trying to resolve systemId as a non-file URL: http://java.sun.com/xml/ns/javaee this sucks :) Question is... should the container resolve it, or is the current behavior OK... -Matthias On Mon, Jan 10, 2011 at 7:08 PM, Matthias Wessendorf mat...@apache.org wrote: looks like we are OK here. (currently downloading JBoss to check details early 2morrow) -M On Mon, Jan 10, 2011 at 7:06 PM, Matthias Wessendorf mat...@apache.org wrote: It looks like the TLD starts with the correct namespaces taglib xmlns=http://java.sun.com/xml/ns/javaee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd; version=2.1 display-nameApache Trinidad Core/display-name ... ... -Matthias On Mon, Jan 10, 2011 at 7:04 PM, Matthias Wessendorf mat...@apache.org wrote: So basically JBoss' JavaEE 6 container is not backwards compatible to EE5. Why are the URLs and elements outdated? Aren't say valid for JavaEE 5 ? -Matthias On Mon, Jan 10, 2011 at 6:09 PM, Christian Kaltepoth christ...@kaltepoth.de wrote: Hey Matthias, Although not being a team member I would like to add a comment on this. I recently had major problems deploying some of the MyFaces artifacts to the just released JBoss AS 6.0.0.Final. The problems were caused by invalid TLD descriptors generated by the MyFaces Builder Plugin. As far as I can tell the current trunk of Trinidad for JSF 1.2 is also affected by this. Perhaps it would be a good idea if somebody of the Trinidad team takes a look at this before starting the release. Please refer to the following Tomahawk issue for details: https://issues.apache.org/jira/browse/TOMAHAWK-1560 Kind regards Christian https://issues.apache.org/jira/browse/TOMAHAWK-1560 2011/1/10, Matthias Wessendorf mat...@apache.org: Hi, I've created a Trinidad 1.2.14 release candidate, with the following artifacts up for a vote: SVN source tag (r1057250): http://svn.apache.org/repos/asf/myfaces/trinidad/tags/trinidad-1.2.14/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachemyfaces-013/ Source release: https://repository.apache.org/content/repositories/orgapachemyfaces-013/org/apache/myfaces/trinidad/trinidad/1.2.14/trinidad-1.2.14-source-release.zip Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Christian Kaltepoth Blog: http://chkal.blogspot.com/ Twitter: http://twitter.com/chkal -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Christian Kaltepoth Blog: http://chkal.blogspot.com/ Twitter: http://twitter.com/chkal
[core] Improve error reporting and logging
Hi, the most wanted feature which our coders want is more consistent and human-readable error reporting and logging. Here is a example: If user specifies f:ajax without eventName for a component without defaultEventName, myfaces throw a execption: Now (myfaces 2.0.3): eventName could not be defined for f:ajax tag with no wrap mode. Improved (example only; from my copy of myfaces): MF0345: Your ajax tag does not specify eventName and component com.foo.Bazz does not provide the default one. Please use one from available: [change, blur, focus ...]; Tag location: XYZ.xhtml line 56 column 23, f:ajax . / Component: id: componentId, class: com.foo.BazzInput, component type: org.renderkit.Input ViewId: YYZ.xhml, located in file system as: /tmp/deploy/weabpp/XYZ.xhtml PhaseId: RENDER_RESPONSE Details: ... a detailed description of this problem + suggestions, example of code. References: # Click for problem MF0345 in MYFACES knowledge database (hypertext link) # Contact your technology team : m...@to.me # If you think this a bug report it: jira.project.org What do you think about this idea? (I'll describe our requirements and what I found so far in next emails) Regards, Kočičák
Re: [core] Improve error reporting and logging
Hi Kocicak, 1 Regards, Jakob 2011/1/10 Martin Koci martin.kocicak.k...@gmail.com: Hi, the most wanted feature which our coders want is more consistent and human-readable error reporting and logging. Here is a example: If user specifies f:ajax without eventName for a component without defaultEventName, myfaces throw a execption: Now (myfaces 2.0.3): eventName could not be defined for f:ajax tag with no wrap mode. Improved (example only; from my copy of myfaces): MF0345: Your ajax tag does not specify eventName and component com.foo.Bazz does not provide the default one. Please use one from available: [change, blur, focus ...]; Tag location: XYZ.xhtml line 56 column 23, f:ajax . / Component: id: componentId, class: com.foo.BazzInput, component type: org.renderkit.Input ViewId: YYZ.xhml, located in file system as: /tmp/deploy/weabpp/XYZ.xhtml PhaseId: RENDER_RESPONSE Details: ... a detailed description of this problem + suggestions, example of code. References: # Click for problem MF0345 in MYFACES knowledge database (hypertext link) # Contact your technology team : m...@to.me # If you think this a bug report it: jira.project.org What do you think about this idea? (I'll describe our requirements and what I found so far in next emails) Regards, Kočičák -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at
[jira] Created: (TRINIDAD-2002) TrinidadFilterImpl FacesContext initialization
TrinidadFilterImpl FacesContext initialization -- Key: TRINIDAD-2002 URL: https://issues.apache.org/jira/browse/TRINIDAD-2002 Project: MyFaces Trinidad Issue Type: Improvement Affects Versions: 2.0.0-alpha Reporter: Andy Schwartz Priority: Minor ADF Faces hooks into Trinidad's TrinidadFilterImpl sub-filter service and uses this to perform early configuration/initialization work. In particular, we use the ApplicationFactory to get at the Application instance and then create/add converters to the Application. This works fine on Mojarra 2.0.x releases. However, this fails in both: - MyFaces 2.0.x - Mojarra 2.1.x In both cases, the reason for the failure is that access to the FacesContext is required but is not yet available. In MyFaces 2.0.x, the FacesContext/ExternalContext is required by Application.createConverter()/setConverterProperties() in order to determine the value of the javax.faces.DATETIMECONVERTER_DEFAULT_TIMEZONE_IS_SYSTEM_TIMEZONE context parameter. In Mojarra 2.1.x, the ApplicationFactory requires access to the FacesContext in order to create the Application instance. While we can work around this issue at the ADF Faces level, TrinidadFilterImpl is already well positioned to address this - ie. TrinidadFilterImpl has access to the PseudoFacesContext and already sets this up for other cases (eg. for Configurator.beginRequest()). I am logging this issue to request that we take advantage of the existing support that TrinidadFilterImpl/PseudoFacesContext provides for early FacesContext access and extend this to TrinidadFilterImpl.init(). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-2002) TrinidadFilterImpl FacesContext initialization
[ https://issues.apache.org/jira/browse/TRINIDAD-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12979792#action_12979792 ] Andy Schwartz commented on TRINIDAD-2002: - This patch: https://issues.apache.org/jira/secure/attachment/12467925/TRINIDAD-2002.patch Demonstrates how we might implement this change. TrinidadFilterImpl FacesContext initialization -- Key: TRINIDAD-2002 URL: https://issues.apache.org/jira/browse/TRINIDAD-2002 Project: MyFaces Trinidad Issue Type: Improvement Affects Versions: 2.0.0-alpha Reporter: Andy Schwartz Priority: Minor Attachments: TRINIDAD-2002.patch ADF Faces hooks into Trinidad's TrinidadFilterImpl sub-filter service and uses this to perform early configuration/initialization work. In particular, we use the ApplicationFactory to get at the Application instance and then create/add converters to the Application. This works fine on Mojarra 2.0.x releases. However, this fails in both: - MyFaces 2.0.x - Mojarra 2.1.x In both cases, the reason for the failure is that access to the FacesContext is required but is not yet available. In MyFaces 2.0.x, the FacesContext/ExternalContext is required by Application.createConverter()/setConverterProperties() in order to determine the value of the javax.faces.DATETIMECONVERTER_DEFAULT_TIMEZONE_IS_SYSTEM_TIMEZONE context parameter. In Mojarra 2.1.x, the ApplicationFactory requires access to the FacesContext in order to create the Application instance. While we can work around this issue at the ADF Faces level, TrinidadFilterImpl is already well positioned to address this - ie. TrinidadFilterImpl has access to the PseudoFacesContext and already sets this up for other cases (eg. for Configurator.beginRequest()). I am logging this issue to request that we take advantage of the existing support that TrinidadFilterImpl/PseudoFacesContext provides for early FacesContext access and extend this to TrinidadFilterImpl.init(). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-2002) TrinidadFilterImpl FacesContext initialization
[ https://issues.apache.org/jira/browse/TRINIDAD-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Schwartz updated TRINIDAD-2002: Status: Patch Available (was: Open) TrinidadFilterImpl FacesContext initialization -- Key: TRINIDAD-2002 URL: https://issues.apache.org/jira/browse/TRINIDAD-2002 Project: MyFaces Trinidad Issue Type: Improvement Affects Versions: 2.0.0-alpha Reporter: Andy Schwartz Priority: Minor Attachments: TRINIDAD-2002.patch ADF Faces hooks into Trinidad's TrinidadFilterImpl sub-filter service and uses this to perform early configuration/initialization work. In particular, we use the ApplicationFactory to get at the Application instance and then create/add converters to the Application. This works fine on Mojarra 2.0.x releases. However, this fails in both: - MyFaces 2.0.x - Mojarra 2.1.x In both cases, the reason for the failure is that access to the FacesContext is required but is not yet available. In MyFaces 2.0.x, the FacesContext/ExternalContext is required by Application.createConverter()/setConverterProperties() in order to determine the value of the javax.faces.DATETIMECONVERTER_DEFAULT_TIMEZONE_IS_SYSTEM_TIMEZONE context parameter. In Mojarra 2.1.x, the ApplicationFactory requires access to the FacesContext in order to create the Application instance. While we can work around this issue at the ADF Faces level, TrinidadFilterImpl is already well positioned to address this - ie. TrinidadFilterImpl has access to the PseudoFacesContext and already sets this up for other cases (eg. for Configurator.beginRequest()). I am logging this issue to request that we take advantage of the existing support that TrinidadFilterImpl/PseudoFacesContext provides for early FacesContext access and extend this to TrinidadFilterImpl.init(). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (MYFACES-2920) UISelectOne/UISelectMany validateValue: Before comparing each option, coerce the option value type to the type of component's value
[ https://issues.apache.org/jira/browse/MYFACES-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe reopened MYFACES-2920: - Assignee: Leonardo Uribe Reopening this issue, since later tests revealed problems (see MYFACES-3010 and MYFACES-3011). UISelectOne/UISelectMany validateValue: Before comparing each option, coerce the option value type to the type of component's value --- Key: MYFACES-2920 URL: https://issues.apache.org/jira/browse/MYFACES-2920 Project: MyFaces Core Issue Type: Bug Components: JSR-314 Affects Versions: 2.0.2-SNAPSHOT Environment: myfaces trunk Reporter: Martin Kočí Assignee: Leonardo Uribe Fix For: 2.0.3 Attachments: MYFACES-2920-v2.patch, MYFACES-2920.patch Original Estimate: 0h Remaining Estimate: 0h From JavaDoc UISelectOne/UISelectMany validateValue: ... Before comparing each option, coerce the option value type to the type of this component's value following the Expression Language coercion rules ... More here: http://markmail.org/message/mfhyyiogaz73yfr4 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-3010) 2.0.3 REGRESSION: javax.faces.component._ClassUtils.convertToType
[ https://issues.apache.org/jira/browse/MYFACES-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12979820#action_12979820 ] Kennard Consulting commented on MYFACES-3010: - The IllegalArgumentException is below. Note it appears to be specific to my app, but does not occur with previous versions of MyFaces (2.0.2, JSF 1.2 and JSF 1.1) or with Mojarra: javax.faces.FacesException: java.lang.IllegalArgumentException: Cannot convert Personal of type class org.metawidget.example.shared.addressbook.model.ContactType$1 to class org.metawidget.example.shared.addressbook.model.ContactType$2 at org.apache.myfaces.shared_impl.context.ExceptionHandlerImpl.wrap(ExceptionHandlerImpl.java:241) at org.apache.myfaces.shared_impl.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:156) at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:191) at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:189) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.IllegalArgumentException: Cannot convert Personal of type class org.metawidget.example.shared.addressbook.model.ContactType$1 to class org.metawidget.example.shared.addressbook.model.ContactType$2 at org.apache.el.lang.ELSupport.coerceToType(ELSupport.java:375) at org.apache.el.ExpressionFactoryImpl.coerceToType(ExpressionFactoryImpl.java:46) at javax.faces.component._ClassUtils.convertToType(_ClassUtils.java:337) at javax.faces.component._SelectItemsUtil._convertOrCoerceValue(_SelectItemsUtil.java:133) at javax.faces.component._SelectItemsUtil.matchValue(_SelectItemsUtil.java:65) at javax.faces.component.UISelectOne.validateValue(UISelectOne.java:77) at javax.faces.component.UIInput.validate(UIInput.java:583) at javax.faces.component.UIInput.processValidators(UIInput.java:247) at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1218) at javax.faces.component.UIForm.processValidators(UIForm.java:147) at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1218) at javax.faces.component.UIViewRoot._processValidatorsDefault(UIViewRoot.java:1322) at javax.faces.component.UIViewRoot.access$500(UIViewRoot.java:75) at javax.faces.component.UIViewRoot$ProcessValidatorPhaseProcessor.process(UIViewRoot.java:1397) at javax.faces.component.UIViewRoot._process(UIViewRoot.java:1278) at javax.faces.component.UIViewRoot.processValidators(UIViewRoot.java:754) at org.apache.myfaces.lifecycle.ProcessValidationsExecutor.execute(ProcessValidationsExecutor.java:34) at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:171) ... 14 more 2.0.3 REGRESSION: javax.faces.component._ClassUtils.convertToType - Key: MYFACES-3010 URL: https://issues.apache.org/jira/browse/MYFACES-3010 Project: MyFaces Core Issue Type: Bug Components: General Affects Versions: 2.0.3 Reporter: Kennard Consulting Priority: Critical Attachments: addressbook-faces2.zip Hi guys, Thanks again for the great work you do on MyFaces and your fantastic JIRA response times! I attach a small app that comes from the Metawidget (http://metawidget.org) distribution. I had you do MYFACES-2935 for me for MyFaces 2.0.3, and my app was working great with the 2.0.3-impl-SNAPSHOT.jar and the 2.0.2-api.jar. However now that 2.0.3 is out for real I have tried to upgrade my app, and it fails. To reproduce, please: 1. Unzip the
[jira] Commented: (MYFACES-3010) 2.0.3 REGRESSION: javax.faces.component._ClassUtils.convertToType
[ https://issues.apache.org/jira/browse/MYFACES-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12979858#action_12979858 ] Kennard Consulting commented on MYFACES-3010: - Thanks for discovering that, Leonardo! Where do we go from here? 2.0.3 REGRESSION: javax.faces.component._ClassUtils.convertToType - Key: MYFACES-3010 URL: https://issues.apache.org/jira/browse/MYFACES-3010 Project: MyFaces Core Issue Type: Bug Components: General Affects Versions: 2.0.3 Reporter: Kennard Consulting Priority: Critical Attachments: addressbook-faces2.zip Hi guys, Thanks again for the great work you do on MyFaces and your fantastic JIRA response times! I attach a small app that comes from the Metawidget (http://metawidget.org) distribution. I had you do MYFACES-2935 for me for MyFaces 2.0.3, and my app was working great with the 2.0.3-impl-SNAPSHOT.jar and the 2.0.2-api.jar. However now that 2.0.3 is out for real I have tried to upgrade my app, and it fails. To reproduce, please: 1. Unzip the attached app and deploy as an exploded WAR into Tomcat 2. Run Tomcat and hit http://localhost:8080/addressbook-faces2 3. In the Type dropdown, choose 'Business' and click Search You will see an IllegalArgumentException. Now: 4. Stop Tomcat 5. Inside the exploded WAR, rename myfaces-api-2.0.2.rename.me to myfaces-api-2.0.2.jar (and delete/rename myfaces-api-2.0.3.jar) 6. Restart Tomcat and repeat steps 1-3 This time you will see no such error. So something appears to have broken between myfaces-api-2.0.2.jar and myfaces-api-2.0.3.jar? Hopefully you can reproduce this and it is enough for you to debug the issue. The source code for the small app can be viewed here: http://metawidget.svn.sourceforge.net/viewvc/metawidget/trunk/examples/src/java/org/metawidget/example/faces/addressbook/ http://metawidget.svn.sourceforge.net/viewvc/metawidget/trunk/examples/src/java/org/metawidget/example/shared/addressbook/ Of course, this could well be a case of 2.0.3 being stricter about something and therefore exposing a bug in my code. But my code worked in 2.0.2, JSF 1.2 and JSF 1.1, so hopefully not! Regards, Richard -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-3010) 2.0.3 REGRESSION: javax.faces.component._ClassUtils.convertToType
[ https://issues.apache.org/jira/browse/MYFACES-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12979873#action_12979873 ] Leonardo Uribe commented on MYFACES-3010: - The problem is on the patch applied on MYFACES-2920, we did not take into account other cases when a custom class is used and the values are inherited from a base class. The context where this coercion happens, is to compare a itemValue with the current value, just to check if the selection submitted is valid. The IllegalArgumentException just say that we can't coerce the itemValue to the value class, but that does not means the match should fail. Instead, if the IllegalArgumentException or any other Exception is thrown, we just fallback to use the value without any coercion (in this case selectItem.getValue() ) and swallow the Exception, because after all, it is no relevant. Note if the submitted value can't be matched with a itemValue of the component, an Exception will be thrown later. The other consideration supporting the swallow any exception solution is the posibility that EL coercion could be configured in later versions of unified EL. I think in this case we should wrap the call to _ClassUtils.convertToType in a try / catch block, but I would like to add some junit cases first. 2.0.3 REGRESSION: javax.faces.component._ClassUtils.convertToType - Key: MYFACES-3010 URL: https://issues.apache.org/jira/browse/MYFACES-3010 Project: MyFaces Core Issue Type: Bug Components: General Affects Versions: 2.0.3 Reporter: Kennard Consulting Priority: Critical Attachments: addressbook-faces2.zip Hi guys, Thanks again for the great work you do on MyFaces and your fantastic JIRA response times! I attach a small app that comes from the Metawidget (http://metawidget.org) distribution. I had you do MYFACES-2935 for me for MyFaces 2.0.3, and my app was working great with the 2.0.3-impl-SNAPSHOT.jar and the 2.0.2-api.jar. However now that 2.0.3 is out for real I have tried to upgrade my app, and it fails. To reproduce, please: 1. Unzip the attached app and deploy as an exploded WAR into Tomcat 2. Run Tomcat and hit http://localhost:8080/addressbook-faces2 3. In the Type dropdown, choose 'Business' and click Search You will see an IllegalArgumentException. Now: 4. Stop Tomcat 5. Inside the exploded WAR, rename myfaces-api-2.0.2.rename.me to myfaces-api-2.0.2.jar (and delete/rename myfaces-api-2.0.3.jar) 6. Restart Tomcat and repeat steps 1-3 This time you will see no such error. So something appears to have broken between myfaces-api-2.0.2.jar and myfaces-api-2.0.3.jar? Hopefully you can reproduce this and it is enough for you to debug the issue. The source code for the small app can be viewed here: http://metawidget.svn.sourceforge.net/viewvc/metawidget/trunk/examples/src/java/org/metawidget/example/faces/addressbook/ http://metawidget.svn.sourceforge.net/viewvc/metawidget/trunk/examples/src/java/org/metawidget/example/shared/addressbook/ Of course, this could well be a case of 2.0.3 being stricter about something and therefore exposing a bug in my code. But my code worked in 2.0.2, JSF 1.2 and JSF 1.1, so hopefully not! Regards, Richard -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-3010) 2.0.3 REGRESSION: javax.faces.component._ClassUtils.convertToType
[ https://issues.apache.org/jira/browse/MYFACES-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12979875#action_12979875 ] Kennard Consulting commented on MYFACES-3010: - Okay terrific. I look forward to hearing what you work out, and am very willing to test any changes you want to try. Regards, Richard. 2.0.3 REGRESSION: javax.faces.component._ClassUtils.convertToType - Key: MYFACES-3010 URL: https://issues.apache.org/jira/browse/MYFACES-3010 Project: MyFaces Core Issue Type: Bug Components: General Affects Versions: 2.0.3 Reporter: Kennard Consulting Priority: Critical Attachments: addressbook-faces2.zip Hi guys, Thanks again for the great work you do on MyFaces and your fantastic JIRA response times! I attach a small app that comes from the Metawidget (http://metawidget.org) distribution. I had you do MYFACES-2935 for me for MyFaces 2.0.3, and my app was working great with the 2.0.3-impl-SNAPSHOT.jar and the 2.0.2-api.jar. However now that 2.0.3 is out for real I have tried to upgrade my app, and it fails. To reproduce, please: 1. Unzip the attached app and deploy as an exploded WAR into Tomcat 2. Run Tomcat and hit http://localhost:8080/addressbook-faces2 3. In the Type dropdown, choose 'Business' and click Search You will see an IllegalArgumentException. Now: 4. Stop Tomcat 5. Inside the exploded WAR, rename myfaces-api-2.0.2.rename.me to myfaces-api-2.0.2.jar (and delete/rename myfaces-api-2.0.3.jar) 6. Restart Tomcat and repeat steps 1-3 This time you will see no such error. So something appears to have broken between myfaces-api-2.0.2.jar and myfaces-api-2.0.3.jar? Hopefully you can reproduce this and it is enough for you to debug the issue. The source code for the small app can be viewed here: http://metawidget.svn.sourceforge.net/viewvc/metawidget/trunk/examples/src/java/org/metawidget/example/faces/addressbook/ http://metawidget.svn.sourceforge.net/viewvc/metawidget/trunk/examples/src/java/org/metawidget/example/shared/addressbook/ Of course, this could well be a case of 2.0.3 being stricter about something and therefore exposing a bug in my code. But my code worked in 2.0.2, JSF 1.2 and JSF 1.1, so hopefully not! Regards, Richard -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (MYFACES-3010) 2.0.3 REGRESSION: javax.faces.component._ClassUtils.convertToType
[ https://issues.apache.org/jira/browse/MYFACES-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12979948#action_12979948 ] Imre Osswald edited comment on MYFACES-3010 at 1/11/11 12:16 AM: - Hi Leonardo, i'd like to suggest to add another Version of this method to _ClassUtils convertToTypeNoLogging or convertToType(Object value, Class? desiredClass, boolean doLog) so that: 1) No String concatenation has to take place 2) The log is not spammed with SEVERE messages Also I am not sure if you - in this usecase - want to catch any Exception or only the ones thrown in response to an IllegalArgument (not sure if ELExceptions might be thrown in similar cases) (BTW/OT: I would say that EL coercion is configurable already. Either by registering it's own ExpressionFactory or as far as I know by registering PropertyEditors) Regards, Imre was (Author: ioss): Hi Leonardo, i'd like to suggest to add another Version of this method to _ClassUtils convertToTypeNoLogging or convertToType(Object value, Class? desiredClass, boolean doLog) so that: 1) No String concatenation has to take place 2) The log is not spammed with SEVERE messages Also I am not sure if you - this usecase - want to catch any Exception or only the ones thrown in response to an IllegalArgument (not sure if ELExceptions might be thrown in similar cases) (BTW/OT: I would say that EL coercion is configurable already. Either by registering it's own ExpressionFactory or as far as I know by registering PropertyEditors) Regards, Imre 2.0.3 REGRESSION: javax.faces.component._ClassUtils.convertToType - Key: MYFACES-3010 URL: https://issues.apache.org/jira/browse/MYFACES-3010 Project: MyFaces Core Issue Type: Bug Components: General Affects Versions: 2.0.3 Reporter: Kennard Consulting Priority: Critical Attachments: addressbook-faces2.zip Hi guys, Thanks again for the great work you do on MyFaces and your fantastic JIRA response times! I attach a small app that comes from the Metawidget (http://metawidget.org) distribution. I had you do MYFACES-2935 for me for MyFaces 2.0.3, and my app was working great with the 2.0.3-impl-SNAPSHOT.jar and the 2.0.2-api.jar. However now that 2.0.3 is out for real I have tried to upgrade my app, and it fails. To reproduce, please: 1. Unzip the attached app and deploy as an exploded WAR into Tomcat 2. Run Tomcat and hit http://localhost:8080/addressbook-faces2 3. In the Type dropdown, choose 'Business' and click Search You will see an IllegalArgumentException. Now: 4. Stop Tomcat 5. Inside the exploded WAR, rename myfaces-api-2.0.2.rename.me to myfaces-api-2.0.2.jar (and delete/rename myfaces-api-2.0.3.jar) 6. Restart Tomcat and repeat steps 1-3 This time you will see no such error. So something appears to have broken between myfaces-api-2.0.2.jar and myfaces-api-2.0.3.jar? Hopefully you can reproduce this and it is enough for you to debug the issue. The source code for the small app can be viewed here: http://metawidget.svn.sourceforge.net/viewvc/metawidget/trunk/examples/src/java/org/metawidget/example/faces/addressbook/ http://metawidget.svn.sourceforge.net/viewvc/metawidget/trunk/examples/src/java/org/metawidget/example/shared/addressbook/ Of course, this could well be a case of 2.0.3 being stricter about something and therefore exposing a bug in my code. But my code worked in 2.0.2, JSF 1.2 and JSF 1.1, so hopefully not! Regards, Richard -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-3010) 2.0.3 REGRESSION: javax.faces.component._ClassUtils.convertToType
[ https://issues.apache.org/jira/browse/MYFACES-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12979948#action_12979948 ] Imre Osswald commented on MYFACES-3010: --- Hi Leonardo, i'd like to suggest to add another Version of this method to _ClassUtils convertToTypeNoLogging or convertToType(Object value, Class? desiredClass, boolean doLog) so that: 1) No String concatenation has to take place 2) The log is not spammed with SEVERE messages Also I am not sure if you - this usecase - want to catch any Exception or only the ones thrown in response to an IllegalArgument (not sure if ELExceptions might be thrown in similar cases) (BTW/OT: I would say that EL coercion is configurable already. Either by registering it's own ExpressionFactory or as far as I know by registering PropertyEditors) Regards, Imre 2.0.3 REGRESSION: javax.faces.component._ClassUtils.convertToType - Key: MYFACES-3010 URL: https://issues.apache.org/jira/browse/MYFACES-3010 Project: MyFaces Core Issue Type: Bug Components: General Affects Versions: 2.0.3 Reporter: Kennard Consulting Priority: Critical Attachments: addressbook-faces2.zip Hi guys, Thanks again for the great work you do on MyFaces and your fantastic JIRA response times! I attach a small app that comes from the Metawidget (http://metawidget.org) distribution. I had you do MYFACES-2935 for me for MyFaces 2.0.3, and my app was working great with the 2.0.3-impl-SNAPSHOT.jar and the 2.0.2-api.jar. However now that 2.0.3 is out for real I have tried to upgrade my app, and it fails. To reproduce, please: 1. Unzip the attached app and deploy as an exploded WAR into Tomcat 2. Run Tomcat and hit http://localhost:8080/addressbook-faces2 3. In the Type dropdown, choose 'Business' and click Search You will see an IllegalArgumentException. Now: 4. Stop Tomcat 5. Inside the exploded WAR, rename myfaces-api-2.0.2.rename.me to myfaces-api-2.0.2.jar (and delete/rename myfaces-api-2.0.3.jar) 6. Restart Tomcat and repeat steps 1-3 This time you will see no such error. So something appears to have broken between myfaces-api-2.0.2.jar and myfaces-api-2.0.3.jar? Hopefully you can reproduce this and it is enough for you to debug the issue. The source code for the small app can be viewed here: http://metawidget.svn.sourceforge.net/viewvc/metawidget/trunk/examples/src/java/org/metawidget/example/faces/addressbook/ http://metawidget.svn.sourceforge.net/viewvc/metawidget/trunk/examples/src/java/org/metawidget/example/shared/addressbook/ Of course, this could well be a case of 2.0.3 being stricter about something and therefore exposing a bug in my code. But my code worked in 2.0.2, JSF 1.2 and JSF 1.1, so hopefully not! Regards, Richard -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (MYFACES-3010) 2.0.3 REGRESSION: javax.faces.component._ClassUtils.convertToType
[ https://issues.apache.org/jira/browse/MYFACES-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12979948#action_12979948 ] Imre Osswald edited comment on MYFACES-3010 at 1/11/11 12:17 AM: - Hi Leonardo, i'd like to suggest to add another Version of this method to _ClassUtils convertToTypeNoLogging or convertToType(Object value, Class? desiredClass, boolean doLog) so that: 1) No String concatenation has to take place 2) The log is not spammed with SEVERE messages Also I am not sure if you - in this usecase - want to catch every Exceptions or only the ones thrown in response to an IllegalArgument (not sure if ELExceptions might be thrown in similar cases) (BTW/OT: I would say that EL coercion is configurable already. Either by registering it's own ExpressionFactory or as far as I know by registering PropertyEditors) Regards, Imre was (Author: ioss): Hi Leonardo, i'd like to suggest to add another Version of this method to _ClassUtils convertToTypeNoLogging or convertToType(Object value, Class? desiredClass, boolean doLog) so that: 1) No String concatenation has to take place 2) The log is not spammed with SEVERE messages Also I am not sure if you - in this usecase - want to catch any Exception or only the ones thrown in response to an IllegalArgument (not sure if ELExceptions might be thrown in similar cases) (BTW/OT: I would say that EL coercion is configurable already. Either by registering it's own ExpressionFactory or as far as I know by registering PropertyEditors) Regards, Imre 2.0.3 REGRESSION: javax.faces.component._ClassUtils.convertToType - Key: MYFACES-3010 URL: https://issues.apache.org/jira/browse/MYFACES-3010 Project: MyFaces Core Issue Type: Bug Components: General Affects Versions: 2.0.3 Reporter: Kennard Consulting Priority: Critical Attachments: addressbook-faces2.zip Hi guys, Thanks again for the great work you do on MyFaces and your fantastic JIRA response times! I attach a small app that comes from the Metawidget (http://metawidget.org) distribution. I had you do MYFACES-2935 for me for MyFaces 2.0.3, and my app was working great with the 2.0.3-impl-SNAPSHOT.jar and the 2.0.2-api.jar. However now that 2.0.3 is out for real I have tried to upgrade my app, and it fails. To reproduce, please: 1. Unzip the attached app and deploy as an exploded WAR into Tomcat 2. Run Tomcat and hit http://localhost:8080/addressbook-faces2 3. In the Type dropdown, choose 'Business' and click Search You will see an IllegalArgumentException. Now: 4. Stop Tomcat 5. Inside the exploded WAR, rename myfaces-api-2.0.2.rename.me to myfaces-api-2.0.2.jar (and delete/rename myfaces-api-2.0.3.jar) 6. Restart Tomcat and repeat steps 1-3 This time you will see no such error. So something appears to have broken between myfaces-api-2.0.2.jar and myfaces-api-2.0.3.jar? Hopefully you can reproduce this and it is enough for you to debug the issue. The source code for the small app can be viewed here: http://metawidget.svn.sourceforge.net/viewvc/metawidget/trunk/examples/src/java/org/metawidget/example/faces/addressbook/ http://metawidget.svn.sourceforge.net/viewvc/metawidget/trunk/examples/src/java/org/metawidget/example/shared/addressbook/ Of course, this could well be a case of 2.0.3 being stricter about something and therefore exposing a bug in my code. But my code worked in 2.0.2, JSF 1.2 and JSF 1.1, so hopefully not! Regards, Richard -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
