Unmarshalling Error: prefix xsd is not bound to a namespace

Hi, I have upgraded my web service and now the new webservice uses CXF. When I send my old soap message to the new CXF webservice, i am getting the following response. 'Unmarshalling Error: prefix xsd is not bound to a namespace'. In my soap request, I have the following element. 'Shyam' Here I

[jira] [Created] (CXF-3668) Duplicate Poclies added in Java-First approach

Duplicate Poclies added in Java-First approach -- Key: CXF-3668 URL: https://issues.apache.org/jira/browse/CXF-3668 Project: CXF Issue Type: Bug Components: WS-* Components Affects Ve

[jira] [Resolved] (CXF-3666) Wrong code in MessageBodyWriter example

[ https://issues.apache.org/jira/browse/CXF-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-3666. --- Resolution: Fixed Assignee: Sergey Beryozkin > Wrong code in MessageBodyWriter example >

[jira] [Resolved] (CXF-3662) wadl2java : Return types aren't generated properly on server interfaces for methods with more than 1 response element.

[ https://issues.apache.org/jira/browse/CXF-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-3662. --- Resolution: Fixed Fix Version/s: 2.5 2.4.2 Assignee: Sergey B

[jira] [Resolved] (CXF-3656) Wadl generation problem with @FormParam cause IllegalStateException

[ https://issues.apache.org/jira/browse/CXF-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-3656. --- Resolution: Fixed Fix Version/s: 2.5 2.4.2 thanks for the analysis of

[jira] [Assigned] (CXF-3656) Wadl generation problem with @FormParam cause IllegalStateException

[ https://issues.apache.org/jira/browse/CXF-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin reassigned CXF-3656: - Assignee: Sergey Beryozkin > Wadl generation problem with @FormParam cause IllegalStateExce

[jira] [Updated] (CXF-3667) Content negotiation & ResponseBuilder

[ https://issues.apache.org/jira/browse/CXF-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Łukasz Strzelecki updated CXF-3667: --- Description: With creation of response without content, based on javax.ws.rs.core.Response.Res

[jira] [Updated] (CXF-3667) Content negotiation & ResponseBuilder

[ https://issues.apache.org/jira/browse/CXF-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Łukasz Strzelecki updated CXF-3667: --- Description: With creation of response without content, based on javax.ws.rs.core.Response.Res

[jira] [Updated] (CXF-3667) Content negotiation & ResponseBuilder without entity - wrong Content-Type

[ https://issues.apache.org/jira/browse/CXF-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Łukasz Strzelecki updated CXF-3667: --- Summary: Content negotiation & ResponseBuilder without entity - wrong Content-Type (was: Conte

[jira] [Updated] (CXF-3667) Content negotiation & ResponseBuilder

[ https://issues.apache.org/jira/browse/CXF-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Łukasz Strzelecki updated CXF-3667: --- Description: With creation of response without content, based on javax.ws.rs.core.Response.Res

[jira] [Created] (CXF-3667) Content negotiation & ResponseBuilder

Content negotiation & ResponseBuilder - Key: CXF-3667 URL: https://issues.apache.org/jira/browse/CXF-3667 Project: CXF Issue Type: Bug Components: JAX-RS Affects Versions: 2.4.1 R

[jira] [Created] (CXF-3666) Wrong code in MessageBodyWriter example

Wrong code in MessageBodyWriter example --- Key: CXF-3666 URL: https://issues.apache.org/jira/browse/CXF-3666 Project: CXF Issue Type: Bug Components: Documentation Reporter: Pierre I

[jira] [Commented] (CXF-3653) Bad URLs on generated service list page

[ https://issues.apache.org/jira/browse/CXF-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067078#comment-13067078 ] Donal Fellows commented on CXF-3653: If I fetch {{http://localhost:8080/taverna%2Dserver

[jira] [Created] (CXF-3665) server-sid​e endpoint cleanup problem in spring based CXF scenarios in OSGi

server-sid​e endpoint cleanup problem in spring based CXF scenarios in OSGi --- Key: CXF-3665 URL: https://issues.apache.org/jira/browse/CXF-3665 Project: CXF Issue Type

[jira] [Created] (CXF-3664) wadl2java : xsd data types aren't mapped to java data types properly if they use mixed case.

wadl2java : xsd data types aren't mapped to java data types properly if they use mixed case. Key: CXF-3664 URL: https://issues.apache.org/jira/browse/CXF-3664

[jira] [Created] (CXF-3663) Migrate to Jetty 7.4.4 from 7.4.3.

Migrate to Jetty 7.4.4 from 7.4.3. -- Key: CXF-3663 URL: https://issues.apache.org/jira/browse/CXF-3663 Project: CXF Issue Type: Improvement Components: Transports Affects Versions: 2.4.1

[jira] [Updated] (CXF-3662) wadl2java : Return types aren't generated properly on server interfaces for methods with more than 1 response element.

[ https://issues.apache.org/jira/browse/CXF-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ceri Hughes updated CXF-3662: - Description: My wadl file frequently has more than 1 response element in the method elements, i.e.: {code}

[jira] [Created] (CXF-3662) wadl2java : Return types aren't generated properly on server interfaces for methods with more than 1 response element.

wadl2java : Return types aren't generated properly on server interfaces for methods with more than 1 response element. -- Key: CXF-3662 URL: https:

[jira] [Created] (CXF-3661) Support for enveloped XMLSignatures for JAX-RS clients and endpoints

Support for enveloped XMLSignatures for JAX-RS clients and endpoints Key: CXF-3661 URL: https://issues.apache.org/jira/browse/CXF-3661 Project: CXF Issue Type: New Feature

Issues with Attachments: week of 2011-07-18

CXF - Monday, July 18, 2011 3 Issues with Attachments (sorted oldest to newest) [CXF-3612] wsdl2java error while parsing WSDL having policyreferences within wsdl - Created: 2011-06-22 - Updated: 2011-06-29 - Type: Bug - Fix Versions: [] - Reporter: Viv