[JBoss JIRA] (RF-11469) autocomplete method does not resolve bean if ui:included and only one parameter provided
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-11469?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-11469:
---------------------------------
I would add that [~Trims] additionally reproduced that both 3 or 1 parameter approaches doesn't show autocomplete (suggestions box?) with his sample. But that's another issue I would say.
{quote}
autocomplete looses scope of the beans(in the catch block) and this describes why there is no exception when using bean with 3 arguments. But still on the UI it doesn't work in both cases. There is just no exception in the second case.
{quote}
> autocomplete method does not resolve bean if ui:included and only one parameter provided
> ----------------------------------------------------------------------------------------
>
> Key: RF-11469
> URL: https://issues.jboss.org/browse/RF-11469
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.0.0.Final
> Reporter: u j
> Assignee: Brian Leathem
> Priority: Minor
> Attachments: RF-11469.zip
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> A bean parameter in the autocomplete method is not resolved if the rich:autocomplete is part of a ui:include.
> {code}
> <ui:include src="/searchlocation.xhtml">
> <ui:param name="bean" value="#{searchBean}" />
> </ui:include>
> {code}
> searchlocation.xhtml contains:
> {code}
> <rich:autocomplete id="cityName" mode="ajax" value="#{bean.cityName}" autocompleteMethod="#{bean.suggestCities}" />
> {code}
> The value binding works, but the binding in the autocompleteMethod gives:
> {code}
> 15:26:15,809 SEVERE [org.richfaces.log.Renderkit] (ajp-127.0.0.1-127.0.0.1-8009-1) Target Unreachable, identifier 'bean' resolved to null: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'bean' resolved to null
> at org.apache.el.parser.AstValue.getTarget(AstValue.java:75) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.parser.AstValue.invoke(AstValue.java:183) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.richfaces.renderkit.AutocompleteRendererBase.getItems(AutocompleteRendererBase.java:105) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeItems(AutocompleteRendererBase.java:160) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeMetaComponent(AutocompleteRendererBase.java:271) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RF-13178) RichFaces CDI Push fails with NoSuchElementException in OWB
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13178?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13178:
-------------------------------
Fix Version/s: 5.0.0.Alpha3
> RichFaces CDI Push fails with NoSuchElementException in OWB
> -----------------------------------------------------------
>
> Key: RF-13178
> URL: https://issues.jboss.org/browse/RF-13178
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 4.3.3
> Environment: Tomee 1.5.2 (Apache Tomcat (TomEE)/7.0.37))
> Reporter: Brian Leathem
> Labels: cdi, cdi11, owb
> Fix For: 5.0.0.Alpha3
>
>
> RichFaces push fails with a NoSuchElementException:
> {code}
> SEVERE: Servlet.service() for servlet [FacesServlet] in context with path [] threw exception [javax.el.ELException: java.util.NoSuchElementException] with root cause
> java.util.NoSuchElementException
> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:897)
> at java.util.HashMap$KeyIterator.next(HashMap.java:928)
> at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.getBeanReference(PushCDIExtension.java:172)
> at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.notify(PushCDIExtension.java:140)
> at org.apache.webbeans.event.NotificationManager.fireEvent(NotificationManager.java:429)
> at org.apache.webbeans.container.BeanManagerImpl.fireEvent(BeanManagerImpl.java:484)
> at org.apache.webbeans.event.EventImpl.fire(EventImpl.java:75)
> at ca.bleathem.sample.PushCdiBean.sendMessage(PushCdiBean.java:31)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.webbeans.intercept.InterceptorHandler.invoke(InterceptorHandler.java:322)
> at org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler.invoke(NormalScopedBeanInterceptorHandler.java:117)
> at org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler.invoke(NormalScopedBeanInterceptorHandler.java:108)
> at ca.bleathem.sample.PushCdiBean_$$_javassist_2.sendMessage(PushCdiBean_$$_javassist_2.java)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.el.parser.AstValue.invoke(AstValue.java:278)
> at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:274)
> at org.apache.myfaces.view.facelets.el.ContextAwareTagMethodExpression.invoke(ContextAwareTagMethodExpression.java:96)
> at org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:68)
> at javax.faces.component.UICommand.broadcast(UICommand.java:120)
> at javax.faces.component.UIViewRoot._broadcastAll(UIViewRoot.java:1028)
> at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:286)
> at javax.faces.component.UIViewRoot._process(UIViewRoot.java:1375)
> at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752)
> at org.apache.myfaces.lifecycle.InvokeApplicationExecutor.execute(InvokeApplicationExecutor.java:38)
> at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:170)
> at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:197)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:45)
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
> at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RF-13161) rich:notifyMessages CSS incorrect on MyFaces 2.x
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13161?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-13161:
----------------------------------
Assignee: Lukáš Fryč
> rich:notifyMessages CSS incorrect on MyFaces 2.x
> ------------------------------------------------
>
> Key: RF-13161
> URL: https://issues.jboss.org/browse/RF-13161
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.2.3.Final, 4.2.4, 4.3.0.Final, 4.3.1, 4.3.2, 4.3.3
> Reporter: John Yeary
> Assignee: Lukáš Fryč
> Labels: myfaces
> Fix For: 4.3.4
>
> Attachments: myfaces-rf-example.zip, myfaces-rf-example.zip, RichfacesNotifyMessagesMyFaces.png
>
>
> The FacesMessage Severity levels do not match between Mojarra and MyFaces. As a result, the CSS styling for INFO messages are one level higher than they should be, and FATAL messages are unstyled.
> *Mojarra* - These represent values 0-3
> {noformat}
> /**
> * <p>Array of all defined values, ascending order of ordinal value.
> * Be sure you include any new instances created above, in the
> * same order.</p>
> */
> private static final Severity[] values =
> { SEVERITY_INFO, SEVERITY_WARN, SEVERITY_ERROR, SEVERITY_FATAL };
> {noformat}
> *MyFaces* - These represent values 1-4
> {noformat}
> /**
> * Message severity level indicating an informational message rather than an error.
> */
> public static final FacesMessage.Severity SEVERITY_INFO = new Severity("Info", 1);
> /**
> * Message severity level indicating that an error might have occurred.
> */
> public static final FacesMessage.Severity SEVERITY_WARN = new Severity("Warn", 2);
> /**
> * Message severity level indicating that an error has occurred.
> */
> public static final FacesMessage.Severity SEVERITY_ERROR = new Severity("Error", 3);
> /**
> * Message severity level indicating that a serious error has occurred.
> */
> public static final FacesMessage.Severity SEVERITY_FATAL = new Severity("Fatal", 4);
> {noformat}
> The *<rich:messages/>* component behaves correctly, and may be used as an alternative.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RF-13161) rich:notifyMessages CSS incorrect on MyFaces 2.x
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13161?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13161:
------------------------------------
[~lfryc] +1. I've scheduled it to 4.3.4, and assigned it to you ;)
> rich:notifyMessages CSS incorrect on MyFaces 2.x
> ------------------------------------------------
>
> Key: RF-13161
> URL: https://issues.jboss.org/browse/RF-13161
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.2.3.Final, 4.2.4, 4.3.0.Final, 4.3.1, 4.3.2, 4.3.3
> Reporter: John Yeary
> Assignee: Lukáš Fryč
> Labels: myfaces
> Fix For: 4.3.4
>
> Attachments: myfaces-rf-example.zip, myfaces-rf-example.zip, RichfacesNotifyMessagesMyFaces.png
>
>
> The FacesMessage Severity levels do not match between Mojarra and MyFaces. As a result, the CSS styling for INFO messages are one level higher than they should be, and FATAL messages are unstyled.
> *Mojarra* - These represent values 0-3
> {noformat}
> /**
> * <p>Array of all defined values, ascending order of ordinal value.
> * Be sure you include any new instances created above, in the
> * same order.</p>
> */
> private static final Severity[] values =
> { SEVERITY_INFO, SEVERITY_WARN, SEVERITY_ERROR, SEVERITY_FATAL };
> {noformat}
> *MyFaces* - These represent values 1-4
> {noformat}
> /**
> * Message severity level indicating an informational message rather than an error.
> */
> public static final FacesMessage.Severity SEVERITY_INFO = new Severity("Info", 1);
> /**
> * Message severity level indicating that an error might have occurred.
> */
> public static final FacesMessage.Severity SEVERITY_WARN = new Severity("Warn", 2);
> /**
> * Message severity level indicating that an error has occurred.
> */
> public static final FacesMessage.Severity SEVERITY_ERROR = new Severity("Error", 3);
> /**
> * Message severity level indicating that a serious error has occurred.
> */
> public static final FacesMessage.Severity SEVERITY_FATAL = new Severity("Fatal", 4);
> {noformat}
> The *<rich:messages/>* component behaves correctly, and may be used as an alternative.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RF-11469) autocomplete method does not resolve bean if ui:included and only one parameter provided
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-11469?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-11469:
------------------------------------
To summarize, the autocomplete method does not resolve under the following conditions:
# the autocomplete method in the backing bean is defined with a single parameter, instead of 3
# it's used within a ui:include
Workarounds are to either:
* define your autocomplete method with 3 parameters
* use a composite component, rather than a ui:inlcude.
A resolution to the issue could be to attempt invoking the method with a single parameter when a _MethodNotFoundException_ is thrown, before falling back to the fallback of creating a new MethodExpression.
[~lfryc] the above resolution should work, and would not break backward compatibility in 4.3.x. Then in RF 5 we could simplify the impl and use only the single parameter invocation.
> autocomplete method does not resolve bean if ui:included and only one parameter provided
> ----------------------------------------------------------------------------------------
>
> Key: RF-11469
> URL: https://issues.jboss.org/browse/RF-11469
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.0.0.Final
> Reporter: u j
> Assignee: Brian Leathem
> Priority: Minor
> Attachments: RF-11469.zip
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> A bean parameter in the autocomplete method is not resolved if the rich:autocomplete is part of a ui:include.
> {code}
> <ui:include src="/searchlocation.xhtml">
> <ui:param name="bean" value="#{searchBean}" />
> </ui:include>
> {code}
> searchlocation.xhtml contains:
> {code}
> <rich:autocomplete id="cityName" mode="ajax" value="#{bean.cityName}" autocompleteMethod="#{bean.suggestCities}" />
> {code}
> The value binding works, but the binding in the autocompleteMethod gives:
> {code}
> 15:26:15,809 SEVERE [org.richfaces.log.Renderkit] (ajp-127.0.0.1-127.0.0.1-8009-1) Target Unreachable, identifier 'bean' resolved to null: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'bean' resolved to null
> at org.apache.el.parser.AstValue.getTarget(AstValue.java:75) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.parser.AstValue.invoke(AstValue.java:183) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.richfaces.renderkit.AutocompleteRendererBase.getItems(AutocompleteRendererBase.java:105) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeItems(AutocompleteRendererBase.java:160) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeMetaComponent(AutocompleteRendererBase.java:271) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RF-13178) RichFaces CDI Push fails with NoSuchElementException in OWB
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13178?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13178:
------------------------------------
[~lfryc] Let's resolve this in RF 5. We can then backport to RF 4.3.x as appropriate.
> RichFaces CDI Push fails with NoSuchElementException in OWB
> -----------------------------------------------------------
>
> Key: RF-13178
> URL: https://issues.jboss.org/browse/RF-13178
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 4.3.3
> Environment: Tomee 1.5.2 (Apache Tomcat (TomEE)/7.0.37))
> Reporter: Brian Leathem
> Labels: cdi, cdi11, owb
>
> RichFaces push fails with a NoSuchElementException:
> {code}
> SEVERE: Servlet.service() for servlet [FacesServlet] in context with path [] threw exception [javax.el.ELException: java.util.NoSuchElementException] with root cause
> java.util.NoSuchElementException
> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:897)
> at java.util.HashMap$KeyIterator.next(HashMap.java:928)
> at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.getBeanReference(PushCDIExtension.java:172)
> at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.notify(PushCDIExtension.java:140)
> at org.apache.webbeans.event.NotificationManager.fireEvent(NotificationManager.java:429)
> at org.apache.webbeans.container.BeanManagerImpl.fireEvent(BeanManagerImpl.java:484)
> at org.apache.webbeans.event.EventImpl.fire(EventImpl.java:75)
> at ca.bleathem.sample.PushCdiBean.sendMessage(PushCdiBean.java:31)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.webbeans.intercept.InterceptorHandler.invoke(InterceptorHandler.java:322)
> at org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler.invoke(NormalScopedBeanInterceptorHandler.java:117)
> at org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler.invoke(NormalScopedBeanInterceptorHandler.java:108)
> at ca.bleathem.sample.PushCdiBean_$$_javassist_2.sendMessage(PushCdiBean_$$_javassist_2.java)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.el.parser.AstValue.invoke(AstValue.java:278)
> at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:274)
> at org.apache.myfaces.view.facelets.el.ContextAwareTagMethodExpression.invoke(ContextAwareTagMethodExpression.java:96)
> at org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:68)
> at javax.faces.component.UICommand.broadcast(UICommand.java:120)
> at javax.faces.component.UIViewRoot._broadcastAll(UIViewRoot.java:1028)
> at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:286)
> at javax.faces.component.UIViewRoot._process(UIViewRoot.java:1375)
> at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752)
> at org.apache.myfaces.lifecycle.InvokeApplicationExecutor.execute(InvokeApplicationExecutor.java:38)
> at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:170)
> at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:197)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:45)
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
> at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RF-13189) Update jquery.atmosphere.js in 4.3.x
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13189?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13189:
-------------------------------
Priority: Critical (was: Major)
> Update jquery.atmosphere.js in 4.3.x
> ------------------------------------
>
> Key: RF-13189
> URL: https://issues.jboss.org/browse/RF-13189
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 4.3.4
> Reporter: Lukáš Fryč
> Priority: Critical
> Fix For: 4.3.4
>
>
> The Atmosphere was upgraded to 1.0.17 in RF-13154, but jquery-atmosphere.js (JS) in {{components/core/ui}} project wasn't.
> The problem is jquery-atmosphere.js doesn't even exists in 1.0.17, it was removed after 1.0.13 (i.e. doesn't exist since 1.0.14).
> The new project atmosphere-javascript which contains jquery.atmosphere.js was created instead, but it has different versioning: 2.0.0 and 2.0.1 are available as of today.
> Few notes:
> * I have tried the showcase with Atmosphere 1.0.17 + JS 1.0.13
> ** it works
> ** JS got some changes here which could potentially stabilize
> * I have tried the showcase with Atmosphere 1.0.17 + JS 2.0.1
> ** it works
> ** JS was completely refactored but since it works, it seems API-compatible
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RF-13189) Update jquery.atmosphere.js in 4.3.x
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13189?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13189:
-------------------------------
Issue Type: Task (was: Feature Request)
> Update jquery.atmosphere.js in 4.3.x
> ------------------------------------
>
> Key: RF-13189
> URL: https://issues.jboss.org/browse/RF-13189
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 4.3.4
> Reporter: Lukáš Fryč
> Fix For: 4.3.4
>
>
> The Atmosphere was upgraded to 1.0.17 in RF-13154, but jquery-atmosphere.js (JS) in {{components/core/ui}} project wasn't.
> The problem is jquery-atmosphere.js doesn't even exists in 1.0.17, it was removed after 1.0.13 (i.e. doesn't exist since 1.0.14).
> The new project atmosphere-javascript which contains jquery.atmosphere.js was created instead, but it has different versioning: 2.0.0 and 2.0.1 are available as of today.
> Few notes:
> * I have tried the showcase with Atmosphere 1.0.17 + JS 1.0.13
> ** it works
> ** JS got some changes here which could potentially stabilize
> * I have tried the showcase with Atmosphere 1.0.17 + JS 2.0.1
> ** it works
> ** JS was completely refactored but since it works, it seems API-compatible
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RF-13189) Update jquery.atmosphere.js in 4.3.x
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13189?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13189:
-------------------------------
Fix Version/s: 4.3.4
> Update jquery.atmosphere.js in 4.3.x
> ------------------------------------
>
> Key: RF-13189
> URL: https://issues.jboss.org/browse/RF-13189
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 4.3.4
> Reporter: Lukáš Fryč
> Fix For: 4.3.4
>
>
> The Atmosphere was upgraded to 1.0.17 in RF-13154, but jquery-atmosphere.js (JS) in {{components/core/ui}} project wasn't.
> The problem is jquery-atmosphere.js doesn't even exists in 1.0.17, it was removed after 1.0.13 (i.e. doesn't exist since 1.0.14).
> The new project atmosphere-javascript which contains jquery.atmosphere.js was created instead, but it has different versioning: 2.0.0 and 2.0.1 are available as of today.
> Few notes:
> * I have tried the showcase with Atmosphere 1.0.17 + JS 1.0.13
> ** it works
> ** JS got some changes here which could potentially stabilize
> * I have tried the showcase with Atmosphere 1.0.17 + JS 2.0.1
> ** it works
> ** JS was completely refactored but since it works, it seems API-compatible
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RF-13189) Update jquery.atmosphere.js in 4.3.x
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13189?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13189:
------------------------------------
Note the availability of Atmosphere-jquery 1.0.17:
http://search.maven.org/#artifactdetails%7Corg.atmosphere%7Catmosphere-jq...
> Update jquery.atmosphere.js in 4.3.x
> ------------------------------------
>
> Key: RF-13189
> URL: https://issues.jboss.org/browse/RF-13189
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 4.3.4
> Reporter: Lukáš Fryč
>
> The Atmosphere was upgraded to 1.0.17 in RF-13154, but jquery-atmosphere.js (JS) in {{components/core/ui}} project wasn't.
> The problem is jquery-atmosphere.js doesn't even exists in 1.0.17, it was removed after 1.0.13 (i.e. doesn't exist since 1.0.14).
> The new project atmosphere-javascript which contains jquery.atmosphere.js was created instead, but it has different versioning: 2.0.0 and 2.0.1 are available as of today.
> Few notes:
> * I have tried the showcase with Atmosphere 1.0.17 + JS 1.0.13
> ** it works
> ** JS got some changes here which could potentially stabilize
> * I have tried the showcase with Atmosphere 1.0.17 + JS 2.0.1
> ** it works
> ** JS was completely refactored but since it works, it seems API-compatible
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months