[jira] [Created] (CXF-6979) NPE in AbstractHTTPDestination.invoke when service is invoked very early
Christian Schneider created CXF-6979: Summary: NPE in AbstractHTTPDestination.invoke when service is invoked very early Key: CXF-6979 URL: https://issues.apache.org/jira/browse/CXF-6979 Project: CXF Issue Type: Bug Components: Transports Affects Versions: 3.1.6 Reporter: Christian Schneider Assignee: Christian Schneider Fix For: 3.1.7, 3.2.0 Happens when doing mvn clean install in DOSGi. It seems the incomingObserver is still null at this point. A possible fix is to set the observer before starting the endpoint. java.lang.NullPointerException at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:254) http://apaste.info/xk7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-5855) Introduce support for Server Sent Events
[ https://issues.apache.org/jira/browse/CXF-5855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393466#comment-15393466 ] Jean-Philippe CLEMENT commented on CXF-5855: Hello, any update on this topic? Thanks :) > Introduce support for Server Sent Events > > > Key: CXF-5855 > URL: https://issues.apache.org/jira/browse/CXF-5855 > Project: CXF > Issue Type: Sub-task > Components: Transports >Reporter: Sergey Beryozkin >Assignee: Andriy Redko > > We now have a good WebSocket transport support. It would be good to get > Server Sent Events (SSE) supported on top of it, I believe Atmosphere does > support SSE. > SSE has been voted as one of the most interesting technologies in EE 8 plans > and support for it will very likely be required in JAX-RS. Jersey leads the > way with its SSE support already -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-5855) Introduce support for Server Sent Events
[ https://issues.apache.org/jira/browse/CXF-5855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393478#comment-15393478 ] Sergey Beryozkin commented on CXF-5855: --- Andriy has spent a lot of his time on it, this feature is now operational on the master-jaxrs-2.1 branch. It is part of the JAX-RS 2.1 work and will be merged to the master once we have the early draft 2.1 API published to Central Sergey > Introduce support for Server Sent Events > > > Key: CXF-5855 > URL: https://issues.apache.org/jira/browse/CXF-5855 > Project: CXF > Issue Type: Sub-task > Components: Transports >Reporter: Sergey Beryozkin >Assignee: Andriy Redko > > We now have a good WebSocket transport support. It would be good to get > Server Sent Events (SSE) supported on top of it, I believe Atmosphere does > support SSE. > SSE has been voted as one of the most interesting technologies in EE 8 plans > and support for it will very likely be required in JAX-RS. Jersey leads the > way with its SSE support already -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-5855) Introduce support for Server Sent Events
[ https://issues.apache.org/jira/browse/CXF-5855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393834#comment-15393834 ] Jean-Philippe CLEMENT commented on CXF-5855: Is there any outlook when it would be available in CXF (so after JAX-RS 2.1 would be released)? > Introduce support for Server Sent Events > > > Key: CXF-5855 > URL: https://issues.apache.org/jira/browse/CXF-5855 > Project: CXF > Issue Type: Sub-task > Components: Transports >Reporter: Sergey Beryozkin >Assignee: Andriy Redko > > We now have a good WebSocket transport support. It would be good to get > Server Sent Events (SSE) supported on top of it, I believe Atmosphere does > support SSE. > SSE has been voted as one of the most interesting technologies in EE 8 plans > and support for it will very likely be required in JAX-RS. Jersey leads the > way with its SSE support already -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-5855) Introduce support for Server Sent Events
[ https://issues.apache.org/jira/browse/CXF-5855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393866#comment-15393866 ] Sergey Beryozkin commented on CXF-5855: --- It will be another few months at least, we need a 2.1 API early draft released by spec leads first, and only then start consider merging it all to master > Introduce support for Server Sent Events > > > Key: CXF-5855 > URL: https://issues.apache.org/jira/browse/CXF-5855 > Project: CXF > Issue Type: Sub-task > Components: Transports >Reporter: Sergey Beryozkin >Assignee: Andriy Redko > > We now have a good WebSocket transport support. It would be good to get > Server Sent Events (SSE) supported on top of it, I believe Atmosphere does > support SSE. > SSE has been voted as one of the most interesting technologies in EE 8 plans > and support for it will very likely be required in JAX-RS. Jersey leads the > way with its SSE support already -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CXF-6980) NPE when install cxf-http-async feature
[
https://issues.apache.org/jira/browse/CXF-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang reassigned CXF-6980:
-
Assignee: Freeman Fang
> NPE when install cxf-http-async feature
> ---
>
> Key: CXF-6980
> URL: https://issues.apache.org/jira/browse/CXF-6980
> Project: CXF
> Issue Type: Bug
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>
> exception like
> {code}
> Unexpected problem updating configuration org.apache.cxf.transport.http.async
> java.lang.NullPointerException
> at
> org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduitFactory.addListener(AsyncHTTPConduitFactory.java:288)[298:org.apache.cxf.cxf-rt-transports-http-hc]
> at
> org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduitFactory.(AsyncHTTPConduitFactory.java:146)[298:org.apache.cxf.cxf-rt-transports-http-hc
> at
> org.apache.cxf.transport.http.asyncclient.Activator$ConduitConfigurer.updated(Activator.java:79)[298:org.apache.cxf.cxf-rt-transports-http-hc]
> at
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189)[7:org.apache.felix.configadmin:1.8.4]
> at
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152)[7:org.apache.felix.configadmin:1.8.4]
> at
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85)[7:org.apache.felix.configadmin:1.8.4]
> {code}
> This is caused by if we install cxf-http-async feature without an aync cxf
> client endpoint, there's no CXF bus when init the AsyncHTTPConduitFactory, we
> need handle this case correctly
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CXF-6980) NPE when install cxf-http-async feature
Freeman Fang created CXF-6980:
-
Summary: NPE when install cxf-http-async feature
Key: CXF-6980
URL: https://issues.apache.org/jira/browse/CXF-6980
Project: CXF
Issue Type: Bug
Reporter: Freeman Fang
exception like
{code}
Unexpected problem updating configuration org.apache.cxf.transport.http.async
java.lang.NullPointerException
at
org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduitFactory.addListener(AsyncHTTPConduitFactory.java:288)[298:org.apache.cxf.cxf-rt-transports-http-hc]
at
org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduitFactory.(AsyncHTTPConduitFactory.java:146)[298:org.apache.cxf.cxf-rt-transports-http-hc
at
org.apache.cxf.transport.http.asyncclient.Activator$ConduitConfigurer.updated(Activator.java:79)[298:org.apache.cxf.cxf-rt-transports-http-hc]
at
org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189)[7:org.apache.felix.configadmin:1.8.4]
at
org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152)[7:org.apache.felix.configadmin:1.8.4]
at
org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85)[7:org.apache.felix.configadmin:1.8.4]
{code}
This is caused by if we install cxf-http-async feature without an aync cxf
client endpoint, there's no CXF bus when init the AsyncHTTPConduitFactory, we
need handle this case correctly
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6980) NPE when install cxf-http-async feature
[
https://issues.apache.org/jira/browse/CXF-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394935#comment-15394935
]
Freeman Fang commented on CXF-6980:
---
figured this is already fixed by CXF-6887
> NPE when install cxf-http-async feature
> ---
>
> Key: CXF-6980
> URL: https://issues.apache.org/jira/browse/CXF-6980
> Project: CXF
> Issue Type: Bug
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>
> exception like
> {code}
> Unexpected problem updating configuration org.apache.cxf.transport.http.async
> java.lang.NullPointerException
> at
> org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduitFactory.addListener(AsyncHTTPConduitFactory.java:288)[298:org.apache.cxf.cxf-rt-transports-http-hc]
> at
> org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduitFactory.(AsyncHTTPConduitFactory.java:146)[298:org.apache.cxf.cxf-rt-transports-http-hc
> at
> org.apache.cxf.transport.http.asyncclient.Activator$ConduitConfigurer.updated(Activator.java:79)[298:org.apache.cxf.cxf-rt-transports-http-hc]
> at
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189)[7:org.apache.felix.configadmin:1.8.4]
> at
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152)[7:org.apache.felix.configadmin:1.8.4]
> at
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85)[7:org.apache.felix.configadmin:1.8.4]
> {code}
> This is caused by if we install cxf-http-async feature without an aync cxf
> client endpoint, there's no CXF bus when init the AsyncHTTPConduitFactory, we
> need handle this case correctly
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CXF-6980) NPE when install cxf-http-async feature
[
https://issues.apache.org/jira/browse/CXF-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved CXF-6980.
---
Resolution: Duplicate
> NPE when install cxf-http-async feature
> ---
>
> Key: CXF-6980
> URL: https://issues.apache.org/jira/browse/CXF-6980
> Project: CXF
> Issue Type: Bug
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>
> exception like
> {code}
> Unexpected problem updating configuration org.apache.cxf.transport.http.async
> java.lang.NullPointerException
> at
> org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduitFactory.addListener(AsyncHTTPConduitFactory.java:288)[298:org.apache.cxf.cxf-rt-transports-http-hc]
> at
> org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduitFactory.(AsyncHTTPConduitFactory.java:146)[298:org.apache.cxf.cxf-rt-transports-http-hc
> at
> org.apache.cxf.transport.http.asyncclient.Activator$ConduitConfigurer.updated(Activator.java:79)[298:org.apache.cxf.cxf-rt-transports-http-hc]
> at
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189)[7:org.apache.felix.configadmin:1.8.4]
> at
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152)[7:org.apache.felix.configadmin:1.8.4]
> at
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85)[7:org.apache.felix.configadmin:1.8.4]
> {code}
> This is caused by if we install cxf-http-async feature without an aync cxf
> client endpoint, there's no CXF bus when init the AsyncHTTPConduitFactory, we
> need handle this case correctly
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
