[jira] [Created] (CXF-6913) [doc] Setting SSLSocketFactory on TLSClientParameters switches from async to sync HTTP
Torsten Mielke created CXF-6913:
---
Summary: [doc] Setting SSLSocketFactory on TLSClientParameters
switches from async to sync HTTP
Key: CXF-6913
URL: https://issues.apache.org/jira/browse/CXF-6913
Project: CXF
Issue Type: Improvement
Components: Documentation
Affects Versions: 3.1.6
Reporter: Torsten Mielke
The fix for CXF-5071 introduced a check in AsyncHTTPConduit.setupConnection()
{code:java}
if (uri.getScheme().equals("https")
&& clientParameters != null
&& clientParameters.getSSLSocketFactory() != null) {
//if they configured in an SSLSocketFactory, we cannot do anything
//with it as the NIO based transport cannot use socket created from
//the SSLSocketFactory.
o = false;
}
{code}
that makes CXF switch from an asynchronous to a synchronous HTTP transport if
the TLSClientParameters used sets an SSLSocketFactory.
This behaviour is undocumented and has caused confusion among customers. Can we
get this please documented on page
http://cxf.apache.org/docs/asynchronous-client-http-transport.html
Thanks,
Torsten
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CXF-6900) invalid signature in case of soap fault
[ https://issues.apache.org/jira/browse/CXF-6900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CXF-6900: - Fix Version/s: (was: 3.0.10) > invalid signature in case of soap fault > --- > > Key: CXF-6900 > URL: https://issues.apache.org/jira/browse/CXF-6900 > Project: CXF > Issue Type: Bug > Components: WS-* Components >Affects Versions: 3.0.3 > Environment: windows 2008 jdk 1.6.0_45 >Reporter: david leruse >Assignee: Colm O hEigeartaigh > Fix For: 3.1.7 > > Attachments: server7.log > > > Hello, > Having signature verification problems on the cxf client-side with a .NET > Ws-fed protected webservice, I ask you a little help... > Here is a summary of the problem : > Most of the time, communication works well excepted when we got a soap fault > message. > Indeed signature validation works usually well excepted when > we receive a fault message inside the body of the soap message. Even In this > boundary case, signature verification works well excepted for one element, > the fault message (see the enclosed server7.log file). > After digging a bit, i've found that the calculated digest couldn't be equal > to the claimed one because the content of the message given to the > DigesterOutpustrream is not well canonicalized or normalized. > Partial decrypted msg > ... > >xmlns="http://www.w3.org/2003/05/soap-envelope";>DataNotFoundFault xml:lang="nl-BE">ContextContactInfo with Id '1' does not > exist. xmlns="http://schemas.riziv.fgov.be/contact/2015/08/faults"; > xmlns:i="http://www.w3.org/2001/XMLSchema-instance";>ContextContactInfoNotFoundContextContactInfo > with Id '1' does not exist. > > ... > Predigested input : > http://www.w3.org/2003/05/soap-envelope"; > xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; > u:Id="_3"> xmlns="http://www.w3.org/2003/05/soap-envelope";>DataNotFoundFault xmlns="http://www.w3.org/2003/05/soap-envelope";> xml:lang="nl-BE">ContextContactInfo with Id '1' does not > exist. xmlns="http://schemas.riziv.fgov.be/contact/2015/08/faults";>ContextContactInfoNotFoundContextContactInfo > with Id '1' does not > exist. > Could you please check this problem and give me an advice ? > The library used are : > cxf 3.0.3 > wss4j 2.0.2 > xmlsec 2.0.2 > on a jdk 1.6.0_45 > Thanks in advance > David L -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FEDIZ-166) "No message body writer" error for OAuthError in the OIDC IdP
Colm O hEigeartaigh created FEDIZ-166:
-
Summary: "No message body writer" error for OAuthError in the OIDC
IdP
Key: FEDIZ-166
URL: https://issues.apache.org/jira/browse/FEDIZ-166
Project: CXF-Fediz
Issue Type: Bug
Affects Versions: 1.3.0
Reporter: Colm O hEigeartaigh
Fix For: 1.3.1
When an OAuthError is thrown in the Fediz OIDC IdP, such as for example the
client request redirect URI does not match the stored value, the following
exception is thrown (latest 1.3.1-SNAPSHOT code):
---
ID: 5
Response-Code: 500
Content-Type: text/plain
Headers: {Content-Type=[application/json], Date=[Tue, 24 May 2016 10:22:56 GMT]}
Payload: No message body writer has been found for class
org.apache.cxf.rs.security.oauth2.common.OAuthError, ContentType:
application/json
--
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FEDIZ-167) JPA error with OIDC in Tomcat 8
Colm O hEigeartaigh created FEDIZ-167: - Summary: JPA error with OIDC in Tomcat 8 Key: FEDIZ-167 URL: https://issues.apache.org/jira/browse/FEDIZ-167 Project: CXF-Fediz Issue Type: Bug Reporter: Colm O hEigeartaigh Fix For: 1.3.1 There is a JPA error with the OIDC IdP in Tomcat 8. On the first user authentication, everything seems to happen again. Then if you clear the browser cache and try again you get the error attached below. Reproduced using Apache Tomcat 8.0.33 + HSQLDB 2.3.4. org.apache.openjpa.persistence.RollbackException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred. org.apache.openjpa.persistence.EntityManagerImpl.commit(EntityManagerImpl.java:595) org.apache.cxf.rs.security.oauth2.grants.code.JPACodeDataProvider.saveCodeGrant(JPACodeDataProvider.java:58) org.apache.cxf.rs.security.oauth2.grants.code.JPACodeDataProvider.createCodeGrant(JPACodeDataProvider.java:37) org.apache.cxf.rs.security.oauth2.services.AuthorizationCodeGrantService.getGrantRepresentation(AuthorizationCodeGrantService.java:139) org.apache.cxf.rs.security.oauth2.services.AuthorizationCodeGrantService.createGrant(AuthorizationCodeGrantService.java:99) org.apache.cxf.rs.security.oauth2.services.RedirectionBasedGrantService.startAuthorization(RedirectionBasedGrantService.java:215) org.apache.cxf.rs.security.oidc.idp.OidcAuthorizationCodeService.startAuthorization(OidcAuthorizationCodeService.java:76) org.apache.cxf.rs.security.oauth2.services.RedirectionBasedGrantService.startAuthorization(RedirectionBasedGrantService.java:128) org.apache.cxf.rs.security.oauth2.services.RedirectionBasedGrantService.authorize(RedirectionBasedGrantService.java:94) org.apache.cxf.rs.security.oauth2.services.AuthorizationService.authorize(AuthorizationService.java:58) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:498) org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180) org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:189) org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:99) org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59) org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96) org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:254) org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234) org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208) org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160) org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:180) org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:299) org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:223) javax.servlet.http.HttpServlet.service(HttpServlet.java:622) org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:274) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) org.apache.cxf.fediz.core.servlet.FederationFilter.doFilter(FederationFilter.java:60) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (FEDIZ-166) "No message body writer" error for OAuthError in the OIDC IdP
[
https://issues.apache.org/jira/browse/FEDIZ-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh reassigned FEDIZ-166:
-
Assignee: Colm O hEigeartaigh
> "No message body writer" error for OAuthError in the OIDC IdP
> -
>
> Key: FEDIZ-166
> URL: https://issues.apache.org/jira/browse/FEDIZ-166
> Project: CXF-Fediz
> Issue Type: Bug
>Affects Versions: 1.3.0
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
> Fix For: 1.3.1
>
>
> When an OAuthError is thrown in the Fediz OIDC IdP, such as for example the
> client request redirect URI does not match the stored value, the following
> exception is thrown (latest 1.3.1-SNAPSHOT code):
> ---
> ID: 5
> Response-Code: 500
> Content-Type: text/plain
> Headers: {Content-Type=[application/json], Date=[Tue, 24 May 2016 10:22:56
> GMT]}
> Payload: No message body writer has been found for class
> org.apache.cxf.rs.security.oauth2.common.OAuthError, ContentType:
> application/json
> --
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CXF-6913) [doc] Setting SSLSocketFactory on TLSClientParameters switches from async to sync HTTP
[
https://issues.apache.org/jira/browse/CXF-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang reassigned CXF-6913:
-
Assignee: Freeman Fang
> [doc] Setting SSLSocketFactory on TLSClientParameters switches from async to
> sync HTTP
> --
>
> Key: CXF-6913
> URL: https://issues.apache.org/jira/browse/CXF-6913
> Project: CXF
> Issue Type: Improvement
> Components: Documentation
>Affects Versions: 3.1.6
>Reporter: Torsten Mielke
>Assignee: Freeman Fang
> Labels: documentation
>
> The fix for CXF-5071 introduced a check in AsyncHTTPConduit.setupConnection()
> {code:java}
> if (uri.getScheme().equals("https")
> && clientParameters != null
> && clientParameters.getSSLSocketFactory() != null) {
> //if they configured in an SSLSocketFactory, we cannot do anything
> //with it as the NIO based transport cannot use socket created
> from
> //the SSLSocketFactory.
> o = false;
> }
> {code}
> that makes CXF switch from an asynchronous to a synchronous HTTP transport if
> the TLSClientParameters used sets an SSLSocketFactory.
> This behaviour is undocumented and has caused confusion among customers. Can
> we get this please documented on page
> http://cxf.apache.org/docs/asynchronous-client-http-transport.html
> Thanks,
> Torsten
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CXF-6914) JweJsonWriterInterceptor adds double quotes for non String unencoded payloads
Sergey Beryozkin created CXF-6914: - Summary: JweJsonWriterInterceptor adds double quotes for non String unencoded payloads Key: CXF-6914 URL: https://issues.apache.org/jira/browse/CXF-6914 Project: CXF Issue Type: Bug Reporter: Sergey Beryozkin Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-6914) JweJsonWriterInterceptor adds double quotes for non String unencoded payloads
[ https://issues.apache.org/jira/browse/CXF-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin updated CXF-6914: -- Fix Version/s: 3.2.0 3.1.7 Component/s: JAX-RS Security JAX-RS > JweJsonWriterInterceptor adds double quotes for non String unencoded payloads > -- > > Key: CXF-6914 > URL: https://issues.apache.org/jira/browse/CXF-6914 > Project: CXF > Issue Type: Bug > Components: JAX-RS, JAX-RS Security >Reporter: Sergey Beryozkin >Priority: Minor > Fix For: 3.1.7, 3.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-6914) JweJsonWriterInterceptor adds double quotes for non String unencoded payloads
[ https://issues.apache.org/jira/browse/CXF-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298128#comment-15298128 ] Sergey Beryozkin commented on CXF-6914: --- Resolving for Later just in case > JweJsonWriterInterceptor adds double quotes for non String unencoded payloads > -- > > Key: CXF-6914 > URL: https://issues.apache.org/jira/browse/CXF-6914 > Project: CXF > Issue Type: Bug > Components: JAX-RS, JAX-RS Security >Reporter: Sergey Beryozkin >Priority: Minor > Fix For: 3.1.7, 3.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CXF-6914) JweJsonWriterInterceptor adds double quotes for non String unencoded payloads
[ https://issues.apache.org/jira/browse/CXF-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-6914. --- Resolution: Later The spec actually warns that with the double quote property is lost with the unencoded payload, so it is the responsibility of the application to deal with it > JweJsonWriterInterceptor adds double quotes for non String unencoded payloads > -- > > Key: CXF-6914 > URL: https://issues.apache.org/jira/browse/CXF-6914 > Project: CXF > Issue Type: Bug > Components: JAX-RS, JAX-RS Security >Reporter: Sergey Beryozkin >Priority: Minor > Fix For: 3.1.7, 3.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-6900) invalid signature in case of soap fault
[ https://issues.apache.org/jira/browse/CXF-6900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298149#comment-15298149 ] Colm O hEigeartaigh commented on CXF-6900: -- Hi David, The problem here is actually a problem with the SAAJ implementation that comes with the JDK, where it "forces" the "env" prefix for a SOAP Fault when it does not have a pre-existing prefix. [~dkulp] and I have managed to "work around" this problem in CXF. Your test-case should now be working on the CXF master + 3.1.x-fixes branch. However, I believe it won't be backported to CXF 3.0.x, as there are too many changes involved. Colm. > invalid signature in case of soap fault > --- > > Key: CXF-6900 > URL: https://issues.apache.org/jira/browse/CXF-6900 > Project: CXF > Issue Type: Bug > Components: WS-* Components >Affects Versions: 3.0.3 > Environment: windows 2008 jdk 1.6.0_45 >Reporter: david leruse >Assignee: Colm O hEigeartaigh > Fix For: 3.1.7 > > Attachments: server7.log > > > Hello, > Having signature verification problems on the cxf client-side with a .NET > Ws-fed protected webservice, I ask you a little help... > Here is a summary of the problem : > Most of the time, communication works well excepted when we got a soap fault > message. > Indeed signature validation works usually well excepted when > we receive a fault message inside the body of the soap message. Even In this > boundary case, signature verification works well excepted for one element, > the fault message (see the enclosed server7.log file). > After digging a bit, i've found that the calculated digest couldn't be equal > to the claimed one because the content of the message given to the > DigesterOutpustrream is not well canonicalized or normalized. > Partial decrypted msg > ... > >xmlns="http://www.w3.org/2003/05/soap-envelope";>DataNotFoundFault xml:lang="nl-BE">ContextContactInfo with Id '1' does not > exist. xmlns="http://schemas.riziv.fgov.be/contact/2015/08/faults"; > xmlns:i="http://www.w3.org/2001/XMLSchema-instance";>ContextContactInfoNotFoundContextContactInfo > with Id '1' does not exist. > > ... > Predigested input : > http://www.w3.org/2003/05/soap-envelope"; > xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; > u:Id="_3"> xmlns="http://www.w3.org/2003/05/soap-envelope";>DataNotFoundFault xmlns="http://www.w3.org/2003/05/soap-envelope";> xml:lang="nl-BE">ContextContactInfo with Id '1' does not > exist. xmlns="http://schemas.riziv.fgov.be/contact/2015/08/faults";>ContextContactInfoNotFoundContextContactInfo > with Id '1' does not > exist. > Could you please check this problem and give me an advice ? > The library used are : > cxf 3.0.3 > wss4j 2.0.2 > xmlsec 2.0.2 > on a jdk 1.6.0_45 > Thanks in advance > David L -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CXF-6900) invalid signature in case of soap fault
[ https://issues.apache.org/jira/browse/CXF-6900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CXF-6900. -- Resolution: Fixed > invalid signature in case of soap fault > --- > > Key: CXF-6900 > URL: https://issues.apache.org/jira/browse/CXF-6900 > Project: CXF > Issue Type: Bug > Components: WS-* Components >Affects Versions: 3.0.3 > Environment: windows 2008 jdk 1.6.0_45 >Reporter: david leruse >Assignee: Colm O hEigeartaigh > Fix For: 3.1.7 > > Attachments: server7.log > > > Hello, > Having signature verification problems on the cxf client-side with a .NET > Ws-fed protected webservice, I ask you a little help... > Here is a summary of the problem : > Most of the time, communication works well excepted when we got a soap fault > message. > Indeed signature validation works usually well excepted when > we receive a fault message inside the body of the soap message. Even In this > boundary case, signature verification works well excepted for one element, > the fault message (see the enclosed server7.log file). > After digging a bit, i've found that the calculated digest couldn't be equal > to the claimed one because the content of the message given to the > DigesterOutpustrream is not well canonicalized or normalized. > Partial decrypted msg > ... > >xmlns="http://www.w3.org/2003/05/soap-envelope";>DataNotFoundFault xml:lang="nl-BE">ContextContactInfo with Id '1' does not > exist. xmlns="http://schemas.riziv.fgov.be/contact/2015/08/faults"; > xmlns:i="http://www.w3.org/2001/XMLSchema-instance";>ContextContactInfoNotFoundContextContactInfo > with Id '1' does not exist. > > ... > Predigested input : > http://www.w3.org/2003/05/soap-envelope"; > xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; > u:Id="_3"> xmlns="http://www.w3.org/2003/05/soap-envelope";>DataNotFoundFault xmlns="http://www.w3.org/2003/05/soap-envelope";> xml:lang="nl-BE">ContextContactInfo with Id '1' does not > exist. xmlns="http://schemas.riziv.fgov.be/contact/2015/08/faults";>ContextContactInfoNotFoundContextContactInfo > with Id '1' does not > exist. > Could you please check this problem and give me an advice ? > The library used are : > cxf 3.0.3 > wss4j 2.0.2 > xmlsec 2.0.2 > on a jdk 1.6.0_45 > Thanks in advance > David L -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FEDIZ-166) "No message body writer" error for OAuthError in the OIDC IdP
[
https://issues.apache.org/jira/browse/FEDIZ-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved FEDIZ-166.
---
Resolution: Fixed
> "No message body writer" error for OAuthError in the OIDC IdP
> -
>
> Key: FEDIZ-166
> URL: https://issues.apache.org/jira/browse/FEDIZ-166
> Project: CXF-Fediz
> Issue Type: Bug
>Affects Versions: 1.3.0
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
> Fix For: 1.3.1
>
>
> When an OAuthError is thrown in the Fediz OIDC IdP, such as for example the
> client request redirect URI does not match the stored value, the following
> exception is thrown (latest 1.3.1-SNAPSHOT code):
> ---
> ID: 5
> Response-Code: 500
> Content-Type: text/plain
> Headers: {Content-Type=[application/json], Date=[Tue, 24 May 2016 10:22:56
> GMT]}
> Payload: No message body writer has been found for class
> org.apache.cxf.rs.security.oauth2.common.OAuthError, ContentType:
> application/json
> --
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CXF-6915) Jws Compact does not support unencoded non-detached payloads
Sergey Beryozkin created CXF-6915: - Summary: Jws Compact does not support unencoded non-detached payloads Key: CXF-6915 URL: https://issues.apache.org/jira/browse/CXF-6915 Project: CXF Issue Type: Bug Components: JAX-RS Security Reporter: Sergey Beryozkin Priority: Minor Fix For: 3.1.7, 3.2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-6119) Implement WS-Transfer specification
[ https://issues.apache.org/jira/browse/CXF-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298170#comment-15298170 ] ASF GitHub Bot commented on CXF-6119: - Github user asfgit closed the pull request at: https://github.com/apache/cxf/pull/33 > Implement WS-Transfer specification > --- > > Key: CXF-6119 > URL: https://issues.apache.org/jira/browse/CXF-6119 > Project: CXF > Issue Type: New Feature > Components: JAX-WS Runtime >Reporter: Erich Duda > > Link to the specification: http://www.w3.org/TR/2011/REC-ws-transfer-20111213/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CXF-6119) Implement WS-Transfer specification
[ https://issues.apache.org/jira/browse/CXF-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-6119. -- Resolution: Implemented Assignee: Daniel Kulp Fix Version/s: 3.2.0 > Implement WS-Transfer specification > --- > > Key: CXF-6119 > URL: https://issues.apache.org/jira/browse/CXF-6119 > Project: CXF > Issue Type: New Feature > Components: JAX-WS Runtime >Reporter: Erich Duda >Assignee: Daniel Kulp > Fix For: 3.2.0 > > > Link to the specification: http://www.w3.org/TR/2011/REC-ws-transfer-20111213/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CXF-6916) Problem found when using the latest CXF DOSGi
Chenguang Zhang created CXF-6916: Summary: Problem found when using the latest CXF DOSGi Key: CXF-6916 URL: https://issues.apache.org/jira/browse/CXF-6916 Project: CXF Issue Type: Task Components: Build system Affects Versions: 3.1.1 Reporter: Chenguang Zhang Hello Guys, Recently, i am trying to build the OSGi environment for CXF using DOSGi(version 1.7.0).I can see that CXF has cancelled to release singlebundle for quite a long time.So i have to use the multibundle version. To verify the environment, i just wrote two very simple bundles based on JAX-WS rules to test it. The problem is that when i make all the bundles run well,the the webservice can not be published which means not signs to show the cxf has been running successfully. I can make sure that the bundle has started, it seems that the service is not bound to CXF container.Some traces here: Could you please help to find where is wrong? (Please ignore the Chinese word below :-)) osgi> org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register 信息: Registered blueprint namespace handler for http://cxf.apache.org/transports/http/configuration 五月 24, 2016 9:41:02 下午 org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register 信息: Registered blueprint namespace handler for http://cxf.apache.org/blueprint/bindings/soap 五月 24, 2016 9:41:02 下午 org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register 信息: Registered blueprint namespace handler for http://cxf.apache.org/blueprint/jaxws 五月 24, 2016 9:41:02 下午 org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register 信息: Registered blueprint namespace handler for http://cxf.apache.org/blueprint/simple SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [bundleresource://201.fwk4961455:2/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [bundleresource://201.fwk4961455:3/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. SLF4J: Actual binding is of type [org.slf4j.impl.JCLLoggerFactory] 五月 24, 2016 9:41:02 下午 org.slf4j.impl.JCLLoggerAdapter info 信息: No quiesce support is available, so blueprint components will not participate in quiesce operations 五月 24, 2016 9:41:02 下午 org.apache.cxf.bus.osgi.CXFExtensionBundleListener addExtensions 信息: Adding the extensions from bundle org.apache.cxf.cxf-rt-wsdl (169) [org.apache.cxf.wsdl.WSDLManager] 五月 24, 2016 9:41:02 下午 org.apache.cxf.bus.osgi.CXFExtensionBundleListener addExtensions 信息: Adding the extensions from bundle org.apache.cxf.cxf-rt-bindings-xml (176) [org.apache.cxf.binding.xml.XMLBindingFactory, org.apache.cxf.binding.xml.wsdl11.XMLWSDLExtensionLoader] 五月 24, 2016 9:41:02 下午 org.apache.cxf.bus.osgi.CXFExtensionBundleListener addExtensions 信息: Adding the extensions from bundle org.apache.cxf.cxf-rt-transports-http (177) [org.apache.cxf.transport.http.HTTPTransportFactory, org.apache.cxf.transport.http.HTTPWSDLExtensionLoader, org.apache.cxf.transport.http.policy.HTTPClientAssertionBuilder, org.apache.cxf.transport.http.policy.HTTPServerAssertionBuilder, org.apache.cxf.transport.http.policy.NoOpPolicyInterceptorProvider] 五月 24, 2016 9:41:02 下午 org.apache.cxf.bus.osgi.CXFExtensionBundleListener addExtensions 信息: Adding the extensions from bundle org.apache.cxf.cxf-rt-bindings-soap (184) [org.apache.cxf.binding.soap.SoapBindingFactory, org.apache.cxf.binding.soap.SoapTransportFactory] 五月 24, 2016 9:41:02 下午 org.apache.cxf.bus.osgi.CXFExtensionBundleListener addExtensions 信息: Adding the extensions from bundle org.apache.cxf.cxf-rt-management (189) [org.apache.cxf.management.InstrumentationManager] 五月 24, 2016 9:41:02 下午 org.apache.cxf.bus.osgi.CXFExtensionBundleListener addExtensions 信息: Adding the extensions from bundle org.apache.cxf.cxf-rt-frontend-jaxws (193) [org.apache.cxf.jaxws.context.WebServiceContextResourceResolver] 五月 24, 2016 9:41:02 下午 org.apache.cxf.bus.osgi.CXFExtensionBundleListener addExtensions 信息: Adding the extensions from bundle org.apache.cxf.cxf-rt-transports-http-jetty (204) [org.apache.cxf.transport.http_jetty.JettyDestinationFactory, org.apache.cxf.transport.http_jetty.JettyHTTPServerEngineFactory, org.apache.cxf.transport.http.ContinuationProviderFactory] 五月 24, 2016 9:41:02 下午 org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register 信息: Registered blueprint namespace handler for http://cxf.apache.org/blueprint/core 五月 24, 2016 9:41:02 下午 org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register 信息: Registered blueprint namespace handler for http://cxf.apache.org/configuration/beans 五月 24, 2016 9:41:02 下午 org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register 信息: Registered blueprint namespace handler for http://cxf.apache.org/configuration/parameterized-types 五月 24, 2016 9:41:02 下午 org.apache.cxf.b
[jira] [Updated] (CXF-6916) Problem found when using the latest CXF DOSGi
[ https://issues.apache.org/jira/browse/CXF-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chenguang Zhang updated CXF-6916: - Component/s: OSGi > Problem found when using the latest CXF DOSGi > - > > Key: CXF-6916 > URL: https://issues.apache.org/jira/browse/CXF-6916 > Project: CXF > Issue Type: Task > Components: Build system, OSGi >Affects Versions: 3.1.1 >Reporter: Chenguang Zhang > > Hello Guys, > Recently, i am trying to build the OSGi environment for CXF using > DOSGi(version 1.7.0).I can see that CXF has cancelled to release singlebundle > for quite a long time.So i have to use the multibundle version. > To verify the environment, i just wrote two very simple bundles based on > JAX-WS rules to test it. > The problem is that when i make all the bundles run well,the the webservice > can not be published which means not signs to show the cxf has been running > successfully. > I can make sure that the bundle has started, it seems that the service is not > bound to CXF container.Some traces here: > Could you please help to find where is wrong? > (Please ignore the Chinese word below :-)) > osgi> org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register > 信息: Registered blueprint namespace handler for > http://cxf.apache.org/transports/http/configuration > 五月 24, 2016 9:41:02 下午 > org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register > 信息: Registered blueprint namespace handler for > http://cxf.apache.org/blueprint/bindings/soap > 五月 24, 2016 9:41:02 下午 > org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register > 信息: Registered blueprint namespace handler for > http://cxf.apache.org/blueprint/jaxws > 五月 24, 2016 9:41:02 下午 > org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register > 信息: Registered blueprint namespace handler for > http://cxf.apache.org/blueprint/simple > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [bundleresource://201.fwk4961455:2/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [bundleresource://201.fwk4961455:3/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.slf4j.impl.JCLLoggerFactory] > 五月 24, 2016 9:41:02 下午 org.slf4j.impl.JCLLoggerAdapter info > 信息: No quiesce support is available, so blueprint components will not > participate in quiesce operations > 五月 24, 2016 9:41:02 下午 org.apache.cxf.bus.osgi.CXFExtensionBundleListener > addExtensions > 信息: Adding the extensions from bundle org.apache.cxf.cxf-rt-wsdl (169) > [org.apache.cxf.wsdl.WSDLManager] > 五月 24, 2016 9:41:02 下午 org.apache.cxf.bus.osgi.CXFExtensionBundleListener > addExtensions > 信息: Adding the extensions from bundle org.apache.cxf.cxf-rt-bindings-xml > (176) [org.apache.cxf.binding.xml.XMLBindingFactory, > org.apache.cxf.binding.xml.wsdl11.XMLWSDLExtensionLoader] > 五月 24, 2016 9:41:02 下午 org.apache.cxf.bus.osgi.CXFExtensionBundleListener > addExtensions > 信息: Adding the extensions from bundle org.apache.cxf.cxf-rt-transports-http > (177) [org.apache.cxf.transport.http.HTTPTransportFactory, > org.apache.cxf.transport.http.HTTPWSDLExtensionLoader, > org.apache.cxf.transport.http.policy.HTTPClientAssertionBuilder, > org.apache.cxf.transport.http.policy.HTTPServerAssertionBuilder, > org.apache.cxf.transport.http.policy.NoOpPolicyInterceptorProvider] > 五月 24, 2016 9:41:02 下午 org.apache.cxf.bus.osgi.CXFExtensionBundleListener > addExtensions > 信息: Adding the extensions from bundle org.apache.cxf.cxf-rt-bindings-soap > (184) [org.apache.cxf.binding.soap.SoapBindingFactory, > org.apache.cxf.binding.soap.SoapTransportFactory] > 五月 24, 2016 9:41:02 下午 org.apache.cxf.bus.osgi.CXFExtensionBundleListener > addExtensions > 信息: Adding the extensions from bundle org.apache.cxf.cxf-rt-management (189) > [org.apache.cxf.management.InstrumentationManager] > 五月 24, 2016 9:41:02 下午 org.apache.cxf.bus.osgi.CXFExtensionBundleListener > addExtensions > 信息: Adding the extensions from bundle org.apache.cxf.cxf-rt-frontend-jaxws > (193) [org.apache.cxf.jaxws.context.WebServiceContextResourceResolver] > 五月 24, 2016 9:41:02 下午 org.apache.cxf.bus.osgi.CXFExtensionBundleListener > addExtensions > 信息: Adding the extensions from bundle > org.apache.cxf.cxf-rt-transports-http-jetty (204) > [org.apache.cxf.transport.http_jetty.JettyDestinationFactory, > org.apache.cxf.transport.http_jetty.JettyHTTPServerEngineFactory, > org.apache.cxf.transport.http.ContinuationProviderFactory] > 五月 24, 2016 9:41:02 下午 > org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register > 信息: Registered blueprint namespace handler for > http://cxf.apache.org/blueprint/core > 五月 24, 2016 9:41:02 下午 > org.apache.cxf.bus.blueprint.Namespac
[jira] [Commented] (CXF-6916) Problem found when using the latest CXF DOSGi
[
https://issues.apache.org/jira/browse/CXF-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298274#comment-15298274
]
Chenguang Zhang commented on CXF-6916:
--
Hi,
The above problem is solved,but new problem comes out when i try to see the
wsdl in the browser.
Interceptor for {http://service.cxf.osgi.raymond.com/}IHelloService has thrown
exception, unwinding now
java.lang.ClassCastException: com.sun.xml.internal.stream.XMLOutputFactoryImpl
cannot be cast to javax.xml.stream.XMLOutputFactory
at
javax.xml.stream.XMLOutputFactory.newInstance(XMLOutputFactory.java:29)
at
org.apache.cxf.staxutils.StaxUtils.getXMLOutputFactory(StaxUtils.java:289)
at
org.apache.cxf.staxutils.StaxUtils.createXMLStreamWriter(StaxUtils.java:387)
at
org.apache.cxf.interceptor.StaxOutInterceptor.handleMessage(StaxOutInterceptor.java:81)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
at
org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:112)
at
org.apache.cxf.phase.PhaseInterceptorChain.wrapExceptionAsFault(PhaseInterceptorChain.java:366)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:324)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:251)
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:234)
at
org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:70)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1129)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1065)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
at org.eclipse.jetty.server.Server.handle(Server.java:499)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
at
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
at
org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:744)
Any comment on this problem?
Thanks.
> Problem found when using the latest CXF DOSGi
> -
>
> Key: CXF-6916
> URL: https://issues.apache.org/jira/browse/CXF-6916
> Project: CXF
> Issue Type: Task
> Components: Build system, OSGi
>Affects Versions: 3.1.1
>Reporter: Chenguang Zhang
>
> Hello Guys,
> Recently, i am trying to build the OSGi environment for CXF using
> DOSGi(version 1.7.0).I can see that CXF has cancelled to release singlebundle
> for quite a long time.So i have to use the multibundle version.
> To verify the environment, i just wrote two very simple bundles based on
> JAX-WS rules to test it.
> The problem is that when i make all the bundles run well,the the webservice
> can not be published which means not signs to show the cxf has been running
> successfully.
> I can make sure that the bundle has started, it seems that the service is not
> bound to CXF container.Some traces here:
> Could you please help to find where is wrong?
> (Please ignore the Chinese word below :-))
> osgi> org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register
> 信息: Registered blueprint namespace handler for
> http://cxf.apache.org/transports/http/configuration
> 五月 24, 2016 9:41:02 下午
> org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register
> 信息: Registered blueprint namespace handler for
> http://cxf.apache.org/blueprint/bindings/soap
> 五月 24, 2016 9:41:02 下午
> org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register
> 信息: Registered blueprint namespace handler for
> http://cxf.apache.org/blueprint/jaxws
> 五月 24, 2016 9:41:02 下午
> org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register
> 信息: Registered blueprint namespace handler for
> http://cxf.apache.org/blueprint/simple
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [bundleresource://201.fwk4961455:2/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [bundleresource://201.fwk4961455:3/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.
[jira] [Resolved] (CXF-6915) Jws Compact does not support unencoded non-detached payloads
[ https://issues.apache.org/jira/browse/CXF-6915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-6915. --- Resolution: Fixed Assignee: Sergey Beryozkin > Jws Compact does not support unencoded non-detached payloads > > > Key: CXF-6915 > URL: https://issues.apache.org/jira/browse/CXF-6915 > Project: CXF > Issue Type: Bug > Components: JAX-RS Security >Reporter: Sergey Beryozkin >Assignee: Sergey Beryozkin >Priority: Minor > Fix For: 3.1.7, 3.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CXF-6917) SuperClass and Interface's Annotations are ignored when the Method contains ParameterAnnotation
Neal Hu created CXF-6917:
Summary: SuperClass and Interface's Annotations are ignored when
the Method contains ParameterAnnotation
Key: CXF-6917
URL: https://issues.apache.org/jira/browse/CXF-6917
Project: CXF
Issue Type: Bug
Components: JAX-RS
Affects Versions: 3.1.6
Environment: Mac java 8
Reporter: Neal Hu
Fix For: 3.0.10, 3.2.0, 3.1.8
Suppose we have below interface and its implementation:
public interface HelloWorld {
@GET
@Path("/hello")
String sayHello(@QueryParam("name") String name);
@GET
@Path("/hello3")
String sayHello3();
}
@Path("/")
public class HelloWorldImpl implements HelloWorld {
@Override
public String sayHello(@QueryParam("name") String name){
return "hello " + name;
}
@GET
@Path("/hello2")
public String sayHello2(@QueryParam("name") String name){
return "hello2 " + name;
}
@Override
public String sayHello3(){
return "hello3 ";
}
}
Get /hello3 works good. but Get /hello?name=neal will result in 404. The
expected output is hello neal.
The root cause is in org.apache.cxf.jaxrs.utils.AnnotationUtils:167 CXF ignores
the recurrence search of the method who has parameter annotations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6900) invalid signature in case of soap fault
[ https://issues.apache.org/jira/browse/CXF-6900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298390#comment-15298390 ] david leruse commented on CXF-6900: --- Thanks Colm, i think i'm good for a dirty dirty fix If I want only to decrypt in case of a server error, what would be the best way to do that ? > invalid signature in case of soap fault > --- > > Key: CXF-6900 > URL: https://issues.apache.org/jira/browse/CXF-6900 > Project: CXF > Issue Type: Bug > Components: WS-* Components >Affects Versions: 3.0.3 > Environment: windows 2008 jdk 1.6.0_45 >Reporter: david leruse >Assignee: Colm O hEigeartaigh > Fix For: 3.1.7 > > Attachments: server7.log > > > Hello, > Having signature verification problems on the cxf client-side with a .NET > Ws-fed protected webservice, I ask you a little help... > Here is a summary of the problem : > Most of the time, communication works well excepted when we got a soap fault > message. > Indeed signature validation works usually well excepted when > we receive a fault message inside the body of the soap message. Even In this > boundary case, signature verification works well excepted for one element, > the fault message (see the enclosed server7.log file). > After digging a bit, i've found that the calculated digest couldn't be equal > to the claimed one because the content of the message given to the > DigesterOutpustrream is not well canonicalized or normalized. > Partial decrypted msg > ... > >xmlns="http://www.w3.org/2003/05/soap-envelope";>DataNotFoundFault xml:lang="nl-BE">ContextContactInfo with Id '1' does not > exist. xmlns="http://schemas.riziv.fgov.be/contact/2015/08/faults"; > xmlns:i="http://www.w3.org/2001/XMLSchema-instance";>ContextContactInfoNotFoundContextContactInfo > with Id '1' does not exist. > > ... > Predigested input : > http://www.w3.org/2003/05/soap-envelope"; > xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; > u:Id="_3"> xmlns="http://www.w3.org/2003/05/soap-envelope";>DataNotFoundFault xmlns="http://www.w3.org/2003/05/soap-envelope";> xml:lang="nl-BE">ContextContactInfo with Id '1' does not > exist. xmlns="http://schemas.riziv.fgov.be/contact/2015/08/faults";>ContextContactInfoNotFoundContextContactInfo > with Id '1' does not > exist. > Could you please check this problem and give me an advice ? > The library used are : > cxf 3.0.3 > wss4j 2.0.2 > xmlsec 2.0.2 > on a jdk 1.6.0_45 > Thanks in advance > David L -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-6917) SuperClass and Interface's Annotations are ignored when the Method contains ParameterAnnotation
[
https://issues.apache.org/jira/browse/CXF-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298432#comment-15298432
]
Sergey Beryozkin commented on CXF-6917:
---
I don't think it is a bug, see Annotation Inheritance in the spec
Cheers, Sergey
> SuperClass and Interface's Annotations are ignored when the Method contains
> ParameterAnnotation
> ---
>
> Key: CXF-6917
> URL: https://issues.apache.org/jira/browse/CXF-6917
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.6
> Environment: Mac java 8
>Reporter: Neal Hu
> Fix For: 3.0.10, 3.2.0, 3.1.8
>
>
> Suppose we have below interface and its implementation:
> public interface HelloWorld {
> @GET
> @Path("/hello")
> String sayHello(@QueryParam("name") String name);
> @GET
> @Path("/hello3")
> String sayHello3();
> }
> @Path("/")
> public class HelloWorldImpl implements HelloWorld {
> @Override
> public String sayHello(@QueryParam("name") String name){
> return "hello " + name;
> }
> @GET
> @Path("/hello2")
> public String sayHello2(@QueryParam("name") String name){
> return "hello2 " + name;
> }
> @Override
> public String sayHello3(){
> return "hello3 ";
> }
> }
> Get /hello3 works good. but Get /hello?name=neal will result in 404. The
> expected output is hello neal.
> The root cause is in org.apache.cxf.jaxrs.utils.AnnotationUtils:167 CXF
> ignores the recurrence search of the method who has parameter annotations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6917) SuperClass and Interface's Annotations are ignored when the Method contains ParameterAnnotation
[
https://issues.apache.org/jira/browse/CXF-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298426#comment-15298426
]
Neal Hu commented on CXF-6917:
--
I made a tentative test removing below at AnnotationUtils:167, then both
/hello3 and /hello?name=neal returned as expected. Will attach patch tomorrow.
for (Annotation[] paramAnnotations : m.getParameterAnnotations()) {
if (isValidParamAnnotations(paramAnnotations)) {
LOG.warning("Method " + m.getName() + " in " +
m.getDeclaringClass().getName()
+ " has no JAX-RS Path or HTTP Method
annotations");
return m;
}
}
Neal
> SuperClass and Interface's Annotations are ignored when the Method contains
> ParameterAnnotation
> ---
>
> Key: CXF-6917
> URL: https://issues.apache.org/jira/browse/CXF-6917
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.6
> Environment: Mac java 8
>Reporter: Neal Hu
> Fix For: 3.0.10, 3.2.0, 3.1.8
>
>
> Suppose we have below interface and its implementation:
> public interface HelloWorld {
> @GET
> @Path("/hello")
> String sayHello(@QueryParam("name") String name);
> @GET
> @Path("/hello3")
> String sayHello3();
> }
> @Path("/")
> public class HelloWorldImpl implements HelloWorld {
> @Override
> public String sayHello(@QueryParam("name") String name){
> return "hello " + name;
> }
> @GET
> @Path("/hello2")
> public String sayHello2(@QueryParam("name") String name){
> return "hello2 " + name;
> }
> @Override
> public String sayHello3(){
> return "hello3 ";
> }
> }
> Get /hello3 works good. but Get /hello?name=neal will result in 404. The
> expected output is hello neal.
> The root cause is in org.apache.cxf.jaxrs.utils.AnnotationUtils:167 CXF
> ignores the recurrence search of the method who has parameter annotations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6917) SuperClass and Interface's Annotations are ignored when the Method contains ParameterAnnotation
[
https://issues.apache.org/jira/browse/CXF-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298458#comment-15298458
]
Neal Hu commented on CXF-6917:
--
Seams you are right.
in spec 3.6 Annotation Inheritance
Such annotations are inherited by a corresponding sub-class or implementation
class method provided that the method and its parameters do not have any JAX-RS
annotations of their own.
But personally, i think when the method has parameter annotation we should not
ignore the annotation inheritance in the method.
> SuperClass and Interface's Annotations are ignored when the Method contains
> ParameterAnnotation
> ---
>
> Key: CXF-6917
> URL: https://issues.apache.org/jira/browse/CXF-6917
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.6
> Environment: Mac java 8
>Reporter: Neal Hu
> Fix For: 3.0.10, 3.2.0, 3.1.8
>
>
> Suppose we have below interface and its implementation:
> public interface HelloWorld {
> @GET
> @Path("/hello")
> String sayHello(@QueryParam("name") String name);
> @GET
> @Path("/hello3")
> String sayHello3();
> }
> @Path("/")
> public class HelloWorldImpl implements HelloWorld {
> @Override
> public String sayHello(@QueryParam("name") String name){
> return "hello " + name;
> }
> @GET
> @Path("/hello2")
> public String sayHello2(@QueryParam("name") String name){
> return "hello2 " + name;
> }
> @Override
> public String sayHello3(){
> return "hello3 ";
> }
> }
> Get /hello3 works good. but Get /hello?name=neal will result in 404. The
> expected output is hello neal.
> The root cause is in org.apache.cxf.jaxrs.utils.AnnotationUtils:167 CXF
> ignores the recurrence search of the method who has parameter annotations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6917) SuperClass and Interface's Annotations are ignored when the Method contains ParameterAnnotation
[
https://issues.apache.org/jira/browse/CXF-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298459#comment-15298459
]
Neal Hu commented on CXF-6917:
--
Seams you are right.
in spec 3.6 Annotation Inheritance
Such annotations are inherited by a corresponding sub-class or implementation
class method provided that the method and its parameters do not have any JAX-RS
annotations of their own.
But personally, i think when the method has parameter annotation we should not
ignore the annotation inheritance in the method.
> SuperClass and Interface's Annotations are ignored when the Method contains
> ParameterAnnotation
> ---
>
> Key: CXF-6917
> URL: https://issues.apache.org/jira/browse/CXF-6917
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.6
> Environment: Mac java 8
>Reporter: Neal Hu
> Fix For: 3.0.10, 3.2.0, 3.1.8
>
>
> Suppose we have below interface and its implementation:
> public interface HelloWorld {
> @GET
> @Path("/hello")
> String sayHello(@QueryParam("name") String name);
> @GET
> @Path("/hello3")
> String sayHello3();
> }
> @Path("/")
> public class HelloWorldImpl implements HelloWorld {
> @Override
> public String sayHello(@QueryParam("name") String name){
> return "hello " + name;
> }
> @GET
> @Path("/hello2")
> public String sayHello2(@QueryParam("name") String name){
> return "hello2 " + name;
> }
> @Override
> public String sayHello3(){
> return "hello3 ";
> }
> }
> Get /hello3 works good. but Get /hello?name=neal will result in 404. The
> expected output is hello neal.
> The root cause is in org.apache.cxf.jaxrs.utils.AnnotationUtils:167 CXF
> ignores the recurrence search of the method who has parameter annotations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (CXF-6917) SuperClass and Interface's Annotations are ignored when the Method contains ParameterAnnotation
[
https://issues.apache.org/jira/browse/CXF-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neal Hu updated CXF-6917:
-
Comment: was deleted
(was: Seams you are right.
in spec 3.6 Annotation Inheritance
Such annotations are inherited by a corresponding sub-class or implementation
class method provided that the method and its parameters do not have any JAX-RS
annotations of their own.
But personally, i think when the method has parameter annotation we should not
ignore the annotation inheritance in the method.)
> SuperClass and Interface's Annotations are ignored when the Method contains
> ParameterAnnotation
> ---
>
> Key: CXF-6917
> URL: https://issues.apache.org/jira/browse/CXF-6917
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.6
> Environment: Mac java 8
>Reporter: Neal Hu
> Fix For: 3.0.10, 3.2.0, 3.1.8
>
>
> Suppose we have below interface and its implementation:
> public interface HelloWorld {
> @GET
> @Path("/hello")
> String sayHello(@QueryParam("name") String name);
> @GET
> @Path("/hello3")
> String sayHello3();
> }
> @Path("/")
> public class HelloWorldImpl implements HelloWorld {
> @Override
> public String sayHello(@QueryParam("name") String name){
> return "hello " + name;
> }
> @GET
> @Path("/hello2")
> public String sayHello2(@QueryParam("name") String name){
> return "hello2 " + name;
> }
> @Override
> public String sayHello3(){
> return "hello3 ";
> }
> }
> Get /hello3 works good. but Get /hello?name=neal will result in 404. The
> expected output is hello neal.
> The root cause is in org.apache.cxf.jaxrs.utils.AnnotationUtils:167 CXF
> ignores the recurrence search of the method who has parameter annotations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CXF-6917) SuperClass and Interface's Annotations are ignored when the Method contains ParameterAnnotation
[
https://issues.apache.org/jira/browse/CXF-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Beryozkin resolved CXF-6917.
---
Resolution: Won't Fix
Assignee: Sergey Beryozkin
> SuperClass and Interface's Annotations are ignored when the Method contains
> ParameterAnnotation
> ---
>
> Key: CXF-6917
> URL: https://issues.apache.org/jira/browse/CXF-6917
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.6
> Environment: Mac java 8
>Reporter: Neal Hu
>Assignee: Sergey Beryozkin
> Fix For: 3.0.10, 3.2.0, 3.1.8
>
>
> Suppose we have below interface and its implementation:
> public interface HelloWorld {
> @GET
> @Path("/hello")
> String sayHello(@QueryParam("name") String name);
> @GET
> @Path("/hello3")
> String sayHello3();
> }
> @Path("/")
> public class HelloWorldImpl implements HelloWorld {
> @Override
> public String sayHello(@QueryParam("name") String name){
> return "hello " + name;
> }
> @GET
> @Path("/hello2")
> public String sayHello2(@QueryParam("name") String name){
> return "hello2 " + name;
> }
> @Override
> public String sayHello3(){
> return "hello3 ";
> }
> }
> Get /hello3 works good. but Get /hello?name=neal will result in 404. The
> expected output is hello neal.
> The root cause is in org.apache.cxf.jaxrs.utils.AnnotationUtils:167 CXF
> ignores the recurrence search of the method who has parameter annotations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6917) SuperClass and Interface's Annotations are ignored when the Method contains ParameterAnnotation
[
https://issues.apache.org/jira/browse/CXF-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298802#comment-15298802
]
Sergey Beryozkin commented on CXF-6917:
---
Well this is not the first time users have come across it. But IMHO it is
actually not a good idea to have REST API enablers (annotations) spread around
the class hierarchy and I agree with the spec completely here. In a pure Java
land it would be like having a contract partially represented in the interface
and the impl, with the impl passed around.
If one has the interface to represent the resource methods then why duplicate
some of the annotations on the impl level ?
Thanks
> SuperClass and Interface's Annotations are ignored when the Method contains
> ParameterAnnotation
> ---
>
> Key: CXF-6917
> URL: https://issues.apache.org/jira/browse/CXF-6917
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.6
> Environment: Mac java 8
>Reporter: Neal Hu
> Fix For: 3.0.10, 3.2.0, 3.1.8
>
>
> Suppose we have below interface and its implementation:
> public interface HelloWorld {
> @GET
> @Path("/hello")
> String sayHello(@QueryParam("name") String name);
> @GET
> @Path("/hello3")
> String sayHello3();
> }
> @Path("/")
> public class HelloWorldImpl implements HelloWorld {
> @Override
> public String sayHello(@QueryParam("name") String name){
> return "hello " + name;
> }
> @GET
> @Path("/hello2")
> public String sayHello2(@QueryParam("name") String name){
> return "hello2 " + name;
> }
> @Override
> public String sayHello3(){
> return "hello3 ";
> }
> }
> Get /hello3 works good. but Get /hello?name=neal will result in 404. The
> expected output is hello neal.
> The root cause is in org.apache.cxf.jaxrs.utils.AnnotationUtils:167 CXF
> ignores the recurrence search of the method who has parameter annotations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CXF-6902) Problem with resource that returns Object with CXF version == 3.1.2
[
https://issues.apache.org/jira/browse/CXF-6902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Beryozkin resolved CXF-6902.
---
Resolution: Won't Fix
OK, let me close it the 2nd time :-), thanks
> Problem with resource that returns Object with CXF version == 3.1.2
> ---
>
> Key: CXF-6902
> URL: https://issues.apache.org/jira/browse/CXF-6902
> Project: CXF
> Issue Type: Bug
> Components: JAXB Databinding
>Affects Versions: 3.1.2
>Reporter: Balarami Reddy
>Assignee: Sergey Beryozkin
>
> Hello,
> We have recently migrated from 2.7 to 3.1.2 and we see a behaviour change in
> CXF which blocked us from making progress.
> The sample code below gives "No message body writer has been found for
> response class Integer" which used to work perfect in CXF 2.7
> This is just sample code only. We have in our product several rest calls
> which return integer/long/Object etc based on some calculations.
> @GET
> @Produces(MediaType.APPLICATION_JSON)
> @Path("/getinteger")
> public Response getInteger() {
> return Response.ok(4).build();
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6917) SuperClass and Interface's Annotations are ignored when the Method contains ParameterAnnotation
[
https://issues.apache.org/jira/browse/CXF-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299382#comment-15299382
]
Neal Hu commented on CXF-6917:
--
Sergey,
I agree. Removed the annotation in the impl's method parameter resolved the
problem. BTW, what is IMHO stands for? Thanks.
Neal
> SuperClass and Interface's Annotations are ignored when the Method contains
> ParameterAnnotation
> ---
>
> Key: CXF-6917
> URL: https://issues.apache.org/jira/browse/CXF-6917
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.6
> Environment: Mac java 8
>Reporter: Neal Hu
>Assignee: Sergey Beryozkin
> Fix For: 3.0.10, 3.2.0, 3.1.8
>
>
> Suppose we have below interface and its implementation:
> public interface HelloWorld {
> @GET
> @Path("/hello")
> String sayHello(@QueryParam("name") String name);
> @GET
> @Path("/hello3")
> String sayHello3();
> }
> @Path("/")
> public class HelloWorldImpl implements HelloWorld {
> @Override
> public String sayHello(@QueryParam("name") String name){
> return "hello " + name;
> }
> @GET
> @Path("/hello2")
> public String sayHello2(@QueryParam("name") String name){
> return "hello2 " + name;
> }
> @Override
> public String sayHello3(){
> return "hello3 ";
> }
> }
> Get /hello3 works good. but Get /hello?name=neal will result in 404. The
> expected output is hello neal.
> The root cause is in org.apache.cxf.jaxrs.utils.AnnotationUtils:167 CXF
> ignores the recurrence search of the method who has parameter annotations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
