[jira] [Created] (CXF-4395) ClaimsAttributeStatementProvider add claims for subject of onbehalf/actas
Oliver Wulff created CXF-4395: - Summary: ClaimsAttributeStatementProvider add claims for subject of onbehalf/actas Key: CXF-4395 URL: https://issues.apache.org/jira/browse/CXF-4395 Project: CXF Issue Type: Bug Components: Services Affects Versions: 2.6.1 Reporter: Oliver Wulff Assignee: Oliver Wulff Fix For: 2.6.2, 2.7.0 The ClaimsAttributeStatementProvider only checks the principal of the WS-SecurityHeader. In the case of OnBehalfOf or ActAs, the principal of this token must have higher priority. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4395) ClaimsAttributeStatementProvider add claims for subject of onbehalf/actas
[ https://issues.apache.org/jira/browse/CXF-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Wulff updated CXF-4395: -- Issue Type: Improvement (was: Bug) > ClaimsAttributeStatementProvider add claims for subject of onbehalf/actas > -- > > Key: CXF-4395 > URL: https://issues.apache.org/jira/browse/CXF-4395 > Project: CXF > Issue Type: Improvement > Components: Services >Affects Versions: 2.6.1 >Reporter: Oliver Wulff >Assignee: Oliver Wulff > Fix For: 2.6.2, 2.7.0 > > > The ClaimsAttributeStatementProvider only checks the principal of the > WS-SecurityHeader. In the case of OnBehalfOf or ActAs, the principal of this > token must have higher priority. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-4395) ClaimsAttributeStatementProvider add claims for subject of onbehalf/actas
[ https://issues.apache.org/jira/browse/CXF-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Wulff resolved CXF-4395. --- Resolution: Fixed > ClaimsAttributeStatementProvider add claims for subject of onbehalf/actas > -- > > Key: CXF-4395 > URL: https://issues.apache.org/jira/browse/CXF-4395 > Project: CXF > Issue Type: Bug > Components: Services >Affects Versions: 2.6.1 >Reporter: Oliver Wulff >Assignee: Oliver Wulff > Fix For: 2.6.2, 2.7.0 > > > The ClaimsAttributeStatementProvider only checks the principal of the > WS-SecurityHeader. In the case of OnBehalfOf or ActAs, the principal of this > token must have higher priority. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-4144) CXF JAXRS | Complex response types are not present in the generated wadl when returning list of objects
[
https://issues.apache.org/jira/browse/CXF-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Beryozkin resolved CXF-4144.
---
Resolution: Fixed
Fix Version/s: 2.7.0
2.6.2
2.5.5
Assignee: Sergey Beryozkin
This can be optionally supported if org.apache.cxf.jaxrs.model.wadl.XMLName
annotation is available
> CXF JAXRS | Complex response types are not present in the generated wadl when
> returning list of objects
> ---
>
> Key: CXF-4144
> URL: https://issues.apache.org/jira/browse/CXF-4144
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.5.2
>Reporter: Gayathri.Muralidharan
>Assignee: Sergey Beryozkin
> Labels: jax-rs, wadl, wadl2java
> Fix For: 2.5.5, 2.6.2, 2.7.0
>
>
> We use cxf 2.5.2 along with spring for exposing and consuming restful
> services. For distributing the service interface classes, we started using
> wadl2java goal (which generates interface classes based on the given wadl
> file)
> The generated wadl doesnt contain the proper response type, because of which
> i guess, the generated interfaces all have 'Response' as the return type.
> Ex. if the restful get method returns 'List' , the generated wadl contains
> the following segment only:
>
> and the corresponding interface generated from this wadl file contains the
> return type as 'Response'
> Can someone suggest what needs to be done to prevent the actual response type
> from getting lost? Are any annotations (like ElementClass ? how to use it ?)
> or providers required?
> Current code:
> @GET
> @Path("/itemsForCategory")
> @Produces("application/json")
> @Description("getItemsForCategory")
> public List getItemsForCategory(@QueryParam("category")String category)
> {//implementation}
> Found
> http://cxf.547215.n5.nabble.com/Problem-with-WADL-generation-and-returning-a-List-of-objects-td4713351.html#a5507490
> . But the issue doesnt seem to be fixed.
> Can someone help us out here?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-4325) ws?js not working with Spring based config in JBoss 7.1
[ https://issues.apache.org/jira/browse/CXF-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401407#comment-13401407 ] Timothy Heider commented on CXF-4325: - I will attach my sample project tomorrow. > ws?js not working with Spring based config in JBoss 7.1 > --- > > Key: CXF-4325 > URL: https://issues.apache.org/jira/browse/CXF-4325 > Project: CXF > Issue Type: Bug > Components: JavaScript Client, JAX-WS Runtime >Affects Versions: 2.6 > Environment: Linux + JBoss 7.1 > project in Netbeans 7.1.2. Simple WAR (clean project) >Reporter: Timothy Heider >Priority: Minor > Fix For: NeedMoreInfo > > > I have everything working except for the one thing I really want: ?js code > rendering. It returns this: > http://schemas.xmlsoap.org/soap/envelope/";> > > > soap:Server > > No such operation: null (HTTP GET PATH_INFO: /pbx/pbxnull) > > > > > which is the same as if the JS wasn't hooked in at all. > Here is my beans.xml file: > http://www.springframework.org/schema/beans"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:jaxws="http://cxf.apache.org/jaxws"; > xmlns:jaxrs="http://cxf.apache.org/jaxrs"; > xsi:schemaLocation=" > http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans-2.0.xsd > http://cxf.apache.org/jaxws > http://cxf.apache.org/schemas/jaxws.xsd > http://cxf.apache.org/jaxrs > http://cxf.apache.org/schemas/jaxrs.xsd";> > > > >resource="classpath:META-INF/cxf/cxf-extension-javascript-client.xml"/> > implementor="realise.pbx.core.PbxCoreImpl" > address="/pbx"/> > > I am able to get wsdl's by ?wsdl and execute services using > JaxWsProxyFactoryBean. > The beverages sample works with the same jar's to generate JS so I know the > feature works. I'm somewhat baffled. I built the 2.6.0 source today but I > thought before I dig in too much more I would see if you knew about something > like this already being a problem. > Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
