jhorcule, first of all thanks for insisting on "use strict" pragma. In every program, I make it a point to use "strict" and "warning" pragmas, Here I left it go somehow.

The modified "byName sub" in your server code, gave what I was looking for.
"Warn" also helped me to check the structure of the document passed to the server.

Regarding the custom serializer,I've implemented the serializer and deserializer on both client/server ends which looks as below:
#Client my $uri = 'Delivery'; my $serializer = DataSerializer->new; print $res->fault ? $res->faultstring. "\n" : $res->result; BEGIN{ package DataSerializer; @DataSerializer::ISA = 'SOAP::Serializer'; sub xmlize { my $self = shift; my($name, $attrs, $values, $id) = @{+shift}; $attrs ||= {}; # keep only namespace attributes for all elements my $a = $attrs->{xmlns} ? {xmlns => $attrs->{xmlns}} : {}; return $self->SUPER::xmlize([$name, $a, $values, $id]); } sub envelope { $_[2] = (UNIVERSAL::isa($_[2] => 'SOAP::Data') ? $_[2] : SOAP::Data->name($_[2])->attr({xmlns => $uri})) if $_[1] =~ /^(?:method|response)$/; shift->SUPER::envelope(@_); } } #End BEGIN block #SERVER SOAP::Transport::HTTP::CGI -> dispatch_to($uri) -> serializer(DataSerializer->new) -> handle; package DataSerializer; @DataSerializer::ISA = 'SOAP::Serializer'; sub xmlize { my $self = shift; my($name, $attrs, $values, $id) = @{+shift}; $attrs ||= {}; # keep only namespace attributes for all elements my $a = $attrs->{xmlns} ? {xmlns => $attrs->{xmlns}} : {}; return $self->SUPER::xmlize([$name, $a, $values, $id]); } sub envelope { $_[2] = (UNIVERSAL::isa($_[2] => 'SOAP::Data') ? $_[2] : SOAP::Data->name($_[2])->attr({xmlns => $uri})) if $_[1] =~ /^(?:method|response)$/; shift->SUPER::envelope(@_); } } #End BEGIN block
Do you think that the above serializer/deserializer is sufficient or any changes need to be made..

I also wanted to ask one question regarding the XMLschema . I'd like to change the schema definition to '2001', currently the generated SOAP envelope returns xmlns as '1999'.
Thanks once again for your suggestions.

In reply to Re^2: SOAP - Returning response from Server to Client request based on the <Action> by chanakya
in thread SOAP - Returning response from Server to Client request based on the <Action> by chanakya

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.