[jira] [Created] (MYFACES-3385) Entered values for input fields conatined in a Composite Component are lost, if the CC is used in a datatable

Entered values for input fields conatined in a Composite Component are lost, if the CC is used in a datatable - Key: MYFACES-3385 URL:

Re: svn commit: r1197378 - in /myfaces/extensions/cdi/trunk/jee-modules/jpa-module: api/ api/src/main/java/org/apache/myfaces/extensions/cdi/jpa/api/datasource/ impl/src/main/java/org/apache/myfaces/e

I'll revert that and do it cleanly. And you should check your svn client, Idea apparently trashes the svn history... LieGrue, strub - Original Message - From: gpetra...@apache.org gpetra...@apache.org To: comm...@myfaces.apache.org Cc: Sent: Friday, November 4, 2011 2:11 AM

please use svn commandline and not idea or eclipse for checkin

please use svn commandline and not idea or eclipse for checkin because both use svnkit which apparently trashes the svn history and is buggy with svn mv etc. known issues all together ... LieGrue, strub

Re: please use svn commandline and not idea or eclipse for checkin

actually svnkit seems to don't make any svn mv at all but just del+add files on rename etc. This really trashes all the svn merge abilities, history etc. E.g. svn merge -r 1197418:1197092 https://svn.apache.org/repos/asf/myfaces/extensions/cdi/trunk doesnt work at all and I need to recopy all

Re: svn commit: r1197378 - in /myfaces/extensions/cdi/trunk/jee-modules/jpa-module: api/ api/src/main/java/org/apache/myfaces/extensions/cdi/jpa/api/datasource/ impl/src/main/java/org/apache/myfaces/e

hi mark, there is no need to use a different client. it's just the order of doing it. originally i planned something different which would have resulted in the same. at the end of the refactoring it was more like the original version, but i didn't revert the whole work just for a simpler diff of

Re: svn commit: r1197378 - in /myfaces/extensions/cdi/trunk/jee-modules/jpa-module: api/ api/src/main/java/org/apache/myfaces/extensions/cdi/jpa/api/datasource/ impl/src/main/java/org/apache/myfaces/e

In general renaming or moving classes around the codebase in a SVN repo should be done via svn copy origfile newfile +  change newfile + svn delete origfile + svn commit newfile This way all the history will be retained. Sadly most IDEs (using svnkit) just make a svn delete orig + svn add

[jira] [Created] (EXTCDI-238) cleanup javadoc

cleanup javadoc --- Key: EXTCDI-238 URL: https://issues.apache.org/jira/browse/EXTCDI-238 Project: MyFaces CODI Issue Type: Task Affects Versions: 1.0.1 Reporter: Gerhard Petracek Priority: Minor

Re: [jira] [Created] (TRINIDAD-2155) Incomplete serialization implementation in AccessibilityProfile$SerializableAccessibilityProfile

Hi, Can someone review and apply this fix ?. Thanks, Prakash On 11/1/2011 4:15 PM, Prakash Udupa (Created) (JIRA) wrote: Incomplete serialization implementation in AccessibilityProfile$SerializableAccessibilityProfile

[jira] [Resolved] (MYFACES-3385) Entered values for input fields conatined in a Composite Component are lost, if the CC is used in a datatable

[ https://issues.apache.org/jira/browse/MYFACES-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MYFACES-3385. - Resolution: Fixed Fix Version/s: 2.1.4 2.0.10

How to deactivate myfaces CODI producer method (CDI)?

I have two procuder methods to the FactesContext type. Myfaces has one producer method in FacesInformationProducer class and i have in another jar other producer to same type. This causes a Ambiguous Dependency exception. How can i solve this problem? Thanks! -- View this message in context:

Re: How to deactivate myfaces CODI producer method (CDI)?

hi, you can create a cdi extension, observe ProcessAnnotatedType and call ProcessAnnotatedType#veto if the class (returned by processAnnotatedType.getAnnotatedType().getJavaClass()) is org.apache.myfaces.extensions.cdi.jsf.impl.util.FacesInformationProducer regards, gerhard http://www.irian.at

Re: How to deactivate myfaces CODI producer method (CDI)?

Thanks Gerhard. This solved my problem. Gerhard Petracek wrote: hi, you can create a cdi extension, observe ProcessAnnotatedType and call ProcessAnnotatedType#veto if the class (returned by processAnnotatedType.getAnnotatedType().getJavaClass()) is

@ViewAccessScoped does not work!

I have a bean 'X' annotated with @ViewAccessScoped but this scope does not work. When i access the view 'A' that uses the bean X and does change to view 'B' that uses the bean 'X' too, i lose the bean state. How can i solve this problem? Below my configuration: config implementation:

Re: @ViewAccessScoped does not work!

I am using myfaces-extcdi-dist-jsf2 version 0 0.9.5 primefaces version 2.2.1 lindberg wrote: I have a bean 'X' annotated with @ViewAccessScoped but this scope does not work. When i access the view 'A' that uses the bean X and does change to view 'B' that uses the bean 'X' too, i lose the

[jira] [Resolved] (MYFACES-3375) MyFaces can incorrectly determine that Portlets are not supported

[ https://issues.apache.org/jira/browse/MYFACES-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MYFACES-3375. - Resolution: Fixed Fix Version/s: 2.1.4 2.0.10

Re: @ViewAccessScoped does not work!

Hi! As first step you should upgrade to extcdi-1.0.1 which got released 2 months ago. This is the last stable version. 0.9.5 was one of our very first public packages and we fixed a _lot_ issues since then. LieGrue, strub - Original Message - From: lindberg grebdn...@hotmail.com

Re: @ViewAccessScoped does not work!

@mark: i agree with you that using the latest version makes a lot of sense, however we never had such an issue. @lindberg: please provide more details (e.g. how you are navigating to view 'B'). regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses

[jira] [Commented] (MYFACES-3383) Self nested Composite Component leads to EL Stack Overflow

[ https://issues.apache.org/jira/browse/MYFACES-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13144324#comment-13144324 ] Leonardo Uribe commented on MYFACES-3383: - I have checked the example provided,

[jira] [Resolved] (EXTCDI-238) cleanup javadoc

[ https://issues.apache.org/jira/browse/EXTCDI-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved EXTCDI-238. - Resolution: Fixed Fix Version/s: 1.0.2 cleanup javadoc ---

Re: @ViewAccessScoped does not work!

I updated to 1.0.1 version. I using prettyfaces 3.3.0 and when I use pretty the ViewAccessScoped does not work. When I remove pretty works. What can i do? Is there any required configuration or integration to use myfaces CODI with prettyfaces? When i return in my action method the view by

Re: @ViewAccessScoped does not work!

hi, you have to map the window-id parameter in your prettyfaces config or you use the server-side window-handler (which doesn't support e.g. page-refreshes). regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional

[jira] [Created] (MFCOMMONS-44) Remove gzip compression feature from myfaces commons resourcehandler

Remove gzip compression feature from myfaces commons resourcehandler Key: MFCOMMONS-44 URL: https://issues.apache.org/jira/browse/MFCOMMONS-44 Project: MyFaces Commons