SOAP::Lite parses the WSDL and creates the stub in memory which is
time consuming. If you have the WSDL, you can use stubmaker.pl to
create the stub and then include the generated pm file in your
program. Skip the service call and call the function directly. (See
SOAP::Lite man page).

Jonathan

--- In soaplite@yahoogroups.com, mp_gs@y... wrote:
> Hello
>
> Does anyone know how to optimize the performance of SOAP::Lite and
> WSDL or maybe recommend another solution? As of now it takes 2
> seconds.
>
> Thanks,
> Mike

I have a SOAP method which returns a date (currently as a
string). Reading SOAP::Lite documentation
<URL:http://guide.soaplite.com/#types%20and%20names>, I do not find
the list of supported types for SOAP::Data->type but, reading the
code, it seems "date" is not one of them.

In CPAN, I've found a SOAP::DateTime. Is it the only solution?

NAME
        SOAP::DateTime - Support for converting dates to
        "xsd:dateTime" format

SYNOPSIS
          use SOAP::DateTime;
          my $soap_datetime = ConvertDate($arbitrary_date);


DESCRIPTION
        "SOAP::DateTime" converts dates into the format required
        by the "xsd:dateTime" type.

On Fri, Apr 02, 2004 at 12:58:52PM +0200,
  Stephane Bortzmeyer <bortzmeyer@...> wrote
  a message of 41 lines which said:

> In CPAN, I've found a SOAP::DateTime. Is it the only solution?

Using the above module to format the date and
SOAP::Data->type('xsd:datetime' => XXX) to tag it properly, I can send
what seems to be proper SOAP elements.

Now, how can I deserialize them in Perl? The client, also written in
SOAP::Lite, says:

SOAP::Deserializer::deserialize: ()
SOAP::Parser::decode: ()
Unrecognized type '{http://www.w3.org/1999/XMLSchema}datetime'

while the SOAP answer is:

<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:namesp6="http://xml.apache.org/xml-soap"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"><SOAP-ENV:Body><namesp5:status_tick\
etResponse xmlns:namesp5="http://nic.fr/Ticket"><s-gensym23
xsi:type="namesp6:SOAPStruct"><auth
xsi:type="xsd:string">A2950FFEAAFBAD17</auth><state xsi:type="xsd:string">DNS
Non Pret</state><operation xsi:type="xsd:string">Creation</operation><form
xsi:type="xsd:int">301988</form><domain
xsi:type="xsd:string">logan2004.fr</domain><creation_date
xsi:type="xsd:datetime">2003-06-10T12:59:00</creation_date><seed
xsi:type="xsd:int">442724</seed><remark xsi:type="xsd:string">Nouvel Etat: DNS
Non Pret
</remark><modification_date
xsi:type="xsd:datetime">2003-07-10T10:50:00</modification_date><number
xsi:type="xsd:string">NIC000000500893</number></s-gensym23></namesp5:status_tick\
etResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>

The question "How to deserialize datetimes?" seem to come up often on
that list but not the answer :-}

Hi,
I'm trying to use SOAP::Lite as a client to interface with an internal SOAP
based API at my company.  My client platform is Linux/mod_perl and the server
platform is Java.  The API requests are extremely large and complex, and I've
had no succuess using SOAP::Schema or the stubmaker utility in generating the
proper SOAP envelope with the company provided WSDL.  I've looked at
SOAP::Data::Builder a little, but I'm not sure this would solve my problem,
and even if it did, it would be a lot of up front work just to generate the
proper request schema.  I am, however, able to derive the proper request
envelopes statically (and quickly), using a desktop XML editor that can parse
WSDL (XML Spy).

Because I am able to do this, and in the interest of saving time, I was hoping
there was a way to just provide the pre-formatted SOAP XML request envelopes
to SOPA::Lite, bypassing any SOAP::Data and SOAP::Serializer steps
all-together, and just have SOAP::Lite take care of the transport and response
portion of the request/response cycle.  I was looking at the code for
SOAP::Lite and SOAP::Transport::HTTP and cannot see any point in the code
where one could just easily insert their own envelope structure for transport.

I guess my question is ... Is it possible to to insert your own request
envelope and if so, how/where can I do it?

Thanks in advance for any assistance you can offer.
Cheers,
  - Jeff

At 13:52:48 on 02-04-2004 Stephane Bortzmeyer <bortzmeyer@...>
wrote:

>On Fri, Apr 02, 2004 at 12:58:52PM +0200,
> Stephane Bortzmeyer <bortzmeyer@...> wrote
> a message of 41 lines which said:
>
>> In CPAN, I've found a SOAP::DateTime. Is it the only solution?
>
>Using the above module to format the date and
>SOAP::Data->type('xsd:datetime' => XXX) to tag it properly, I can
>>send
>what seems to be proper SOAP elements.
>
>Now, how can I deserialize them in Perl? The client, also written
>>in
>SOAP::Lite, says:
>
>SOAP::Deserializer::deserialize: ()
>SOAP::Parser::decode: ()
>Unrecognized type '{http://www.w3.org/1999/XMLSchema}datetime'
>
>while the SOAP answer is:
>
><?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
>>xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
>>SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
>>xmlns:namesp6="http://xml.apache.org/xml-soap"
>>xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
>>xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
>>xmlns:xsd="http://www.w3.org/1999/XMLSchema"><SOAP-ENV:Body><namesp5
>>:status_ticketResponse
>>xmlns:namesp5="http://nic.fr/Ticket"><s-gensym23
>>xsi:type="namesp6:SOAPStruct"><auth
>>xsi:type="xsd:string">A2950FFEAAFBAD17</auth><state
>>xsi:type="xsd:string">DNS Non Pret</state><operation
>>xsi:type="xsd:string">Creation</operation><form
>>xsi:type="xsd:int">301988</form><domain
>>xsi:type="xsd:string">logan2004.fr</domain><creation_date
>>xsi:type="xsd:datetime">2003-06-10T12:59:00</creation_date><seed
>>xsi:type="xsd:int">442724</seed><remark xsi:type="xsd:string">Nouvel
>>Etat: DNS Non Pret
></remark><modification_date
>xsi:type="xsd:datetime">2003-07-10T10:50:00</modification_date><num
>>ber
>xsi:type="xsd:string">NIC000000500893</number></s-gensym23></namesp
>>5:status_ticketResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>
>
>The question "How to deserialize datetimes?" seem to come up often
>>on
>that list but not the answer :-}

The type is dateTime not datetime and your server needs to specify the 2001
namespace not 1999, i.e. xmlns:xsd="http://www.w3.org/2001/XMLSchema". The
element will then be deserialised simply as the string value. If you want a Perl
time value then you will have to do the conversion yourself.

Regards
Duncan

I have been lagging in packaging the latest set of updates for
SOAP::Lite because they are all tied into WSDL2Perl, but in the next
release, the 2001 schema becomes default, and the type detector was
upgraded to detect primitives more reliably and consistently.

SOAP::Lite will also have integrated with it, a datetime formatter, so
that such values can be generated more easily.

I know that doesn't help you now, but know that the feature is coming.

Duncan Cameron wrote:

> At 13:52:48 on 02-04-2004 Stephane Bortzmeyer <bortzmeyer@...>
> wrote:
>
> >On Fri, Apr 02, 2004 at 12:58:52PM +0200,
> > Stephane Bortzmeyer <bortzmeyer@...> wrote
> > a message of 41 lines which said:
> >
> >> In CPAN, I've found a SOAP::DateTime. Is it the only solution?
> >
> >Using the above module to format the date and
> >SOAP::Data->type('xsd:datetime' => XXX) to tag it properly, I can
> >>send
> >what seems to be proper SOAP elements.
> >
> >Now, how can I deserialize them in Perl? The client, also written
> >>in
> >SOAP::Lite, says:
> >
> >SOAP::Deserializer::deserialize: ()
> >SOAP::Parser::decode: ()
> >Unrecognized type '{http://www.w3.org/1999/XMLSchema}datetime'
> <http://www.w3.org/1999/XMLSchema%7Ddatetime%27>
> >
> >while the SOAP answer is:
> >
> ><?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
> >>xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
> >>SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> >>xmlns:namesp6="http://xml.apache.org/xml-soap"
> >>xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> >>xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
> >>xmlns:xsd="http://www.w3.org/1999/XMLSchema"><SOAP-ENV:Body><namesp5
> >>:status_ticketResponse
> >>xmlns:namesp5="http://nic.fr/Ticket"><s-gensym23
> >>xsi:type="namesp6:SOAPStruct"><auth
> >>xsi:type="xsd:string">A2950FFEAAFBAD17</auth><state
> >>xsi:type="xsd:string">DNS Non Pret</state><operation
> >>xsi:type="xsd:string">Creation</operation><form
> >>xsi:type="xsd:int">301988</form><domain
> >>xsi:type="xsd:string">logan2004.fr</domain><creation_date
> >>xsi:type="xsd:datetime">2003-06-10T12:59:00</creation_date><seed
> >>xsi:type="xsd:int">442724</seed><remark xsi:type="xsd:string">Nouvel
> >>Etat: DNS Non Pret
> ></remark><modification_date
> >xsi:type="xsd:datetime">2003-07-10T10:50:00</modification_date><num
> >>ber
> >xsi:type="xsd:string">NIC000000500893</number></s-gensym23></namesp
> >>5:status_ticketResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>
> >
> >The question "How to deserialize datetimes?" seem to come up often
> >>on
> >that list but not the answer :-}
>
> The type is dateTime not datetime and your server needs to specify the
> 2001 namespace not 1999, i.e.
> xmlns:xsd="http://www.w3.org/2001/XMLSchema". The element will then be
> deserialised simply as the string value. If you want a Perl time value
> then you will have to do the conversion yourself.
>
> Regards
> Duncan
>
>
>
> ------------------------------------------------------------------------
> *Yahoo! Groups Links*
>
>     * To visit your group on the web, go to:
>       http://groups.yahoo.com/group/soaplite/
>
>     * To unsubscribe from this group, send an email to:
>       soaplite-unsubscribe@yahoogroups.com
>       <mailto:soaplite-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>
>     * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>.
>
>

On Fri, 2 Apr 2004, Byrne Reese wrote:

> I have been lagging in packaging the latest set of updates for
> SOAP::Lite because they are all tied into WSDL2Perl, but in the next
> release, the 2001 schema becomes default, and the type detector was
> upgraded to detect primitives more reliably and consistently.

Byrne,

Will the upcoming release properly handle literalxml encoding?  I recently
posted a workaround to enable the current version to handle this, but it
would be nice if that weren't required.

Steve

--
----------------------------------------------------------------
Steven N. Hirsch       tie-line: 446-6557     ext: 802-769-6557

Staff Engineer                     Methodology Integration Team
ASIC Product Development           IBM Microelectronics
----------------------------------------------------------------

On Fri, Apr 02, 2004 at 10:19:16PM +0000,
  Duncan Cameron <dcameron@...> wrote
  a message of 57 lines which said:

> The type is dateTime not datetime

Yes, sorry for the stupid bug. Although it is not enough to solve the
problem.

> and your server needs to specify the 2001 namespace not 1999,
> i.e. xmlns:xsd="http://www.w3.org/2001/XMLSchema".

I do not find how to do so with SOAP::Lite (yes, my server is written
in SOAP::Lite, too).

> The element will then be deserialised simply as the string value. If
> you want a Perl time value then you will have to do the conversion
> yourself.

No problem, HTTP::Date is here for that :-)

--- Stephane Bortzmeyer <bortzmeyer@...> wrote:
>
> > and your server needs to specify the 2001 namespace not 1999,
> > i.e. xmlns:xsd="http://www.w3.org/2001/XMLSchema".
>
> I do not find how to do so with SOAP::Lite (yes, my server is written
> in SOAP::Lite, too).

From memory, on the server side something like

my $daemon = SOAP::Transport::HTTP::Daemon # etc

$daemon->serializer->xmlschema('2001');
or
$daemon->serializer->version('1.1');

will cause the 2001 namespace to be used.

Regards

Duncan






___________________________________________________________
WIN FREE WORLDWIDE FLIGHTS - nominate a cafe in the Yahoo! Mail Internet Cafe
Awards  www.yahoo.co.uk/internetcafes

--- Duncan Cameron <duncan_cameron2002@...> wrote:
>  --- Stephane Bortzmeyer <bortzmeyer@...> wrote:
> >
> > > and your server needs to specify the 2001 namespace not 1999,
> > > i.e. xmlns:xsd="http://www.w3.org/2001/XMLSchema".
> >
> > I do not find how to do so with SOAP::Lite (yes, my server is
> written
> > in SOAP::Lite, too).
>
> From memory, on the server side something like
>
> my $daemon = SOAP::Transport::HTTP::Daemon # etc
>
> $daemon->serializer->xmlschema('2001');
> or
> $daemon->serializer->version('1.1');
>
> will cause the 2001 namespace to be used.
>
Sorry to reply to my own posting but the soapversion() call doesn't
work on a server in the same way as a client. Try

SOAP::Lite->soapversion('1.2');

/before/ creating your server daemon.

Regards
Duncan






___________________________________________________________
WIN FREE WORLDWIDE FLIGHTS - nominate a cafe in the Yahoo! Mail Internet Cafe
Awards  www.yahoo.co.uk/internetcafes

Which UDDI specification does UDDI::Lite support? I read in the
O'Reilly book that it only supports version 1. I don't see anything
in the POD indicating which spec it supports. Is there any way to
access UDDI version 2 and 3 APIs?

Thanks,
Mark

I am having trouble accessing the complex output from a web service.

If I do it this way:

=======================================================
my  $s = SOAP::Lite
     -> uri('urn:uddi-org:api_v2')
     -> on_action(sub { sprintf '"%s"', @_ })
     -> proxy('http://localhost:8080/uddi/inquiry', timeout =>
$SOAP::Test::TIMEOUT);


my $result = $s->call(SOAP::Data
          ->name('find_business')
          ->attr({xmlns => 'urn:uddi-org:api_v2', generic => '2.0'})
   =>  # Arguments
   SOAP::Data->name(name => '%')
   )->result;

while ( my($key, $value) = each %{$result}) {
     print "level1 $key = $value\n";
     while ( my($key1, $value1) = each %{$value} ) {
         print "   level2 $key1 = $value1\n";
     }
}
===================================================

I get a reference to a hash which also contains references to hashes.
The problem is, I am getting back two "businessInfo" elements (in the
trace output) but the hash only contains one.

I read the documentation and thought it said I could get access to
the SOAP::SOM if I used the OO interface. I tried a few things but
they generate an incorrect SOAP message. I can't set the attributes
on "find_business". And, it prefixes that element with "namesp1:".

Can someone please help me or tell me where to get help? If I can
make this work, I have a chance of using it for a large project at
work instead of Java. I either need to know how to get access to the
complex results of the example above. Or, I need to know how to do
an "OO" call and set attributes (and not get the unwanted "namesp1:"
prefix on the method element.

Thanks,
Mark

After poking around I'm able to make this work enough for my purposes
(or learn more).

One thing I was doing wrong was using ")->result" on the end of
the "call" method. When I tried to use my $result as an SOM object,
it complained that it was an unblessed reference. I noticed an
example in http://groups.yahoo.com/group/soaplite/message/3350 (a
useful "how to" about setting complex elements) which got me to see
it.

I then proceeded to find $result->dataof('//businessInfo/*') doesn't
work. After 3 hours, I noticed the posting
http://groups.yahoo.com/group/soaplite/message/3369 (and replies to
it). The single quotes have to be double quotes ("). After I did
that, I was able to access multiple occurences of elements in the
output.

Thanks,
Mark

On Sat, Apr 03, 2004 at 02:30:54PM +0100,
  Duncan Cameron <duncan_cameron2002@...> wrote
  a message of 37 lines which said:

> Sorry to reply to my own posting but the soapversion() call doesn't
> work on a server in the same way as a client. Try
>
> SOAP::Lite->soapversion('1.2');

It seems completely ignored, I get the same namespace.

My code:

SOAP::Lite->soapversion('1.2');
my $daemon = SOAP::Transport::HTTP::CGI
     -> dispatch_to('/local/lib/soap', '*',
                    '', '');
$daemon->handle;

My server (Apache 1 + mod_perl):

<Location /soap>
         SetHandler perl-script
         PerlHandler Apache::Registry
         PerlSendHeader On
         Options +ExecCGI
         DirectoryIndex dispatcher
</Location>

My result:

<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
xmlns:namesp2="http://xml.apache.org/xml-soap"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
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:Body><namesp1:hello_dateR\
esponse
xmlns:namesp1="http://nic.fr/TestOnly"><s-gensym3
xsi:type="namesp2:SOAPStruct"><Message
xsi:type="xsd:string">World</Message><Date
xsi:type="xsd:dateTime">2004-04-01T16:01:13</Date></s-gensym3></namesp1:hello_da\
teResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>

I'm trying to return a fault object from a soap::lite server to a java
client, however tcptunnel tells me this:




<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:namesp2="http://namespaces.soaplite.com/perl"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:B
ody><namesp1:shutdownnowResponse
xmlns:namesp1="urn:Bevan::Worker"><SOAP__Fault
xsi:type="namesp2:SOAP__Fault"><_faultstring
xsi:type="xsd:string">orderly server
shutdown</_faultstring><_faultactor
xsi:type="xsd:string">http://localhost:9000/</_faultactor><_faultcode
xsi:type="xsd:string">Server.OrderlyShutdown</_faultcode></SOAP__Fault
></namesp1:shutdownnowResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>




Firstly, the java client (using the Apache SOAP module, *not* Axis)
tells me that it doesn't recognise SOAP_Fault. However, when I attempt
to use a BeanSerializer with the Fault class as the template, it
doesn't recognise the _faultstring, _faultactor or _faultcode. The
underscores seem to be the problem, as in other examples produced from
SOAP::lite, they seem to be missing. Is there a simple solution to
this?




TIA




r.

This is the proper way to return a SOAP::Fault from SOAP::Lite:

die SOAP::Fault->faultcode("Client")
                         ->faultstring(...)
                         ->faultactor(...);

Is that you are doing?

regwillingham wrote:

> I'm trying to return a fault object from a soap::lite server to a java
> client, however tcptunnel tells me this:
>
>
>
>
> <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
> xmlns:namesp2="http://namespaces.soaplite.com/perl"
> xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
> xmlns:xsd="http://www.w3.org/1999/XMLSchema"
> SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:B
> ody><namesp1:shutdownnowResponse
> xmlns:namesp1="urn:Bevan::Worker"><SOAP__Fault
> xsi:type="namesp2:SOAP__Fault"><_faultstring
> xsi:type="xsd:string">orderly server
> shutdown</_faultstring><_faultactor
> xsi:type="xsd:string">http://localhost:9000/</_faultactor><_faultcode
> xsi:type="xsd:string">Server.OrderlyShutdown</_faultcode></SOAP__Fault
> ></namesp1:shutdownnowResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>
>
>
>
>
> Firstly, the java client (using the Apache SOAP module, *not* Axis)
> tells me that it doesn't recognise SOAP_Fault. However, when I attempt
> to use a BeanSerializer with the Fault class as the template, it
> doesn't recognise the _faultstring, _faultactor or _faultcode. The
> underscores seem to be the problem, as in other examples produced from
> SOAP::lite, they seem to be missing. Is there a simple solution to
> this?
>
>
>
>
> TIA
>
>
>
>
> r.
>
>
>
> *Yahoo! Groups Sponsor*
> ADVERTISEMENT
>
<http://rd.yahoo.com/SIG=12cj9alv3/M=290828.4794622.5939935.1261774/D=egroupweb/\
S=1705701014:HM/EXP=1081267381/A=1950450/R=0/SIG=124u9bhid/*http://ashnin.com/cl\
k/muryutaitakenattogyo?YH=4794622&yhad=1950450>
>
>
>
> ------------------------------------------------------------------------
> *Yahoo! Groups Links*
>
>     * To visit your group on the web, go to:
>       http://groups.yahoo.com/group/soaplite/
>
>     * To unsubscribe from this group, send an email to:
>       soaplite-unsubscribe@yahoogroups.com
>       <mailto:soaplite-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>
>     * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>.
>
>

Fair enough... here is a little bit on datetimes with SOAP::Lite...

A recent module to CPAN seems to help address the problem:
http://search.cpan.org/~mcmahon/SOAP-DateTime-0.01/

  From the README: "This is a little utility module that converts dates
into the format required by the SOAP 'xsd:dateTime' type. It's just a
dumb little wrapper around Date::Manip, because that's the lazy way to
make sure that we are forgiving in what we accept."

So there is also Date::Manip (obviously).
http://search.cpan.org/~sbeck/DateManip-5.42a/Manip.pod

Bottom line, SOAP::Lite doesn't (since Perl is so loosely typed) do any
type deserialization for you. Not to anything but a SCALAR. Perhaps that
is something we should more clearly document and provide workarounds for.

The flip side of course is that the next version of SOAP::Lite, which
will ship with wsdl2perl, will handle dates more gracefully and
recognize all of their permutations. From the source of the next release
of SOAP::Lite:

       _typelookup => {
...
        'gMonth' =>
           [35, sub { $_[0] =~ /^--\d\d--(-\d\d:\d\d)?$/; }, 'as_gMonth'],
           'gDay' =>
           [40, sub { $_[0] =~ /^---\d\d(-\d\d:\d\d)?$/; }, 'as_gDay'],
           'gYear' =>
           [45, sub { $_[0] =~ /^-?\d\d\d\d(-\d\d:\d\d)?$/; }, 'as_gYear'],
           'gMonthDay' =>
           [50, sub { $_[0] =~ /^-\d\d-\d\d(-\d\d:\d\d)?$/; },
'as_gMonthDay'],
           'gYearMonth' =>
           [55, sub { $_[0] =~ /^-?\d\d\d\d-\d\d(Z|([+-]\d\d:\d\d))?$/;
}, 'as_gYearMonth'],
           'date' =>
           [60, sub { $_[0] =~
/^-?\d\d\d\d-\d\d-\d\d(Z|([+-]\d\d:\d\d))?$/; }, 'as_date'],
           'time' =>
           [70, sub { $_[0] =~
/^\d\d:\d\d:\d\d(\.\d\d\d)?(Z|([+-]\d\d:\d\d))?$/; }, 'as_time'],
           'dateTime' =>
           [75, sub { $_[0] =~
/^\d\d\d\d-\d\d-\d\dT\d\d:\d\d:\d\d(\.\d\d\d)?(Z|([+-]\d\d:\d\d))?$/; },
'as_dateTime'],
           'duration' =>
           [80, sub { $_[0] =~
/^-?P(\d+Y)?(\d+M)?(\dD)?(T(\d+H)?(\d+M)?(\d+S)?)?$/; }, 'as_duration'],
           'duration' =>
           [85, sub { $_[0] =~
/^-?P(\d+Y)?(\d+M)?(\dD)?(T(\d+H)?(\d+M)?(\d+S)?)?$/; }, 'as_duration'],
...
       },

Stephane Bortzmeyer wrote:

> On Fri, Apr 02, 2004 at 12:58:52PM +0200,
> Stephane Bortzmeyer <bortzmeyer@...> wrote
> a message of 41 lines which said:
>
> > In CPAN, I've found a SOAP::DateTime. Is it the only solution?
>
> Using the above module to format the date and
> SOAP::Data->type('xsd:datetime' => XXX) to tag it properly, I can send
> what seems to be proper SOAP elements.
>
> Now, how can I deserialize them in Perl? The client, also written in
> SOAP::Lite, says:
>
> SOAP::Deserializer::deserialize: ()
> SOAP::Parser::decode: ()
> Unrecognized type '{http://www.w3.org/1999/XMLSchema}datetime'
> <http://www.w3.org/1999/XMLSchema%7Ddatetime%27>
>
> while the SOAP answer is:
>
> <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
> xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
> SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> xmlns:namesp6="http://xml.apache.org/xml-soap"
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
>
xmlns:xsd="http://www.w3.org/1999/XMLSchema"><SOAP-ENV:Body><namesp5:status_tick\
etResponse
> xmlns:namesp5="http://nic.fr/Ticket"><s-gensym23
> xsi:type="namesp6:SOAPStruct"><auth
> xsi:type="xsd:string">A2950FFEAAFBAD17</auth><state
> xsi:type="xsd:string">DNS Non Pret</state><operation
> xsi:type="xsd:string">Creation</operation><form
> xsi:type="xsd:int">301988</form><domain
> xsi:type="xsd:string">logan2004.fr</domain><creation_date
> xsi:type="xsd:datetime">2003-06-10T12:59:00</creation_date><seed
> xsi:type="xsd:int">442724</seed><remark xsi:type="xsd:string">Nouvel
> Etat: DNS Non Pret
> </remark><modification_date
> xsi:type="xsd:datetime">2003-07-10T10:50:00</modification_date><number
>
xsi:type="xsd:string">NIC000000500893</number></s-gensym23></namesp5:status_tick\
etResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>
>
>
> The question "How to deserialize datetimes?" seem to come up often on
> that list but not the answer :-}
>
> ------------------------------------------------------------------------
> *Yahoo! Groups Links*
>
>     * To visit your group on the web, go to:
>       http://groups.yahoo.com/group/soaplite/
>
>     * To unsubscribe from this group, send an email to:
>       soaplite-unsubscribe@yahoogroups.com
>       <mailto:soaplite-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>
>     * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>.
>
>

Ok folks - I am in need of a little help. Before I bang my head
against the keyboard one last time, I thought I might consult my
follow perl hackers for some advice.

I upgraded majordojo using RPMs to the latest Redhat 9 (yes I know
support has been discontinued - thank you Redhat). In the process
perl 5.8.0 was installed... which naturally requires me to upgrade
all my perl modules etc. So the state of my system, which was once
Redhat 7.3 running perl 5.6.1, is now running Redhat 9 (in theory),
and perl 5.8.3 (I upgraded from source to the latest hoping it would
resolve my problem).

Now, here is the problem:
I have a CGI that makes a SOAP call, and when it does, I get the
following message:
> '501 Can't locate object method "new" via
package "LWP::Protocol::https" (Crypt::SSLeay not installed) at
browse.cgi line 61'

But I have installed Crypt::SSLeay, lib-www, etc... I have installed
all the necessary files. My proof?

When I run the script from the command line as ROOT it works. Ok, so
this naturally leads me to believe that I have a permissions problem.
But where!? I have traversed the ENTIRE /usr/local/lib/perl5
directory heirarchy looking for permissions that are suspect, and
every directory has the global execute bit set, every .so file has
the global execute bit as well. Every file is globally readable. So
what gives?

I have since installed from source openssl-0.9.7d just to make sure.
What am I missing here? This is killing me. I am running Redhat 9 at
home, and everything works great. I am running Redhat 9 from the
office, and everything is cool. Clearly something is not right with
my RPM upgrade, but where do I start to track it down.

Frustratingly Yours,
Byrne

On Tue, Apr 06, 2004 at 12:49:05PM -0700,
  Byrne Reese <byrne@...> wrote
  a message of 116 lines which said:

> A recent module to CPAN seems to help address the problem:
> http://search.cpan.org/~mcmahon/SOAP-DateTime-0.01/

I know it and mentioned it in my first message. It only handles
serialization, my problem being the deserialization.

> Bottom line, SOAP::Lite doesn't (since Perl is so loosely typed) do
> any type deserialization for you.

I do not see the connection with my problem. Python and PHP are no
more typed than Perl and both can deserialize xsd:dateTime (they just
produce a string for a type they do not know, that I parse after). Why
can't SOAP::Lite do the same?

On Tue, Apr 06, 2004 at 10:19:38PM -0000,
  Byrne Reese <byrne@...> wrote
  a message of 53 lines which said:

> So the state of my system, which was once Redhat 7.3 running perl
> 5.6.1, is now running Redhat 9 (in theory), and perl 5.8.3

RedHat, like FreeBSD, does not really support upgrades. It is probably
better to reinstall.

> When I run the script from the command line as ROOT it works. Ok, so
> this naturally leads me to believe that I have a permissions
> problem.  But where!?

As non-root:

% strace perl YOUR-SCRIPT.pl |& grep -i permission

Should give you something like:

open("/usr/lib/perl5/auto/Crypt/SSLeay/SSLeay.so", O_RDONLY) = -1 EACCES
(Permission denied)

Ok folks - I am in need of a little help. Before I bang my head against
the keyboard one last time, I thought I might consult my follow perl
hackers for some advice.

I upgraded majordojo using RPMs to the latest Redhat 9 (yes I know
support has been discontinued - thank you Redhat). In the process perl
5.8.0 was installed... which naturally requires me to upgrade all my
perl modules etc. So the state of my system, which was once Redhat 7.3
running perl 5.6.1, is now running Redhat 9 (in theory), and perl 5.8.3
(I upgraded from source to the latest hoping it would resolve my problem).

Now, here is the problem:
I have a CGI that makes a SOAP call, and when it does, I get the
following message:
  > '501 Can't locate object method "new" via package
"LWP::Protocol::https" (Crypt::SSLeay not installed) at browse.cgi line 61'

But I have installed Crypt::SSLeay, lib-www, etc... I have installed all
the necessary files. My proof?

When I run the script from the command line as ROOT it works. Ok, so
this naturally leads me to believe that I have a permissions problem.
But where!? I have traversed the ENTIRE /usr/local/lib/perl5 directory
heirarchy looking for permissions that are suspect, and every directory
has the global execute bit set, every .so file has the global execute
bit as well. Every file is globally readable. So what gives?

I have since installed from source openssl-0.9.7d just to make sure.
What am I missing here? This is killing me. I am running Redhat 9 at
home, and everything works great. I am running Redhat 9 from the office,
and everything is cool. Clearly something is not right with my RPM
upgrade, but where do I start to track it down.

Frustratingly Yours,
Byrne

A majordomo installed as RPM will necessarily use the Perl installed as RPM,
that would be 5.8.0. I guess you have installed 5.8.3 under /usr/local, but
5.8.0 is under /usr.

Thus: what Perl have you installed libwww, Crypt::SSLeay, and friends into,
5.8.0 or 5.8.3?
What Perl does majordomo use? Does it probably set $ENV{PERL5LIB}?

I really suspect that, when running under majordomo, your CGI uses the
LWP::UserAgent from the wrong Perl, the one that does not have Crypt::SSLeay
installed.

Try to insert someting like that immediately at the top of your CGI:

	 #!/usr/..../perl       # whatever the first line currently is
	 use Config qw(myconfig config_sh);
	 BEGIN {
		 print STDERR myconfig().config_sh();
		 while my($k, $v) = each(%ENV) {
			 print STDERR "ENV{$k} = $v\n";
		 }
		 print STDERR "<".join(">\n<", @INC).">\n";
	 }

	 # here comes the rest of the original CGI

given, that STDERR is not redirected to /dev/null. If so, you may still open a
file inside of the BEGIN block and print into that file. The output should give
you more that enough info about the actual Perl running the CGI under majordomo.

Not knowing how your CGI is actually started, please consider the possibility,
that the first line (the "#!/usr/...") may not be evaluated at all if there is a
wrapper CGI that calls your program with "system('/some/path/to/some/perl',
'scriptname');".

Hmm ... that's all from the top of my head. Hope that helps.

----
  Dipl.Ing. Andreas Manessinger
  Referat EG2 - Informations- und Kommunikationsdienste
  Magistrat der Stadt Wien, Magistratsabteilung 14 - ADV,
  Rathausstr. 1, A-1082 Wien
  E-Mail: man@...
  Tel: (+43 1) 4000-91176
  Fax: (+43 1) 4000-99-91176
  WWW: http://www.wien.gv.at/egov/

Hi all..
   Trying to get a perl client working correctly with a WebMethods
Glue server.  The problem I'm running into is that I need to send
back an array of anyType with each array element potentially being a
different type.  Something like:

<params_array SOAP-ENC:arrayType="xsd:anyType[1]" xsi:type="SOAP-
ENC:Array">
<i xsi:type="xsd:string">some_parameter</i>
</params_array>

Basically what is happening is that this is getting cast to an Object
[] on the Java side and then each element gets cast to a specific
class passed in by a string array following it.  But, Glue can't cast
anyType to String, for example.

Right now I can only seem to coax SOAP::Data into building me arrays
that have all the same type.  Any suggestions?  A quick search didn't
turn up anything similar.

Thanks in advance for your help.

Stephen

SOAP::Lite can do the same... or as you point out: should do that same.
Again, I see no impedement to getting a result from a server, and then
fetching a string value from somewhere in the the result, and passing it
through to Date::Manip to parse the date more effectively... or hell
writing my own regular expression like:

my ($year,$month,$day,$hour,$min,$sec,$ms,$timezone) = ($date =~
/^(\d\d\d\d)-(\d\d)-(\d\d)T(\d\d):(\d\d):(\d\d)(\.\d\d\d)?(Z|([+-]\d\d:\d\d))?$/\
);

Stephane Bortzmeyer wrote:
> On Tue, Apr 06, 2004 at 12:49:05PM -0700,
> Byrne Reese <byrne@...> wrote
> a message of 116 lines which said:
>
>  > A recent module to CPAN seems to help address the problem:
>  > http://search.cpan.org/~mcmahon/SOAP-DateTime-0.01/
>
> I know it and mentioned it in my first message. It only handles
> serialization, my problem being the deserialization.
>
>  > Bottom line, SOAP::Lite doesn't (since Perl is so loosely typed) do
>  > any type deserialization for you.
>
> I do not see the connection with my problem. Python and PHP are no
> more typed than Perl and both can deserialize xsd:dateTime (they just
> produce a string for a type they do not know, that I parse after). Why
> can't SOAP::Lite do the same?
>
>
> ------------------------------------------------------------------------
> *Yahoo! Groups Links*
>
>     * To visit your group on the web, go to:
>       http://groups.yahoo.com/group/soaplite/
>
>     * To unsubscribe from this group, send an email to:
>       soaplite-unsubscribe@yahoogroups.com
>       <mailto:soaplite-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>
>     * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>.
>
>

If I have a Perl web service like:
****************************************************
#!/usr/bin/perl -w
use SOAP::Transport::HTTP;
SOAP::Transport::HTTP::CGI
     -> dispatch_to('Temperatures')
     -> handle;
package Temperatures;
sub new
{
my $self = shift;
my $class = ref($self) || $self;
bless {_temperature => shift} => $class;
}
sub as_celsius
{
my $self = shift;
return $self->f2c( $self->{_temperature} );
}
****************************************************

and I am calling it like:

****************************************************
#!/usr/bin/perl -w
use SOAP::Lite;
my $soap = SOAP::Lite
     -> uri('http://blah.blah.com/Temperatures')
     -> proxy('http://blah.blah.com/cgi-bin/temper.cgi');
# accept Fahrenheit
my $temperatures = $soap
     -> call(new => 99)
     -> result;
print $soap
     -> as_celsius($temperatures)
     -> result;

How would I call this same web service using Coldfusion?

Any help is appreciated.

Mike

Stephane,

You saved me. The strace did the trick - I should've known that trick.
:) But I didn't. :/

Anyway - strace told me exactly where the permission problem was - there
were quite a few actually - and presto everything started working again.

Thanks again!
Byrne

Stephane Bortzmeyer wrote:

> On Tue, Apr 06, 2004 at 10:19:38PM -0000,
>  Byrne Reese <byrne@...> wrote
>  a message of 53 lines which said:
>
>
>>So the state of my system, which was once Redhat 7.3 running perl
>>5.6.1, is now running Redhat 9 (in theory), and perl 5.8.3
>
>
> RedHat, like FreeBSD, does not really support upgrades. It is probably
> better to reinstall.
>
>
>>When I run the script from the command line as ROOT it works. Ok, so
>>this naturally leads me to believe that I have a permissions
>>problem.  But where!?
>
>
> As non-root:
>
> % strace perl YOUR-SCRIPT.pl |& grep -i permission
>
> Should give you something like:
>
> open("/usr/lib/perl5/auto/Crypt/SSLeay/SSLeay.so", O_RDONLY) = -1 EACCES
(Permission denied)
>

Hi,

I'm trying to send a multipart/related SOAP message with an
attachment to a webservice (implemented in Java using Apache Axis).

(I know that this is not *officially* supported by SOAP::MIME but it
seems to be pretty close - read on).

The server croaks in trying to parse the message.

The reason, I found, was that the MIME::Entity uses "\n" as the
boundary delimiter and the Java code (Axis) expects "\r\n" as the
boundary delimiter.

If I fix the print_body sub in MIME::Entity as so, this actually
works:

=== start ===

foreach $part ($self->parts) {
    $out->print("--$boundary\r\n"); #Krishnan:added \r
    $part->print($out);
    $out->print("\r\n"); #Krishnan: add \r ### needed for next
delim/close
}

$out->print("--$boundary--\r\n"); #Krishnan: add \r

=== end ===

I *think* the MIME RFC requires CRLF - is there any particular
reason why MIME::Entity does not do this?

Regards.
Krishnan

I generated a custom SOAP::Lite client using stubmaker.pl and an
appropriate WSDL file.

What I want to do is to override the endpoint at runtime. I tried:

my $client = new GeneratedStub;
$client->proxy($url);
$client->servicecall(); # etc.

but it insists on using the endpoints that it saw in the WSDL. Is
there any way to override this behavior? Should what I'm trying even
be supported? Am I doing something wrong?

Regards,
Krishnan

Hi,

I'm trying to create an attribute of type xsd:dateTime using:

my $x = SOAP::Data->value($date)->type('dateTime'));

The error I get is:

Schema/namespace for type 'dateTime' is not specified.

I can use ->type('date') OK but this results in the server
(impelemented in Java using Apache Axis, by the way)
to ignore the time component of the attribute.

I'm using SOAP::Lite 0.55 (I think).

Any ideas?

Regards,
Krishnan

hi all,

I have released some ebXML perl modules (using XML::Xerces and/or
SOAP::Lite) as a proof of concept -- with a little hand-holding they can
ping a Hermes MSH succesfully.

I was hoping some other perl webservice developers might want to get
involved in getting a working perl ebXML MSH implementation working.

So far the classes have a lot of documentation, some examples and as
pointed out already have worked with Hermes for very basic communication.

the modules can of course be found at CPAN, they are ebXML and
ebXML::Message, you can also check out the (pretty basic) website at
http://droogs.org/ebxml/

cheers,

A.

--
Aaron J Trevena - Perl Hacker, Kung Fu Geek, Internet Consultant
AutoDia --- Automatic UML and HTML Specifications from Perl, C++
and Any Datasource with a Handler.     http://droogs.org/autodia