Menu
▾
▴
soaplite-devel — SOAP::Lite developers
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(7) |
Dec
(5) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
|
Feb
|
Mar
(1) |
Apr
(23) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
|
Dec
(2) |
| 2005 |
Jan
(2) |
Feb
|
Mar
|
Apr
(1) |
May
(6) |
Jun
(4) |
Jul
(4) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(4) |
| 2006 |
Jan
(1) |
Feb
(6) |
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
(1) |
Aug
(4) |
Sep
(4) |
Oct
(4) |
Nov
(6) |
Dec
(3) |
| 2007 |
Jan
(1) |
Feb
(6) |
Mar
|
Apr
(2) |
May
(1) |
Jun
(1) |
Jul
(2) |
Aug
|
Sep
(12) |
Oct
(19) |
Nov
(7) |
Dec
(7) |
| 2008 |
Jan
(14) |
Feb
(27) |
Mar
(23) |
Apr
(5) |
May
|
Jun
(1) |
Jul
|
Aug
(9) |
Sep
(22) |
Oct
|
Nov
(5) |
Dec
(7) |
| 2009 |
Jan
|
Feb
(3) |
Mar
(1) |
Apr
(3) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
(8) |
Mar
|
Apr
(1) |
May
|
Jun
(5) |
Jul
(4) |
Aug
(2) |
Sep
(5) |
Oct
(1) |
Nov
(2) |
Dec
(2) |
| 2011 |
Jan
(1) |
Feb
(1) |
Mar
(3) |
Apr
|
May
(7) |
Jun
(3) |
Jul
(8) |
Aug
(9) |
Sep
(5) |
Oct
(4) |
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(5) |
May
|
Jun
|
Jul
(1) |
Aug
(2) |
Sep
(6) |
Oct
(20) |
Nov
(15) |
Dec
(11) |
| 2013 |
Jan
(1) |
Feb
(40) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Jason S. <jas...@gm...> - 2008-09-10 14:32:29
|
Hey Soapers,
Here is a message I just posted to the MOBY group.
questions:
1) Why does SOAP::SOM::match() discard all the attributes on internal
XML elements? Isn't this a bug?
2) Why doesn't the SOM class have a method like document() that
returns the XML payload of the soap:Body tag? This seems important for
easy implementation of document/literal encoding.
Cheers, jas.
---------- Forwarded message ----------
From: Jason Stewart <jas...@gm...>
Date: Wed, Sep 10, 2008 at 7:58 PM
Subject: More info on SOAP::Lite document/literal
To: Core developer announcements <mob...@li...>
Hey Eddie,
So I dug a bit on the server side and this is what I found.
If your server class subclasses from SOAP::Server::Parameters, the
method will get an extra parameter of type SOAP::SOM which gives
access to all the request information. That object contains a lot of
methods for searching the soap envelope - but it converts all the data
it finds into a SOAP::Data instance - which throws away all attributes
not located at the root of the data being returned. For example if the
XML looked like this:
<soap:Body>
<q0:sayHello xmlns="urn:HelloWorld#">
<name>Joe Blow</name>
<givenName middlename="Windy">Joe</givenName>
</q0:sayHello>
</soap:Body>
and we did a query like $root = $som->dataof('//Body'), then $root
would be the soap:Body and we would see all of the sub-elements but
not their attributes. Only if we do $gn = $som->dataof('//givenName')
do we actually get the givenName element with the middlename attribute
still intact.
But the $som object has all the information in an internal hash table
- both as a hash table representation of the entire message and the
HTTP::Request object with the original XML.
What I don't understand is why when the dataof() method traverses the
internal hash table structure it throws away all the attributes not on
the root element being returned.
Also, I don't understand why there isn't a method that just returns
the content of the soap:Body element as plain XML - this should be the
default behavior for document/literal. I would like to see a call
something like $xml = $som->document();
Any thoughts of how I could make this interface most useful for MOBY
purposes? I will have to alter the internal SOAP::Lite code, and send
the patches to the maintainers.
Cheers, jas.
|
|
From: Peter C. <pfc...@ho...> - 2008-09-09 18:24:16
|
I¹ve been using SOAP::Lite 0.60a quite extensively over the past several years, and when I finally updated to .71, I ran into an issue with utf-8 encoded characters getting double-encoded. Rolling back to 0.60a corrected the problem. Has anyone else seen this issue or know what might have caused it? |
|
From: Robbie B. <rob...@gm...> - 2008-09-09 08:05:32
|
2008/9/8 Jason Stewart <jas...@gm...>: > Hey Soapers, > > I'm trying to get a grip on the claims of SOAP::Lite supporting > document/literal. I have a contract that will pay me to implement full > doc/literal support in S::L - but I just need to figure out what is > there, what is working, what isn't, and what needs to get done. > Hi Jason I had similar problems use S::L as a client connecting to a .NET doc/lit service. I can't quite remember the ins and outs, but here's some notes I made along the way: http://www.robbiebow.co.uk/blog/2008/03/soaplite-client-for-documentli.html I very much doubt this will be the answer for you but it might help. I'm trying to build up a cookbook for SOAP::Lite so if you come up with anything you think could be useful do let me know and we can add it there ;) Regards |
|
From: Jason S. <jas...@gm...> - 2008-09-08 15:58:50
|
Hey Soapers,
I'm trying to get a grip on the claims of SOAP::Lite supporting
document/literal. I have a contract that will pay me to implement full
doc/literal support in S::L - but I just need to figure out what is
there, what is working, what isn't, and what needs to get done.
I just wrote a message to the developers of the MOBY project - heavy
consumers of S::L - and got this response.
Martin, do you or anyone else have a response to Eddies problem of how
to include attributes in the output message?
Cheers, jas.
---------- Forwarded message ----------
From: Edward Kawas <edw...@gm...>
Date: Mon, Sep 8, 2008 at 8:46 PM
Subject: Re: [MOBY-dev] SOAP::Lite claims support for document/literal
To: Core developer announcements <mob...@li...>
Hi Jason,
One of the problems that I have with soap lite and trying to perform doc/lit
requests/responses is the inability to use attributes in the request.
Since that statement doesn't make too much sense (to some it might have ;-),
I will provide an example:
I modified the wsdl that you sent to include an attribute in the givenName
element, so that a request now looks like:
<q0:sayHello>
<name>Joe Blow</name>
<givenName middlename="Windy">Joe</givenName>
</q0:sayHello>
The server side code is simply:
sub sayHello {
SOAP::Data->name('sayHelloResult')->value( Dumper(\@_) );
}
So all that I am doing is dumping whatever is sent to the server.
The response is
<sayHelloResponse xmlns="urn:HelloWorld">
<sayHelloResult xsi:type="xsd:string">$VAR1 = [ 'HelloWorld', 'Joe Blow',
'Joe' ];</sayHelloResult>
</sayHelloResponse>
I do believe that this is one of the biggest stumbling blocks so far.
Because numerous Moby api calls use attributes. One such example is the
retrieveService call.
My dispatcher code is below!
Eddie
------ CODE START -----
#!/usr/bin/perl -w
# _________________________________________________________________
use SOAP::Transport::HTTP;
if ($ENV{REQUEST_METHOD} eq "GET") {
if (lc($ENV{QUERY_STRING} || "") eq "wsdl") {
require CGI;
my $q = CGI->new();
my $wsdl = HelloWorld::wsdl();
my $c = length($wsdl);
print $q->header(-type=>'application/xml',-Content-length=>$c);
print "$wsdl";
}
} else {
my $x = new SOAP::Transport::HTTP::CGI;
$x->dispatch_to('/var/www/cgi-bin', 'HelloWorld');
$x->handle;
}
package HelloWorld;
use Data::Dumper;
sub sayHello {
SOAP::Data->name('sayHelloResult')->value( Dumper(\@_) );
}
sub wsdl {
return <<EOF;
<?xml version="1.0" encoding="UTF-8" ?>
<definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="urn:HelloWorld"
targetNamespace="urn:HelloWorld"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
<s:schema targetNamespace="urn:HelloWorld">
<s:element name="sayHello">
<s:complexType>
<s:sequence>
<s:element minOccurs="0"
maxOccurs="1"
name="name"
type="s:string" />
<s:element minOccurs="0"
maxOccurs="1"
name="givenName"
nillable="1">
<s:complexType>
<s:simpleContent>
<s:extension base="s:string">
<s:attribute name="middlename"
use="required" type="s:string">
</s:attribute>
</s:extension>
</s:simpleContent>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="sayHelloResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0"
maxOccurs="1"
name="sayHelloResult" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</types>
<message name="sayHelloSoapIn">
<part name="parameters" element="s0:sayHello" />
</message>
<message name="sayHelloSoapOut">
<part name="parameters" element="s0:sayHelloResponse" />
</message>
<portType name="Service1Soap">
<operation name="sayHello">
<input message="s0:sayHelloSoapIn" />
<output message="s0:sayHelloSoapOut" />
</operation>
</portType>
<binding name="Service1Soap" type="s0:Service1Soap">
<soap:binding
transport="http://schemas.xmlsoap.org/soap/http"
style="document" />
<operation name="sayHello">
<soap:operation soapAction="urn:HelloWorld#sayHello"
/>
<input>
<soap:body use="literal" />
</input>
<output>
<soap:body use="literal" />
</output>
</operation>
</binding>
<service name="HelloWorld">
<port name="HelloWorldSoap" binding="s0:Service1Soap">
<soap:address
location="http://ubuntu.localhost/cgi-bin/doc-lit.pl" />
</port>
</service>
</definitions>
EOF
}
1;
------ CODE END ------
-----Original Message-----
From: mob...@li...
[mailto:mob...@li...] On Behalf Of Jason Stewart
Sent: September-08-08 4:07 AM
To: Core developer announcements
Subject: [MOBY-dev] SOAP::Lite claims support for document/literal
Hey Moby-devs,
The version of SOAP::Lite in CVS claims to support Document/literal
encoding - I need help determing if this support is sufficient. Can
you look this over?
=head3 DOCUMENT/LITERAL
SOAP web services using the document/literal message encoding are usually
described by some Web Service Definition. Our web service has the following
WSDL description:
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns:s0="urn:HelloWorld"
targetNamespace="urn:HelloWorld"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
<s:schema targetNamespace="urn:HelloWorld">
<s:element name="sayHello">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="name"
type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="givenName"
type="s:string" nillable="1" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="sayHelloResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1"
name="sayHelloResult" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</types>
<message name="sayHelloSoapIn">
<part name="parameters" element="s0:sayHello" />
</message>
<message name="sayHelloSoapOut">
<part name="parameters" element="s0:sayHelloResponse" />
</message>
<portType name="Service1Soap">
<operation name="sayHello">
<input message="s0:sayHelloSoapIn" />
<output message="s0:sayHelloSoapOut" />
</operation>
</portType>
<binding name="Service1Soap" type="s0:Service1Soap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"
style="document" />
<operation name="sayHello">
<soap:operation soapAction="urn:HelloWorld#sayHello"/>
<input>
<soap:body use="literal" />
</input>
<output>
<soap:body use="literal" />
</output>
</operation>
</binding>
<service name="HelloWorld">
<port name="HelloWorldSoap" binding="s0:Service1Soap">
<soap:address location="http://localhost:80//helloworld.pl" />
</port>
</service>
</definitions>
The XML message (inside the SOAP Envelope) look like this:
<sayHello xmlns="urn:HelloWorld">
<name>Kutter</name>
<givenName>Martin</givenName>
</sayHello>
<sayHelloResponse>
<sayHelloResult>Hello Martin Kutter!</sayHelloResult>
</sayHelloResponse>
You can call this web service with the following client code:
use SOAP::Lite;
my $soap = SOAP::Lite->new( proxy => 'http://localhost:80/helloworld.pl');
$soap->on_action( sub { "urn:HelloWorld#sayHello" });
$soap->autotype(0);
$soap->default_ns('urn:HelloWorld');
my $som = $soap->call("sayHello",
SOAP::Data->name('name')->value( 'Kutter' ),
SOAP::Data->name('givenName')->value('Martin'),
);
die $som->fault->{ faultstring } if ($som->fault);
print $som->result, "\n";
=head2 Differences between the implementations
You may have noticed that there's no between the rpc/literal
and the document/literal example's implementation. In fact, from
SOAP::Lite's
point of view, the only differences between rpc/literal and document/literal
that parameters are always named.
In our example, the rpc/literal variant already used named parameters (by
using a single complexType only as positional parameter), so there's no
difference at all.
The differences would have been bigger if the rpc/literal example had used
more than one positional parameter, but this is quite unlikely to happen in
the future: Current interoperability standards (like the WS-I basic profile)
mandate the use of a single complexType as only parameter in rpc/literal
calls.
-- snip --
Help me on this one - is this valid? Is it sufficient for what MOBY
and the rest of the Perl world needs? I suggest that I test this claim
against:
* perl SOAP::Lite client = axis Java server
* java client = perl SOAP::Lite server
I could use some suggestions for how to make these tests useful.
Cheers, jas.
_______________________________________________
MOBY-dev mailing list
MOB...@li...
http://lists.open-bio.org/mailman/listinfo/moby-dev
_______________________________________________
MOBY-dev mailing list
MOB...@li...
http://lists.open-bio.org/mailman/listinfo/moby-dev
|
|
From: Bob D. <bob...@ya...> - 2008-08-20 15:39:17
|
gsoap's discussion of MIME support is here http://www.cs.fsu.edu/~engelen/soapdoc2.html#tth_sEc13.2 Also, I should note that I hacked MIME::Entity to remove that multipart MIME message, and gsoap no longer gave the error about no XML element tag. So I'm pretty sure that's not supposed to be in there in the absence of any sort of XML around it. But after this hack, gsoap and SOAP::Lite just sat there indefinitly, and when I canceled it, it said: SOAP 1.1 fault: SOAP-ENV:Client [no subcode] "End of file or no input: An established connection was aborted by the software in your host machine." So now I'm wondering if SOAP::Lite is terminating the connection properly on its side (since I'm not getting any response back from the server, unless I cancel it) Thanks for everyone's help. Bob --- On Wed, 8/20/08, Paul Kulchenko <pau...@ya...> wrote: From: Paul Kulchenko <pau...@ya...> Subject: Re: [Soaplite-devel] [Fwd: SOAP with Attachments not supported?] To: "Martin Kutter" <mar...@fe...>, "Robbie Bow" <rob...@gm...> Cc: "soaplite-devel" <soa...@li...>, bob...@ya... Date: Wednesday, August 20, 2008, 2:44 PM I don't see anything wrong on the S::L side. Bob, do you know if gSOAP supports MIME? "Supports single/multipart MIME attachment (parsing side only)." This used to be the case, but since then Byrne added MIME support for generated messages too. The description needs to be updated. Paul. --- On Tue, 8/19/08, Robbie Bow <rob...@gm...> wrote: > From: Robbie Bow <rob...@gm...> > Subject: Re: [Soaplite-devel] [Fwd: SOAP with Attachments not supported?] > To: "Martin Kutter" <mar...@fe...> > Cc: "soaplite-devel" <soa...@li...>, bob...@ya... > Date: Tuesday, August 19, 2008, 3:25 PM > Sorry, I'm afraid I don't. I did once look at > getting the MIME tests working > but really didn't know what I was doing :( > > 2008/8/19 Martin Kutter <mar...@fe...> > > > Hi, > > > > does someone know why this call fails? > > > > Unfortunately, I'm not a MIME expert. > > > > Martin > > > > -------- Weitergeleitete Nachricht -------- > > > Von: Bob Dole > <bob...@ya...> > > > Antwort an: bob...@ya... > > > An: kut...@us... > > > Betreff: SOAP with Attachments not supported? > > > Datum: Mon, 18 Aug 2008 12:50:07 -0700 (PDT) > > > > > > Quick prefix which could make it so that you > don't have to answer the > > > long question: does "Supports > single/multipart MIME attachment > > > (parsing side only)." mean that a SOAP::Lite > client can't send SwA? > > > > > > The longer question is why the following > doesn't work. I have a > > > SOAP::Lite client and a gSOAP server. I want to > send a MIME file from > > > one to the other. > > > > > > Here's the message I sent to the gSOAP list: > > > > ------------------------------------------------------ > > > > > > I am trying to send a MIME encoded file from a > SOAP::Lite client to a > > > gSOAP server, but the server is giving me the > following error which I > > > don't understand, since I'm not that > experienced with SOAP: > > > Error 6 fault: SOAP-ENV:Client [no subcode] > > > "No XML element tag" > > > Detail: [no detail] > > > The following is the command I run (I include the > source at the end > > > incase the raw messages don't show an obvious > error) > > > $ ./MIMEsend.pl soapcpp2.exe > > > Calling client setup > > > SOAP::Transport::new: () > > > SOAP::Serializer::new: () > > > SOAP::Deserializer::new: () > > > SOAP::Parser::new: () > > > SOAP::Lite::new: () > > > SOAP::Transport::HTTP::Client::new: () > > > Calling sendMIME > > > SOAP::Data::new: () > > > SOAP::Lite::call: () > > > SOAP::Serializer::envelope: () > > > SOAP::Serializer::envelope: sendMIME > SOAP::Data=HASH(0x1075d488) > > > SOAP::Data::new: () > > > SOAP::Data::new: () > > > SOAP::Data::new: () > > > SOAP::Data::new: () > > > SOAP::Data::new: () > > > SOAP::Transport::HTTP::Client::send_receive: > HTTP::Request=HASH > > > (0x1060ece8) > > > SOAP::Transport::HTTP::Client::send_receive: POST > > > http://192.168.0.131:1234/ HTTP/1.1 > > > Accept: text/xml > > > Accept: multipart/* > > > Accept: application/soap > > > Content-Length: 600620 > > > Content-Type: Multipart/Related; > type="text/xml"; > > > start="<main_envelope>"; > boundary="----------=_1219045514-2988-0"; cha > > > rset=utf-8 > > > SOAPAction: "capture#sendMIME" > > > This is a multi-part message in MIME format... > > > ------------=_1219045514-2988-0 > > > Content-Type: text/xml > > > Content-Disposition: inline > > > Content-Location: /main_envelope > > > Content-ID: <main_envelope> > > > <?xml version="1.0" > encoding="UTF-8"?><SOAP-ENV:Envelope > > > xmlns:namesp1="capture" > xmlns:SOAP-ENV="http://schemas.xmlsoap. > > > org/soap/envelope/" > > > > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" > > > xmlns:xsi="http://www.w3.org/2001/XMLSchem > > > a-instance" > xmlns:xsd="http://www.w3.org/2001/XMLSchema" SOAP- > > > > ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encodin > > > > g/"><SOAP-ENV:Body><namesp1:sendMIME><magicNumber > > > > xsi:type="xsd:int">123</magicNumber></namesp1:sendMIME></SOAP-ENV:Body > > > ></SOAP-ENV:Envelope> > > > ------------=_1219045514-2988-0 > > > Content-Type: application/exe; > name="soapcpp2.exe" > > > Content-Disposition: attachment; > filename="soapcpp2.exe" > > > Content-Transfer-Encoding: base64 > > > MIME-Version: 1.0 > > > X-Mailer: MIME-tools 5.427 (Entity 5.427) > > > > TVqQAAMAAAAEAAAA//8AALgAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAA > > > ...MIME FILE... > > > TkdQQURESU5HWFhQQURESU5H > > > ------------=_1219045514-2988-0-- > > > SOAP::Transport::HTTP::Client::send_receive: > HTTP::Response=HASH > > > (0x1076f8c8) > > > SOAP::Transport::HTTP::Client::send_receive: 500 > read failed: > > > Connection reset by peer > > > Content-Type: text/plain > > > Client-Date: Mon, 18 Aug 2008 07:45:28 GMT > > > Client-Warning: Internal response > > > 500 read failed: Connection reset by peer > > > SOAP::Deserializer::deserialize: () > > > SOAP::Parser::decode: () > > > 500 read failed: Connection reset by peer at > ./MIMEsend.pl line 23 > > > SOAP::Transport::HTTP::Client::DESTROY: () > > > SOAP::Data::DESTROY: () > > > SOAP::Data::DESTROY: () > > > SOAP::Data::DESTROY: () > > > SOAP::Parser::DESTROY: () > > > SOAP::Transport::DESTROY: () > > > SOAP::Serializer::DESTROY: () > > > SOAP::Data::DESTROY: () > > > SOAP::Data::DESTROY: () > > > SOAP::Deserializer::DESTROY: () > > > SOAP::Data::DESTROY: () > > > SOAP::Lite::DESTROY: () > > > > > > > > > So my first question would be, is it because of > the "This is a multi- > > > part message in MIME format..."? Is that the > thing missing the XML > > > element it's talking about? Because > that's the only thing I can see > > > that seems to differ from the SwA spec. > > > > > > So for the record, my gSOAP code looks like this > (basically just the > > > example code from the documentation): > > > > > > int ns__sendMIME(struct soap *soap, int > magicNumber, int &result){ > > > struct soap_multipart * attachment; > > > for(attachment = soap->mime.list; attachment; > attachment = > > > attachment->next){ > > > printf("MIME attachment:\n"); > > > printf("Memory=%p\n", > (*attachment).ptr); > > > printf("Size=%ul\n", > (*attachment).size); > > > printf("Encoding=%d\n", > (int)(*attachment).encoding); > > > printf("Type=%s\n", > (*attachment).type? > > > (*attachment).type:"null"); > > > printf("ID=%s\n", > (*attachment).id? > > > (*attachment).id:"null"); > > > printf("Location=%s\n", > (*attachment).location? > > > (*attachment).location:"null"); > > > printf("Description=%s\n", > (*attachment).description? > > > (*attachment).description:"null"); > > > } > > > printf("magicNumber = %#x\n", > magicNumber); > > > if(magicNumber == 123){ > > > result = 42; > > > } > > > else{ > > > result = 0; > > > } > > > return SOAP_OK; > > > } > > > > > > My SOAP::Lite code looks like this: > > > > > > #!perl > > > use SOAP::Lite +trace => 'all'; > > > #use SOAP::Lite; > > > use SOAP::Lite::Packager; > > > use MIME::Entity; > > > my $ent = build MIME::Entity > > > Type => > "application/exe", > > > Path => $ARGV[0], > > > Filename => $ARGV[0], > > > Disposition => "attachment"; > > > print "\nCalling client > setup\n\n"; > > > $client = SOAP::Lite > > > -> > packager(SOAP::Lite::Packager::MIME->new) > > > -> parts([$ent]) > > > -> > proxy('http://192.168.0.131:1234/') > > > -> ns('capture'); > > > print "\nCalling > sendMIME\n\n"; > > > $data = SOAP::Data->name(magicNumber => > "123"); > > > $result = $client->sendMIME($data); > > > #print "result = $result\n"; > > > > > > Thanks for any help you can give! > > > > > > Bob > > > > > > > > > > ------------------------------------------------------------------------- > > This SF.Net email is sponsored by the Moblin Your Move > Developer's > > challenge > > Build the coolest Linux based applications with Moblin > SDK & win great > > prizes > > Grand prize is a trip for two to an Open Source event > anywhere in the world > > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > _______________________________________________ > > Soaplite-devel mailing list > > Soa...@li... > > > https://lists.sourceforge.net/lists/listinfo/soaplite-devel > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move > Developer's challenge > Build the coolest Linux based applications with Moblin SDK > & win great prizes > Grand prize is a trip for two to an Open Source event > anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________ > Soaplite-devel mailing list > Soa...@li... > https://lists.sourceforge.net/lists/listinfo/soaplite-devel |
|
From: Paul K. <pau...@ya...> - 2008-08-20 14:44:12
|
I don't see anything wrong on the S::L side. Bob, do you know if gSOAP supports MIME? "Supports single/multipart MIME attachment (parsing side only)." This used to be the case, but since then Byrne added MIME support for generated messages too. The description needs to be updated. Paul. --- On Tue, 8/19/08, Robbie Bow <rob...@gm...> wrote: > From: Robbie Bow <rob...@gm...> > Subject: Re: [Soaplite-devel] [Fwd: SOAP with Attachments not supported?] > To: "Martin Kutter" <mar...@fe...> > Cc: "soaplite-devel" <soa...@li...>, bob...@ya... > Date: Tuesday, August 19, 2008, 3:25 PM > Sorry, I'm afraid I don't. I did once look at > getting the MIME tests working > but really didn't know what I was doing :( > > 2008/8/19 Martin Kutter <mar...@fe...> > > > Hi, > > > > does someone know why this call fails? > > > > Unfortunately, I'm not a MIME expert. > > > > Martin > > > > -------- Weitergeleitete Nachricht -------- > > > Von: Bob Dole > <bob...@ya...> > > > Antwort an: bob...@ya... > > > An: kut...@us... > > > Betreff: SOAP with Attachments not supported? > > > Datum: Mon, 18 Aug 2008 12:50:07 -0700 (PDT) > > > > > > Quick prefix which could make it so that you > don't have to answer the > > > long question: does "Supports > single/multipart MIME attachment > > > (parsing side only)." mean that a SOAP::Lite > client can't send SwA? > > > > > > The longer question is why the following > doesn't work. I have a > > > SOAP::Lite client and a gSOAP server. I want to > send a MIME file from > > > one to the other. > > > > > > Here's the message I sent to the gSOAP list: > > > > ------------------------------------------------------ > > > > > > I am trying to send a MIME encoded file from a > SOAP::Lite client to a > > > gSOAP server, but the server is giving me the > following error which I > > > don't understand, since I'm not that > experienced with SOAP: > > > Error 6 fault: SOAP-ENV:Client [no subcode] > > > "No XML element tag" > > > Detail: [no detail] > > > The following is the command I run (I include the > source at the end > > > incase the raw messages don't show an obvious > error) > > > $ ./MIMEsend.pl soapcpp2.exe > > > Calling client setup > > > SOAP::Transport::new: () > > > SOAP::Serializer::new: () > > > SOAP::Deserializer::new: () > > > SOAP::Parser::new: () > > > SOAP::Lite::new: () > > > SOAP::Transport::HTTP::Client::new: () > > > Calling sendMIME > > > SOAP::Data::new: () > > > SOAP::Lite::call: () > > > SOAP::Serializer::envelope: () > > > SOAP::Serializer::envelope: sendMIME > SOAP::Data=HASH(0x1075d488) > > > SOAP::Data::new: () > > > SOAP::Data::new: () > > > SOAP::Data::new: () > > > SOAP::Data::new: () > > > SOAP::Data::new: () > > > SOAP::Transport::HTTP::Client::send_receive: > HTTP::Request=HASH > > > (0x1060ece8) > > > SOAP::Transport::HTTP::Client::send_receive: POST > > > http://192.168.0.131:1234/ HTTP/1.1 > > > Accept: text/xml > > > Accept: multipart/* > > > Accept: application/soap > > > Content-Length: 600620 > > > Content-Type: Multipart/Related; > type="text/xml"; > > > start="<main_envelope>"; > boundary="----------=_1219045514-2988-0"; cha > > > rset=utf-8 > > > SOAPAction: "capture#sendMIME" > > > This is a multi-part message in MIME format... > > > ------------=_1219045514-2988-0 > > > Content-Type: text/xml > > > Content-Disposition: inline > > > Content-Location: /main_envelope > > > Content-ID: <main_envelope> > > > <?xml version="1.0" > encoding="UTF-8"?><SOAP-ENV:Envelope > > > xmlns:namesp1="capture" > xmlns:SOAP-ENV="http://schemas.xmlsoap. > > > org/soap/envelope/" > > > > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" > > > xmlns:xsi="http://www.w3.org/2001/XMLSchem > > > a-instance" > xmlns:xsd="http://www.w3.org/2001/XMLSchema" SOAP- > > > > ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encodin > > > > g/"><SOAP-ENV:Body><namesp1:sendMIME><magicNumber > > > > xsi:type="xsd:int">123</magicNumber></namesp1:sendMIME></SOAP-ENV:Body > > > ></SOAP-ENV:Envelope> > > > ------------=_1219045514-2988-0 > > > Content-Type: application/exe; > name="soapcpp2.exe" > > > Content-Disposition: attachment; > filename="soapcpp2.exe" > > > Content-Transfer-Encoding: base64 > > > MIME-Version: 1.0 > > > X-Mailer: MIME-tools 5.427 (Entity 5.427) > > > > TVqQAAMAAAAEAAAA//8AALgAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAA > > > ...MIME FILE... > > > TkdQQURESU5HWFhQQURESU5H > > > ------------=_1219045514-2988-0-- > > > SOAP::Transport::HTTP::Client::send_receive: > HTTP::Response=HASH > > > (0x1076f8c8) > > > SOAP::Transport::HTTP::Client::send_receive: 500 > read failed: > > > Connection reset by peer > > > Content-Type: text/plain > > > Client-Date: Mon, 18 Aug 2008 07:45:28 GMT > > > Client-Warning: Internal response > > > 500 read failed: Connection reset by peer > > > SOAP::Deserializer::deserialize: () > > > SOAP::Parser::decode: () > > > 500 read failed: Connection reset by peer at > ./MIMEsend.pl line 23 > > > SOAP::Transport::HTTP::Client::DESTROY: () > > > SOAP::Data::DESTROY: () > > > SOAP::Data::DESTROY: () > > > SOAP::Data::DESTROY: () > > > SOAP::Parser::DESTROY: () > > > SOAP::Transport::DESTROY: () > > > SOAP::Serializer::DESTROY: () > > > SOAP::Data::DESTROY: () > > > SOAP::Data::DESTROY: () > > > SOAP::Deserializer::DESTROY: () > > > SOAP::Data::DESTROY: () > > > SOAP::Lite::DESTROY: () > > > > > > > > > So my first question would be, is it because of > the "This is a multi- > > > part message in MIME format..."? Is that the > thing missing the XML > > > element it's talking about? Because > that's the only thing I can see > > > that seems to differ from the SwA spec. > > > > > > So for the record, my gSOAP code looks like this > (basically just the > > > example code from the documentation): > > > > > > int ns__sendMIME(struct soap *soap, int > magicNumber, int &result){ > > > struct soap_multipart * attachment; > > > for(attachment = soap->mime.list; attachment; > attachment = > > > attachment->next){ > > > printf("MIME attachment:\n"); > > > printf("Memory=%p\n", > (*attachment).ptr); > > > printf("Size=%ul\n", > (*attachment).size); > > > printf("Encoding=%d\n", > (int)(*attachment).encoding); > > > printf("Type=%s\n", > (*attachment).type? > > > (*attachment).type:"null"); > > > printf("ID=%s\n", > (*attachment).id? > > > (*attachment).id:"null"); > > > printf("Location=%s\n", > (*attachment).location? > > > (*attachment).location:"null"); > > > printf("Description=%s\n", > (*attachment).description? > > > (*attachment).description:"null"); > > > } > > > printf("magicNumber = %#x\n", > magicNumber); > > > if(magicNumber == 123){ > > > result = 42; > > > } > > > else{ > > > result = 0; > > > } > > > return SOAP_OK; > > > } > > > > > > My SOAP::Lite code looks like this: > > > > > > #!perl > > > use SOAP::Lite +trace => 'all'; > > > #use SOAP::Lite; > > > use SOAP::Lite::Packager; > > > use MIME::Entity; > > > my $ent = build MIME::Entity > > > Type => > "application/exe", > > > Path => $ARGV[0], > > > Filename => $ARGV[0], > > > Disposition => "attachment"; > > > print "\nCalling client > setup\n\n"; > > > $client = SOAP::Lite > > > -> > packager(SOAP::Lite::Packager::MIME->new) > > > -> parts([$ent]) > > > -> > proxy('http://192.168.0.131:1234/') > > > -> ns('capture'); > > > print "\nCalling > sendMIME\n\n"; > > > $data = SOAP::Data->name(magicNumber => > "123"); > > > $result = $client->sendMIME($data); > > > #print "result = $result\n"; > > > > > > Thanks for any help you can give! > > > > > > Bob > > > > > > > > > > ------------------------------------------------------------------------- > > This SF.Net email is sponsored by the Moblin Your Move > Developer's > > challenge > > Build the coolest Linux based applications with Moblin > SDK & win great > > prizes > > Grand prize is a trip for two to an Open Source event > anywhere in the world > > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > _______________________________________________ > > Soaplite-devel mailing list > > Soa...@li... > > > https://lists.sourceforge.net/lists/listinfo/soaplite-devel > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move > Developer's challenge > Build the coolest Linux based applications with Moblin SDK > & win great prizes > Grand prize is a trip for two to an Open Source event > anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________ > Soaplite-devel mailing list > Soa...@li... > https://lists.sourceforge.net/lists/listinfo/soaplite-devel |
|
From: Robbie B. <rob...@gm...> - 2008-08-19 20:25:17
|
Sorry, I'm afraid I don't. I did once look at getting the MIME tests working but really didn't know what I was doing :( 2008/8/19 Martin Kutter <mar...@fe...> > Hi, > > does someone know why this call fails? > > Unfortunately, I'm not a MIME expert. > > Martin > > -------- Weitergeleitete Nachricht -------- > > Von: Bob Dole <bob...@ya...> > > Antwort an: bob...@ya... > > An: kut...@us... > > Betreff: SOAP with Attachments not supported? > > Datum: Mon, 18 Aug 2008 12:50:07 -0700 (PDT) > > > > Quick prefix which could make it so that you don't have to answer the > > long question: does "Supports single/multipart MIME attachment > > (parsing side only)." mean that a SOAP::Lite client can't send SwA? > > > > The longer question is why the following doesn't work. I have a > > SOAP::Lite client and a gSOAP server. I want to send a MIME file from > > one to the other. > > > > Here's the message I sent to the gSOAP list: > > ------------------------------------------------------ > > > > I am trying to send a MIME encoded file from a SOAP::Lite client to a > > gSOAP server, but the server is giving me the following error which I > > don't understand, since I'm not that experienced with SOAP: > > Error 6 fault: SOAP-ENV:Client [no subcode] > > "No XML element tag" > > Detail: [no detail] > > The following is the command I run (I include the source at the end > > incase the raw messages don't show an obvious error) > > $ ./MIMEsend.pl soapcpp2.exe > > Calling client setup > > SOAP::Transport::new: () > > SOAP::Serializer::new: () > > SOAP::Deserializer::new: () > > SOAP::Parser::new: () > > SOAP::Lite::new: () > > SOAP::Transport::HTTP::Client::new: () > > Calling sendMIME > > SOAP::Data::new: () > > SOAP::Lite::call: () > > SOAP::Serializer::envelope: () > > SOAP::Serializer::envelope: sendMIME SOAP::Data=HASH(0x1075d488) > > SOAP::Data::new: () > > SOAP::Data::new: () > > SOAP::Data::new: () > > SOAP::Data::new: () > > SOAP::Data::new: () > > SOAP::Transport::HTTP::Client::send_receive: HTTP::Request=HASH > > (0x1060ece8) > > SOAP::Transport::HTTP::Client::send_receive: POST > > http://192.168.0.131:1234/ HTTP/1.1 > > Accept: text/xml > > Accept: multipart/* > > Accept: application/soap > > Content-Length: 600620 > > Content-Type: Multipart/Related; type="text/xml"; > > start="<main_envelope>"; boundary="----------=_1219045514-2988-0"; cha > > rset=utf-8 > > SOAPAction: "capture#sendMIME" > > This is a multi-part message in MIME format... > > ------------=_1219045514-2988-0 > > Content-Type: text/xml > > Content-Disposition: inline > > Content-Location: /main_envelope > > Content-ID: <main_envelope> > > <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope > > xmlns:namesp1="capture" xmlns:SOAP-ENV="http://schemas.xmlsoap. > > org/soap/envelope/" > > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" > > xmlns:xsi="http://www.w3.org/2001/XMLSchem > > a-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" SOAP- > > ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encodin > > g/"><SOAP-ENV:Body><namesp1:sendMIME><magicNumber > > xsi:type="xsd:int">123</magicNumber></namesp1:sendMIME></SOAP-ENV:Body > > ></SOAP-ENV:Envelope> > > ------------=_1219045514-2988-0 > > Content-Type: application/exe; name="soapcpp2.exe" > > Content-Disposition: attachment; filename="soapcpp2.exe" > > Content-Transfer-Encoding: base64 > > MIME-Version: 1.0 > > X-Mailer: MIME-tools 5.427 (Entity 5.427) > > TVqQAAMAAAAEAAAA//8AALgAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAA > > ...MIME FILE... > > TkdQQURESU5HWFhQQURESU5H > > ------------=_1219045514-2988-0-- > > SOAP::Transport::HTTP::Client::send_receive: HTTP::Response=HASH > > (0x1076f8c8) > > SOAP::Transport::HTTP::Client::send_receive: 500 read failed: > > Connection reset by peer > > Content-Type: text/plain > > Client-Date: Mon, 18 Aug 2008 07:45:28 GMT > > Client-Warning: Internal response > > 500 read failed: Connection reset by peer > > SOAP::Deserializer::deserialize: () > > SOAP::Parser::decode: () > > 500 read failed: Connection reset by peer at ./MIMEsend.pl line 23 > > SOAP::Transport::HTTP::Client::DESTROY: () > > SOAP::Data::DESTROY: () > > SOAP::Data::DESTROY: () > > SOAP::Data::DESTROY: () > > SOAP::Parser::DESTROY: () > > SOAP::Transport::DESTROY: () > > SOAP::Serializer::DESTROY: () > > SOAP::Data::DESTROY: () > > SOAP::Data::DESTROY: () > > SOAP::Deserializer::DESTROY: () > > SOAP::Data::DESTROY: () > > SOAP::Lite::DESTROY: () > > > > > > So my first question would be, is it because of the "This is a multi- > > part message in MIME format..."? Is that the thing missing the XML > > element it's talking about? Because that's the only thing I can see > > that seems to differ from the SwA spec. > > > > So for the record, my gSOAP code looks like this (basically just the > > example code from the documentation): > > > > int ns__sendMIME(struct soap *soap, int magicNumber, int &result){ > > struct soap_multipart * attachment; > > for(attachment = soap->mime.list; attachment; attachment = > > attachment->next){ > > printf("MIME attachment:\n"); > > printf("Memory=%p\n", (*attachment).ptr); > > printf("Size=%ul\n", (*attachment).size); > > printf("Encoding=%d\n", (int)(*attachment).encoding); > > printf("Type=%s\n", (*attachment).type? > > (*attachment).type:"null"); > > printf("ID=%s\n", (*attachment).id? > > (*attachment).id:"null"); > > printf("Location=%s\n", (*attachment).location? > > (*attachment).location:"null"); > > printf("Description=%s\n", (*attachment).description? > > (*attachment).description:"null"); > > } > > printf("magicNumber = %#x\n", magicNumber); > > if(magicNumber == 123){ > > result = 42; > > } > > else{ > > result = 0; > > } > > return SOAP_OK; > > } > > > > My SOAP::Lite code looks like this: > > > > #!perl > > use SOAP::Lite +trace => 'all'; > > #use SOAP::Lite; > > use SOAP::Lite::Packager; > > use MIME::Entity; > > my $ent = build MIME::Entity > > Type => "application/exe", > > Path => $ARGV[0], > > Filename => $ARGV[0], > > Disposition => "attachment"; > > print "\nCalling client setup\n\n"; > > $client = SOAP::Lite > > -> packager(SOAP::Lite::Packager::MIME->new) > > -> parts([$ent]) > > -> proxy('http://192.168.0.131:1234/') > > -> ns('capture'); > > print "\nCalling sendMIME\n\n"; > > $data = SOAP::Data->name(magicNumber => "123"); > > $result = $client->sendMIME($data); > > #print "result = $result\n"; > > > > Thanks for any help you can give! > > > > Bob > > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Soaplite-devel mailing list > Soa...@li... > https://lists.sourceforge.net/lists/listinfo/soaplite-devel > |
|
From: Martin K. <mar...@fe...> - 2008-08-19 19:15:09
|
Hi, does someone know why this call fails? Unfortunately, I'm not a MIME expert. Martin -------- Weitergeleitete Nachricht -------- > Von: Bob Dole <bob...@ya...> > Antwort an: bob...@ya... > An: kut...@us... > Betreff: SOAP with Attachments not supported? > Datum: Mon, 18 Aug 2008 12:50:07 -0700 (PDT) > > Quick prefix which could make it so that you don't have to answer the > long question: does "Supports single/multipart MIME attachment > (parsing side only)." mean that a SOAP::Lite client can't send SwA? > > The longer question is why the following doesn't work. I have a > SOAP::Lite client and a gSOAP server. I want to send a MIME file from > one to the other. > > Here's the message I sent to the gSOAP list: > ------------------------------------------------------ > > I am trying to send a MIME encoded file from a SOAP::Lite client to a > gSOAP server, but the server is giving me the following error which I > don't understand, since I'm not that experienced with SOAP: > Error 6 fault: SOAP-ENV:Client [no subcode] > "No XML element tag" > Detail: [no detail] > The following is the command I run (I include the source at the end > incase the raw messages don't show an obvious error) > $ ./MIMEsend.pl soapcpp2.exe > Calling client setup > SOAP::Transport::new: () > SOAP::Serializer::new: () > SOAP::Deserializer::new: () > SOAP::Parser::new: () > SOAP::Lite::new: () > SOAP::Transport::HTTP::Client::new: () > Calling sendMIME > SOAP::Data::new: () > SOAP::Lite::call: () > SOAP::Serializer::envelope: () > SOAP::Serializer::envelope: sendMIME SOAP::Data=HASH(0x1075d488) > SOAP::Data::new: () > SOAP::Data::new: () > SOAP::Data::new: () > SOAP::Data::new: () > SOAP::Data::new: () > SOAP::Transport::HTTP::Client::send_receive: HTTP::Request=HASH > (0x1060ece8) > SOAP::Transport::HTTP::Client::send_receive: POST > http://192.168.0.131:1234/ HTTP/1.1 > Accept: text/xml > Accept: multipart/* > Accept: application/soap > Content-Length: 600620 > Content-Type: Multipart/Related; type="text/xml"; > start="<main_envelope>"; boundary="----------=_1219045514-2988-0"; cha > rset=utf-8 > SOAPAction: "capture#sendMIME" > This is a multi-part message in MIME format... > ------------=_1219045514-2988-0 > Content-Type: text/xml > Content-Disposition: inline > Content-Location: /main_envelope > Content-ID: <main_envelope> > <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope > xmlns:namesp1="capture" xmlns:SOAP-ENV="http://schemas.xmlsoap. > org/soap/envelope/" > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" > xmlns:xsi="http://www.w3.org/2001/XMLSchem > a-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" SOAP- > ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encodin > g/"><SOAP-ENV:Body><namesp1:sendMIME><magicNumber > xsi:type="xsd:int">123</magicNumber></namesp1:sendMIME></SOAP-ENV:Body > ></SOAP-ENV:Envelope> > ------------=_1219045514-2988-0 > Content-Type: application/exe; name="soapcpp2.exe" > Content-Disposition: attachment; filename="soapcpp2.exe" > Content-Transfer-Encoding: base64 > MIME-Version: 1.0 > X-Mailer: MIME-tools 5.427 (Entity 5.427) > TVqQAAMAAAAEAAAA//8AALgAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAA > ...MIME FILE... > TkdQQURESU5HWFhQQURESU5H > ------------=_1219045514-2988-0-- > SOAP::Transport::HTTP::Client::send_receive: HTTP::Response=HASH > (0x1076f8c8) > SOAP::Transport::HTTP::Client::send_receive: 500 read failed: > Connection reset by peer > Content-Type: text/plain > Client-Date: Mon, 18 Aug 2008 07:45:28 GMT > Client-Warning: Internal response > 500 read failed: Connection reset by peer > SOAP::Deserializer::deserialize: () > SOAP::Parser::decode: () > 500 read failed: Connection reset by peer at ./MIMEsend.pl line 23 > SOAP::Transport::HTTP::Client::DESTROY: () > SOAP::Data::DESTROY: () > SOAP::Data::DESTROY: () > SOAP::Data::DESTROY: () > SOAP::Parser::DESTROY: () > SOAP::Transport::DESTROY: () > SOAP::Serializer::DESTROY: () > SOAP::Data::DESTROY: () > SOAP::Data::DESTROY: () > SOAP::Deserializer::DESTROY: () > SOAP::Data::DESTROY: () > SOAP::Lite::DESTROY: () > > > So my first question would be, is it because of the "This is a multi- > part message in MIME format..."? Is that the thing missing the XML > element it's talking about? Because that's the only thing I can see > that seems to differ from the SwA spec. > > So for the record, my gSOAP code looks like this (basically just the > example code from the documentation): > > int ns__sendMIME(struct soap *soap, int magicNumber, int &result){ > struct soap_multipart * attachment; > for(attachment = soap->mime.list; attachment; attachment = > attachment->next){ > printf("MIME attachment:\n"); > printf("Memory=%p\n", (*attachment).ptr); > printf("Size=%ul\n", (*attachment).size); > printf("Encoding=%d\n", (int)(*attachment).encoding); > printf("Type=%s\n", (*attachment).type? > (*attachment).type:"null"); > printf("ID=%s\n", (*attachment).id? > (*attachment).id:"null"); > printf("Location=%s\n", (*attachment).location? > (*attachment).location:"null"); > printf("Description=%s\n", (*attachment).description? > (*attachment).description:"null"); > } > printf("magicNumber = %#x\n", magicNumber); > if(magicNumber == 123){ > result = 42; > } > else{ > result = 0; > } > return SOAP_OK; > } > > My SOAP::Lite code looks like this: > > #!perl > use SOAP::Lite +trace => 'all'; > #use SOAP::Lite; > use SOAP::Lite::Packager; > use MIME::Entity; > my $ent = build MIME::Entity > Type => "application/exe", > Path => $ARGV[0], > Filename => $ARGV[0], > Disposition => "attachment"; > print "\nCalling client setup\n\n"; > $client = SOAP::Lite > -> packager(SOAP::Lite::Packager::MIME->new) > -> parts([$ent]) > -> proxy('http://192.168.0.131:1234/') > -> ns('capture'); > print "\nCalling sendMIME\n\n"; > $data = SOAP::Data->name(magicNumber => "123"); > $result = $client->sendMIME($data); > #print "result = $result\n"; > > Thanks for any help you can give! > > Bob > |
|
From: Peter C. <pfc...@ho...> - 2008-08-18 14:20:03
|
Anybody remember SOAP on a ROPE? (Simple Object Access Protocol on a Remote Object Proxy Engine) I think it was a Microsoft deal. I don't remember much about it, but I've always thought it was funny. > From: Scott Wiersdorf <sc...@pe...> > Date: Mon, 18 Aug 2008 08:14:56 -0600 > To: <soa...@li...> > Subject: Re: [Soaplite-devel] Order > > On Mon, Aug 18, 2008 at 06:33:43AM -0700, James Norris wrote: >> This Message kindly goes to the Owner or Sales Manager of the Shop. >> >> My name is Rev.James Norris and I am Interested in Ordering some of your Soap > > Uh, guys, someone should really get in touch with this poor minister > and send him some nice flowery-smelling soap. I'll pay for > shipping. Ordering "Soap" over the Internet? He sounds desperate! > > Scott > -- > Scott Wiersdorf > <sc...@pe...> > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Soaplite-devel mailing list > Soa...@li... > https://lists.sourceforge.net/lists/listinfo/soaplite-devel > |
|
From: Scott W. <sc...@pe...> - 2008-08-18 14:15:05
|
On Mon, Aug 18, 2008 at 06:33:43AM -0700, James Norris wrote: > This Message kindly goes to the Owner or Sales Manager of the Shop. > > My name is Rev.James Norris and I am Interested in Ordering some of your Soap Uh, guys, someone should really get in touch with this poor minister and send him some nice flowery-smelling soap. I'll pay for shipping. Ordering "Soap" over the Internet? He sounds desperate! Scott -- Scott Wiersdorf <sc...@pe...> |
|
From: James N. <rev...@ya...> - 2008-08-18 13:33:50
|
This Message kindly goes to the Owner or Sales Manager of the Shop.
My name is Rev.James Norris and I am Interested in Ordering some of your Soap So try and e-mail me back with the Types, Sizes, Price Ranges and also advice is you do take Surcharges when accepting Visa or Master Credit Card and provide your full name and Direct Phone # for more Discussion. I Hope to hear from you soon.
Kindest Regards,
Rev. James Norris
|
|
From: Robbie B. <rob...@gm...> - 2008-08-16 22:19:59
|
Madness! Having just perused the Catalyst::Manual I now see that it's actually a separate package and all the documents are .pod files. I reckon that's the way to go a separate distribution for the manual. 2008/8/17 Robbie Bow <rob...@gm...>: > Hi all > > So I set out this evening to start a cookbook and when I got to > looking for a suitable place to put it I noticed > trunk/lib/SOAP/Lite/Cookbook.pod in the repository but cannot find it > on search.cpan.org - has it been released? > > Anyway, I've combined that and my effort of this evening into one > file. Following the example of how the Catalyst documentation, I've > added it as a .pm that contains only pod documentation, and will be > putting it in a new directory, viz: > > /lib/SOAP/Lite/Manual/ > > I would also like to move all the other documentation from the > packages themselves into the Manual directory in appropriate .pm pod > only files. Then the documentation in the true packages should simply > link to the manual. > > Sane idea? Should I be doing this in trunk or in a new branch? > > Cheers > > > > Robbie > |
|
From: Robbie B. <rob...@gm...> - 2008-08-16 22:14:30
|
Hi all So I set out this evening to start a cookbook and when I got to looking for a suitable place to put it I noticed trunk/lib/SOAP/Lite/Cookbook.pod in the repository but cannot find it on search.cpan.org - has it been released? Anyway, I've combined that and my effort of this evening into one file. Following the example of how the Catalyst documentation, I've added it as a .pm that contains only pod documentation, and will be putting it in a new directory, viz: /lib/SOAP/Lite/Manual/ I would also like to move all the other documentation from the packages themselves into the Manual directory in appropriate .pm pod only files. Then the documentation in the true packages should simply link to the manual. Sane idea? Should I be doing this in trunk or in a new branch? Cheers Robbie |
|
From: Yunika S. <u05...@nu...> - 2008-06-11 14:03:32
|
Dear Mr/Ms,
I have a problem in using SOAP::Lite for my application. I would like to
ask for your help.
I want to build a Perl Web Client consuming WSDL (resulted from Apache
CFX Web Service).
The Web Service has a method called Test, which just returns the input.
Both output and input are of type string.
Here is my expected XML output:
EXPECTED OUTPUT:
<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP
-ENV:Body><Test <http://schemas.xmlsoap.org/soap/encoding/>
xmlns="http://test.test.test">TEXT_APPEAR</Test></SOAP-ENV:Body></SOAP-E
NV:Envelope>
SOAP::Transport::HTTP::Client::send_receive: HTTP/1.1 200 OK
Server: Jetty(6.1.6)
Content-Length: 206
Content-Type: text/xml
Client-Date: Wed, 11 Jun 2008 10:21:18 GMT
Client-Peer: 127.0.0.1:7650
SOAPAction: ""
I have tried following all the examples from the web but none of them
can give me the expected output xml. They give one extra element nested
around the input text.
My Perl Code (version 1):
use SOAP::Lite + trace => 'debug';
my $svc;
my $resp;
eval
{
$svc= SOAP::Lite
->service("http://localhost:8000/ <http://localhost:8000/> ");
$resp = $svc->Test('TEXT_APPEAR');
};
die "Got Error: $@" if($@);
OUTPUT:
<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance
<http://www.w3.org/1999/XMLSchema-instance> "
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/
<http://schemas.xmlsoap.org/soap/encoding/> "
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/
<http://schemas.xmlsoap.org/soap/envelope/> "
xmlns:xsd="http://www.w3.org/1999/XMLSchema
<http://www.w3.org/1999/XMLSchema> "
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP
-ENV:Body><Test <http://schemas.xmlsoap.org/soap/encoding/>
xmlns="http://test.test.test"><Test>TEXT_APPEAR</Test></Test></SOAP-ENV:
Body></SOAP-ENV:Envelope>
SOAP::Transport::HTTP::Client::send_receive: HTTP/1.1 200 OK
Server: Jetty(6.1.6)
Content-Length: 206
Content-Type: text/xml
Client-Date: Wed, 11 Jun 2008 10:21:18 GMT
Client-Peer: 127.0.0.1:7650
SOAPAction: ""
My Perl Code (version 2):
use SOAP::Lite + trace => 'debug';
my $svc;
my $resp;
eval
{
$svc= SOAP::Lite
->service("http://localhost:8000 <http://localhost:8000> ")
->proxy("http://localhost);
$resp = $svc->call(SOAP::Data->name('Test')
->attr ({'xmlns'=>'http://sth.sth.sth'})
=> "TEXT_APPEAR");
};
die "Got Error: $@" if($@);
OUTPUT:
<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP
-ENV:Body><Test <http://schemas.xmlsoap.org/soap/encoding/>
xmlns="http://test.test.test"><c-gensym3
<http://xml.ms.com/ns/msjava/greeter>
xsi:type="xsd:int">TEXT_APPEAR</c-gensym3></Greeter></SOAP-ENV:Body></SO
AP-ENV:Envelope>
SOAP::Transport::HTTP::Client::send_receive: HTTP/1.1 200 OK
Server: Jetty(6.1.6)
Content-Length: 272
Content-Type: text/xml; charset=utf-8
Client-Date: Wed, 11 Jun 2008 10:29:25 GMT
Client-Peer: 127.0.0.1:7650
Could you help me to solve this issue?
Looking forward to your reply, I really thank you very much for your
kind attention.
Sincerely yours,
Yunika
|
|
From: Martin K. <mar...@fe...> - 2008-04-30 15:15:06
|
Hi, I'm getting more and more mails complainin about unresolved namespace issues in SOAP-Lite. The name causing most current problems is SOAP::Packager - a equally named (but older) module is included in the SOAP Distribution. The result of the namespace conflict is, that SOAP::Lite is not installable via cpan (or perl -MCPAN -e shell). This adds quite a barrier to many perl users. I'd suggest we concentrate on resolving the namespace issues, and put out a modified version as "0.8" as fast as possible. We haven't reached 1.0 yet, so it's certainly not a new major release - but maybe the larger gap warns users a bit, and I'll certainly drop a note in the readme. Besides moving everything without a need to stay in the SOAP namespace (the stuff from "Programming Web-Services with Perl" should stay, as moving it would make large parts of the book unusable), conflicting modules should be moved into SOAP/Lite.pm. This way, they are not regarded as conflict by the CPAN indexer. As moving / renaming stuff is likely to break things, I'd like to provide most packages with both the old and the new name. The old-named ones should issue a warning when used. What's desperately needed is tests: We just cannot be sure we don't break SOAP::Lite internally without tests, so I'll devote my energy to improving the test suite first. Any support is welcome ;-) Martin |
|
From: MKUTTER <MK...@cp...> - 2008-04-16 20:08:29
|
Hi Graham, hi Keith, thanks for taking up this issue. There are some long-standing bug report in SOAP::Lite's queues on RT and sf.net, and me and the other SOAP::Lite developers are currently working towards cleaning up the namespace issues in SOAP::Lite, which we hope to resolve by 0.73 (the current 0.71 uses the old names, and 0.72 will support both the "old" conflicting and new names). We haven't set up dates yet, so all I have by now is some vague "it'll take about a year until we reach 0.73" feeling. I know people are still using the SOAP distribution, even though it seems to be unmaintained since 2000, so I actually don't aim to take over the complete namespace. However, I think that transferring some single names like SOAP::Packager would help SOAP::Lite users to easily find new versions until we've fixed things up. Martin Am Mittwoch, den 16.04.2008, 09:45 -0500 schrieb Graham Barr: > Keith, Martin, Byrne, > > SOAP::Packager appears in both the SOAP distribution and the SOAP- > Lite distribution. > > Keith has namespace ownership because the SOAP distribution was > uploaded back in 2000, but has not been updated since. > > Keith, do you intend to update the SOAP distribution ? If not would > you mind relinquishing the namespace to Martin and Byrne so that SOAP- > Lite, which is actively maintained, can stop showing as unauthorized > on search.cpan.org > > Thanks, > Graham. > > > |
|
From: Martin K. <mar...@fe...> - 2008-04-14 18:37:23
|
Hi, I'll be at YAPC Europe 2008 in Copenhagen, Aug 13-15. Maybe we can setup some BoF session - would be a nice thing to actually meet face 2 face. Martin |
|
From: Martin K. <mar...@fe...> - 2008-04-14 18:07:35
|
Hi, I just fixed a bad memory leak and wrapped things up as 0.71.02 on CPAN (usually available within a day or two - sourceforge is faster: https://sourceforge.net/project/showfiles.php?group_id=66000 ) Martin |
|
From: Robbie B. <rob...@gm...> - 2008-04-10 10:40:57
|
Hello all I'm attempting to write up some examples for a tutorial / quickstart guide and am currently deriving examples of clients for doc/lit style services. Here's the first example: use SOAP::Lite +trace; use strict; my $uri = 'http://www.webserviceX.NET'; my $url = 'http://www.webservicex.net/globalweather.asmx'; my $client = SOAP::Lite -> uri($uri) -> on_action( sub { join '/', $uri, $_[1] } ) -> proxy($url) -> autotype(0) -> readable(1); my $args = { CityName => 'Cambridge', CountryName => 'United Kingdom', }; $client->GetWeather($args)->attr({xmlns => $uri}); However, the XML this sends to the service is thus: <?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> <GetWeather xmlns="http://www.webserviceX.NET"> <c-gensym3> <CountryName>United Kingdom</CountryName> <CityName>Cambridge</CityName> </c-gensym3> </GetWeather> </soap:Body> </soap:Envelope> Note the c-gensym3 wrapper around my arguments, which causes the request to fail. I get around this with this: use SOAP::Lite +trace; use strict; my $uri = 'http://www.webserviceX.NET'; my $url = 'http://www.webservicex.net/globalweather.asmx'; my $client = SOAP::Lite -> uri($uri) -> on_action( sub { join '/', $uri, $_[1] } ) -> proxy($url) -> autotype(0) -> readable(1); my $args = { CityName => 'Cambridge', CountryName => 'United Kingdom', }; my $data = handroll($args); $client->GetWeather($data)->attr({xmlns => $uri}); sub handroll { my $hash = shift; my @array; while(my($key,$value) = each %$hash) { push @array, SOAP::Data->name($key)->value($value); } return \@array; } Which produces the following XML: <?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> <GetWeather xmlns="http://www.webserviceX.NET"> <CountryName>United Kingdom</CountryName> <CityName>Cambridge</CityName> </GetWeather> </soap:Body> </soap:Envelope> Note now there is no c-gensym wrapper, and the service accepts the request and returns my results as expected (try it, it's a valid working service). The question I have is: is there a more elegant way to avoid the c-gensym wrapper and, if not, might it be a good idea to add such a way to S::L? Cheers Robbie |
|
From: Bradley D. <bj...@bj...> - 2008-03-31 23:45:27
|
Greetings folks, On Sun, Mar 30, 2008 at 08:11:38PM +0200, Martin Kutter wrote: > In the meantime, there's always tests - trying to improve SOAP::Lite's > test coverage should keep you busy for some time... Aha - that sounds like a place I could start. I'll have a conversation with Robbie over a pint and see if I can't find somewhere to start adding tests. :) > Slightly off-topic: has anyone plans to visit YAPC Europe? Seeing that I'm on this side of the planet this year I'm hoping to get over there. Cheerio, Brad -- Bradley Dean Software Engineer - http://bjdean.id.au/ Email: bj...@bj... Skype: sk...@bj... Mobile(Aus): +61-413014395 Mobile(UK): +44-7846895073 |
|
From: Martin K. <mar...@fe...> - 2008-03-30 18:11:56
|
Hi Robbie, I actually hoped to get some more responses on my last post ;-) However, usually silence means consent, so I'd just follow the path of leaving the modules officially documented (lined out a post before), and moving the rest. In the meantime, there's always tests - trying to improve SOAP::Lite's test coverage should keep you busy for some time... ... and another important one is the reversal of namespace handling: SOAP::Lite users frequently stumble across it (I answered a post to the yahoo group touching the issue yesterday or so). I'll set up a bug report ;-) Slightly off-topic: has anyone plans to visit YAPC Europe? Martin Am Sonntag, den 30.03.2008, 18:30 +0100 schrieb Robbie Bow: > Martin, > > Have you decided on the name space issue and also, what will be > included in the next release? Or, in other words, what can I do for > the the next release ;o) > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Soaplite-devel mailing list > Soa...@li... > https://lists.sourceforge.net/lists/listinfo/soaplite-devel > |
|
From: Robbie B. <rob...@gm...> - 2008-03-30 17:30:51
|
Martin, Have you decided on the name space issue and also, what will be included in the next release? Or, in other words, what can I do for the the next release ;o) |
|
From: Martin K. <mar...@fe...> - 2008-03-29 14:55:41
|
Hi, I just uploaded 0.71.01 to CPAN. It's a minor bugfix release for 0.71, containing the following fixes: ! #34515: Printing UTF-8 through SOAP::Transport::HTTP throws a warning ! [1904955] Subclassing XMLRPC::Serializer broken Martin |
|
From: Martin K. <mar...@fe...> - 2008-03-24 09:58:27
|
Hi, I just commited a fix to SOAP-Lite/trunk adressing https://sourceforge.net/tracker/index.php?func=detail&aid=1604320&group_id=66000&atid=513017 As Mikhail Gusarov correctly states, the WS-I basic profile does not allow a part of a rpc/literal operation message to contain xsi:nil="true". However, this attribute may be required by document/literal webservices, and might be required (I don't know) by rpc/encoded webservices. For document/literal, I think that stubmaker should set up the parameters to be encoded with the nil attribute when required. Does anyone know how rpc/encoded webservices behave? Martin Am Montag, den 24.03.2008, 02:01 -0700 schrieb kut...@us...: > Revision: 218 > http://soaplite.svn.sourceforge.net/soaplite/?rev=218&view=rev > Author: kutterma > Date: 2008-03-24 02:01:27 -0700 (Mon, 24 Mar 2008) > > Log Message: > ----------- > - fixes [ 1604320 ] xsi:nil on part accessor in argless message > This needs discussion: The removal of the xsi:nil="true" attribute on an empty method may break document/literal and rpc/encoded webservices. > > Modified Paths: > -------------- > trunk/Changes > trunk/lib/SOAP/Serializer.pm > trunk/t/SOAP/Serializer.t > > > This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > soaplite-commit mailing list > soa...@li... > https://lists.sourceforge.net/lists/listinfo/soaplite-commit > |
|
From: Martin K. <mar...@fe...> - 2008-03-24 09:11:06
|
Hi Brad, Ooops I didn't recognise this one. I actually fixed a duplicate: https://sourceforge.net/tracker/index.php?func=detail&aid=1416700&group_id=66000&atid=513017 Closed, Martin Am Sonntag, den 16.03.2008, 22:34 +0000 schrieb Bradley Dean: > Hi Martin, > > I've been looking around for things to do - thought this looked like a > simple one but it's already done (by you, back in version 85). > > Might be worth updating the status in the tracker. > > Cheerio, > > Brad > > On Sun, Mar 02, 2008 at 11:54:15PM +0100, Martin Kutter wrote: > > Hi Bradley, > > > > welcome and thanks again (in advance ;-) > > > > I guess robbie told you what SOAP::Lite is like... > > > > You have commit access to SOAP::Lite's SVN located at > > > > https://soaplite.svn.sourceforge.net/svnroot/soaplite/ > > > > You can pick tracker items from SOAP::Lite's sf.net trackers. > > > > Let me know if you have plans on what to do first. > > > > It's proablby best to always cc the list when plannign - there's Paul > > Kulchenko, Byrne and some other regulars among the list readers. > > > > Martin > > > > Am Sonntag, den 02.03.2008, 18:42 +0000 schrieb Bradley Dean: > > > bjdean > |
113 messages has been excluded from this view by a project administrator.
