[jira] [Commented] (CXF-7013) SAML token using ws-security.callback-handler as for UT with ID attribute value
[ https://issues.apache.org/jira/browse/CXF-7013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15436403#comment-15436403 ] Grzegorz Maczuga commented on CXF-7013: --- Thanks Colm, that indeed will fix the issue I have w/o additional checks. > SAML token using ws-security.callback-handler as for UT with ID attribute > value > --- > > Key: CXF-7013 > URL: https://issues.apache.org/jira/browse/CXF-7013 > Project: CXF > Issue Type: Bug > Components: Core >Affects Versions: 3.0.6 >Reporter: Grzegorz Maczuga >Assignee: Colm O hEigeartaigh >Priority: Minor > > Processing of SAML token results in call of configured > ws-security.callback-handler same as for Username Token. > When CXF receives (no UT in it): > >ID="Abc-1" IssueInstant="2016-08-16T08:13:47Z" Version="2.0"> > Format="urn:oasis:names:tc:SAML:1.1:nameid-format:X509SubjectName">CN=user > >Format="urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified">some_name >... > > it calls configured: > ws-security.callback-handler=com.SecurityCallback > with ID="Abc-1" from above Security section as username. > Ignoring this and moving on has no impact on processing SAML token but if > SecurityCallback does some funny stuff (or at list logging) for each received > UT it is really confusing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CXF-6992) ParamConverterProvider invoked with wrong types
[
https://issues.apache.org/jira/browse/CXF-6992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Beryozkin resolved CXF-6992.
---
Resolution: Fixed
Assignee: Sergey Beryozkin
Fix Version/s: 3.0.11
> ParamConverterProvider invoked with wrong types
> ---
>
> Key: CXF-6992
> URL: https://issues.apache.org/jira/browse/CXF-6992
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.5
>Reporter: Zoltan Farkas
>Assignee: Sergey Beryozkin
> Fix For: 3.2.0, 3.1.8, 3.0.11
>
>
> I have created a type: MyType
> and registered a ParameterConverterProvider to serialize/de-serialize my type.
> when I use my type as in a JAX-RS as:
> {code}
> @QueryParam("qparam") List>
> {code}
> end invoke the enpoint with:
> http://service/enpoint?qparam=abc&qparam=cde
> I get ParameterConverterProvider.getConverter(Integer.class,...) invoked
> instead of
> ParameterConverterProvider.getConverter(MyType.class,...)
> which does not look right to me, as such CXF tries to parse the qparam as
> Integer instead of MyType...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CXF-7023) SOAP over JMS transport does not use XA transactions with Websphere MQ resource adapter
Nikolay Boklaschuk created CXF-7023: --- Summary: SOAP over JMS transport does not use XA transactions with Websphere MQ resource adapter Key: CXF-7023 URL: https://issues.apache.org/jira/browse/CXF-7023 Project: CXF Issue Type: Bug Components: JMS Affects Versions: 3.1.7 Reporter: Nikolay Boklaschuk When using Websphere MQ resource adapter Inbound one-way service does not uses XA transactions. This is because WMQ adapter decides to use XA transaction when creates jms connection, but connection opened in JMSDestination, and transaction started in PollingMessageListnerContainer after connection created. Futhermore WMQ adapter holds only one session per connection. I have patched XAPoller to hold connection for each thread, it works, but may be there are better way to provide support for WMQ adapter? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CXF-7017) @BeanParam not working in subresource
[
https://issues.apache.org/jira/browse/CXF-7017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Beryozkin resolved CXF-7017.
---
Resolution: Fixed
Assignee: Sergey Beryozkin
Fix Version/s: 3.0.11
3.1.8
3.2.0
> @BeanParam not working in subresource
> -
>
> Key: CXF-7017
> URL: https://issues.apache.org/jira/browse/CXF-7017
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.6
> Environment: Java 1.8.0_91
> Tomee 7.0.1
>Reporter: Nicos Tegos
>Assignee: Sergey Beryozkin
> Fix For: 3.2.0, 3.1.8, 3.0.11
>
>
> Hello,
> I tried to inject a BeanParam into a subresource. This doesn't work,
> resulting in an exception (Stacktrace can be found at the end).
> It works perfectly if I inject a QueryParam into the subresource.
> I provided a minimal example with all classes below. To get the exception
> just use the relative path:
> resource/?searchType=1&maxItems=1
> {code}
> package cxfbug.beanparam.app.config;
> import javax.enterprise.context.RequestScoped;
> import javax.ws.rs.Path;
> import javax.ws.rs.Produces;
> import javax.ws.rs.QueryParam;
> @RequestScoped
> @Path("resource")
> @Produces("application/json")
> public class Resource
> {
> @Path("/")
> public Object getSubresource(@QueryParam("searchType") final int
> searchType)
> {
> if (searchType == 1)
> {
> return new BeanParamSubresource();
> }
> return new QueryParamSubresource();
> }
> }
> {code}
> The subresource using QueryParam only:
> {code}
> package cxfbug.beanparam.app.config;
> import javax.ws.rs.GET;
> import javax.ws.rs.QueryParam;
> public class QueryParamSubresource
> {
> @GET
> public LimitedListSearchCriteria get(@QueryParam("maxItems") final int
> maxItems)
> {
> final LimitedListSearchCriteria criteria = new
> LimitedListSearchCriteria();
> criteria.setMaxItems(maxItems);
> return criteria;
> }
> }
> {code}
> The subresource using BeanParam:
> {code}
> package cxfbug.beanparam.app.config;
> import javax.ws.rs.BeanParam;
> import javax.ws.rs.GET;
> public class BeanParamSubresource
> {
> @GET
> public LimitedListSearchCriteria get(@BeanParam final
> LimitedListSearchCriteria searchCriteria)
> {
> return searchCriteria;
> }
> }
> {code}
> Class to be used as bean:
> {code}
> package cxfbug.beanparam.app.config;
> import javax.ws.rs.QueryParam;
> public class LimitedListSearchCriteria
> {
> @QueryParam("maxItems")
> private int maxItems;
> public int getMaxItems()
> {
> return maxItems;
> }
> public void setMaxItems(final int maxItems)
> {
> this.maxItems = maxItems;
> }
> }
> {code}
> Exception when using BeanParam:
> {noformat}
> Aug 19, 2016 9:34:05 PM org.apache.cxf.jaxrs.utils.JAXRSUtils
> createBeanParamValue
> WARNUNG: Bean parameter info is not available
> Aug 19, 2016 9:34:05 PM
> org.apache.cxf.jaxrs.impl.WebApplicationExceptionMapper toResponse
> WARNUNG: javax.ws.rs.InternalServerErrorException: HTTP 500 Internal Server
> Error
> at
> org.apache.cxf.jaxrs.utils.SpecExceptions.toInternalServerErrorException(SpecExceptions.java:79)
> at
> org.apache.cxf.jaxrs.utils.ExceptionUtils.toInternalServerErrorException(ExceptionUtils.java:106)
> at
> org.apache.cxf.jaxrs.utils.JAXRSUtils.createBeanParamValue(JAXRSUtils.java:1052)
> at
> org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameter(JAXRSUtils.java:836)
> at
> org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameters(JAXRSUtils.java:789)
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:257)
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:99)
> at
> org.apache.openejb.server.cxf.rs.AutoJAXRSInvoker.invoke(AutoJAXRSInvoker.java:68)
> 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.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:254)
> at
> org.apache.openejb.server.cxf.rs.CxfRsHttpListener.doInvoke(CxfRsHttpListener.java:251)
> at
> org.apache.tomee.webservices.CXFJAXRSFilter.doFilter(CXFJAXRSFilter.java:94)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFil
[jira] [Created] (CXF-7024) Support original WADL namespace prefix without incrementing it
Sergey Beryozkin created CXF-7024: - Summary: Support original WADL namespace prefix without incrementing it Key: CXF-7024 URL: https://issues.apache.org/jira/browse/CXF-7024 Project: CXF Issue Type: Improvement Components: JAX-RS Reporter: Sergey Beryozkin Priority: Minor Fix For: 3.2.0, 3.1.8 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CXF-7024) Support original WADL namespace prefix without incrementing it
[ https://issues.apache.org/jira/browse/CXF-7024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-7024. --- Resolution: Fixed Assignee: Sergey Beryozkin > Support original WADL namespace prefix without incrementing it > -- > > Key: CXF-7024 > URL: https://issues.apache.org/jira/browse/CXF-7024 > Project: CXF > Issue Type: Improvement > Components: JAX-RS >Reporter: Sergey Beryozkin >Assignee: Sergey Beryozkin >Priority: Minor > Fix For: 3.2.0, 3.1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
