Hello,

I am struggling to get some SOAP request working using SOAP Ligth and PHP on the
requesting side and PERL on the server I am requesting information from. I have
never worked with SOAP before.

When printing the trace, etc., the URL I am trying to connect to looks wired:
"http://192.168.1.101/otrs/rpc.pl". I guess that could be part of the problem
(but what do I know...). Here is the trace:



     Fault message: Could not connect to host
     Fault code: 0
     array(2) {
       [0]=>
       array(4) {
         ["function"]=>
         string(11) "__doRequest"
         ["class"]=>
         string(10) "SoapClient"
         ["type"]=>
         string(2) "->"
         ["args"]=>
         array(5) {
           [0]=>
           string(645) "
     userpasswordTicketObjectTicketCreateNumber
     "
           [1]=>
           string(35) "http://192.168.1.101/otrs/rpc.pl"
           [2]=>
           string(13) "Core#Dispatch"
           [3]=>
           int(1)
           [4]=>
           int(0)
         }
       }
       [1]=>
       array(6) {
         ["file"]=>
         string(54) "/Library/WebServer/Documents/SMICTestProject/index.php"
         ["line"]=>
         int(37)
         ["function"]=>
         string(10) "__soapCall"
         ["class"]=>
         string(10) "SoapClient"
         ["type"]=>
         string(2) "->"
         ["args"]=>
         array(2) {
           [0]=>
           string(8) "Dispatch"
           [1]=>
           array(4) {
             [0]=>
             string(8) "user"
             [1]=>
             string(11) "password"
             [2]=>
             string(12) "TicketObject"
             [3]=>
             string(18) "TicketCreateNumber"
           }
         }
       }
     }
     Fault trace: // Of some reason this ends up after the actual trace
     Fault line: 37

Here is the code that generates the exception:

         try {
     $client = new SoapClient(null, array(

         'location'  => "http://192.168.1.101/otrs/rpc.pl",
         'uri'       => "Core",
         'trace'     => 1,
         'login'     => "user",
         'password'  => "password",
         'style'     => SOAP_RPC,
         'use'       => SOAP_ENCODED
     ));


     $ticketnumber = $client->__soapCall("Dispatch", array("user", "password",
"TicketObject", "TicketCreateNumber"));
     //Here happens a lot of things, but since this code is never reached I skip
including it.

     } catch (SoapFault $fault) {
     //trigger_error("SOAP Fault: (faultcode: {$fault->faultcode}, faultstring:
{$fault->faultstring})", E_USER_ERROR);
     echo "Fault message: ".$fault->getMessage()."\n";
     echo "Fault code: ".$fault->getCode()."\n";
     echo "Fault trace: ".var_dump($fault->getTrace())."\n";
     echo "Fault line: ".$fault->getLine()."\n";
     echo "Bad SOAP request\n";
     echo "REQUEST:\n".$client->__getLastRequest()."\n";
     echo "RESPONSE:\n".$client->__getLastResponse()."\n";
     echo "</pre>";
     exit;
     }

What is the problem and what how can I fix it? Should I encode the URL...?

I included just what I thought was necessary, please let me know if I should add
something. There is absolutely nothing in any logs I can include here, which I
find strange itself.

I'm using OpenSUSE/Apache on the server side and OsX/Apache/PHP on the client
side.

Thank you in advance!

Hi, I see plenty of examples of building complex data types using SOAP::Lite
client side, but no real examples of processing these server side.

I need to process nested lists coming into the server.

1) How do I get access to the body of the request on the server side?
2) Are there any examples of picking apart nested lists?

Thanks for your help, L

Hi all, having an issue running SOAP Lite 0.71 under Glassfish 3.1.1. Whenever I
send a request in that has content length > 512 bytes the server does not appear
to see the request and client times out.

Not sure if this is a GF or SOAP Lite issue, but does anyone have any ideas?

Thanks, L

Hi, can anyone tell me how to access the raw XML content in a CGI server please?

Thanks, Lee

I.m looking for help to implement data transfer using perl SOAP.  We need to
connect to a state agency to transfer files.  Any help is appreciated.

Here's what we need.

•         The ProcessRoster web service's WSDL is located at:

https://www.state.tx.us/ProcessEdRoster/Service1.asmx?wsdl

•         The formats of the xml (request and response) is noted in the
attachments
•         Our authentication requires a security token.  Your application should
reference this from a config file (as I am sure this will periodically change). 
Please note the snippet of code (C# .Net) to instantiate the authentication
class and set the token:

WebReferenceName.ValidationSoapHeader hdr =
   new WebReferenceName.ValidationSoapHeader();
hdr.DevToken = "xx";


•         Instantiation and request of the web service (snippet of code):

WebReferenceName.Service1 ws =
   new WebReferenceName.Service1();
WebReferenceName.ProcessRoster("your xml request");

Hi *,

I try to write a simple Perl SOAP Client for these services:

http://almdemo.polarion.com/polarion/ws/services/SessionWebService?wsdl
http://almdemo.polarion.com/polarion/ws/services/TrackerWebService?wsdl
http://almdemo.polarion.com/polarion/ws/services/ProjectWebService?wsdl


My script looks like this now:
---snip---
...
my $SessionWebServicesoap = SOAP::Lite
-> proxy($SessionWebServiceURI)
-> uri($SessionWebServiceURI);

my $TrackerWebServicesoap = SOAP::Lite
-> proxy($TrackerWebServiceURI)
-> uri($TrackerWebServiceURI);

my $ProjectWebServicesoap = SOAP::Lite
-> proxy($ProjectWebServiceURI)
-> uri($ProjectWebServiceURI);

my $response;

print "\n";

#get session
my $session = $SessionWebServicesoap->logIn(
         SOAP::Data->name('userName')->value($user),
         SOAP::Data->name('password')->value($password)
);
my $sessionID = $session->{'_content'}[2][0][4]{'sessionID'};
print "session is: ".$sessionID."\n";

my $authHeader = SOAP::Header->name('sessionID')->value($sessionID);

$response = $ProjectWebServicesoap->getProject("productbacklog");
die $response->faultstring if ($response->fault);
my $IObject = $response->result;
print $response->result, "\n";

$response = $TrackerWebServicesoap->createWorkItem($IObject,$authHeader);
die $response->faultstring if ($response->fault);
print $response->result, "\n";


exit;
---snap---


Unfortunately I always get the following error message:
session is: 9109123277697179703
Project=HASH(0x6b6c4e0)
com.polarion.platform.security.PermissionDeniedException: Permission
com.polarion.persistence.object.WorkItem.key.created.modify denied for user null
in context null at soap6.pl line 56.


Do you have an idea how to add the session ID to my SOAP-Request Header?

I think somebody had the same problem with python's suds here:
https://fedorahosted.org/suds/ticket/233


Thank you.

Best regards,
Tobias


This email is intended solely for the use of the individual to whom it is
addressed and may contain confidential and/or privileged material. Any views or
opinions presented are solely those of the author and do not necessarily
represent those of AGCO. If you are not the intended recipient, be advised that
you have received this email in error and that any use, dissemination,
forwarding, printing or copying of this email is strictly prohibited. Neither
AGCO nor the sender accepts any responsibility for viruses and it is your
responsibility to scan and virus check the e-mail and its attachment(s) (if
any).

Hi *,

I try to write a simple Perl SOAP Client for these services:

http://almdemo.polarion.com/polarion/ws/services/SessionWebService?wsdl
http://almdemo.polarion.com/polarion/ws/services/TrackerWebService?wsdl
http://almdemo.polarion.com/polarion/ws/services/ProjectWebService?wsdl


My script looks like this now:
---snip---
...
my $SessionWebServicesoap = SOAP::Lite
-> proxy($SessionWebServiceURI)
-> uri($SessionWebServiceURI);

my $TrackerWebServicesoap = SOAP::Lite
-> proxy($TrackerWebServiceURI)
-> uri($TrackerWebServiceURI);

my $ProjectWebServicesoap = SOAP::Lite
-> proxy($ProjectWebServiceURI)
-> uri($ProjectWebServiceURI);

my $response;

print "\n";

#get session
my $session = $SessionWebServicesoap->logIn(
	 SOAP::Data->name('userName')->value($user),
	 SOAP::Data->name('password')->value($password)
);
my $sessionID = $session->{'_content'}[2][0][4]{'sessionID'};
print "session is: ".$sessionID."\n";

my $authHeader = SOAP::Header->name('sessionID')->value($sessionID);

$response = $ProjectWebServicesoap->getProject("productbacklog");
die $response->faultstring if ($response->fault);
my $IObject = $response->result;
print $response->result, "\n";

$response = $TrackerWebServicesoap->createWorkItem($IObject,$authHeader);
die $response->faultstring if ($response->fault);
print $response->result, "\n";


exit;
---snap---


Unfortunately I always get the following error message:
session is: 9109123277697179703
Project=HASH(0x6b6c4e0)
com.polarion.platform.security.PermissionDeniedException: Permission
com.polarion.persistence.object.WorkItem.key.created.modify denied for
user null in context null at soap6.pl line 56.


Do you have a idea how to add the session ID to my SOAP-Request Header?

I think somebody had the same problem with python's suds here:
https://fedorahosted.org/suds/ticket/233



Thank you.
Tobias

Hi *,

sorry, about Double posting - I thought that my first message hasn't
transmitted correctly.

In the meantime I was able to solve the problem by myself:

---snip---
my $SessionWebServicesoap = SOAP::Lite

->readable(1)

->proxy($SessionWebServiceURI)

->uri($SessionWebServiceURI)

;

$SessionWebServicesoap->autotype(0);

my $SessionWebServicesoapSerializer = $SessionWebServicesoap->serializer();

$SessionWebServicesoapSerializer->register_ns(
'http://ws.polarion.com/session', 'ns1' );



my $ProjectWebServicesoap = SOAP::Lite

->readable(1)

->proxy($ProjectWebServiceURI)

->uri($ProjectWebServiceURI)

;

$ProjectWebServicesoap->autotype(0);

my $ProjectWebServicesoapSerializer = $ProjectWebServicesoap->serializer();

$ProjectWebServicesoapSerializer->register_ns(
'http://ws.polarion.com/session', 'ns1' );





my $TrackerWebServicesoap = SOAP::Lite

->readable(1)

->proxy($TrackerWebServiceURI)

->uri($TrackerWebServiceURI)

;

$TrackerWebServicesoap->autotype(0);

my $TrackerWebServicesoapSerializer = $TrackerWebServicesoap->serializer();

$TrackerWebServicesoapSerializer->register_ns(
'http://ws.polarion.com/session', 'ns1' );



my $response;



print "\n";



#get session

my $session = $SessionWebServicesoap->logIn(

	 SOAP::Data->name('userName')->value($user),

	 SOAP::Data->name('password')->value($password)

);

my $sessionID = $session->{'_content'}[2][0][4]{'sessionID'};

print "session is: ".$sessionID."\n";



my $authHeader = SOAP::Header->name('ns1:sessionID')->value($sessionID);



$response = $TrackerWebServicesoap->getWorkItemById("projectname",
"TEST-1", $authHeader);

die $response->faultstring if ($response->fault);

print Dumper($response->result);


---snap---

The important stuff is the "register_ns" and the "$authheader" part.
Now it works perfect and I can go forward with this script... :)

Maybe somebody will find this solution useful in future.


Best regards,
Tobias

I'm having trouble getting a soap response to validate because there does not
seem to be an easy way to change the prefix of type attributes. Setting
$obj->type() to anything always uses xsi:type, which is fine for standard types,
but not for complex types defined in the wsdl. I tried setting prefix but that
didn't help.

I'd also like to be able to set the additional namespaces in the Envelope.

This has kept me busy for a few days, any help would be really appreciated.

Hello
I have some php-Code to connect to a soap-Server and I'm trying to figure out
how I can do the same connection with SOAP::Lite.
I'm not able to find the corresponding classes and methods in SOAP::Lite.

Here is the php-Code:

$client
=
new SoapClient
     ("http://130.60.19.86/evasys_01/services/soapserver-v50.wsdl");

$header_input = array('Login' => "soap", 'Password' => "xxx" );
$soapHeaders = new SoapHeader('soapserver-v50.wsdl',
                               'Header',
                                $header_input);
$client->__setSoapHeaders( $soapHeaders );

I would be glad if somebody could help me.

Regards
Daniel

I'm using JIRA::Client which uses SOAP::Lite to fetch an "issue" from a JIRA
server.

My code was fetching the owner of the ticket as $ticket->{assignee}, and this
was a scalar.

Last Friday the code started to fail because $ticket->{assignee} was now
returning a "String" object.

It appears that the WSDL changed (along with the SOAP response).  When I ran the
code on the public JIRA server I received a scalar again.

The XML markup seems to have changed from this (on the public JIRA server):

<assignee xsi:type="xsd:string">andreyev</assignee>

Which deserializes like this (simple scalar):

$ perl -MData::Dumper -MSOAP::Lite -le 'local $/; print Data::Dumper::Dumper(
SOAP::Deserializer->deserialize( <> )->result->{assignee} )'  jira_test.xml
$VAR1 = 'andreyev';


To this structure:

<assignee xsi:type="ns2:String" xmlns:ns2="http://lang.java"><bytes
xsi:type="xsd:base64Binary">YmlsbEBpcGFyYWRpZ21sksisvbQ==</bytes><empty
xsi:type="xsd:boolean">false</empty></assignee>


Which deserializes like this:

  perl -MData::Dumper -MSOAP::Lite -le 'local $/; print Data::Dumper::Dumper(
SOAP::Deserializer->deserialize( <> )->result->{assignee} )'  issue.xml
$VAR1 = bless( {
                  'bytes' => 'bill@...',
                  'empty' => 0
                }, 'String' );

I rarely use SOAP, so this may be a dumb question:

Could  JIRA::Client have somehow seen this change and handled it automatically? 
Or is this just a non-compatible API change?

And what methods end on available on this "String" class?

Does SOAP::LIte just turn any complex element into an object?  I mean w/o the
WDSL how does SOAP::Lite know what this object should look like -- just by the
structure of the XML?

Here's the public WSDL, if curious:

https://jira.atlassian.com/rpc/soap/jirasoapservice-v2?wsdl

I work with a large CPAN installation.  SOAP.pm also comes
with a SOAP::Packager module.  So, one or the other of them
breaks.  Can this be resolved in the next version by moving
everything fully under the SOAP::Lite::* namespace?

Thanks.

-Mark

I am having an issue using SOAP::Lite->service and not being able to check for
faultstring or is_success like there is when I use SOAP::Lite->new

I am unable to use the service when I use SOAP::Lite->new, but have no issue
when using the service using SOAP::Lite->service. I need to be able to read the
server response just in case the service is down. When I dump out
$soap(Dumper($soap)) I notice that there is no SOAP::Transport object. Is there
any way to retrieve the server response?

I am using Perl connecting to an ASP service.

Thanks in advance.

Have a server running SOAP::Lite (0.711) to manage soap requests and return
results as an apache service/handler. It's working close to perfect except for
this one nagging problem. The SOAP::Lite library keeps creating a namesp1
pointing to soaplite.com and assuming all my new types are part of that
namespace.

For example, this request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:util="http://util.com/API/SOAP/Utils">
    <soapenv:Header/>
    <soapenv:Body>
       <util:getSLAs>
             <util:sla_ids>100</util:sla_ids>
       </util:getSLAs>
    </soapenv:Body>
</soapenv:Envelope>

Gives this response:

<soap:Envelope
  soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
  xmlns:namesp1="http://namespaces.soaplite.com/perl"
  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"
  xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Body>
       <getSLASResponse xmlns="http://util.com/API/SOAP/Utils">
          <sla_list soapenc:arrayType="namesp1:SLAObject[1]"
xsi:type="soapenc:Array">
             <SLAObject xsi:type="namesp1:SLAObject" xmlns="">
                <sla_id xsi:type="xsd:int">100</sla_id>
                <sla_name xsi:type="xsd:string">sample sla</sla_name>
                <active xsi:type="xsd:boolean">true</active>
             </SLAObject>
          </sla_list>
       </getSLASResponse>
    </soap:Body>
</soap:Envelope>

Which would be great except for this extraneous namesp1 which SOAP::Lite keeps
putting in there.

It's obviously smart enough to use the original request namespace for the
response object. If it didn't prefix the complex types with namesp1, it would be
fine, but nothing I try will get rid of that. I can add a ->type("foo:Object")
to the SOAP::Data call creating the object, which removes namesp1, but then I
don't have a "foo" namespace in the Response which causes the opposite problem.
Using ->prefix('') or ->uri('') doesn't remove it either.

I can get the effect I want by modifying the SOAP::Lite library to autotype(0)
when generating the response, but I can't do that in production. I can't find
another place to use that hook.

Any help here?

Hi List,

I have to call a Webservice named GetManufacturers that does not accept any
parameter.

Unfortunately SOAP::LIte (0.714) generates  <admin:GetManufacturers
xsi:nil="true" /> instead of <admin:GetManufacturers/> in the SOAP Body, which
is not accpetd by the SOAP server.

All I found so far on the web is the hint to create my own serializer to solve
this.  I dont think this will solve my problem as I dont want to change the
behaviour of SOAP::Lite with regard to serialization of an undefined parameter
but rather want to skip the parameter serialization for parameterless method
calls completely.

After some UTSL I changed line 1593 in SOAP::LIte from

$body->set_value($parameters ? \$parameters : SOAP::Utils::encode_data()) if
$body;

to

$body->set_value($parameters, \$parameters) if $body && $parameters;

which results in the "correct" body tag as described above.

I would like to know if there is a better way to achieve this or if not,
whether we could make this behaviour configuration dependend lets say over a
method call like $handle->suppress_nils_in_parameterless_calls(1|0) as
already implemented for calls like $handle->use_default_ns()

Best regards,

Klaus
--
Polymer physicists are into chains.
-

Hi Folks,

I'm relatively new to SOAPLite, as I inherited an application which relies on it
for web services (from a client perspective). I'm trying to generate a SOAP call
like this (tested in SOAPUI):

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:ns="http://delegosoftware.com/ns"
  xmlns:def="http://delegosoftware.com/definitions">
    <soapenv:Header/>
    <soapenv:Body>
       <ns:AuthorizationRequest>
          <def:AuthorizationRequestProcess>
             <def:Authorize encrypt="false" merchant="DEMOMERCHANT">
                <def:CCAUT>
                   <def:Ccins>Visa</def:Ccins>
                   <def:Ccnum>B598A5ED6C7024D3-1111</def:Ccnum>
                   <def:Datbi>20140930</def:Datbi>
                   <def:Ccname>JOE CONSUMER</def:Ccname>
		   <def:Autwv>154.18</def:Autwv>
                   <def:Ccwae>USD</def:Ccwae>
                   <def:Merch>DEMOMERCHANT</def:Merch>
		 <def:Cvval>111</def:Cvval>
                </def:CCAUT>
             </def:Authorize>
          </def:AuthorizationRequestProcess>
       </ns:AuthorizationRequest>
    </soapenv:Body>
</soapenv:Envelope>
+--------------------------------
Nothing too fancy here. Basic call to AuthorizationRequest with a bunch of
parameters.


My perl (SOAPLite) to do the equivalent is:

use SOAP::Lite +trace;

my $soap = SOAP::Lite ->uri('http://carina.delego.ca:8080')
	 ->proxy( 'http://carina.delego.ca:8080/DelegoWS/services/DelegoWS' ) ;

$soap->service('http://carina.delego.ca:8080/DelegoWS/services/DelegoWS?wsdl' )
;
$soap->readable(1) ;

my $serializer = $soap->serializer();
$serializer->register( 'http://delegosoftware.com/ns', 'ns' );


$serializer->namespaces({
"http://schemas.xmlsoap.org/soap/envelope/"=>"soapenv",
"http://delegosoftware.com/ns"=>"ns",
"http://delegosoftware.com/definitions"=>"def"});


my $cardtype = 'Visa' ;
my $expdate = '20141231' ;
my $cardnum = 'B598A5ED6C7024D3-1111' ;
my $nameoncard = 'JOE CONSUMER' ;
my $authamount = 150.12 ;
my $currency = 'USD' ;
my $merchid = 'DEMOMERCHANT' ;
my $cvv = 111 ;
my $street = '6415 Hwy 70' ;
my $zip = 10000 ;


my $som = $soap->call('ns:AuthorizationRequest',
	 SOAP::Data->name('def:AuthorizationRequestProcess'
	 => \SOAP::Data->name('def:Authorize' =>
	 \SOAP::Data->name('def:CCAUT' =>
	 \SOAP::Data->value(
		 SOAP::Data->name("def:Ccins" => $cardtype)->type(''),
		 SOAP::Data->name("def:Datbi" => $expdate)->type(''),
		 SOAP::Data->name("def:Ccnum" => $cardnum)->type(''),
		 SOAP::Data->name("def:Ccname" => $nameoncard)->type(''),
		 SOAP::Data->name("def:Autwv" => $authamount)->type('')->type(''),
		 SOAP::Data->name("def:Ccwae" => $currency)->type(''),
		 SOAP::Data->name("def:Merch" => $merchid)->type(''),
		 SOAP::Data->name("def:Cvval" => $cvv)->type(''),
		 SOAP::Data->name("def:Stras" => $street)->type(''),
		 SOAP::Data->name("def:Pstlz" => $zip)->type('')
		 )
	 ))->attr({encrypt => false,merchant => $merchid})
	 )
) ;

+-----------------------------------------------------------
Again, nothing particularly involved. But the issue comes with the XML this
generates:

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope
     soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
     xmlns:def="http://delegosoftware.com/definitions"
     xmlns:ns="http://delegosoftware.com/ns"
     xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
     <ns:AuthorizationRequest xmlns:ns="http://carina.delego.ca:8080">
       <def:AuthorizationRequestProcess>
         <def:Authorize encrypt="false" merchant="DEMOMERCHANT">
           <def:CCAUT>
             <def:Ccins>Visa</def:Ccins>

             <def:Datbi>20141231</def:Datbi>

             <def:Ccnum>B598A5ED6C7024D3-1111</def:Ccnum>

             <def:Ccname>JOE CONSUMER</def:Ccname>

             <def:Autwv>150.12</def:Autwv>

             <def:Ccwae>USD</def:Ccwae>

             <def:Merch>DEMOMERCHANT</def:Merch>

             <def:Cvval>111</def:Cvval>

             <def:Stras>6415 Hwy 70</def:Stras>

             <def:Pstlz>10000</def:Pstlz>
           </def:CCAUT>
         </def:Authorize>
       </def:AuthorizationRequestProcess>
     </ns:AuthorizationRequest>
   </soapenv:Body>
</soapenv:Envelope>
+---------------------------------------------------------------

How can I make SOAPLITE suppress the:

xmlns:ns="http://carina.delego.ca:8080

or at least the :ns

from the

<ns:AuthorizationRequest    line, so it better matches the SOAPUI example which
I know works?


Cheers,

Grant

Hi Grant,

> SOAP::Lite ->uri('http://carina.delego.ca:8080')

this causes the namespace attribute on your WS-Operation-Element (eg the
first argument to proxy->call(...))

use ->uri("http://delegosoftware.com/ns") instead, then you should get the
expected result.

Cheers,
martin

> -----Ursprüngliche Nachricht-----
> Von: soaplite@yahoogroups.com [mailto:soaplite@yahoogroups.com] Im Auftrag
> von grantcblair
> Gesendet: Donnerstag, 29. März 2012 21:59
> An: soaplite@yahoogroups.com
> Betreff: [soaplite] Would REALLY appreciate help - new to SOAPLite
>
> Hi Folks,
>
> I'm relatively new to SOAPLite, as I inherited an application which relies
on it for web
> services (from a client perspective). I'm trying to generate a SOAP call
like this
> (tested in SOAPUI):
>
> <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
>  xmlns:ns="http://delegosoftware.com/ns"
>  xmlns:def="http://delegosoftware.com/definitions">
>    <soapenv:Header/>
>    <soapenv:Body>
>       <ns:AuthorizationRequest>
>          <def:AuthorizationRequestProcess>
>             <def:Authorize encrypt="false" merchant="DEMOMERCHANT">
>                <def:CCAUT>
>                   <def:Ccins>Visa</def:Ccins>
>                   <def:Ccnum>B598A5ED6C7024D3-1111</def:Ccnum>
>                   <def:Datbi>20140930</def:Datbi>
>                   <def:Ccname>JOE CONSUMER</def:Ccname>
> 		  <def:Autwv>154.18</def:Autwv>
>                   <def:Ccwae>USD</def:Ccwae>
>                   <def:Merch>DEMOMERCHANT</def:Merch>
> 	 <def:Cvval>111</def:Cvval>
>                </def:CCAUT>
>             </def:Authorize>
>          </def:AuthorizationRequestProcess>
>       </ns:AuthorizationRequest>
>    </soapenv:Body>
> </soapenv:Envelope>
> +--------------------------------
> Nothing too fancy here. Basic call to AuthorizationRequest with a bunch of
> parameters.
>
>
> My perl (SOAPLite) to do the equivalent is:
>
> use SOAP::Lite +trace;
>
> my $soap = SOAP::Lite ->uri('http://carina.delego.ca:8080')
>  ->proxy( 'http://carina.delego.ca:8080/DelegoWS/services/DelegoWS' )
;
>
>
$soap->service('http://carina.delego.ca:8080/DelegoWS/services/DelegoWS?wsdl
' )
> ;
> $soap->readable(1) ;
>
> my $serializer = $soap->serializer();
> $serializer->register( 'http://delegosoftware.com/ns', 'ns' );
>
>
> $serializer->namespaces({
> "http://schemas.xmlsoap.org/soap/envelope/"=>"soapenv",
> "http://delegosoftware.com/ns"=>"ns",
> "http://delegosoftware.com/definitions"=>"def"});
>
>
> my $cardtype = 'Visa' ;
> my $expdate = '20141231' ;
> my $cardnum = 'B598A5ED6C7024D3-1111' ;
> my $nameoncard = 'JOE CONSUMER' ;
> my $authamount = 150.12 ;
> my $currency = 'USD' ;
> my $merchid = 'DEMOMERCHANT' ;
> my $cvv = 111 ;
> my $street = '6415 Hwy 70' ;
> my $zip = 10000 ;
>
>
> my $som = $soap->call('ns:AuthorizationRequest',
>  SOAP::Data->name('def:AuthorizationRequestProcess'
>  => \SOAP::Data->name('def:Authorize' =>
>  \SOAP::Data->name('def:CCAUT' =>
>  \SOAP::Data->value(
> 	 SOAP::Data->name("def:Ccins" => $cardtype)->type(''),
> 	 SOAP::Data->name("def:Datbi" => $expdate)->type(''),
> 	 SOAP::Data->name("def:Ccnum" => $cardnum)->type(''),
> 	 SOAP::Data->name("def:Ccname" => $nameoncard)->type(''),
> 	 SOAP::Data->name("def:Autwv" => $authamount)->type('')-
> >type(''),
> 	 SOAP::Data->name("def:Ccwae" => $currency)->type(''),
> 	 SOAP::Data->name("def:Merch" => $merchid)->type(''),
> 	 SOAP::Data->name("def:Cvval" => $cvv)->type(''),
> 	 SOAP::Data->name("def:Stras" => $street)->type(''),
> 	 SOAP::Data->name("def:Pstlz" => $zip)->type('')
> 	 )
>  ))->attr({encrypt => false,merchant => $merchid})
>  )
> ) ;
>
> +-----------------------------------------------------------
> Again, nothing particularly involved. But the issue comes with the XML
this
> generates:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <soapenv:Envelope
>     soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
>     xmlns:def="http://delegosoftware.com/definitions"
>     xmlns:ns="http://delegosoftware.com/ns"
>     xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
>   <soapenv:Body>
>     <ns:AuthorizationRequest xmlns:ns="http://carina.delego.ca:8080">
>       <def:AuthorizationRequestProcess>
>         <def:Authorize encrypt="false" merchant="DEMOMERCHANT">
>           <def:CCAUT>
>             <def:Ccins>Visa</def:Ccins>
>
>             <def:Datbi>20141231</def:Datbi>
>
>             <def:Ccnum>B598A5ED6C7024D3-1111</def:Ccnum>
>
>             <def:Ccname>JOE CONSUMER</def:Ccname>
>
>             <def:Autwv>150.12</def:Autwv>
>
>             <def:Ccwae>USD</def:Ccwae>
>
>             <def:Merch>DEMOMERCHANT</def:Merch>
>
>             <def:Cvval>111</def:Cvval>
>
>             <def:Stras>6415 Hwy 70</def:Stras>
>
>             <def:Pstlz>10000</def:Pstlz>
>           </def:CCAUT>
>         </def:Authorize>
>       </def:AuthorizationRequestProcess>
>     </ns:AuthorizationRequest>
>   </soapenv:Body>
> </soapenv:Envelope>
> +---------------------------------------------------------------
>
> How can I make SOAPLITE suppress the:
>
> xmlns:ns="http://carina.delego.ca:8080
>
> or at least the :ns
>
> from the
>
> <ns:AuthorizationRequest    line, so it better matches the SOAPUI example
which I
> know works?
>
>
> Cheers,
>
> Grant
>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

Above is the code I have and below is the request and the response. I
been looking all over this mailing list and the web for this answer, but
could not find it.

I know the error is:

Possible SOAP version mismatch: Envelope namespace
http://schemas.xmlsoap.org/wsdl/soap/ was unexpected. Expecting
http://schemas.xmlsoap.org/soap/envelope/.

I was just wondering how to fix it with my current structure of the code
I have below.

Thanks,
Shane



#!perl -w

use SOAP::Lite +trace => 'debug';

my $lmi_Soap = SOAP::Lite->new();

my $lmi_WSDL =

$lmi_Soap->service('https://secure.logmeinrescue.com/api/api.asmx?wsdl')\
;

$lmi_Soap->soapversion('1.2');

my $lmi_requestAuthCode =
    $lmi_WSDL->requestAuthCode( 'xxx', "xxx" );




SOAP::Transport::HTTP::Client::send_receive: POST
https://secure.logmeinrescue.c
om/api/api.asmx HTTP/1.1
Accept: text/xml
Accept: multipart/*
Accept: application/soap
Content-Length: 837
Content-Type: text/xml; charset=utf-8
SOAPAction:
"https://secure.logmeinrescue.com/API/API.asmx/requestAuthCode"

<?xml version="1.0" encoding="UTF-8"?><soap:Envelope
xmlns:tm="http://microsoft.
com/wsdl/mime/textMatching/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap1
2/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
soap:encodingStyle="http:
//schemas.xmlsoap.org/soap/encoding/"
xmlns:soap="http://schemas.xmlsoap.org/wsd
l/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns:wsdl="http://schemas.x
mlsoap.org/wsdl/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:so
apenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:http="http://schemas.xml
soap.org/wsdl/http/"
xmlns:tns="https://secure.logmeinrescue.com/API/API.asmx"><
soap:Body><tns:requestAuthCode><sEmail
xsi:type="s:string">XXXXX</sEmail><sPassword
xsi:type="s:string">XXXXX</sPassword></tns:request
AuthCode></soap:Body></soap:Envelope>


SOAP::Transport::HTTP::Client::send_receive: HTTP/1.1 500 Internal
Server Error
Cache-Control: private
Date: Fri, 13 Apr 2012 15:15:13 GMT
Server: Microsoft-IIS/7.5
Content-Length: 835
Content-Type: text/xml; charset=utf-8
Client-Date: Fri, 13 Apr 2012 15:15:11 GMT
Client-Peer: 69.25.20.195:443
Client-Response-Num: 1
Client-SSL-Cert-Issuer: /C=US/O=Thawte, Inc./CN=Thawte SSL CA
Client-SSL-Cert-Subject: /C=US/ST=Massachusetts/L=Woburn/O=LogMeIn,
Inc./OU=Secu
re Application Development/CN=secure.logmeinrescue.com
Client-SSL-Cipher: AES128-SHA
Client-SSL-Socket-Class: IO::Socket::SSL
X-Powered-By: ASP.NET

<?xml version="1.0" encoding="utf-8"?><soap:Envelope
xmlns:soap="http://schemas.
xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Header><soap12:Upgrad\
e xmln
s:soap12="http://www.w3.org/2003/05/soap-envelope"><soap12:SupportedEnve\
lope qna
me="soap:Envelope"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" /><soa
p12:SupportedEnvelope qname="soap12:Envelope"
xmlns:soap12="http://www.w3.org/20
03/05/soap-envelope"
/></soap12:Upgrade></soap:Header><soap:Body><soap:Fault><fa
ultcode>soap:VersionMismatch</faultcode><faultstring>Possible SOAP
version misma
tch: Envelope namespace http://schemas.xmlsoap.org/wsdl/soap/ was
unexpected. Ex
pecting http://schemas.xmlsoap.org/soap/envelope/.</faultstring><detail
/></soap
:Fault></soap:Body></soap:Envelope>

Press any key to continue . . .

I'm trying to get SOAP::Lite to work with our Verisign Managed DNS
product, but I'm having some difficulties in defining the soap objects
and wanted to know if I could get a small crash course on building and
reading the SOAP messages and replies.

The WSDL that I am using is here:
https://api.verisigndns.com/dnsa-ws/V2.0/dnsaapi?wsdl

The API is naturally:
https://api.verisigndns.com

At the top I'm defining:
use SOAP::Lite +autodispatch =>
        uri     => 'https://api.verisigndns.com/dnsa-ws/V2.0/dnsaapi?wsdl',
        proxy   => 'https://api.verisigndns.com';

and my attempted call for 'getCustomerList' is:
my $soap = SOAP::Lite->call(
        SOAP::Header->name('authInfo'),
        SOAP::Header->name('userToken'),
        SOAP::Header->name('userName','<username>'),
        SOAP::Header->name('password','<password>'),
        SOAP::Data->name('getCustomerList')
        );

doing 'print $soap;' prints the number 1; not sure if this is success
or not... because I don't see the related output per a python script
that I had. Also 'print $soap->result;' prints nothing...

Is there a way that I can display the soap envelope before I fire it
off to the API? and then decode/print the response? I'm trying to
search for this but I'm at a loss.

Naturally they have a very expansive API, so I have to write lots of
containers to utilize this, but if I can define the functions to build
my SOAPs then great, but I just can't see the data structures via my
normal methods. Help?

~Brian

Hi Brian,

> The WSDL that I am using is here:
> https://api.verisigndns.com/dnsa-ws/V2.0/dnsaapi?wsdl
>
> The API is naturally:
> https://api.verisigndns.com
>
> At the top I'm defining:
> use SOAP::Lite +autodispatch =>
>        uri     => 'https://api.verisigndns.com/dnsa-ws/V2.0/dnsaapi?wsdl',
>        proxy   => 'https://api.verisigndns.com';
>
> and my attempted call for 'getCustomerList' is:
> my $soap = SOAP::Lite->call(
>        SOAP::Header->name('authInfo'),
>        SOAP::Header->name('userToken'),
>        SOAP::Header->name('userName','<username>'),
>        SOAP::Header->name('password','<password>'),
>        SOAP::Data->name('getCustomerList')
>        );
>

The wsdl you refer to does not contain a specification of the contents of a
"authInfo" element.
I suppose, the expected header-structure is something like:

<authInfo>
   <userToken>
     <userName>name</userName>
    <password>pWpW</password>
  </userToken>
</authInfo

i.e. authInfo is of complex type.
You might find an idea how to create such header data in:

http://www.wlp-systems.de/soap-lite-and-ws-security.html

> Is there a way that I can display the soap envelope before I fire it off
to the
> API? and then decode/print the response? I'm trying to search for this but
I'm
> at a loss.

There are some way, the simplest one:
use SOAP::Lite (+trace => [qw(transport debug parameters)]);

HTH,
Martin

Hi,

I'm new to SOAPLite and am struggling to solve this problem; hopefully, someone
more knowledgeable can help me get past this.

Using this small program, I'm trying to establish an SSL Client-Authenticated
session to request a web-service:

--------------------
#!perl -w

   use SOAP::Lite +trace;

   $ENV{HTTPS_CA_FILE}   = "certs/my-ca.pem";
   $ENV{HTTPS_CERT_FILE} = "certs/client-cert.pem";
   $ENV{HTTPS_KEY_FILE}  = "certs/client-pvkey.pem";
   $ENV{HTTPS_CERT_PASS} = "ejbca";
   $ENV{HTTPS_DEBUG} = 1;

   print SOAP::Lite
     -> uri('http://ws.protocol.core.ejbca.org')
     -> proxy('https://atlas.mysite.com:8443/ejbca/ejbcaws/ejbcaws')
     -> getAvailableCAs()
     -> result;
--------------------

It consistently fails.  The error in the trace is summarized below:

***************
Client-Warning: Internal response

Can't connect to atlas.mysite.com:8443

LWP::Protocol::https::Socket: SSL connect attempt failed because of handshake
problems error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
at /home/anoor/perl/lib/perl5/LWP/Protocol/http.pm line 51.
***************

More data-points:

- I'm using all current versions of the required modules;

- There is no proxy involved;

- openssl s_client works perfectly with the certs/keys/CA files
   shown in the perl program; I am able to connect and request a
   page from the site;

- The net-ssl-test script from the Crypt-SSLeay-0.58 module is also
   able to connect with the above-mentioned certs/key;

- The web-service is definitely working because I am able to verify
   that the service returns a response when tested with SOAPUI;

- The client, server and CA certificates are all using the
   RSAwithSHA256 algorithm for the CA's signature (not sure if this
   is relevant; from what I understand SOAPLite ultimately relies on
   the OpenSSL library for the crypto work, so it ought to work given
   that s_client does.

What am I missing here?  Thanks, in advance, for your suggestions.

Arshad

Thanks to Mark Allen on the LWP mailing list, the answer can be found here:

http://www.mail-archive.com/libwww@perl.org/msg06964.html

(In case that link doesn't work for any reason, the brief answer is: I had to
include "use Net::SSL;" in my Perl program to make it work.  Apparently, the
newer LWP module uses the IO::Socket::SSL module instead of the older Net::SSL,
which ignores the environment variables in the program pointing to my digital
certificates.  By forcing the program to use Net::SSL, it picks up the variables
and works fine).

Arshad

--- In soaplite@yahoogroups.com, "noorarshad" <arshad@...> wrote:
>
> Hi,
>
> I'm new to SOAPLite and am struggling to solve this problem; hopefully,
someone more knowledgeable can help me get past this.
>
> Using this small program, I'm trying to establish an SSL Client-Authenticated
session to request a web-service:
>
> --------------------
> #!perl -w
>
>   use SOAP::Lite +trace;
>
>   $ENV{HTTPS_CA_FILE}   = "certs/my-ca.pem";
>   $ENV{HTTPS_CERT_FILE} = "certs/client-cert.pem";
>   $ENV{HTTPS_KEY_FILE}  = "certs/client-pvkey.pem";
>   $ENV{HTTPS_CERT_PASS} = "ejbca";
>   $ENV{HTTPS_DEBUG} = 1;
>
>   print SOAP::Lite
>     -> uri('http://ws.protocol.core.ejbca.org')
>     -> proxy('https://atlas.mysite.com:8443/ejbca/ejbcaws/ejbcaws')
>     -> getAvailableCAs()
>     -> result;
> --------------------
>
> It consistently fails.  The error in the trace is summarized below:
>
> ***************
> Client-Warning: Internal response
>
> Can't connect to atlas.mysite.com:8443
>
> LWP::Protocol::https::Socket: SSL connect attempt failed because of handshake
problems error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
at /home/anoor/perl/lib/perl5/LWP/Protocol/http.pm line 51.
> ***************
>
> More data-points:
>
> - I'm using all current versions of the required modules;
>
> - There is no proxy involved;
>
> - openssl s_client works perfectly with the certs/keys/CA files
>   shown in the perl program; I am able to connect and request a
>   page from the site;
>
> - The net-ssl-test script from the Crypt-SSLeay-0.58 module is also
>   able to connect with the above-mentioned certs/key;
>
> - The web-service is definitely working because I am able to verify
>   that the service returns a response when tested with SOAPUI;
>
> - The client, server and CA certificates are all using the
>   RSAwithSHA256 algorithm for the CA's signature (not sure if this
>   is relevant; from what I understand SOAPLite ultimately relies on
>   the OpenSSL library for the crypto work, so it ought to work given
>   that s_client does.
>
> What am I missing here?  Thanks, in advance, for your suggestions.
>
> Arshad
>

I've taken over some code for my company and need some help.  We have a soap
lite script which is called from another module.  The calling module contains
the following:

     $self->{path} = '/TktServices/services/TicketSoapHttpPort';
     $self->{method_name} = 'getTicketRequest';
     $self->{method_attr} = {
       "xmlns"=> 'http://xxxx.xxx.com/ticket/v1' }

This in turns calls the underlying module containing the soap calls.
There is an entry in the module that issues this:

my $data = SOAP::Data->name($self->{method_name})->attr($self->{method_attr});


And then he enters the data and parameters in this way:

   $self->{request} = $soap->serializer->envelope(method => $data, @params);

I need to add several namespaces to the envelope in order to get this to work. 
However am I using the correct command.  Is there a way to add it to the
serializer->envelope above.

$soap->serializer->namespaces({
      
"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.x\
sd"=>"xmlns:m2",
       "http://xxxx.xxx.com/ticket/v1"=>"xmlns:q0",
       "http://xxx.xxx.com/commonheader/v3"=>"xmlns:q1",
       "http://xxxxxxx.xxxx.xxx.com/ticket"=>"xmlns:q2",
});

Cause when I run the script I don't see these namespaces in the envelope.

Also there is this entry in the header:

<soapenv:Header>

<m2:Security
xmlns:m2="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-sec\
ext-1.0.xsd">


Questions:

1) Can I add this namespace to the header?
2) Is there a difference between adding the namespace to the envelope versus the
header?
3) If I were to be successful on adding the namespaces do i need to add the attr
to this header name or does the namespace take care of it:

  
("m2:Security")->attr({'xmlns:m2'=>'http://docs.oasis-open.org/wss/2004/01/oasis\
-200401-wss-wssecurity-secext-1.0.xsd'})


Please help.

I am running several perl scripts using SOAP::Lite and I need to capture if we
receive an error, specifically a '500 Internal Server Error'.  Is there a
variable within the soap structure where I can check for this error?  I capture
the output in my

       $self->{content} = $soap->call($data => @params);

call but that doesn't include the SOAP::Transport::HTTP::Client::send_receive:
error.