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 But true, there is currently no WSDL file for the OTRS core API (http://dev.otrs.org/ ) but you could without. @Santini: Maybe you can explain what you want to do and we can look for an example integration. What do you mean? -Martin -- ((otrs)) :: OTRS AG :: Europaring 4 :: D - 94315 Straubing Fon: +49 (0) 9421 56818 0 :: Fax: +49 (0) 9421 56818 18 http://www.otrs.com/ :: Communication with success! Address of record: Bad Homburg Local Court: Bad Homburg, HRB 10751 Tax number: 003/240/97505 Chairman of the Supervisory Board: Burchard Steinbild Executive Board: André Mindermann (CEO), Martin Edenhofer NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/

On 3 Apr 2009, at 13:50, Roberto Santini wrote:

Hi everybody, thanks for replay. I have spent the last two days trying to write a SOAP Java client for OTRS, but without result. All that I need to do is create new ticket and view the opened tickets from Java, only this. Can you help me?

Follow Martin's link to the OpenNMS intrgration. It does exactly that. There is wsdl included and it works with apache axis (_not_ axis 2). ... J

On 3 Apr 2009, at 15:05, Roberto Santini wrote:

On Fri, 3 Apr 2009 14:24:36 +0100, jonathan sartin

...

wrote:

...

Follow Martin's link to the OpenNMS intrgration. It does exactly that. There is wsdl included and it works with apache axis (_not_ axis 2).

... J Hi Jonathan, I have followed the Martin's link and I have downloaded the source files of OpenNMS. I have find the file OtrsTicketerPlugin.java, but all the classes required, like TicketServicePort_PortType and TicketServiceLocator, are not included into the project. So, how can I implement my own SOAP client?

You're right, the stubs are not included. They are generated by maven when you do something like an "mvn compile" in the project root directory. That's the whole point of wsdl, is it not? Look at the pom.xml file in the root directory for pointers, the wsdl2java goal is the relevant bit. Anyhow we're wandering off topic a bit ;-). You probably need to look at the apache axis documentation if you want to take this approach. It's all perfectly possible. Cheers ... J

On 7 Apr 2009, at 13:56, Roberto Santini wrote:

...

You're right, the stubs are not included. They are generated by maven when you do something like an "mvn compile" in the project root directory. That's the whole point of wsdl, is it not? Look at the pom.xml file in the root directory for pointers, the wsdl2java goal is the relevant bit. Thank you Jonathan, maven has generate all the stub classes and all work fine. Now I have one question for you. When I search one Ticket your module return it with +2 hours in creation time filed. Is possible to fix it in someway?

My first guess is that your default timezone when you invoke java is incorrect. Try setting that explicitly. Cheers ... J

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