[jira] [Updated] (MYFACES-4130) CDI @ManagedProperty does not work with all types
[ https://issues.apache.org/jira/browse/MYFACES-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Nicolucci updated MYFACES-4130: Status: Patch Available (was: Open) > CDI @ManagedProperty does not work with all types > - > > Key: MYFACES-4130 > URL: https://issues.apache.org/jira/browse/MYFACES-4130 > Project: MyFaces Core > Issue Type: Bug > Components: JSR-372 >Affects Versions: 2.3.0-beta >Reporter: Paul Nicolucci >Assignee: Paul Nicolucci > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MYFACES-4130) CDI @ManagedProperty does not work with all types
Paul Nicolucci created MYFACES-4130: --- Summary: CDI @ManagedProperty does not work with all types Key: MYFACES-4130 URL: https://issues.apache.org/jira/browse/MYFACES-4130 Project: MyFaces Core Issue Type: Bug Components: JSR-372 Affects Versions: 2.3.0-beta Reporter: Paul Nicolucci -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOBAGO-1773) Allow tc:style on tc:tab
[
https://issues.apache.org/jira/browse/TOBAGO-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107578#comment-16107578
]
Hudson commented on TOBAGO-1773:
SUCCESS: Integrated in Jenkins build Tobago Trunk #968 (See
[https://builds.apache.org/job/Tobago%20Trunk/968/])
TOBAGO-1773 Allow tc:style on tc:tab
* css classes and styles are now added to tc:tab (hnoeth:
[http://svn.apache.org/viewvc/?view=rev&rev=1803549])
* (edit)
tobago-trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/renderkit/renderer/TabGroupRenderer.java
> Allow tc:style on tc:tab
>
>
> Key: TOBAGO-1773
> URL: https://issues.apache.org/jira/browse/TOBAGO-1773
> Project: MyFaces Tobago
> Issue Type: Improvement
> Components: Core
>Affects Versions: 3.0.4
>Reporter: Henning Noeth
>Assignee: Henning Noeth
>Priority: Minor
>
> {code}
>
> ...
> {code}
> The tc:style tag doesn't have an effect.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (TOBAGO-1773) Allow tc:style on tc:tab
Henning Noeth created TOBAGO-1773:
-
Summary: Allow tc:style on tc:tab
Key: TOBAGO-1773
URL: https://issues.apache.org/jira/browse/TOBAGO-1773
Project: MyFaces Tobago
Issue Type: Improvement
Components: Core
Affects Versions: 3.0.4
Reporter: Henning Noeth
Assignee: Henning Noeth
Priority: Minor
{code}
...
{code}
The tc:style tag doesn't have an effect.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (TOBAGO-1767) tc:date: days in the past should have an specific CSS class
[ https://issues.apache.org/jira/browse/TOBAGO-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107463#comment-16107463 ] Hudson commented on TOBAGO-1767: SUCCESS: Integrated in Jenkins build Tobago Trunk #967 (See [https://builds.apache.org/job/Tobago%20Trunk/967/]) TOBAGO-1767 tc:date: days in the past should have an specific CSS class * css class is set after changing month (hnoeth: [http://svn.apache.org/viewvc/?view=rev&rev=1803541]) * (edit) tobago-trunk/tobago-theme/tobago-theme-standard/src/main/resources/META-INF/resources/tobago/standard/tobago-bootstrap/_version/js/tobago-calendar.js > tc:date: days in the past should have an specific CSS class > --- > > Key: TOBAGO-1767 > URL: https://issues.apache.org/jira/browse/TOBAGO-1767 > Project: MyFaces Tobago > Issue Type: Improvement > Components: Themes >Affects Versions: 3.0.4 >Reporter: Henning Noeth >Assignee: Henning Noeth >Priority: Minor > > Add the css class 'past' to all days which are in the past. > This provides an easy way to greyout the numbers of the past days with CSS. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYFACES-4129) When @FacesConfig annotation is used in a CDI bean, implicit EL objects don't work
[ https://issues.apache.org/jira/browse/MYFACES-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107342#comment-16107342 ] Dora Rajappan commented on MYFACES-4129: Applied patch and built 2.3.0 , deployed the war and tested this with pluto 3.0.0. Application scope is fine. > When @FacesConfig annotation is used in a CDI bean, implicit EL objects don't > work > -- > > Key: MYFACES-4129 > URL: https://issues.apache.org/jira/browse/MYFACES-4129 > Project: MyFaces Core > Issue Type: Bug >Affects Versions: 2.3.0-beta >Reporter: Eduardo Breijo > Attachments: ImplicitELObjects.war, MYFACES-4129.patch > > > When the @javax.faces.annotation.FacesConfig annotation is used in a CDI > bean, the implicit EL Objects from JSF 2.3 spec section 5.9.2 don't work. > This is because when that FacesConfig annotation is in a bean we remove the > implicit EL resolver from the chain so we don't have any mechanism for CDI to > do the resolution of the implicit objects. > Tested this on Mojarra and it works fine, with or without @FacesConfig > annotation. > A sample app is provided. It can be deployed on tomcat: > 1) Drive a request to: http://localhost:8080/ImplicitELObjects/index.jsf > 2) You should see that Application: ApplicationScope: and Component: are > empty since they cannot be resolved -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MYFACES-4128) pushComponentToEL should be called before isVisitable is called in visitTree of UIData, UIForm, UINamingContainer and UIRepeat
[ https://issues.apache.org/jira/browse/MYFACES-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Bohmann resolved MYFACES-4128. Resolution: Fixed Fix Version/s: 2.3.0 2.2.13 2.1.19 2.0.25 2.0.25-SNAPSHOT > pushComponentToEL should be called before isVisitable is called in visitTree > of UIData, UIForm, UINamingContainer and UIRepeat > -- > > Key: MYFACES-4128 > URL: https://issues.apache.org/jira/browse/MYFACES-4128 > Project: MyFaces Core > Issue Type: Bug >Affects Versions: 2.0.24, 2.1.18, 2.2.12, 2.3.0-beta >Reporter: Bernd Bohmann >Assignee: Bernd Bohmann > Fix For: 2.0.25-SNAPSHOT, 2.0.25, 2.1.19, 2.2.13, 2.3.0 > > Attachments: MYFACES-4128.patch > > > The implementation of UIComponent.visitTree is correct but pushComponentToEL > in UIData, UIForm, UINamingContainer and UIRepeat is called too late. > 'component' expressions will fail in these components. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYFACES-4128) pushComponentToEL should be called before isVisitable is called in visitTree of UIData, UIForm, UINamingContainer and UIRepeat
[ https://issues.apache.org/jira/browse/MYFACES-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107315#comment-16107315 ] Bernd Bohmann commented on MYFACES-4128: patch applied to all branches >= 2.0.x and trunk > pushComponentToEL should be called before isVisitable is called in visitTree > of UIData, UIForm, UINamingContainer and UIRepeat > -- > > Key: MYFACES-4128 > URL: https://issues.apache.org/jira/browse/MYFACES-4128 > Project: MyFaces Core > Issue Type: Bug >Affects Versions: 2.0.24, 2.1.18, 2.2.12, 2.3.0-beta >Reporter: Bernd Bohmann >Assignee: Bernd Bohmann > Attachments: MYFACES-4128.patch > > > The implementation of UIComponent.visitTree is correct but pushComponentToEL > in UIData, UIForm, UINamingContainer and UIRepeat is called too late. > 'component' expressions will fail in these components. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOBAGO-1751) Add META-tags to -tag
[ https://issues.apache.org/jira/browse/TOBAGO-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107299#comment-16107299 ] Guido Dubois commented on TOBAGO-1751: -- Now it works fine. Just a question: How about an attribute for injecting a file in raw format into the section? > Add META-tags to -tag > --- > > Key: TOBAGO-1751 > URL: https://issues.apache.org/jira/browse/TOBAGO-1751 > Project: MyFaces Tobago > Issue Type: New Feature > Components: Core >Reporter: Guido Dubois >Assignee: Udo Schnurpfeil >Priority: Minor > Fix For: 4.0.0 > > > Is there a simple way to include META-tags to the section of a > ? > It would be nice to have a tag according to or file=""> for this. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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&focusedCommentId=16107287#comment-16107287 ] Dora Rajappan commented on MYFACES-4127: Myfaces CDI integration to route the call via DefaultContextualInstanceStrategy.getIfExists rather than via DefaultContextualInstanceStrategy.get to show the ContextNotActiveException. Throwing ContextNotActiveException from FlowHandlerImpl (public Flow getCurrentFlow(FacesContext context)) when window is null fails lifecycle execute testcase. Hence not an option. > 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 > Attachments: ConfigItems.java > > > 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] with qualifiers [@FlowMap @Any] > declared as [[UnbackedAnnotatedMethod] @Produces @FlowMap @ApplicationScoped > public > org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer.getFlowMap()] > declared on Managed Bean [class > org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer] with qualifiers > [@Any @Default] > at > org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer.getFlowMap(ApplicationScopeObjectProducer.java:73) > StackTrace: > at > org.jboss.weld.bean.AbstractProducerBean.checkReturnValue(AbstractProducerBean.java:136) > at [internal classes] > at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96) > at > org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100) > at [internal classes] > at java.lang.String.valueOf(String.java:2994) > at java.lang.StringBuilder.append(StringBuilder.java:131) > at > com.ibm.ws.jsf23.fat.beans.ELImplicitObjectBean.execute(ELImplicitObjectBean.java:163) > On Mojarra 2.3, we get a different exception which looks more appropriate. > org.jboss.weld.contexts.ContextNotActiveException: WELD-001303: No active > contexts for scope type javax.faces.flow.FlowScoped > > org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:623) > > org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:89) > > org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63) > > org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:87) > > org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:125) > > org.jboss.weld.util.Map$1302817811$Proxy$_$$_WeldClientProxy.toString(Unknown > Source) > java.lang.String.valueOf(String.java:2994) > java.lang.StringBuilder.append(StringBuilder.java:131) > > com.ibm.ws.jsf23.fat.beans.ELImplicitObjectBean.execute(ELImplicitObjectBean.java:163) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOBAGO-1772) ResourceServlet: Resource not found if resourceDirs have the same prefix
[ https://issues.apache.org/jira/browse/TOBAGO-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volker Weber resolved TOBAGO-1772. -- Resolution: Fixed Fix Version/s: 2.1.1 > ResourceServlet: Resource not found if resourceDirs have the same prefix > - > > Key: TOBAGO-1772 > URL: https://issues.apache.org/jira/browse/TOBAGO-1772 > Project: MyFaces Tobago > Issue Type: Bug > Components: Core >Affects Versions: 2.1.0 >Reporter: Volker Weber >Assignee: Volker Weber > Fix For: 2.1.1 > > > We have two modules, one extends the other, which have the same resourceDir > prefix > * module 1: tobago-modules/testModule > * module 2: tobago-modules/testModuleExtras > The resources from _tobago-modules/testModuleExtras_ are not available. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOBAGO-1772) ResourceServlet: Resource not found if resourceDirs have the same prefix
[ https://issues.apache.org/jira/browse/TOBAGO-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107015#comment-16107015 ] Hudson commented on TOBAGO-1772: SUCCESS: Integrated in Jenkins build Tobago 2.0.x #1489 (See [https://builds.apache.org/job/Tobago%202.0.x/1489/]) TOBAGO-1772 - ResourceServlet: Resource not found if resourceDirs have the same prefix (weber: [http://svn.apache.org/viewvc/?view=rev&rev=1803495]) * (edit) tobago-2.0.x/tobago-core/src/main/java/org/apache/myfaces/tobago/servlet/ResourceServlet.java > ResourceServlet: Resource not found if resourceDirs have the same prefix > - > > Key: TOBAGO-1772 > URL: https://issues.apache.org/jira/browse/TOBAGO-1772 > Project: MyFaces Tobago > Issue Type: Bug > Components: Core >Affects Versions: 2.1.0 >Reporter: Volker Weber >Assignee: Volker Weber > > We have two modules, one extends the other, which have the same resourceDir > prefix > * module 1: tobago-modules/testModule > * module 2: tobago-modules/testModuleExtras > The resources from _tobago-modules/testModuleExtras_ are not available. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOBAGO-1772) ResourceServlet: Resource not found if resourceDirs have the same prefix
Volker Weber created TOBAGO-1772: Summary: ResourceServlet: Resource not found if resourceDirs have the same prefix Key: TOBAGO-1772 URL: https://issues.apache.org/jira/browse/TOBAGO-1772 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 2.1.0 Reporter: Volker Weber Assignee: Volker Weber We have two modules, one extends the other, which have the same resourceDir prefix * module 1: tobago-modules/testModule * module 2: tobago-modules/testModuleExtras The resources from _tobago-modules/testModuleExtras_ are not available. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
