Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7777901
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 1, 20262026-06-01T18:15:37+00:00 2026-06-01T18:15:37+00:00

Scenario: The client is a Perl script using SOAP::Lite . The server is a

  • 0

Scenario:

  • The client is a Perl script using SOAP::Lite.
  • The server is a Java based application using Spring and CXF.

My client is producing based on the WSDL the following SOAP request:

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Body>
        <createFolder xmlns="http://xyz.com/">
            <parentId xsi:type="xsd:string">1</parentId>
            <folderName xsi:type="xsd:string">Test</folderName>
        </createFolder>
    </soap:Body>
</soap:Envelope>

This request will fail against CXF. After several investigations I found out that the following manually produced request will work:

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xyz="http://xyz.com/">
    <soap:Body>
        <xyz:createFolder>
            <parentId xsi:type="xsd:string">1</parentId>
            <folderName xsi:type="xsd:string">Test</folderName>
        </xyz:createFolder>
    </soap:Body>
</soap:Envelope>

The difference is the namespace definition for the element createFolder.

My question is: How can I configure SOAPLite to create the working SOAP request?

Or vice versa: How can CXF be configured to accept the SOAP::Lite request style?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-01T18:15:38+00:00Added an answer on June 1, 2026 at 6:15 pm

    Look under ns. If gives a similarly qualified name for root element of the fragment

    Using the following:

    SOAP::Lite->new->proxy( 'http://somewhere.com' )
        ->ns( 'http://xyz.com/', 'xyz' )->createFolder( 
          SOAP::Data->new( name => 'parentId',   value => 1, type => 'xsd:string' )
        , SOAP::Data->new( name => 'folderName', value => 'Test' ) 
        );
    

    I got the following:

    <?xml version="1.0" encoding="UTF-8"?>
    <soap:Envelope 
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
        xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" 
        xmlns:xyz="http://xyz.com/" 
        xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
        soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" 
        xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
    >
      <soap:Body>
        <xyz:createFolder>
          <parentId   xsi:type="xsd:string">1</parentId>
          <folderName xsi:type="xsd:string">Test</folderName>
        </xyz:createFolder>
      </soap:Body>
    </soap:Envelope>
    

    And I think that’s what you want.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

My scenario is as follows: I have a client-server application. The client is deployed
I am using a client-server scenario. The client communicates with the server(which is a
We are developing an Client-Server-Scenario where the client application will be installed on hundred
I am using WCF service in my client-server application and I am facing following
Scenario: WCF client app, calling a web-service (JAVA) operation, wich requires a complex object
Consider and client server scenario and you got two options: You can include Server's
Say I have a simple client/server scenario with one method: // client code $client
My scenario is this: A client application executes a HTTP POST against an endpoint
we have this scenario: A server which contains needed data and client component which
Hi I have code which sets up a basic client to server scenario and

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.