[jira] [Commented] (MYFACES-4127) Unexpected exception thrown when FlowMap is injected on a RequestScoped bean
[ https://issues.apache.org/jira/browse/MYFACES-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159502#comment-16159502 ] Thomas Andraschko commented on MYFACES-4127: It should already work now but it would be great if you could review. Also did a small refactoring on the packages and some artifacts. JFYI: there are some tickets which targets 2.3.0 (only 6 left) and it would be great if you could check MYFACES-4133. > Unexpected exception thrown when FlowMap is injected on a RequestScoped bean > > > Key: MYFACES-4127 > URL: https://issues.apache.org/jira/browse/MYFACES-4127 > Project: MyFaces Core > Issue Type: Bug >Affects Versions: 2.3.0-beta >Reporter: Eduardo Breijo >Assignee: Leonardo Uribe >Priority: Minor > Fix For: 2.3.0 > > Attachments: ConfigItems.java, ELImplicitObjectsViaCDI.war, > ELImplicitObjectsViaCDI.war.zip > > > When @FlowMap is injected on a RequestScoped bean, and you try to use that > object (which should be null since we are not inside of a flow), an > unexpected exception is thrown. This was noted after JIRA issue: > https://issues.apache.org/jira/browse/MYFACES-4126 > Caused by: org.jboss.weld.exceptions.IllegalProductException: WELD-52: > Cannot return null from a non-dependent producer method: Producer for > Producer Method [Map
[jira] [Commented] (MYFACES-4127) Unexpected exception thrown when FlowMap is injected on a RequestScoped bean
[ https://issues.apache.org/jira/browse/MYFACES-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159495#comment-16159495 ] Leonardo Uribe commented on MYFACES-4127: - It is possible to use a dynamic producer but it requires copy/paste some code that is already in MyFaces codebase. > Unexpected exception thrown when FlowMap is injected on a RequestScoped bean > > > Key: MYFACES-4127 > URL: https://issues.apache.org/jira/browse/MYFACES-4127 > Project: MyFaces Core > Issue Type: Bug >Affects Versions: 2.3.0-beta >Reporter: Eduardo Breijo >Assignee: Leonardo Uribe >Priority: Minor > Fix For: 2.3.0 > > Attachments: ConfigItems.java, ELImplicitObjectsViaCDI.war, > ELImplicitObjectsViaCDI.war.zip > > > When @FlowMap is injected on a RequestScoped bean, and you try to use that > object (which should be null since we are not inside of a flow), an > unexpected exception is thrown. This was noted after JIRA issue: > https://issues.apache.org/jira/browse/MYFACES-4126 > Caused by: org.jboss.weld.exceptions.IllegalProductException: WELD-52: > Cannot return null from a non-dependent producer method: Producer for > Producer Method [Map
[jira] [Commented] (MYFACES-4127) Unexpected exception thrown when FlowMap is injected on a RequestScoped bean
[ https://issues.apache.org/jira/browse/MYFACES-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159486#comment-16159486 ] Thomas Andraschko commented on MYFACES-4127: Nvm, got a solution which seems to work fine. [~eduardobreijo] please retest. > Unexpected exception thrown when FlowMap is injected on a RequestScoped bean > > > Key: MYFACES-4127 > URL: https://issues.apache.org/jira/browse/MYFACES-4127 > Project: MyFaces Core > Issue Type: Bug >Affects Versions: 2.3.0-beta >Reporter: Eduardo Breijo >Priority: Minor > Fix For: 2.3.0 > > Attachments: ConfigItems.java, ELImplicitObjectsViaCDI.war, > ELImplicitObjectsViaCDI.war.zip > > > When @FlowMap is injected on a RequestScoped bean, and you try to use that > object (which should be null since we are not inside of a flow), an > unexpected exception is thrown. This was noted after JIRA issue: > https://issues.apache.org/jira/browse/MYFACES-4126 > Caused by: org.jboss.weld.exceptions.IllegalProductException: WELD-52: > Cannot return null from a non-dependent producer method: Producer for > Producer Method [Map
[jira] [Commented] (MYFACES-4127) Unexpected exception thrown when FlowMap is injected on a RequestScoped bean
[ https://issues.apache.org/jira/browse/MYFACES-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159439#comment-16159439 ] Thomas Andraschko commented on MYFACES-4127: [~lu4242] I checked the case and i think we must use @FlowScoped for the producer. However, it's not that easy as @FlowScopd can't be used on method. So probably we must create a second internal FlowScoped or create dynamic producer bean. The first approach would be easier. Maybe you have a good idea to implement this. > Unexpected exception thrown when FlowMap is injected on a RequestScoped bean > > > Key: MYFACES-4127 > URL: https://issues.apache.org/jira/browse/MYFACES-4127 > Project: MyFaces Core > Issue Type: Bug >Affects Versions: 2.3.0-beta >Reporter: Eduardo Breijo >Priority: Minor > Fix For: 2.3.0 > > Attachments: ConfigItems.java, ELImplicitObjectsViaCDI.war, > ELImplicitObjectsViaCDI.war.zip > > > When @FlowMap is injected on a RequestScoped bean, and you try to use that > object (which should be null since we are not inside of a flow), an > unexpected exception is thrown. This was noted after JIRA issue: > https://issues.apache.org/jira/browse/MYFACES-4126 > Caused by: org.jboss.weld.exceptions.IllegalProductException: WELD-52: > Cannot return null from a non-dependent producer method: Producer for > Producer Method [Map
[jira] [Commented] (MYFACES-4151) When @FacesConfig is not present, EL resolution in managed beans should not be performed
[ https://issues.apache.org/jira/browse/MYFACES-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158947#comment-16158947 ] Eduardo Breijo commented on MYFACES-4151: - I don't see any logic on FacesScopeContextExtension that verifies the FacesConfig.Version > When @FacesConfig is not present, EL resolution in managed beans should not > be performed > - > > Key: MYFACES-4151 > URL: https://issues.apache.org/jira/browse/MYFACES-4151 > Project: MyFaces Core > Issue Type: Bug >Affects Versions: 2.3.0-beta >Reporter: Eduardo Breijo >Priority: Minor > > According to the JSF 2.3 spec section 5.6.3 "CDI for EL Resolution" - When > @FacesConfig annotation is present in any of the managed beans, the > ImplicitObjectELResolver is not present in the chain, instead CDI is used to > perform EL resolution. However, when @FacesConfig is not present, we are > still using CDI to perform EL resolution in the managed beans. > On Mojarra, app does not start, throwing DeploymentExceptions similar to > this: > org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied > dependencies for type FacesContext with qualifiers @Default > at injection point [BackedAnnotatedField] @Inject private > com.ibm.ws.jsf23.fat.beans.TestBean.facesContext > at com.ibm.ws.jsf23.fat.beans.TestBean.facesContext(TestBean.java:0) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MYFACES-4151) When @FacesConfig is not present, EL resolution in managed beans should not be performed
Eduardo Breijo created MYFACES-4151: --- Summary: When @FacesConfig is not present, EL resolution in managed beans should not be performed Key: MYFACES-4151 URL: https://issues.apache.org/jira/browse/MYFACES-4151 Project: MyFaces Core Issue Type: Bug Affects Versions: 2.3.0-beta Reporter: Eduardo Breijo Priority: Minor According to the JSF 2.3 spec section 5.6.3 "CDI for EL Resolution" - When @FacesConfig annotation is present in any of the managed beans, the ImplicitObjectELResolver is not present in the chain, instead CDI is used to perform EL resolution. However, when @FacesConfig is not present, we are still using CDI to perform EL resolution in the managed beans. On Mojarra, app does not start, throwing DeploymentExceptions similar to this: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type FacesContext with qualifiers @Default at injection point [BackedAnnotatedField] @Inject private com.ibm.ws.jsf23.fat.beans.TestBean.facesContext at com.ibm.ws.jsf23.fat.beans.TestBean.facesContext(TestBean.java:0) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOBAGO-1797) Disabled should not contain a command
[ https://issues.apache.org/jira/browse/TOBAGO-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158797#comment-16158797 ] Hudson commented on TOBAGO-1797: SUCCESS: Integrated in Jenkins build Tobago Trunk #1010 (See [https://builds.apache.org/job/Tobago%20Trunk/1010/]) Merged from trunk TOBAGO-1797: Disabled should not contain a (henning: rev fa90faf42d2e2c66fe5fcf7724a507bf9deae112) * (edit) tobago-core/src/main/java/org/apache/myfaces/tobago/internal/renderkit/renderer/TabGroupRenderer.java > Disabled should not contain a command > -- > > Key: TOBAGO-1797 > URL: https://issues.apache.org/jira/browse/TOBAGO-1797 > Project: MyFaces Tobago > Issue Type: Bug > Components: Themes >Affects Versions: 3.0.5 >Reporter: Udo Schnurpfeil >Assignee: Udo Schnurpfeil >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOBAGO-1759) Update Bootstrap to 4.0.0 beta 1 (from alpha 6)
[ https://issues.apache.org/jira/browse/TOBAGO-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158793#comment-16158793 ] Hudson commented on TOBAGO-1759: SUCCESS: Integrated in Jenkins build Tobago Trunk #1009 (See [https://builds.apache.org/job/Tobago%20Trunk/1009/]) TOBAGO-1759 Update Bootstrap to 4.0.0 beta 1 (from alpha 6) * fix for (henning: rev fc677a84b81e78cc5bec2f3bbce4f446800611b3) * (edit) tobago-theme/tobago-theme-standard/src/main/resources/META-INF/resources/tobago/standard/tobago-bootstrap/_version/js/tobago-dropdown.js > Update Bootstrap to 4.0.0 beta 1 (from alpha 6) > --- > > Key: TOBAGO-1759 > URL: https://issues.apache.org/jira/browse/TOBAGO-1759 > Project: MyFaces Tobago > Issue Type: Task > Components: Core, Themes >Reporter: Udo Schnurpfeil >Assignee: Henning Noeth > > Can be started after Bootstrap has released an beta version. > * Remind: Check if the problem with BootstrapClass.FADE in PopupRenderer is > solved (TOBAGO-1758). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (MYFACES-4127) Unexpected exception thrown when FlowMap is injected on a RequestScoped bean
[ https://issues.apache.org/jira/browse/MYFACES-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158710#comment-16158710 ] Eduardo Breijo edited comment on MYFACES-4127 at 9/8/17 2:33 PM: - Source code provided on ELImplicitObjectsViaCDI.war.zip was (Author: eduardobreijo): Source code > Unexpected exception thrown when FlowMap is injected on a RequestScoped bean > > > Key: MYFACES-4127 > URL: https://issues.apache.org/jira/browse/MYFACES-4127 > Project: MyFaces Core > Issue Type: Bug >Affects Versions: 2.3.0-beta >Reporter: Eduardo Breijo >Priority: Minor > Fix For: 2.3.0 > > Attachments: ConfigItems.java, ELImplicitObjectsViaCDI.war, > ELImplicitObjectsViaCDI.war.zip > > > When @FlowMap is injected on a RequestScoped bean, and you try to use that > object (which should be null since we are not inside of a flow), an > unexpected exception is thrown. This was noted after JIRA issue: > https://issues.apache.org/jira/browse/MYFACES-4126 > Caused by: org.jboss.weld.exceptions.IllegalProductException: WELD-52: > Cannot return null from a non-dependent producer method: Producer for > Producer Method [Map
Re: Migrate all MyFaces projects to Git
> Finally I have a working setup to migrate the subversion history to git. > I already started with Tobago yesterday, Trinidad will follow till Sunday. > > The result for Tobago is the following, will send another mail after > having pushed this to Gitbox: Tobago is finished: https://gitbox.apache.org/repos/asf/myfaces-tobago.git Please no longer use svn for Tobago, I've requested to set it to readonly. Cheers Dennis