[jira] [Created] (FEDIZ-213) Spring plugins don't handle token expiration properly
Colm O hEigeartaigh created FEDIZ-213: - Summary: Spring plugins don't handle token expiration properly Key: FEDIZ-213 URL: https://issues.apache.org/jira/browse/FEDIZ-213 Project: CXF-Fediz Issue Type: Bug Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.3.3, 1.4.3 The Spring plugins don't handle token expiration properly. The token context is not stored prior to redirection and so validation fails. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (FEDIZ-213) Spring plugins don't handle token expiration properly
[ https://issues.apache.org/jira/browse/FEDIZ-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved FEDIZ-213. --- Resolution: Fixed > Spring plugins don't handle token expiration properly > - > > Key: FEDIZ-213 > URL: https://issues.apache.org/jira/browse/FEDIZ-213 > Project: CXF-Fediz > Issue Type: Bug >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 1.3.3, 1.4.3 > > > The Spring plugins don't handle token expiration properly. The token context > is not stored prior to redirection and so validation fails. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (CXF-7529) [osgi] Stale CXF's javax.ws.rs.ext.RuntimeDelegate after refreshing rt-frontend-jaxrs bundle
[
https://issues.apache.org/jira/browse/CXF-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved CXF-7529.
---
Resolution: Fixed
> [osgi] Stale CXF's javax.ws.rs.ext.RuntimeDelegate after refreshing
> rt-frontend-jaxrs bundle
>
>
> Key: CXF-7529
> URL: https://issues.apache.org/jira/browse/CXF-7529
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS Security, OSGi
>Affects Versions: 3.1.13, 3.2.0
>Reporter: Grzegorz Grzybek
>Assignee: Freeman Fang
> Fix For: 3.1.14, 3.2.1
>
>
> When CXF JAX-RS runtime is initialized,
> {{javax.ws.rs.ext.RuntimeDelegate#cachedDelegate}} still keeps old instance
> leading to CL leaks and errors like this:
> {noformat}
> java.lang.NoClassDefFoundError:
> org/apache/cxf/jaxrs/impl/MetadataMap$KeyComparator
> at org.apache.cxf.jaxrs.impl.MetadataMap.keySet(MetadataMap.java:178)
> at javax.ws.rs.core.Response.fromResponse(Response.java:573)
> at
> org.apache.camel.component.cxf.jaxrs.SimpleCxfRsBinding.buildResponse(SimpleCxfRsBinding.java:170)
> at
> org.apache.camel.component.cxf.jaxrs.SimpleCxfRsBinding.populateCxfRsResponseFromExchange(SimpleCxfRsBinding.java:152)
> at
> org.apache.camel.component.cxf.jaxrs.CxfRsInvoker.returnResponse(CxfRsInvoker.java:184)
> at
> org.apache.camel.component.cxf.jaxrs.CxfRsInvoker.asyncInvoke(CxfRsInvoker.java:110)
> at
> org.apache.camel.component.cxf.jaxrs.CxfRsInvoker.performInvocation(CxfRsInvoker.java:68)
> at
> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:189)
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:99)
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59)
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.resume(PhaseInterceptorChain.java:278)
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:78)
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:254)
> at
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160)
> at
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:180)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:299)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:218)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:274)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)
> at
> org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
> at
> org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:287)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at
> org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handleAsync(Server.java:545)
> at org.eclipse.jetty.server.HttpChannel.handle
[jira] [Resolved] (CXF-7528) [osgi] rt-transports-http should not fail during servlet unregistration
[
https://issues.apache.org/jira/browse/CXF-7528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved CXF-7528.
---
Resolution: Fixed
> [osgi] rt-transports-http should not fail during servlet unregistration
> ---
>
> Key: CXF-7528
> URL: https://issues.apache.org/jira/browse/CXF-7528
> Project: CXF
> Issue Type: Improvement
> Components: OSGi
>Affects Versions: 3.2.0
>Reporter: Grzegorz Grzybek
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.1.14, 3.2.1
>
>
> When OSGi framework is reprovisioned (e.g., during Karaf feature
> reinstallation), there may be a race related to CXF servlet
> registration/unregistration and we can see this in logs:
> {noformat}
> 2017-08-02 09:04:23,554 | ERROR | lixDispatchQueue | cxf-rt-transports-http
> | FrameworkEvent ERROR - org.apache.cxf.cxf-rt-transports-http
> java.lang.IllegalArgumentException: Alias [/cxf] was never registered
> at
> org.ops4j.pax.web.service.internal.HttpServiceStarted.unregister(HttpServiceStarted.java:278)
> at
> org.ops4j.pax.web.service.internal.HttpServiceProxy.unregister(HttpServiceProxy.java:77)
> at
> org.apache.cxf.transport.http.osgi.ServletExporter.updated(ServletExporter.java:54)
> at
> org.apache.cxf.transport.http.osgi.HttpServiceTrackerCust.removedService(HttpServiceTrackerCust.java:52)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:956)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:1)
> at
> org.osgi.util.tracker.AbstractTracked.untrack(AbstractTracked.java:341)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:902)
> at
> org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:943)
> at
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:794)
> at
> org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:544)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4445)
> at org.apache.felix.framework.Felix.access$000(Felix.java:77)
> at org.apache.felix.framework.Felix$1.serviceChanged(Felix.java:404)
> at
> org.apache.felix.framework.ServiceRegistry.unregisterService(ServiceRegistry.java:153)
> at
> org.apache.felix.framework.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:128)
> at
> org.ops4j.pax.web.service.internal.Activator.updateController(Activator.java:336)
> at
> org.ops4j.pax.web.service.internal.Activator$2.run(Activator.java:286)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> I think it'd be good to just print warning (or information) and continue.
> When http service is reregistered, servlet will be registered in proper
> instance of HttpService
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CXF-7510) SSE integration in CDI abruptly fails with no indication why
[
https://issues.apache.org/jira/browse/CXF-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200274#comment-16200274
]
Sergey Beryozkin commented on CXF-7510:
---
Hi Andriy, the actual SSEFeature, can it be auto-discovered in the CDI case so
that it's not manually created ? I added a CXF Provider annotation to it
thanks, Sergey
> SSE integration in CDI abruptly fails with no indication why
>
>
> Key: CXF-7510
> URL: https://issues.apache.org/jira/browse/CXF-7510
> Project: CXF
> Issue Type: Bug
>Reporter: John D. Ament
>Assignee: Andriy Redko
>
> https://lists.apache.org/thread.html/10d99c0d013a3d23361a3898171e7bd2b311a509349433db3b6cacaa@%3Cusers.cxf.apache.org%3E
> has more details
> Intermittently, when bootstrapping CXF + CDI, the integration for SSE will
> fail. When it fails, there's no log messages indicating the issue, however
> attempts to invoke any rest endpoint will give a warning like:
> {code}
> Sep 17, 2017 7:50:33 PM org.apache.cxf.transport.servlet.ServletController
> invoke
> WARNING: Can't find the request for http://my-hostname:4403/rest's Observer
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CXF-7528) [osgi] rt-transports-http should not fail during servlet unregistration
[
https://issues.apache.org/jira/browse/CXF-7528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200279#comment-16200279
]
Freeman Fang commented on CXF-7528:
---
Patch applied on behalf of Grzegorz Grzybek with thanks!
> [osgi] rt-transports-http should not fail during servlet unregistration
> ---
>
> Key: CXF-7528
> URL: https://issues.apache.org/jira/browse/CXF-7528
> Project: CXF
> Issue Type: Improvement
> Components: OSGi
>Affects Versions: 3.2.0
>Reporter: Grzegorz Grzybek
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.1.14, 3.2.1
>
>
> When OSGi framework is reprovisioned (e.g., during Karaf feature
> reinstallation), there may be a race related to CXF servlet
> registration/unregistration and we can see this in logs:
> {noformat}
> 2017-08-02 09:04:23,554 | ERROR | lixDispatchQueue | cxf-rt-transports-http
> | FrameworkEvent ERROR - org.apache.cxf.cxf-rt-transports-http
> java.lang.IllegalArgumentException: Alias [/cxf] was never registered
> at
> org.ops4j.pax.web.service.internal.HttpServiceStarted.unregister(HttpServiceStarted.java:278)
> at
> org.ops4j.pax.web.service.internal.HttpServiceProxy.unregister(HttpServiceProxy.java:77)
> at
> org.apache.cxf.transport.http.osgi.ServletExporter.updated(ServletExporter.java:54)
> at
> org.apache.cxf.transport.http.osgi.HttpServiceTrackerCust.removedService(HttpServiceTrackerCust.java:52)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:956)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:1)
> at
> org.osgi.util.tracker.AbstractTracked.untrack(AbstractTracked.java:341)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:902)
> at
> org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:943)
> at
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:794)
> at
> org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:544)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4445)
> at org.apache.felix.framework.Felix.access$000(Felix.java:77)
> at org.apache.felix.framework.Felix$1.serviceChanged(Felix.java:404)
> at
> org.apache.felix.framework.ServiceRegistry.unregisterService(ServiceRegistry.java:153)
> at
> org.apache.felix.framework.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:128)
> at
> org.ops4j.pax.web.service.internal.Activator.updateController(Activator.java:336)
> at
> org.ops4j.pax.web.service.internal.Activator$2.run(Activator.java:286)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> I think it'd be good to just print warning (or information) and continue.
> When http service is reregistered, servlet will be registered in proper
> instance of HttpService
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CXF-7529) [osgi] Stale CXF's javax.ws.rs.ext.RuntimeDelegate after refreshing rt-frontend-jaxrs bundle
[
https://issues.apache.org/jira/browse/CXF-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200278#comment-16200278
]
Freeman Fang commented on CXF-7529:
---
Patch applied on behalf of Grzegorz Grzybek with thanks!
> [osgi] Stale CXF's javax.ws.rs.ext.RuntimeDelegate after refreshing
> rt-frontend-jaxrs bundle
>
>
> Key: CXF-7529
> URL: https://issues.apache.org/jira/browse/CXF-7529
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS Security, OSGi
>Affects Versions: 3.1.13, 3.2.0
>Reporter: Grzegorz Grzybek
>Assignee: Freeman Fang
> Fix For: 3.1.14, 3.2.1
>
>
> When CXF JAX-RS runtime is initialized,
> {{javax.ws.rs.ext.RuntimeDelegate#cachedDelegate}} still keeps old instance
> leading to CL leaks and errors like this:
> {noformat}
> java.lang.NoClassDefFoundError:
> org/apache/cxf/jaxrs/impl/MetadataMap$KeyComparator
> at org.apache.cxf.jaxrs.impl.MetadataMap.keySet(MetadataMap.java:178)
> at javax.ws.rs.core.Response.fromResponse(Response.java:573)
> at
> org.apache.camel.component.cxf.jaxrs.SimpleCxfRsBinding.buildResponse(SimpleCxfRsBinding.java:170)
> at
> org.apache.camel.component.cxf.jaxrs.SimpleCxfRsBinding.populateCxfRsResponseFromExchange(SimpleCxfRsBinding.java:152)
> at
> org.apache.camel.component.cxf.jaxrs.CxfRsInvoker.returnResponse(CxfRsInvoker.java:184)
> at
> org.apache.camel.component.cxf.jaxrs.CxfRsInvoker.asyncInvoke(CxfRsInvoker.java:110)
> at
> org.apache.camel.component.cxf.jaxrs.CxfRsInvoker.performInvocation(CxfRsInvoker.java:68)
> at
> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:189)
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:99)
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59)
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.resume(PhaseInterceptorChain.java:278)
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:78)
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:254)
> at
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160)
> at
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:180)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:299)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:218)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:274)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)
> at
> org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
> at
> org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:287)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at
> org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.S
[jira] [Commented] (CXF-7510) SSE integration in CDI abruptly fails with no indication why
[
https://issues.apache.org/jira/browse/CXF-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200291#comment-16200291
]
Andriy Redko commented on CXF-7510:
---
Hi Sergey,
The discovery is controlled by `bean-discovery-mode` property, which right now
is set to `all`, so the SseFeature and companion classes should be discovered
(and they are). Another option, suggested by [~johndament], is to use
`annotated` which means we should add CDI annotations (like `@Dependable`) in
order for classes to be discovered. Thanks.
Best Regards,
Andriy Redko
> SSE integration in CDI abruptly fails with no indication why
>
>
> Key: CXF-7510
> URL: https://issues.apache.org/jira/browse/CXF-7510
> Project: CXF
> Issue Type: Bug
>Reporter: John D. Ament
>Assignee: Andriy Redko
>
> https://lists.apache.org/thread.html/10d99c0d013a3d23361a3898171e7bd2b311a509349433db3b6cacaa@%3Cusers.cxf.apache.org%3E
> has more details
> Intermittently, when bootstrapping CXF + CDI, the integration for SSE will
> fail. When it fails, there's no log messages indicating the issue, however
> attempts to invoke any rest endpoint will give a warning like:
> {code}
> Sep 17, 2017 7:50:33 PM org.apache.cxf.transport.servlet.ServletController
> invoke
> WARNING: Can't find the request for http://my-hostname:4403/rest's Observer
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (CXF-7510) SSE integration in CDI abruptly fails with no indication why
[
https://issues.apache.org/jira/browse/CXF-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200312#comment-16200312
]
Sergey Beryozkin edited comment on CXF-7510 at 10/11/17 1:53 PM:
-
Hi Andriy, and John, - if it's is already discoverable then I guess there's no
need to add another annotations to it, as indeed, it is expected to work
without CDI as well...
thanks
was (Author: sergey_beryozkin):
Hi Andriy, ad John, - if it's is already discoverable then I guess there's no
need to add another annotations to it, as indeed, it is expected to work
without CDI as well...
thanks
> SSE integration in CDI abruptly fails with no indication why
>
>
> Key: CXF-7510
> URL: https://issues.apache.org/jira/browse/CXF-7510
> Project: CXF
> Issue Type: Bug
>Reporter: John D. Ament
>Assignee: Andriy Redko
>
> https://lists.apache.org/thread.html/10d99c0d013a3d23361a3898171e7bd2b311a509349433db3b6cacaa@%3Cusers.cxf.apache.org%3E
> has more details
> Intermittently, when bootstrapping CXF + CDI, the integration for SSE will
> fail. When it fails, there's no log messages indicating the issue, however
> attempts to invoke any rest endpoint will give a warning like:
> {code}
> Sep 17, 2017 7:50:33 PM org.apache.cxf.transport.servlet.ServletController
> invoke
> WARNING: Can't find the request for http://my-hostname:4403/rest's Observer
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CXF-7510) SSE integration in CDI abruptly fails with no indication why
[
https://issues.apache.org/jira/browse/CXF-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200312#comment-16200312
]
Sergey Beryozkin commented on CXF-7510:
---
Hi Andriy, ad John, - if it's is already discoverable then I guess there's no
need to add another annotations to it, as indeed, it is expected to work
without CDI as well...
thanks
> SSE integration in CDI abruptly fails with no indication why
>
>
> Key: CXF-7510
> URL: https://issues.apache.org/jira/browse/CXF-7510
> Project: CXF
> Issue Type: Bug
>Reporter: John D. Ament
>Assignee: Andriy Redko
>
> https://lists.apache.org/thread.html/10d99c0d013a3d23361a3898171e7bd2b311a509349433db3b6cacaa@%3Cusers.cxf.apache.org%3E
> has more details
> Intermittently, when bootstrapping CXF + CDI, the integration for SSE will
> fail. When it fails, there's no log messages indicating the issue, however
> attempts to invoke any rest endpoint will give a warning like:
> {code}
> Sep 17, 2017 7:50:33 PM org.apache.cxf.transport.servlet.ServletController
> invoke
> WARNING: Can't find the request for http://my-hostname:4403/rest's Observer
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CXF-7510) SSE integration in CDI abruptly fails with no indication why
[
https://issues.apache.org/jira/browse/CXF-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200326#comment-16200326
]
John D. Ament commented on CXF-7510:
Technically the discovery in this way will only work in some deployment
scenarios (e.g. WARs). I'm using Java SE/CDI SE, so the present beans.xml
would never be valid.
> SSE integration in CDI abruptly fails with no indication why
>
>
> Key: CXF-7510
> URL: https://issues.apache.org/jira/browse/CXF-7510
> Project: CXF
> Issue Type: Bug
>Reporter: John D. Ament
>Assignee: Andriy Redko
>
> https://lists.apache.org/thread.html/10d99c0d013a3d23361a3898171e7bd2b311a509349433db3b6cacaa@%3Cusers.cxf.apache.org%3E
> has more details
> Intermittently, when bootstrapping CXF + CDI, the integration for SSE will
> fail. When it fails, there's no log messages indicating the issue, however
> attempts to invoke any rest endpoint will give a warning like:
> {code}
> Sep 17, 2017 7:50:33 PM org.apache.cxf.transport.servlet.ServletController
> invoke
> WARNING: Can't find the request for http://my-hostname:4403/rest's Observer
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CXF-7510) SSE integration in CDI abruptly fails with no indication why
[
https://issues.apache.org/jira/browse/CXF-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200331#comment-16200331
]
Sergey Beryozkin commented on CXF-7510:
---
Right, but the actual SSEFeature should remain neutral.
> SSE integration in CDI abruptly fails with no indication why
>
>
> Key: CXF-7510
> URL: https://issues.apache.org/jira/browse/CXF-7510
> Project: CXF
> Issue Type: Bug
>Reporter: John D. Ament
>Assignee: Andriy Redko
>
> https://lists.apache.org/thread.html/10d99c0d013a3d23361a3898171e7bd2b311a509349433db3b6cacaa@%3Cusers.cxf.apache.org%3E
> has more details
> Intermittently, when bootstrapping CXF + CDI, the integration for SSE will
> fail. When it fails, there's no log messages indicating the issue, however
> attempts to invoke any rest endpoint will give a warning like:
> {code}
> Sep 17, 2017 7:50:33 PM org.apache.cxf.transport.servlet.ServletController
> invoke
> WARNING: Can't find the request for http://my-hostname:4403/rest's Observer
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CXF-7510) SSE integration in CDI abruptly fails with no indication why
[
https://issues.apache.org/jira/browse/CXF-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200337#comment-16200337
]
John D. Ament commented on CXF-7510:
Ah, nevermind. I see you already pushed up the change to add
{{bean-discovery-mode}}
> SSE integration in CDI abruptly fails with no indication why
>
>
> Key: CXF-7510
> URL: https://issues.apache.org/jira/browse/CXF-7510
> Project: CXF
> Issue Type: Bug
>Reporter: John D. Ament
>Assignee: Andriy Redko
>
> https://lists.apache.org/thread.html/10d99c0d013a3d23361a3898171e7bd2b311a509349433db3b6cacaa@%3Cusers.cxf.apache.org%3E
> has more details
> Intermittently, when bootstrapping CXF + CDI, the integration for SSE will
> fail. When it fails, there's no log messages indicating the issue, however
> attempts to invoke any rest endpoint will give a warning like:
> {code}
> Sep 17, 2017 7:50:33 PM org.apache.cxf.transport.servlet.ServletController
> invoke
> WARNING: Can't find the request for http://my-hostname:4403/rest's Observer
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CXF-7510) SSE integration in CDI abruptly fails with no indication why
[
https://issues.apache.org/jira/browse/CXF-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200515#comment-16200515
]
Andriy Redko commented on CXF-7510:
---
Thant's right, the SseFeature should remain neutral, and
{code}bean-discovery-mode{code} is there. [~johndament] could you please check
out if 3.2.1-SNAPSHOT works for you? The test is green for me after all the
changes.
> SSE integration in CDI abruptly fails with no indication why
>
>
> Key: CXF-7510
> URL: https://issues.apache.org/jira/browse/CXF-7510
> Project: CXF
> Issue Type: Bug
>Reporter: John D. Ament
>Assignee: Andriy Redko
>
> https://lists.apache.org/thread.html/10d99c0d013a3d23361a3898171e7bd2b311a509349433db3b6cacaa@%3Cusers.cxf.apache.org%3E
> has more details
> Intermittently, when bootstrapping CXF + CDI, the integration for SSE will
> fail. When it fails, there's no log messages indicating the issue, however
> attempts to invoke any rest endpoint will give a warning like:
> {code}
> Sep 17, 2017 7:50:33 PM org.apache.cxf.transport.servlet.ServletController
> invoke
> WARNING: Can't find the request for http://my-hostname:4403/rest's Observer
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
