> > I am also watching the SOAP discussions. It is funny to see, that > many > > people have same troubles with OTRS via SOAP. > > > > Wouldn't it be easier for everyone in the OTRS ML, if WSDLs for at > > least the > > rpc-example.pl would be available? > > I cannot imagine, that it is so complex under perl, to generate the > > standard > > WSDL, which could be uses for many other systems (.net, Java, C+ > > +, ...) > > > > Sorry for my really odd reaction, but this topic pop ups very often > > on this > > list and in my opinion without any solution. Wouldn't a WSDL > > corresponding > > to the rpc-example.pl be easy from perl to define? Every side would > > profit > > from this! > > I've been following this too. You probably need to read my previous > posts as to why it's not entirely trivial though. If it was, you'd > have already done it, right ;-) > > The example in the distribution creates a ticket number. I suspect > you're going to want to do something a little more than that (like > create a ticket or an article).
It would be easier for everyone if the existing code, in this case the rpc-example.pl, wouldn't be so magic. 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. 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. Best regards, Hans _______________________________________________ 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
