On 3 Apr 2009, at 09:58, Martin Edenhofer wrote:
Hi Santini, hi Darko,
On Apr 3, 2009, at 10:09 , Palic, Darko wrote:
I was a coach of a student research project for connecting OTRS to our Java application. http://www.mail-archive.com/dev@otrs.org/msg01859.html
The conclusion of the work is, that OTRS uses a prorietary SOAP solution. It has nothing to do with the webservice standard! Matter- of-fact is, that we had to implement our own OTRS-SOAP client. Our tries to define a WSDL for the needed OTRS services failed. The cause was the very unusual way to communicate with the OTRS- Webservice. E.g. you have to do multiple SOAP-calls to get one business transaction...
OTRS is using the perl standard SOAP module SOAP::Lite (http://search.cpan.org/~mkutter/SOAP-Lite-0.710.08/lib/OldDocs/SOAP/Lite.pm ). This is also used for Perls Salesforce oder SAP SOAP communication.
So I would say this is no prorietary SOAP solution. :)
There is also a other solution which is using OTRS and Java via a SOAP interface. See als http://www.opennms.org/index.php/OTRS_Integration
OK, so here's my two pence worth. IT's true that SOAP::Lite does not by default return data formatted according to a standard SOAP schema. This is an issue if you're using something like Apache Axis as your SOAP client. There's a lot of discussion about this out there on the net. The fact is that SOAP::Lite is showing it's age somewhat. It is perfectly possible to get it to play nicely with other SOAP clients, but you've got to be prepared to do some work on the server side to make up for SOAP::Lite's shortcomings. It's a bit harsh to lay the deficiencies of SOAP::Lite at OTRS's door though ;-) Cheers ... J