Hi Hans..
It would be easier for everyone if the existing code, in this case the
rpc-example.pl, wouldn't be so magic.
It's magic because SOAP::Lite clients can deserialise the messages
into a blessed hash that you can treat as an object on the client
side. So with SOAP::Lite on each end you have no need for wsdl so
long as you know your object's interface. Also in the absence of
interface or type information from Perl, there isn't a simple way of
automatically generating reasonable WSDL (or accurately setting the
types for the returned elements, come to that - SOAP::Lite will
guess, but it's often wrong). Anyway....
To be more precise, if someone could see the working rpc-example.pl
and the
corresponding WSDLs, the bootstrapping in the OTRS_SOAP-MyApp-
project would
be much much easier.
I agree. And if you hold on for a few days, I'll tidy up the work
that I have done on Tickets and Articles and let it loose for your
scrutiny ;-)
Therefore I suggest, to generate (e.g. manually) WSDLs for the
rpc-example.pl. All other WSDLs would be a nice to have and could
be done
later.
Hopefully this will help you in that respect too. But really,
properly formatting SOAP messages and WSDL for consumption by other
clients using SOAP::Lite is not trivial. Did you see this one:
http://www.pfconrey.com/programming/soap/interop.shtml
It's in the nature of Open Source projects to only gain capabilities
when someone needs them badly enough. I'm just traveling the same
path as you ;-)
Cheers ... J
_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
