Hi, I just noticed that there was something to replace SOAP::Lite, I believe one should give the XML::Compile::SOAP module a try. I have switched to a Java-based project about a year ago, so I have stopped to follow up on perl and soap services. Stil, I think we have enough perl competence here, fair enough at least to try to come up with something or at least give the BioMart programmers some feedback. But I do not know if external contributions to the BioMart would be welcome at the moment.
Best Am Mar 23, 2010 um 4:07 PM schrieb Leandro Hermida: > Hi, > > I agree I've used SOAP::Lite extensively and yes it can be a pain in the > neck. Development and improvements do continue with it though, 0.711 was > just released on CPAN the other day. > > Have you guys tried looking at XML::Compile::SOAP? It is a competitor and > replacement to SOAP::Lite and I think very good. I use it now over > SOAP::Lite for writing my clients and have been very happy with it. I would > recommend trying to write the BioMart SOAP server using it and related > modules instead. > > -L > > On Tue, Mar 23, 2010 at 3:31 PM, Michael Dondrup <[email protected]> > wrote: > Oh, > > it wasn't my intention to propose a re-implementation of the whole BioMart. > From a user's perspective it doesn't matter so much, that is true. > I believe too that asking for a re-implementation of an existing software > "just because" would not be such a good argument. > There are some arguments for both languages, and I think the actual BioMart > is doing fine in Perl, except the soap portion. > This might be because the SOAP::Lite module as fine as it was at its time, > is quite dated and there are some interoperability issues. > It is possible however to generate compatible messages with it but it takes > some expertise. > > The core advantage of Java over perl is for our use-case the availability of > several more developed SOAP implementations like > Axis2 or javaWS that allow for WS-I compliance and code generation. > > Maybe it is possible to replace only portions of the system? This depends on > how much work has already been done on the > Java code. Also I noticed that this is an open-source project and that it > could draw from many resources for the services implementation. > But I do not really know how community contributions are handled within this > project. So would it be possible to > get access to the sources, and provide patches if necessary? > > Best > > > > > Am Mar 23, 2010 um 2:30 PM schrieb Joachim Baran: > > > On 23 March 2010 12:42, Leandro Hermida <[email protected]> wrote: > >> [..] In my opinion the is no reason to change to Java other than > >> just because and this would be a shame. > > Perhaps Java is more suitable for larger projects from a software > > engineering point-of-view. There has been quite a lot of work being > > done on design patterns in Java -- as opposed to Perl's TIMTOWTDI. > > > > BW, > > Joachim > > > > -- > > B.1079 Michael Smith Building > > Faculty of Life Sciences > > The University of Manchester > > Oxford Road > > Manchester > > M13 9PT > > United Kingdom > >
