[jira] [Created] (FEDIZ-179) Update IdP to Spring Security 3.2
Colm O hEigeartaigh created FEDIZ-179: - Summary: Update IdP to Spring Security 3.2 Key: FEDIZ-179 URL: https://issues.apache.org/jira/browse/FEDIZ-179 Project: CXF-Fediz Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.4.0 Update IdP to Spring Security 3.2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-6969) CXF Async HTTP Transport - add supports to configure httpclient with new method
[ https://issues.apache.org/jira/browse/CXF-6969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663447#comment-15663447 ] Sergey Beryozkin commented on CXF-6969: --- Hi Freeman Thanks, yes, that was always there, one would pass String properties via JAX-RS 2.0 Configuration and they would make it into AsyncHttpConduit where some of them would be wrapped into RequestConfig. And I agree that some properties are not even client specific. So now that I look deeper into this issue I'm actually not sure what this issue is about. [~violkim], can you clarify, what *new method* of configuring *which* properties you'd like to be supported ? > CXF Async HTTP Transport - add supports to configure httpclient with new > method > --- > > Key: CXF-6969 > URL: https://issues.apache.org/jira/browse/CXF-6969 > Project: CXF > Issue Type: Improvement > Components: Transports >Reporter: Chester Kim >Assignee: Freeman Fang > > Refer to https://issues.apache.org/jira/browse/CXF-6964 > Configuration of timeout and etc of httpclient with properties are deprecated > in the latest version of apache httpcomponents. We need to go with new way > (Configuration class). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FEDIZ-179) Update IdP to Spring Security 3.2
[ https://issues.apache.org/jira/browse/FEDIZ-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved FEDIZ-179. --- Resolution: Fixed > Update IdP to Spring Security 3.2 > - > > Key: FEDIZ-179 > URL: https://issues.apache.org/jira/browse/FEDIZ-179 > Project: CXF-Fediz > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 1.4.0 > > > Update IdP to Spring Security 3.2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CXF-7131) JAX-WS Client: HolderInInterceptor misbehaving on multipart/repalted SwA message: IndexOutOfBoundException
Diego Pietralunga created CXF-7131:
--
Summary: JAX-WS Client: HolderInInterceptor misbehaving on
multipart/repalted SwA message: IndexOutOfBoundException
Key: CXF-7131
URL: https://issues.apache.org/jira/browse/CXF-7131
Project: CXF
Issue Type: Bug
Components: JAX-WS Runtime
Affects Versions: 3.1.8
Environment: Oracle JDK 1.7.0_79 64-Bit, Linux (OpenSuse 42.1)
Reporter: Diego Pietralunga
Hi.
I'm getting a IndexOutOfBoundException when receiving a SwA message
(multipart/related).
I produce the stubs with Wsdl2Java with params
"-verbose -autoNameResolution -client" on my wsdl; operation looks ok with
this output:
Loading FrontEnd jaxws ...
Loading DataBinding jaxb ...
wsdl2java -verbose -autoNameResolution -client -d cxfIssuesJira3
./apache-cxf-3.1.8/ricercaImprese1.2-icar.wsdl
wsdl2java - Apache CXF 3.1.8
Nov 14, 2016 12:16:40 PM org.apache.cxf.wsdl11.WSDLServiceBuilder
checkForWrapped
INFO: Operation {http://it.ictechnology.pcad.ws}ricercaImpreseCodiceFiscale
cannot be unwrapped, input and output messages (if present) must contain only a
single part
Nov 14, 2016 12:16:40 PM org.apache.cxf.wsdl11.WSDLServiceBuilder
checkForWrapped
INFO: Operation {http://it.ictechnology.pcad.ws}ricercaImpreseNRea cannot be
unwrapped, input and output messages (if present) must contain only a single
part
Nov 14, 2016 12:16:40 PM org.apache.cxf.wsdl11.WSDLServiceBuilder
checkForWrapped
INFO: Operation {http://it.ictechnology.pcad.ws}ricercaImpreseDenominazione
cannot be unwrapped, input and output messages (if present) must contain only a
single part
This generates the Port/Service/Holders architecture. I populate data for the
request and then I launch the generated client program untouched, except for:
- Using BindingProvider.ENDPOINT_ADDRESS_PROPERTY to set the target
-adding WSS4JOutInterceptor to provide USERNAME_TOKEN & password callback
method to the endpoint (getting a proxy)
Upon invocation, I get:
/***/
WARNING: Interceptor for
{http://it.ictechnology.pcad.ws}ricercaImpreseService#{http://it.ictechnology.pcad.ws}ricercaImpreseCodiceFiscale
has thrown exception, unwinding now
java.lang.IndexOutOfBoundsException: Index: 3, Size: 3
at java.util.ArrayList.rangeCheck(ArrayList.java:635)
at java.util.ArrayList.get(ArrayList.java:411)
at
org.apache.cxf.message.MessageContentsList.get(MessageContentsList.java:80)
at
org.apache.cxf.jaxws.interceptors.HolderInInterceptor.handleMessage(HolderInInterceptor.java:69)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:798)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1670)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1551)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1348)
at
org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651)
at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139)
at com.sun.proxy.$Proxy33.ricercaImpreseCodiceFiscale(Unknown Source)
at
ws.pcad.ictechnology.it.RicercaImprese_RicercaImprese_Client.main(RicercaImprese_RicercaImprese_Client.java:101)
Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: Index: 3,
Size: 3
at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:161)
at com.sun.proxy.$Proxy33.ricercaImpreseCodiceFiscale(Unknown Source)
at
ws.pcad.ictechnology.it.RicercaImprese_RicercaImprese_Client.main(RicercaImprese_RicercaImprese_Client.java:101)
Caused by: java.lang.IndexOutOfBoundsException: Index: 3, Size: 3
at java.util.ArrayList.rangeCheck(ArrayList.java:635)
at java.util.ArrayList.get(ArrayList.java:411)
at
org.apache.cxf.message.MessageContentsList.get(MessageContentsList.java:80)
at
org.apache.cxf.jaxws.interceptors.HolderInInterceptor.handleMessage(HolderInInte
[jira] [Updated] (CXF-7131) JAX-WS Client: HolderInInterceptor misbehaving on multipart/repalted SwA message: IndexOutOfBoundException
[
https://issues.apache.org/jira/browse/CXF-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diego Pietralunga updated CXF-7131:
---
Description:
Hi.
I'm getting a IndexOutOfBoundException when receiving a SwA message
(multipart/related).
I produce the stubs with Wsdl2Java with params
"-verbose -autoNameResolution -client" on my wsdl; operation looks ok with
this output:
Loading FrontEnd jaxws ...
Loading DataBinding jaxb ...
wsdl2java -verbose -autoNameResolution -client -d cxfIssuesJira3
./apache-cxf-3.1.8/ricercaImprese1.2-icar.wsdl
wsdl2java - Apache CXF 3.1.8
Nov 14, 2016 12:16:40 PM org.apache.cxf.wsdl11.WSDLServiceBuilder
checkForWrapped
INFO: Operation {http://it.ictechnology.pcad.ws}ricercaImpreseCodiceFiscale
cannot be unwrapped, input and output messages (if present) must contain only a
single part
Nov 14, 2016 12:16:40 PM org.apache.cxf.wsdl11.WSDLServiceBuilder
checkForWrapped
INFO: Operation {http://it.ictechnology.pcad.ws}ricercaImpreseNRea cannot be
unwrapped, input and output messages (if present) must contain only a single
part
Nov 14, 2016 12:16:40 PM org.apache.cxf.wsdl11.WSDLServiceBuilder
checkForWrapped
INFO: Operation {http://it.ictechnology.pcad.ws}ricercaImpreseDenominazione
cannot be unwrapped, input and output messages (if present) must contain only a
single part
This generates the Port/Service/Holders architecture. I populate data for the
request and then I launch the generated client program untouched, except for:
- Using BindingProvider.ENDPOINT_ADDRESS_PROPERTY to set the target
- adding WSS4JOutInterceptor to provide USERNAME_TOKEN & password callback
method to the endpoint (getting a proxy)
Upon invocation, I get:
/***/
WARNING: Interceptor for
{http://it.ictechnology.pcad.ws}ricercaImpreseService#{http://it.ictechnology.pcad.ws}ricercaImpreseCodiceFiscale
has thrown exception, unwinding now
java.lang.IndexOutOfBoundsException: Index: 3, Size: 3
at java.util.ArrayList.rangeCheck(ArrayList.java:635)
at java.util.ArrayList.get(ArrayList.java:411)
at
org.apache.cxf.message.MessageContentsList.get(MessageContentsList.java:80)
at
org.apache.cxf.jaxws.interceptors.HolderInInterceptor.handleMessage(HolderInInterceptor.java:69)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:798)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1670)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1551)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1348)
at
org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651)
at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139)
at com.sun.proxy.$Proxy33.ricercaImpreseCodiceFiscale(Unknown Source)
at
ws.pcad.ictechnology.it.RicercaImprese_RicercaImprese_Client.main(RicercaImprese_RicercaImprese_Client.java:101)
Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: Index: 3,
Size: 3
at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:161)
at com.sun.proxy.$Proxy33.ricercaImpreseCodiceFiscale(Unknown Source)
at
ws.pcad.ictechnology.it.RicercaImprese_RicercaImprese_Client.main(RicercaImprese_RicercaImprese_Client.java:101)
Caused by: java.lang.IndexOutOfBoundsException: Index: 3, Size: 3
at java.util.ArrayList.rangeCheck(ArrayList.java:635)
at java.util.ArrayList.get(ArrayList.java:411)
at
org.apache.cxf.message.MessageContentsList.get(MessageContentsList.java:80)
at
org.apache.cxf.jaxws.interceptors.HolderInInterceptor.handleMessage(HolderInInterceptor.java:69)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:798)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1670)
[jira] [Commented] (CXF-7131) JAX-WS Client: HolderInInterceptor misbehaving on multipart/repalted SwA message: IndexOutOfBoundException
[
https://issues.apache.org/jira/browse/CXF-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663779#comment-15663779
]
Diego Pietralunga commented on CXF-7131:
Linking an example incoming message (Multipart/related Swa) as logged by CXF
LoggingInInterceptor (default settings) here: http://pastebin.com/Q8S3qyJw
> JAX-WS Client: HolderInInterceptor misbehaving on multipart/repalted SwA
> message: IndexOutOfBoundException
> --
>
> Key: CXF-7131
> URL: https://issues.apache.org/jira/browse/CXF-7131
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
>Affects Versions: 3.1.8
> Environment: Oracle JDK 1.7.0_79 64-Bit, Linux (OpenSuse 42.1)
>Reporter: Diego Pietralunga
>
> Hi.
> I'm getting a IndexOutOfBoundException when receiving a SwA message
> (multipart/related).
> I produce the stubs with Wsdl2Java with params
> "-verbose -autoNameResolution -client" on my wsdl; operation looks ok
> with this output:
>
> Loading FrontEnd jaxws ...
> Loading DataBinding jaxb ...
> wsdl2java -verbose -autoNameResolution -client -d cxfIssuesJira3
> ./apache-cxf-3.1.8/ricercaImprese1.2-icar.wsdl
> wsdl2java - Apache CXF 3.1.8
> Nov 14, 2016 12:16:40 PM org.apache.cxf.wsdl11.WSDLServiceBuilder
> checkForWrapped
> INFO: Operation {http://it.ictechnology.pcad.ws}ricercaImpreseCodiceFiscale
> cannot be unwrapped, input and output messages (if present) must contain only
> a single part
> Nov 14, 2016 12:16:40 PM org.apache.cxf.wsdl11.WSDLServiceBuilder
> checkForWrapped
> INFO: Operation {http://it.ictechnology.pcad.ws}ricercaImpreseNRea cannot be
> unwrapped, input and output messages (if present) must contain only a single
> part
> Nov 14, 2016 12:16:40 PM org.apache.cxf.wsdl11.WSDLServiceBuilder
> checkForWrapped
> INFO: Operation {http://it.ictechnology.pcad.ws}ricercaImpreseDenominazione
> cannot be unwrapped, input and output messages (if present) must contain only
> a single part
>
> This generates the Port/Service/Holders architecture. I populate data for the
> request and then I launch the generated client program untouched, except for:
> - Using BindingProvider.ENDPOINT_ADDRESS_PROPERTY to set the target
> - adding WSS4JOutInterceptor to provide USERNAME_TOKEN & password callback
> method to the endpoint (getting a proxy)
> Upon invocation, I get:
> /***/
> WARNING: Interceptor for
> {http://it.ictechnology.pcad.ws}ricercaImpreseService#{http://it.ictechnology.pcad.ws}ricercaImpreseCodiceFiscale
> has thrown exception, unwinding now
> java.lang.IndexOutOfBoundsException: Index: 3, Size: 3
> at java.util.ArrayList.rangeCheck(ArrayList.java:635)
> at java.util.ArrayList.get(ArrayList.java:411)
> at
> org.apache.cxf.message.MessageContentsList.get(MessageContentsList.java:80)
> at
> org.apache.cxf.jaxws.interceptors.HolderInInterceptor.handleMessage(HolderInInterceptor.java:69)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:798)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1670)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1551)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1348)
> at
> org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
> at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651)
> at
> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277)
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
> at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139)
> at com.sun.proxy.$Proxy33.ricercaImpreseCodiceFiscale(Unknown Source)
> at
> ws.pcad.ictechnology.it.RicercaImprese_RicercaImprese_Client.main(RicercaImprese_RicercaImprese_Client.java:101)
> Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: Index: 3,
> Size: 3
> at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:161)
> at com.sun.proxy.$Pr
[jira] [Assigned] (CXF-7130) Maven plugin to invoke SOAP service
[ https://issues.apache.org/jira/browse/CXF-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7130: - Assignee: Freeman Fang > Maven plugin to invoke SOAP service > --- > > Key: CXF-7130 > URL: https://issues.apache.org/jira/browse/CXF-7130 > Project: CXF > Issue Type: Improvement > Components: Tooling >Affects Versions: 3.2.0 > Environment: Any >Reporter: Zoran Regvart >Assignee: Freeman Fang >Priority: Minor > > I needed a Maven plugin that would allow me to invoke SOAP service as a part > of Maven lifecycle so I implemented one, and I'm hoping that you can include > it in CXF. > The plugin has the functionality of calling SOAP service given a WSDL, port, > service, operation, request body and optional SOAP headers. Additionally > Maven project properties can be set from the response using XPath expressions > and additional XPath expression can be used to determine if the request needs > to be repeated. > This is a minimal implementation that I needed for my use-case, hope you find > it useful and that it can be incorporated in CXF. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-7117) Swagger2Feature not working in OSGi container when jaxrs server address not attached to CXF servlet
[
https://issues.apache.org/jira/browse/CXF-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15665689#comment-15665689
]
Andriy Redko commented on CXF-7117:
---
Hey [~nsaboy],
I have done a quick investigation and indeed, [~sergey_beryozkin] is right: the
issue is that ServletConfig, which Swagger uses for different parameters
resolution, is not available in case of the embedded Jetty transport. I will
try to figure out what options do we have here, but as for now, not much we can
do. As you already know, using `scan` would help but will interleave with other
JAX-RS resources deployed.
Thanks!
Best Regards,
Andriy Redko
> Swagger2Feature not working in OSGi container when jaxrs server address not
> attached to CXF servlet
> ---
>
> Key: CXF-7117
> URL: https://issues.apache.org/jira/browse/CXF-7117
> Project: CXF
> Issue Type: Bug
> Components: OSGi
>Affects Versions: 3.1.8
> Environment: Apache Karaf 3.0.8
>Reporter: Concombre Masqué
>Assignee: Andriy Redko
>
> Just modify sample description_swagger2_osgi as follows:
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
>
>
>
>
>
>
>
>
> address="http://localhost:9091/test/swaggerSample";>
>
>
>
>
>
>
>
>
>
>
>
>
> Then deploy modified bundle into Karaf and browse Swagger service definition
> at http://localhost:9091/test/swaggerSample/swagger.json
> Result is:
> {"swagger":"2.0"}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CXF-7132) CDI Multi-app tests fail when classes have scope
John D. Ament created CXF-7132: -- Summary: CDI Multi-app tests fail when classes have scope Key: CXF-7132 URL: https://issues.apache.org/jira/browse/CXF-7132 Project: CXF Issue Type: Bug Affects Versions: 3.1.9 Reporter: John D. Ament Fix For: 3.1.9 The multi-app tests fail due how to instances are managed in proxyable environments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-7132) CDI Multi-app tests fail when classes have scope
[ https://issues.apache.org/jira/browse/CXF-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated CXF-7132: --- Description: The multi-app tests fail due how to instances are managed in proxyable environments. When a normal scoped CDI Bean is used, the class is wrong. CXF is referencing the real class and getting a per-request instance of a CdiResourceProvider based instance. This causes fields to not be injected. (was: The multi-app tests fail due how to instances are managed in proxyable environments.) > CDI Multi-app tests fail when classes have scope > > > Key: CXF-7132 > URL: https://issues.apache.org/jira/browse/CXF-7132 > Project: CXF > Issue Type: Bug >Affects Versions: 3.1.9 >Reporter: John D. Ament > Fix For: 3.1.9 > > > The multi-app tests fail due how to instances are managed in proxyable > environments. When a normal scoped CDI Bean is used, the class is wrong. > CXF is referencing the real class and getting a per-request instance of a > CdiResourceProvider based instance. This causes fields to not be injected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-7132) CDI Multi-app tests fail when classes have scope
[ https://issues.apache.org/jira/browse/CXF-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15665896#comment-15665896 ] ASF GitHub Bot commented on CXF-7132: - GitHub user johnament opened a pull request: https://github.com/apache/cxf/pull/195 [CXF-7132] Use the original class when it comes to determining classe… …s for ResourceProvider usage. You can merge this pull request into a Git repository by running: $ git pull https://github.com/johnament/cxf CXF-7132 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cxf/pull/195.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #195 commit 6964968e9a43970290576f01f8634f8d892ebf03 Author: John D. Ament Date: 2016-11-15T01:26:58Z [CXF-7132] Use the original class when it comes to determining classes for ResourceProvider usage. > CDI Multi-app tests fail when classes have scope > > > Key: CXF-7132 > URL: https://issues.apache.org/jira/browse/CXF-7132 > Project: CXF > Issue Type: Bug >Affects Versions: 3.1.9 >Reporter: John D. Ament > Fix For: 3.1.9 > > > The multi-app tests fail due how to instances are managed in proxyable > environments. When a normal scoped CDI Bean is used, the class is wrong. > CXF is referencing the real class and getting a per-request instance of a > CdiResourceProvider based instance. This causes fields to not be injected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CXF-7133) Don't rely on disabled scanning in CDI
John D. Ament created CXF-7133: -- Summary: Don't rely on disabled scanning in CDI Key: CXF-7133 URL: https://issues.apache.org/jira/browse/CXF-7133 Project: CXF Issue Type: Bug Components: Integration Affects Versions: 3.1.9 Reporter: John D. Ament Fix For: 3.1.9 In CXF-7097, a scan tag was added to turn off default application scanning. This approach doesn't work for all packaging types, and creates a bit of an issue informing consumers. Would be better if the class were just written correctly to not be discovered. I have a patch, will raise after the other one. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
