[jira] Resolved: (TOBAGO-825) Add markup support for any other graphical components.

[ https://issues.apache.org/jira/browse/TOBAGO-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Schnurpfeil resolved TOBAGO-825. Fix Version/s: 1.5.0-alpha-2 1.5.0 Resolution: Fixed Add markup

[jira] Resolved: (TOBAGO-617) markup attribute at tc:popup

[ https://issues.apache.org/jira/browse/TOBAGO-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Schnurpfeil resolved TOBAGO-617. Fix Version/s: 1.5.0-alpha-2 Resolution: Fixed markup attribute at tc:popup

[jira] Commented: (TRINIDAD-1870) tr:commandLink blocks tr:panelAccordion

[ https://issues.apache.org/jira/browse/TRINIDAD-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909151#action_12909151 ] Cedric Durmont commented on TRINIDAD-1870: -- Still having the bug with beta1.

Problems using LifeCycleProvider and LifecycleProviderFactory Instances

Hello, Currently MyFaces uses static DEFAULT_LIFECYCLE_PROVIDER instance in the DefaultLifecycleProviderFactory. But, it creates problems in containers, such as Tomcat. Indeed, it is not possible to use META-INF/services approach because of using static instance.

[jira] Created: (EXTCDI-52) names for beans provided by codi should be defined centrally

names for beans provided by codi should be defined centrally Key: EXTCDI-52 URL: https://issues.apache.org/jira/browse/EXTCDI-52 Project: MyFaces CODI Issue Type: Improvement

[jira] Created: (EXTVAL-117) support for a custom ValidatorFactory as alternative for BeanAwareValidatorFactory

support for a custom ValidatorFactory as alternative for BeanAwareValidatorFactory -- Key: EXTVAL-117 URL: https://issues.apache.org/jira/browse/EXTVAL-117 Project:

[jira] Commented: (MYFACES-2915) UIComponent attribute defaults are not used when bound to managed bean property by EL, even if the managed bean property is null

[ https://issues.apache.org/jira/browse/MYFACES-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909191#action_12909191 ] Jakob Korherr commented on MYFACES-2915: I agree with Leonardo. This should be

Re: [DISCUSS] [GSoC] Automated webapp test framework integration

Hi Leo, Yes, please fall back to the test-webapp for now. We have to work on the webapp-test module a lot before it will really be useful for us, I guess. Regards, Jakob 2010/9/9 Leonardo Uribe lu4...@gmail.com: Hi Testing the example provided, and changing its dependencies to

[jira] Created: (MYFACES-2919) LifecycleProvider Based Problems and Tomcat7 LifeCycleProvider Support

LifecycleProvider Based Problems and Tomcat7 LifeCycleProvider Support -- Key: MYFACES-2919 URL: https://issues.apache.org/jira/browse/MYFACES-2919 Project: MyFaces Core

[jira] Updated: (MYFACES-2919) LifecycleProvider Based Problems and Tomcat7 LifeCycleProvider Support

[ https://issues.apache.org/jira/browse/MYFACES-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gurkan Erdogdu updated MYFACES-2919: Status: Patch Available (was: Open) LifecycleProvider Based Problems and Tomcat7

[jira] Commented: (TRINIDAD-1910) portal: common.js is included serveral times

[ https://issues.apache.org/jira/browse/TRINIDAD-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909200#action_12909200 ] Daniel Niklas commented on TRINIDAD-1910: - one more comment: this patch only

[jira] Resolved: (EXTVAL-117) support for a custom ValidatorFactory as alternative for BeanAwareValidatorFactory

[ https://issues.apache.org/jira/browse/EXTVAL-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved EXTVAL-117. - Fix Version/s: 1.2.4-SNAPSHOT 2.0.4-SNAPSHOT

[jira] Reopened: (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:all-tabpanel ] Frank Mittag reopened MYFACES-2911: --- I think I understand now why you have the entry, but this restriction seems to be more a

[jira] Created: (MYFACES-2920) UISelectOne/UISelectMany validateValue: Before comparing each option, coerce the option value type to the type of component's value

UISelectOne/UISelectMany validateValue: Before comparing each option, coerce the option value type to the type of component's value --- Key:

[jira] Updated: (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 ] Martin Kočí updated MYFACES-2920: - Status: Patch Available (was: Open) UISelectOne/UISelectMany validateValue: Before comparing

Re: _SelectItemsUtil._ValueConverter

Hi, please review https://issues.apache.org/jira/browse/MYFACES-2920 1) JavaDoc explicitly mentions EL coecion but not Converter:

JBoss integration

Hello just out of curiosity because the JBOSS AS6 release schedule has been released, what is the status on the JBOSS MyFaces integration? Leo? any idea? Werner

Re: _SelectItemsUtil._ValueConverter

Hi, The patch looks good, but actually I did not test it myself. Have you also tried it with enum values? Funny that the TCK does not fail here, because the spec explicitly tells us to use coercion. If it works well with enums, +1 on committing this patch. Regards, Jakob 2010/9/14 Martin Koci

[jira] Commented: (MYFACES-2618) Don't warn if there is no submitted value in the current request for every EditableValueHolder

[ https://issues.apache.org/jira/browse/MYFACES-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909278#action_12909278 ] Jakob Korherr commented on MYFACES-2618: Yes you could do that! Nope, it uses

[jira] Commented: (MYFACES-2919) LifecycleProvider Based Problems and Tomcat7 LifeCycleProvider Support

[ https://issues.apache.org/jira/browse/MYFACES-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909297#action_12909297 ] Jakob Korherr commented on MYFACES-2919: Hi Gurkan, I provided another patch

[jira] Created: (MYFACESTEST-33) WebappTesterImpl does not need to be proxied

WebappTesterImpl does not need to be proxied Key: MYFACESTEST-33 URL: https://issues.apache.org/jira/browse/MYFACESTEST-33 Project: MyFaces Test Issue Type: Improvement Components:

[jira] Resolved: (MYFACESTEST-33) WebappTesterImpl does not need to be proxied

[ https://issues.apache.org/jira/browse/MYFACESTEST-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr resolved MYFACESTEST-33. -- Resolution: Fixed WebappTesterImpl does not need to be proxied

[jira] Created: (TRINIDAD-1915) CheckedSerializationMap check if delegate is Serializable

CheckedSerializationMap check if delegate is Serializable - Key: TRINIDAD-1915 URL: https://issues.apache.org/jira/browse/TRINIDAD-1915 Project: MyFaces Trinidad Issue Type: Bug

Re: JBoss integration

Hi All code for that is in place, and on this issue: https://issues.apache.org/jira/browse/MYFACES-2860 There is a zip that contains the necessary stuff to make it run. regards, Leonardo Uribe 2010/9/14 Werner Punz werner.p...@gmail.com Hello just out of curiosity because the JBOSS AS6

[jira] Resolved: (TRINIDAD-1915) CheckedSerializationMap check if delegate is Serializable

[ https://issues.apache.org/jira/browse/TRINIDAD-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf resolved TRINIDAD-1915. -- Fix Version/s: 2.0.0.3-core Resolution: Fixed

Re: JBoss integration

MyFaces 2.0.1 will be included in milestone 4. I just added it over the weekend. If you build JBoss AS from trunk you can play around with it. The doc for JSF integration is here: http://www.jboss.org/jbossas/docs/6-x/Component-Documentation/jsf.html You'll want to look at part 2 and part

[jira] Updated: (TRINIDAD-1913) All tr:group component attributes to specify boundary and title preferences

[ https://issues.apache.org/jira/browse/TRINIDAD-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Cooper updated TRINIDAD-1913: -- Status: Resolved (was: Patch Available) Assignee: Matt Cooper Fix

Re: JBoss integration

Hi 2010/9/14 ssilv...@redhat.com MyFaces 2.0.1 will be included in milestone 4. I just added it over the weekend. If you build JBoss AS from trunk you can play around with it. The doc for JSF integration is here: http://www.jboss.org/jbossas/docs/6-x/Component-Documentation/jsf.html

Re: Problems using LifeCycleProvider and LifecycleProviderFactory Instances

Hi 2010/9/14 Gurkan Erdogdu gurkanerdo...@yahoo.com Hello, Currently MyFaces uses static DEFAULT_LIFECYCLE_PROVIDER instance in the DefaultLifecycleProviderFactory. But, it creates problems in containers, such as Tomcat. Indeed, it is not possible to use META-INF/services approach because

[jira] Commented: (MYFACES-2919) LifecycleProvider Based Problems and Tomcat7 LifeCycleProvider Support

[ https://issues.apache.org/jira/browse/MYFACES-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909401#action_12909401 ] Gurkan Erdogdu commented on MYFACES-2919: - Thanks Jakob, go for it, patch is

Re: JBoss integration

Quoting Leonardo Uribe lu4...@gmail.com: I have planned to start that release procedure for 2.0.2 today or tomorrow, so I think we could release 2.0.3 on November. That's good. Since the tighter integration with JBoss annotation scanning hasn't been tested, I'll be surprised if we don't

[jira] Updated: (MYFACES-2919) LifecycleProvider Based Problems and Tomcat7 LifeCycleProvider Support

[ https://issues.apache.org/jira/browse/MYFACES-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr updated MYFACES-2919: --- Status: Resolved (was: Patch Available) Fix Version/s: 2.0.2-SNAPSHOT

Re: Problems using LifeCycleProvider and LifecycleProviderFactory Instances

Hi, Here is the related issue in the JIRA: MYFACES-2919 Regards, Jakob 2010/9/14 Leonardo Uribe lu4...@gmail.com: Hi 2010/9/14 Gurkan Erdogdu gurkanerdo...@yahoo.com Hello, Currently MyFaces uses static DEFAULT_LIFECYCLE_PROVIDER instance in the DefaultLifecycleProviderFactory. But, it

[jira] Created: (MYFACES-2921) FlashImpl should set a correct path for the Cookies

FlashImpl should set a correct path for the Cookies --- Key: MYFACES-2921 URL: https://issues.apache.org/jira/browse/MYFACES-2921 Project: MyFaces Core Issue Type: Bug Components:

[jira] Reopened: (MYFACES-2919) LifecycleProvider Based Problems and Tomcat7 LifeCycleProvider Support

[ https://issues.apache.org/jira/browse/MYFACES-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe reopened MYFACES-2919: - I have some questions about this patch: 1. Why some code has changed to swallow all

[jira] Resolved: (MYFACES-2921) FlashImpl should set a correct path for the Cookies

[ https://issues.apache.org/jira/browse/MYFACES-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr resolved MYFACES-2921. Fix Version/s: 2.0.2-SNAPSHOT Resolution: Fixed FlashImpl should set a correct

Re: FlashImpl : oam.Flash.RENDERMAP.TOKEN and number of Cookies

Hi, I just fixed this problem in MYFACES-2921. Regards, Jakob 2010/9/10 Jakob Korherr jakob.korh...@gmail.com: Hi Kočičák, Yes, you're right. We have to use cookie.setPath(/);, because we really only need one cookie for the whole webapp. Thanks for pointing this out! Regards, Jakob

[jira] Commented: (MYFACES-2919) LifecycleProvider Based Problems and Tomcat7 LifeCycleProvider Support

[ https://issues.apache.org/jira/browse/MYFACES-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909446#action_12909446 ] Jakob Korherr commented on MYFACES-2919: Hi Leo, 1. It was changed to catch

[jira] Created: (MYFACES-2922) [PERF] Improvements for @ResourceDependency handling

[PERF] Improvements for @ResourceDependency handling Key: MYFACES-2922 URL: https://issues.apache.org/jira/browse/MYFACES-2922 Project: MyFaces Core Issue Type: Improvement

Re: Myfaces vs. mojarra restore view performance

Hi, please review https://issues.apache.org/jira/browse/MYFACES-2922 and apply if possible. Thanks, Kočičák Leonardo Uribe píše v Pá 06. 08. 2010 v 13:07 -0500: Hi 2010/8/6 Martin Koci martin.k...@aura.cz Hi, is it possible to cache inspected classes

[jira] Resolved: (EXTCDI-52) names for beans provided by codi should be defined centrally

[ https://issues.apache.org/jira/browse/EXTCDI-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved EXTCDI-52. Resolution: Fixed names for beans provided by codi should be defined centrally

[jira] Created: (EXTCDI-53) eval producers for all config entries

eval producers for all config entries - Key: EXTCDI-53 URL: https://issues.apache.org/jira/browse/EXTCDI-53 Project: MyFaces CODI Issue Type: Task Components: Core, JEE-BV1-Module,

[jira] Commented: (EXTCDI-53) eval producers for all config entries

[ https://issues.apache.org/jira/browse/EXTCDI-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909481#action_12909481 ] Gerhard Petracek commented on EXTCDI-53: advantage: - short syntax - users don't

[jira] Issue Comment Edited: (EXTCDI-53) eval producers for all config entries

[ https://issues.apache.org/jira/browse/EXTCDI-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909481#action_12909481 ] Gerhard Petracek edited comment on EXTCDI-53 at 9/14/10 6:15 PM:

[jira] Commented: (EXTCDI-53) eval producers for all config entries

[ https://issues.apache.org/jira/browse/EXTCDI-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909484#action_12909484 ] Gerhard Petracek commented on EXTCDI-53: if there are no objections, i move the

[jira] Commented: (MYFACES-2919) LifecycleProvider Based Problems and Tomcat7 LifeCycleProvider Support

[ https://issues.apache.org/jira/browse/MYFACES-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909485#action_12909485 ] Leonardo Uribe commented on MYFACES-2919: - Hi Jakob 1. Yes, but if there is one

[jira] Commented: (TRINIDAD-1819) PPR Issues in Windows Mobile 6

[ https://issues.apache.org/jira/browse/TRINIDAD-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909487#action_12909487 ] Tadashi Enomori commented on TRINIDAD-1819: --- The patch looks good. Adding some

[jira] Commented: (MYFACES-2919) LifecycleProvider Based Problems and Tomcat7 LifeCycleProvider Support

[ https://issues.apache.org/jira/browse/MYFACES-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909491#action_12909491 ] Jakob Korherr commented on MYFACES-2919: OK, great :) LifecycleProvider Based

[jira] Resolved: (EXTCDI-53) eval producers for all config entries

[ https://issues.apache.org/jira/browse/EXTCDI-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved EXTCDI-53. Fix Version/s: 1.0.0-SNAPSHOT Resolution: Fixed eval producers for all config

[jira] Created: (MYFACESTEST-34) Get rid of @Deployment method in test classes

Get rid of @Deployment method in test classes - Key: MYFACESTEST-34 URL: https://issues.apache.org/jira/browse/MYFACESTEST-34 Project: MyFaces Test Issue Type: Improvement Components:

[jira] Resolved: (MYFACESTEST-34) Get rid of @Deployment method in test classes

[ https://issues.apache.org/jira/browse/MYFACESTEST-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr resolved MYFACESTEST-34. -- Resolution: Fixed Get rid of @Deployment method in test classes