By high level API I mean anything not machine generated. That could be classes that use biojava objects or a more humanized or smarter interface to the boilerplate code.
- Mark On 28 May 2009, 2:53 PM, "James Procter" <[email protected]> wrote: Hi All. Mark Schreiber wrote: > There was a recent discussion of generated code on the list. A good solutio... Just to clarify - by high-level API you mean the interface to the code that takes biojava objects as arguments and translates them into parameters for the service and vice versa for the results ? With regard to the recent(ish) discussion about modularisation in BJ3, I'd suggest that a module is created for each distinct WSDL containing the glue code for connecting BJ objects with the boilerplate code. The glue code implements factory methods to generate instances of appropriate BJ service APIs, which are defined in a core BJ module. This means that the WSDL + API implementation is decoupled from the BJ service API. Does that make sense (and/or am I simply stating the obvious here) ? Jim. -- ------------------------------------------------------------------- J. B. Procter (ENFIN/VAMSAS) Barton Bioinformatics Research Group Phone/Fax:+44(0)1382 388734/345764 http://www.compbio.dundee.ac.uk The University of Dundee is a Scottish Registered Charity, No. SC015096. _______________________________________________ Biojava-l mailing list - [email protected].... _______________________________________________ Biojava-l mailing list - [email protected] http://lists.open-bio.org/mailman/listinfo/biojava-l
