Wolfgang Toepfer ist außer Haus.
Ich werde ab dem 06.09.2010 nicht im Büro sein. Ich kehre zurück am 27.09.2010. I will be out of the office from 06.09.2010. I will be returning on 27.09.2010. Ich werde Ihre Nachricht nach meiner Rückkehr beantworten. ** http://www.pta.de Mit 1955 Erfahrungsberichten aus 41 Jahren erfolgreicher Projektarbeit! ** PTA Programmier-Technische Arbeiten GmbH Seckenheimer Str. 65-67, 68165 Mannheim Amtsgericht Mannheim, HRB 1139 USt-IdNr.: DE 143 839 368 Geschaeftsfuehrer: Dipl.-Ing. Peter Fischer Dr. Harald W. Busch Dipl.-Kfm. Knut Fischer
Re: [DISCUSS] [GSoC] Automated webapp test framework integration
Hi, Thinking about it, it may be better at the moment to commit it into the gsoc folder and enhance it first. Then when we think we can do the first alpha release, we can move it into a different folder. However I really think that it should be separated from MyFaces-test, since MyFaces-test is a mocking framework and webapp-test is kind of an integration testing framework. But we can deal with this question later. Regards, Jakob 2010/9/4 Leonardo Uribe lu4...@gmail.com Hi No objections for my side, but could you be more explicit about what you gonna do? Do you want to include it as a separate module for myfaces-test (note this requires an official vote)? or maybe create a branch on myfaces-test so we can enhance it and when it is ready, do some alpha/beta releases?. regards, Leonardo Uribe 2010/9/4 Jakob Korherr jakob.korh...@gmail.com Hi, If no objections I'll start the integration today into myfaces/test/webapptest. Regards, Jakob 2010/8/23 Jakob Korherr jakob.korh...@gmail.com Hi, Since GSoC is over, we can now integrate the code into our codebase. The code currently lives in a google code project [1]. Because of the fact that this is a test framework, I would really like to put it into the test folder rather then creating a new (myfaces-)top-level entry. However I do not want to integrate it into the current MyFaces test framework (that currently lives in the test folder), because this is a completely different thing and IMO we have to be able to do separate releases of those two. In addition I would like to create a new project in the JIRA for the automated webapp tests framework. Something like WEBAPPTEST. Suggestions are welcome! What do you think? Any objections, thoughts, ideas? Thanks for looking into this! Regards, Jakob [1] http://code.google.com/p/gsoc2010-automated-myfaces-tests/ -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at
[jira] Created: (MYFACES-2911) OSGi Manifest: MyFaces API Bundle requires IMPL Bundle
OSGi Manifest: MyFaces API Bundle requires IMPL Bundle -- Key: MYFACES-2911 URL: https://issues.apache.org/jira/browse/MYFACES-2911 Project: MyFaces Core Issue Type: Bug Components: General Environment: OSGi container Reporter: Frank Mittag Priority: Minor The MANIFEST.MF file of the org.apache.myfaces.core.api bundle/jar contains the entry: Require-Bundle: org.apache.myfaces.core.impl;bundle-version=2.0.1 So the API bundle requires the IMPL bundle to work. This is not needed and prevents scenarios where the e.g. two IMPL bundles just reference the same API bundle. The easiest solution is just to remove the entry. Frank -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (EXTCDI-50) @ViewAccessScoped annotation must not be used as Qualifier
[ https://issues.apache.org/jira/browse/EXTCDI-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved EXTCDI-50. Fix Version/s: 1.0.0-SNAPSHOT Resolution: Fixed @ViewAccessScoped annotation must not be used as Qualifier -- Key: EXTCDI-50 URL: https://issues.apache.org/jira/browse/EXTCDI-50 Project: MyFaces CODI Issue Type: Bug Components: Core Affects Versions: 1.0.0-SNAPSHOT Reporter: Mark Struberg Fix For: 1.0.0-SNAPSHOT Attachments: EXTCDI-50.patch, EXTCDI-50_v2.patch we currently use the @ViewAccessScoped annotation as a Qualifier in CODI internally. But this is not correct and OWB crashes with an Exception at runtime (I assume Weld will reacts in a similar way). In my situation it happens with a @ViewAccessScoped bean which gets an event via @Observes. At the time the event gets fired, OWB crashes with the following stacktrace: 2010-09-04 18:37:01.414:WARN::/course/errorPage.xhtml java.lang.IllegalArgumentException: Qualifier annotations must be annotated with @Qualifier at org.apache.webbeans.util.AnnotationUtil.checkQualifierConditions(AnnotationUtil.java:906) at org.apache.webbeans.util.AnnotationUtil.checkQualifierConditions(AnnotationUtil.java:882) at org.apache.webbeans.util.AnnotationUtil.checkQualifierConditions(AnnotationUtil.java:870) at org.apache.webbeans.container.BeanManagerImpl.getBeans(BeanManagerImpl.java:669) at org.apache.webbeans.util.WebBeansUtil.getMostSpecializedBean(WebBeansUtil.java:2549) at org.apache.webbeans.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:229) at org.apache.webbeans.event.NotificationManager.fireEvent(NotificationManager.java:441) at org.apache.webbeans.container.BeanManagerImpl.fireEvent(BeanManagerImpl.java:401) at org.apache.webbeans.event.EventImpl.fire(EventImpl.java:74) at at.ac.tuwien.tiss.core.fe.LanguageSettingsHandler.checkLanguage(LanguageSettingsHandler.java:63) One argument more to move our @ViewAccessScoped from a stereotype to a 'real' scope ;) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2911) OSGi Manifest: MyFaces API Bundle requires IMPL Bundle
[ https://issues.apache.org/jira/browse/MYFACES-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12906548#action_12906548 ] Leonardo Uribe commented on MYFACES-2911: - In theory, api requires impl to work, and to be more precise it is not wanted people use different versions of impl with a specific version of api. I think definitively that restriction is needed. Note this entry allow locate myfaces classes using the bundle classloader from api to impl. OSGi Manifest: MyFaces API Bundle requires IMPL Bundle -- Key: MYFACES-2911 URL: https://issues.apache.org/jira/browse/MYFACES-2911 Project: MyFaces Core Issue Type: Bug Components: General Environment: OSGi container Reporter: Frank Mittag Priority: Minor The MANIFEST.MF file of the org.apache.myfaces.core.api bundle/jar contains the entry: Require-Bundle: org.apache.myfaces.core.impl;bundle-version=2.0.1 So the API bundle requires the IMPL bundle to work. This is not needed and prevents scenarios where the e.g. two IMPL bundles just reference the same API bundle. The easiest solution is just to remove the entry. Frank -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[VOTE] release for myfaces archetypes 1.0.2
Hi, I was running the needed tasks to get the 1.0.2 release of Apache MyFaces Build Tools Archetypes out. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.buildtools v1.0.2 (only archetypes) The artifacts are deployed to the nexus repository [1]. The following issues have been addressed in this release: * MYFACES-2515 Archetype for MyFaces 2.0 hello world app * TRINIDAD-1904 Archetype for Trinidad 2.0 * Update archetypes structure to fit the new archetype plugin * Add license headers in various files * Update versions of MyFaces, Mojarra, Jetty, Trinidad To test the archetypes just do the following: Create a project from an archetype: mvn archetype:generate -DarchetypeCatalog=http://people.apache.org/~jakobk/m2_archetypes_102_release Choose an archetype from the list and enter values for groupId, artifactId and version. Then on the path of the generated archetype mvn clean jetty:run or for the 2.0 archetypes mvn clean jetty:run-exploded -PjettyConfig Then open http://localhost:8080 and see if everything works. Please take a look at the 1.0.2 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [2]). [ ] +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, Jakob [1] https://repository.apache.org/content/repositories/orgapachemyfaces-041/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at
Re: [VOTE] release for myfaces archetypes 1.0.2
+1 Regards, Jakob 2010/9/6 Jakob Korherr jakob.korh...@gmail.com: Hi, I was running the needed tasks to get the 1.0.2 release of Apache MyFaces Build Tools Archetypes out. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.buildtools v1.0.2 (only archetypes) The artifacts are deployed to the nexus repository [1]. The following issues have been addressed in this release: * MYFACES-2515 Archetype for MyFaces 2.0 hello world app * TRINIDAD-1904 Archetype for Trinidad 2.0 * Update archetypes structure to fit the new archetype plugin * Add license headers in various files * Update versions of MyFaces, Mojarra, Jetty, Trinidad To test the archetypes just do the following: Create a project from an archetype: mvn archetype:generate -DarchetypeCatalog=http://people.apache.org/~jakobk/m2_archetypes_102_release Choose an archetype from the list and enter values for groupId, artifactId and version. Then on the path of the generated archetype mvn clean jetty:run or for the 2.0 archetypes mvn clean jetty:run-exploded -PjettyConfig Then open http://localhost:8080 and see if everything works. Please take a look at the 1.0.2 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [2]). [ ] +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, Jakob [1] https://repository.apache.org/content/repositories/orgapachemyfaces-041/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at
[jira] Commented: (MYFACES-2911) OSGi Manifest: MyFaces API Bundle requires IMPL Bundle
[ https://issues.apache.org/jira/browse/MYFACES-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12906595#action_12906595 ] Frank Mittag commented on MYFACES-2911: --- Hi Leonardo, in this case it's not clear to me why you have an API and IMPL bundle at all. My understanding is that an API can have different implementations and that an API does NOT know who is implementing it. It there a specific reason why this is different in MyFaces? Frank OSGi Manifest: MyFaces API Bundle requires IMPL Bundle -- Key: MYFACES-2911 URL: https://issues.apache.org/jira/browse/MYFACES-2911 Project: MyFaces Core Issue Type: Bug Components: General Environment: OSGi container Reporter: Frank Mittag Priority: Minor The MANIFEST.MF file of the org.apache.myfaces.core.api bundle/jar contains the entry: Require-Bundle: org.apache.myfaces.core.impl;bundle-version=2.0.1 So the API bundle requires the IMPL bundle to work. This is not needed and prevents scenarios where the e.g. two IMPL bundles just reference the same API bundle. The easiest solution is just to remove the entry. Frank -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] release for myfaces archetypes 1.0.2
+1 2010/9/6 Jakob Korherr jakob.korh...@gmail.com +1 Regards, Jakob 2010/9/6 Jakob Korherr jakob.korh...@gmail.com: Hi, I was running the needed tasks to get the 1.0.2 release of Apache MyFaces Build Tools Archetypes out. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.buildtools v1.0.2 (only archetypes) The artifacts are deployed to the nexus repository [1]. The following issues have been addressed in this release: * MYFACES-2515 Archetype for MyFaces 2.0 hello world app * TRINIDAD-1904 Archetype for Trinidad 2.0 * Update archetypes structure to fit the new archetype plugin * Add license headers in various files * Update versions of MyFaces, Mojarra, Jetty, Trinidad To test the archetypes just do the following: Create a project from an archetype: mvn archetype:generate -DarchetypeCatalog= http://people.apache.org/~jakobk/m2_archetypes_102_releasehttp://people.apache.org/%7Ejakobk/m2_archetypes_102_release Choose an archetype from the list and enter values for groupId, artifactId and version. Then on the path of the generated archetype mvn clean jetty:run or for the 2.0 archetypes mvn clean jetty:run-exploded -PjettyConfig Then open http://localhost:8080 and see if everything works. Please take a look at the 1.0.2 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [2]). [ ] +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, Jakob [1] https://repository.apache.org/content/repositories/orgapachemyfaces-041/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at
Re: [VOTE] release for myfaces archetypes 1.0.2
+1 sent from my Android phone On Sep 7, 2010 4:09 AM, Leonardo Uribe lu4...@gmail.com wrote: +1 2010/9/6 Jakob Korherr jakob.korh...@gmail.com +1 Regards, Jakob 2010/9/6 Jakob Korherr jakob.korh...@gmail.com: Hi, I was running the needed tasks to get the 1.0.2 release of Apache MyFaces Build Tools Archetypes out. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.buildtools v1.0.2 (only archetypes) The artifacts are deployed to the nexus repository [1]. The following issues have been addressed in this release: * MYFACES-2515 Archetype for MyFaces 2.0 hello world app * TRINIDAD-1904 Archetype for Trinidad 2.0 * Update archetypes structure to fit the new archetype plugin * Add license headers in various files * Update versions of MyFaces, Mojarra, Jetty, Trinidad To test the archetypes just do the following: Create a project from an archetype: mvn archetype:generate -DarchetypeCatalog= http://people.apache.org/~jakobk/m2_archetypes_102_release http://people.apache.org/%7Ejakobk/m2_archetypes_102_release Choose an archetype from the list and enter values for groupId, artifactId and version. Then on the path of the generated archetype mvn clean jetty:run or for the 2.0 archetypes mvn clean jetty:run-exploded -PjettyConfig Then open http://localhost:8080 and see if everything works. Please take a look at the 1.0.2 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [2]). [ ] +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, Jakob [1] https://repository.apache.org/content/repositories/orgapachemyfaces-041/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at
Re: [VOTE] release for myfaces archetypes 1.0.2
+1 regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/9/6 Jakob Korherr jakob.korh...@gmail.com +1 Regards, Jakob 2010/9/6 Jakob Korherr jakob.korh...@gmail.com: Hi, I was running the needed tasks to get the 1.0.2 release of Apache MyFaces Build Tools Archetypes out. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.buildtools v1.0.2 (only archetypes) The artifacts are deployed to the nexus repository [1]. The following issues have been addressed in this release: * MYFACES-2515 Archetype for MyFaces 2.0 hello world app * TRINIDAD-1904 Archetype for Trinidad 2.0 * Update archetypes structure to fit the new archetype plugin * Add license headers in various files * Update versions of MyFaces, Mojarra, Jetty, Trinidad To test the archetypes just do the following: Create a project from an archetype: mvn archetype:generate -DarchetypeCatalog= http://people.apache.org/~jakobk/m2_archetypes_102_release Choose an archetype from the list and enter values for groupId, artifactId and version. Then on the path of the generated archetype mvn clean jetty:run or for the 2.0 archetypes mvn clean jetty:run-exploded -PjettyConfig Then open http://localhost:8080 and see if everything works. Please take a look at the 1.0.2 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [2]). [ ] +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, Jakob [1] https://repository.apache.org/content/repositories/orgapachemyfaces-041/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at
