So if I'm running this via a daemon that runs in a mod_perl environment and
I access a service that does have WSS enabled (the code for accessing each
service is kept in different .pm modules; another module imports ::WSS but
this one doesn't), the importing of WSS will carry over to all the
instantiations of XML::Compile? That would explain the behavior...is there
some way to reach down to the writer and tell it to turn mustUnderstand off
when accessing a particular service? I've discovered that the presence of
the security header isn't the actual problem, it's that flag. I've been
messing around with opts_writers but haven't had any luck so far:
my $wsdl = XML::Compile::WSDL11->new( "TicketManagement.wsdl",
opts_writers => {
ignore_unused_tags => 1,
mustUnderstand => []
}
);
Thanks,
Rob Woodard
[email protected]
On Wed, Dec 3, 2014 at 2:04 AM, Mark Overmeer <[email protected]>
wrote:
> > I’m having a terrible time trying to figure out how to get the WSS SOAP
> > header out of my compiled client. For some reason, doing this:
> >
> > use XML::Compile::WSDL11;
> > use XML::Compile::SOAP11;
> > use XML::Compile::Transport::SOAPHTTP;
> > use XML::Compile::C14N::Util qw/C14N_EXC_NO_COMM/;
> > use XML::Compile::Util qw/pack_type/;
> >
> > my $wsdl = XML::Compile::WSDL11->new(“TicketManagement.wsdl");
>
> In above lines you are not loading ::WSS. I guess that another
> component of your program is pulling that in. Can you look for that?
>
> The use (only the use) of security headers leaks from one WSDL into
> the next.
> --
> Regards,
>
> MarkOv
>
> ------------------------------------------------------------------------
> Mark Overmeer MSc MARKOV Solutions
> [email protected] [email protected]
> http://Mark.Overmeer.net http://solutions.overmeer.net
>
>
_______________________________________________
Xml-compile mailing list
[email protected]
http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/xml-compile
