Issues with Attachments: week of 2012-06-11
CXF - Monday, June 11, 2012 8 Issues with Attachments (sorted oldest to newest) [CXF-4289] Coping Request SOAP Headers to Fault response - Created: 2012-05-06 - Updated: 2012-05-17 - Type: Improvement - Fix Versions: [] - Reporter: Andrei Shakirin - Assigned: Ulhas Bhole - Attachments: [JAXWSMethodInvoker.patch] - https://issues.apache.org/jira/browse/CXF-4289 [CXF-4301] Problem with Implicit Soap Headers and @ResponseWrapper in methods with multiple response attributes: NullPointerException in ReflectionServiceFactoryBean or Response-Marshalling Error - Created: 2012-05-09 - Updated: 2012-05-16 - Type: Bug - Fix Versions: [] - Reporter: Andreas Gudian - Assigned: Unassigned - Attachments: [implicit-header-showcase.zip] - https://issues.apache.org/jira/browse/CXF-4301 [CXF-4324] UriInfo uninjectable - Created: 2012-05-18 - Updated: 2012-05-22 - Type: Bug - Fix Versions: [] - Reporter: Chris Eineke - Assigned: Unassigned - Attachments: [uriinfofail.zip] - https://issues.apache.org/jira/browse/CXF-4324 [CXF-4351] No JSON output under OSGi because cxf-rt-frontend-jaxrs is missing Import-Package for org.apache.cxf.jaxrs.provider.json - Created: 2012-05-30 - Updated: 2012-05-31 - Type: Bug - Fix Versions: [] - Reporter: Chris Dolan - Assigned: Unassigned - Attachments: [CXF-4351.patch] - https://issues.apache.org/jira/browse/CXF-4351 [CXF-4359] ParameterizedType#getActualTypeArguments() classes not added to the JAXBContext for JAX-RS providers - Created: 2012-06-05 - Updated: 2012-06-05 - Type: New Feature - Fix Versions: [] - Reporter: Angelo - Assigned: Unassigned - Attachments: [cxf-patch.txt, src.zip] - https://issues.apache.org/jira/browse/CXF-4359 [CXF-4360] NPE in org.apache.cxf.interceptor.WrappedOutInterceptor when WS-RM is enabled - Created: 2012-06-06 - Updated: 2012-06-10 - Type: Bug - Fix Versions: [2.6.2, 2.7.0] - Reporter: Richard Opalka - Assigned: Unassigned - Attachments: [CXF4360.patch, ReliableService.wsdl] - https://issues.apache.org/jira/browse/CXF-4360 [CXF-4367] org.apache.ws.security.WSSecurityException: An invalid security token was provided (Bad TokenType "") - Created: 2012-06-07 - Updated: 2012-06-08 - Type: Bug - Fix Versions: [] - Reporter: Gina Choi - Assigned: Unassigned - Attachments: [DoubleIt.wsdl, adfs_new_simple.wsdl, catalina.2012-06-07.log, clientstore.jks, cxf.xml, servicestore.jks, servicestore.jks] - https://issues.apache.org/jira/browse/CXF-4367 [CXF-4368] LoggingInterceptors don't encourage reuse - Created: 2012-06-09 - Updated: 2012-06-09 - Type: Improvement - Fix Versions: [] - Reporter: Yaytay - Assigned: Unassigned - Attachments: [CXF-4368.diff] - https://issues.apache.org/jira/browse/CXF-4368
[jira] [Commented] (FEDIZ-1) WS-Federation Metadata document published at runtime in RP
[ https://issues.apache.org/jira/browse/FEDIZ-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292695#comment-13292695 ] Oliver Wulff commented on FEDIZ-1: -- thanks juerg. I made some minor updates like: - signature first - moving constants - package mex renamend to metadata - use WSS4J for keystore access (supports pkcs12 as well) - keystore initialization in FederationContext once instead of per request (same as certificatestores) The changes are here: http://svn.apache.org/viewvc?view=revision&revision=1348749 > WS-Federation Metadata document published at runtime in RP > -- > > Key: FEDIZ-1 > URL: https://issues.apache.org/jira/browse/FEDIZ-1 > Project: CXF-Fediz > Issue Type: New Feature > Components: Plugin >Reporter: Oliver Wulff > Attachments: patch.txt > > > plugins/core should be enhanced to generate a WS-Federation Metadata document -- 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] [Created] (CXF-4370) Support the ability to decrypt encrypted Assertions for SAML Web SSO
Colm O hEigeartaigh created CXF-4370: Summary: Support the ability to decrypt encrypted Assertions for SAML Web SSO Key: CXF-4370 URL: https://issues.apache.org/jira/browse/CXF-4370 Project: CXF Issue Type: Improvement Affects Versions: 2.6.1 Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 2.6.2 This task is to support the ability to decrypt encrypted Assertions for SAML Web SSO. -- 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-4370) Support the ability to decrypt encrypted Assertions for SAML Web SSO
[ https://issues.apache.org/jira/browse/CXF-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CXF-4370. -- Resolution: Fixed > Support the ability to decrypt encrypted Assertions for SAML Web SSO > > > Key: CXF-4370 > URL: https://issues.apache.org/jira/browse/CXF-4370 > Project: CXF > Issue Type: Improvement >Affects Versions: 2.6.1 >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 2.6.2 > > > This task is to support the ability to decrypt encrypted Assertions for SAML > Web SSO. -- 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-4369) cxf-xjc-plugin generated unmappable characters using system encoding
[ https://issues.apache.org/jira/browse/CXF-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292837#comment-13292837 ] Liu Jianhong commented on CXF-4369: --- Where can I put -encoding flag to cxf-xjc-plugin's configuration section? and when the 2.6.1 version of cxf-xjc-plugin will released? > cxf-xjc-plugin generated unmappable characters using system encoding > > > Key: CXF-4369 > URL: https://issues.apache.org/jira/browse/CXF-4369 > Project: CXF > Issue Type: Bug > Environment: jdk 1.7 , windows 7 , camel-soap 2.10-SNAPSHOT , > cxf-xjc-plugin 2.6.0 >Reporter: Liu Jianhong > > In camel source,when I buid "camel-soap" component, it genrates unmappable > characters and build failed,the error information as following,and I checked > the document for cxf-xjc-plugin, I not found any solution: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:2.5:compile (default-compile) > on project camel-soap: > Compilation failure: Compilation failure: > [ERROR] > D:\devstudio\soa\source\camel\components\camel-soap\target\generated\src\main\java\org\xmlsoap\schemas\soap\envelope\Fault > .java:[5,40] 错误: 编码UTF-8的不可映射字符 > [ERROR] > D:\devstudio\soa\source\camel\components\camel-soap\target\generated\src\main\java\org\xmlsoap\schemas\soap\envelope\Fault > .java:[5,41] 错误: 编码UTF-8的不可映射字符 -- 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] [Created] (CXF-4371) HTTP OutputStreams block flush()
Daniel Kulp created CXF-4371: Summary: HTTP OutputStreams block flush() Key: CXF-4371 URL: https://issues.apache.org/jira/browse/CXF-4371 Project: CXF Issue Type: Bug Components: Transports Affects Versions: 2.6.1 Reporter: Daniel Kulp Assignee: Daniel Kulp Fix For: 2.6.2 The HTTP output streams block the flush calls to prevent unwanted chunks and network packets with poorly behaving Stax writers. However, this prevents streaming content back in pre-defined chunks by the JAX-RS providers. It would be better to just block the flushs from the StaxOutInterceptor so the non-stax cases can have closer to raw access to the stream. -- 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-4371) HTTP OutputStreams block flush()
[ https://issues.apache.org/jira/browse/CXF-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-4371. -- Resolution: Fixed > HTTP OutputStreams block flush() > > > Key: CXF-4371 > URL: https://issues.apache.org/jira/browse/CXF-4371 > Project: CXF > Issue Type: Bug > Components: Transports >Affects Versions: 2.6.1 >Reporter: Daniel Kulp >Assignee: Daniel Kulp > Fix For: 2.6.2 > > > The HTTP output streams block the flush calls to prevent unwanted chunks and > network packets with poorly behaving Stax writers. However, this prevents > streaming content back in pre-defined chunks by the JAX-RS providers. It > would be better to just block the flushs from the StaxOutInterceptor so the > non-stax cases can have closer to raw access to the stream. -- 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] [Created] (CXF-4372) Using geronimo jaxws API directly
Willem Jiang created CXF-4372: - Summary: Using geronimo jaxws API directly Key: CXF-4372 URL: https://issues.apache.org/jira/browse/CXF-4372 Project: CXF Issue Type: Task Components: OSGi Reporter: Willem Jiang Assignee: Willem Jiang Priority: Minor Fix For: 2.5.5, 2.6.2 geronimo JAXWS spec API bundle already has the locator which works as servicemix specs locator, we should use it instead of servicemix wrap one. -- 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-4372) Using geronimo jaxws API directly
[ https://issues.apache.org/jira/browse/CXF-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293321#comment-13293321 ] Freeman Fang commented on CXF-4372: --- Hi Willem, I'm not sure if we need do it. There was a discussion[1] in Servicemix DEV mailling list to discuss similar issue, also the discussion[2] here compare the cons/pros between the two. IMO we should keep using servicemix jaxws api spec. [1]http://servicemix.396122.n5.nabble.com/DISCUSS-JAXWS-API-2-2-spec-td4932632.html [2]http://irclogs.dankulp.com/logs/irclogger_log/cxf?date=2011-10-24,Mon&sel=56#l52 Freeman > Using geronimo jaxws API directly > - > > Key: CXF-4372 > URL: https://issues.apache.org/jira/browse/CXF-4372 > Project: CXF > Issue Type: Task > Components: OSGi >Reporter: Willem Jiang >Assignee: Willem Jiang >Priority: Minor > Fix For: 2.5.5, 2.6.2 > > > geronimo JAXWS spec API bundle already has the locator which works as > servicemix specs locator, we should use it instead of servicemix wrap one. -- 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] [Created] (FEDIZ-15) Support the publish of the WS-Federation Metadata document
Alex Sarafian created FEDIZ-15: -- Summary: Support the publish of the WS-Federation Metadata document Key: FEDIZ-15 URL: https://issues.apache.org/jira/browse/FEDIZ-15 Project: CXF-Fediz Issue Type: Wish Reporter: Alex Sarafian It would be really good if Fediz supporter WS-Federation Metadata documents like ADFS does. It is really helpful for the .NET stack using the Windows Identity Foundation Federation Utility (FedUtil) for configuration of the WIF stack for Passive and Active profiles. -- 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
