
Hello Santini, 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... Additionally I posted a thread about the bad migration-design of the database. I didn't get any response... http://lists.otrs.org/pipermail/dev/2008-December/002027.html So in my opinion, as you are from the Java/Enterprise world, I would be very careful in investing time and money into a product, which potentially isn't able to migrate your data in a consistent way to the new version! I was using OTRS over nearly three years. Now I am migrating to RequestTracker, because I haven't found any JEE designed Ticketing System for my needs... best regards, Darko