[MOBY-dev] java api

Tue Feb 15 16:35:14 UTC 2005

Hi,

Ben and I just coded some methods that given certain inputs
create DOM elements, parse them, etc for Moby Objects. I
attached the javadoc for them to this message (ignore the
package name and we probably will rethink the method names,
but just as an example take a look). 

Is this something similar to what people would like for
services? I think that Ben is right and that we should
create some interfaces containing methods that people would
find useful and then we could code them. Right now I think
that there is an awful lot of code duplication.

Eddie

> -----Original Message-----
> From: moby-dev-bounces at portal.open-bio.org [mailto:moby-
> dev-bounces at portal.open-bio.org] On Behalf Of Benjamin
> Good
> Sent: Tuesday, February 15, 2005 8:16 AM
> To: moby-dev at biomoby.org
> Subject: [MOBY-dev] java api
> 
> Hi moby-dev,
> 
>  I think this from Simon sums up something that would be
> handy for
> everyone in the jMoby group - both client and service
> providers -(that
> hasn't written their own version already).
> 
> The
> > basic goal was to create some basic classes to simplify
> access to the
> > MOBY payload of a webservice call so that we could
> concentrate on
> > getting the services up rather than parsing the MOBY XML
> and rewriting
> > the XML prior to returning the result.
> 
> I don't really know the protocol here, but perhaps someone
> could post an
> Interface that others could check out, comment on, and
> code to?  Or
> perhaps some one already has a good solution?
> 
> -Ben
> 
> 
> ----------------------------------------------------------
> --------------
> 
> Subject:
> MOBY Service code developments
> From:
> Mark Wilkinson <mwilkinson at mrl.ubc.ca>
> Date:
> Tue, 15 Feb 2005 07:01:50 -0800
> 
> To:
> Ben Good <bgood at mrl.ubc.ca>, Eddie Kawas
> <ed.kawas at gmail.com>, mobydev
> <moby-dev at biomoby.org>
> 
> 
> I think both Ben and Eddie are working on things like this
> as well.  Ben
> is at a course doing "wet" work (ugh!) this week, but
> Eddie should be
> on-line somewhere.
> 
> Xref'ing with each other early on would probably be
> worthwhile - divide
> and conquer  :-)
> 
> I found in Perl that the code used by services was often
> identical to
> that used by clients, so I ended up putting these kinds of
> routines into
> a "neutral" location (MOBY::CommonSubs).  It's probably
> worthwhile
> considering that rather than coding service/client
> specific modules...
> if you haven't already.
> 
> M
> 
> 
> -- Mark Wilkinson Assistant Professor (Bioinformatics)
> Dept. Medical
> Genetics, UBC, Canada
> 
> 
> ----------------------------------------------------------
> --------------
> 
> Subject:
> [moby] Re: [MOBY-dev] BioMOBY developers meeting pre-
> announcement
> From:
> ywong at infobiogen.fr
> Date:
> Tue, 15 Feb 2005 09:18:47 +0100 (CET)
> 
> To:
> "Core developer announcements" <moby-dev at portal.open-
> bio.org>
> 
> 
> Hi,
>   I know that someone at mips (Octave Noubibou) is also
> working on that
> field, on my side, I have an API in Java (based on the
> Python API) that
> helps me to build moby webservices (with axis or j2ee)
> 
> 
> >> Hi Mark,
> >>
> >> I'll see how things are looking and get the
> documentation together. The
> >> basic goal was to create some basic classes to simplify
> access to the
> >> MOBY payload of a webservice call so that we could
> concentrate on
> >> getting the services up rather than parsing the MOBY
> XML and rewriting
> >> the XML prior to returning the result. We've been using
> Axis to handle
> >> the webservice part of the equation, we've created some
> core classes
> >> and have a simple test service prototype that we are
> gearing up to do
> >> something meaningful with. If you have people doing
> similar things it
> >> would be great to get an overview of what you are
> working on too so we
> >> can divide and conquer where possible.
> >>
> >> Simon.
> >>
> >>
> >> On Feb 14, 2005, at 10:04 PM, mwilkinson wrote:
> >>
> >
> >
> >>>> Hey Simon,
> >>>>
> >>>> Please post to the mailing list with your moby java
> activities since I
> >>>> have several people doing similar things - no point
> in duplicating
> >>>> effort if we can split the work  :-)
> >>>>
> >>>> I'll be posting the URL for the registration page
> before weeks end -
> >>>> I'm just waiting for a quote on the room rate.
> >>>>
> >>>> Cheers!
> >>>>
> >>>> M
> >>
> >>
> >> --
> >>
> >> Simon N. Twigger, Ph.D.
> >> Assistant Professor, Department of Physiology
> >> Medical College of Wisconsin
> >> 8701 Watertown Plank Road,
> >> Milwaukee, WI, USA
> >> tel: 414-456-8802
> >> fax: 414-456-6595
> >> AIM/iChat: simontatmcw
> >>
> >>
> >> --
> >>
> >> Simon N. Twigger, Ph.D.
> >> Assistant Professor, Department of Physiology
> >> Medical College of Wisconsin
> >> 8701 Watertown Plank Road,
> >> Milwaukee, WI, USA
> >> tel: 414-456-8802
> >> fax: 414-456-6595
> >> AIM/iChat: simontatmcw
> >>
> >> _______________________________________________
> >> MOBY-dev mailing list
> >> MOBY-dev at biomoby.org
> >> http://www.biomoby.org/mailman/listinfo/moby-dev
> >>
> >
> >
> 
> 
> _______________________________________________
> MOBY-dev mailing list
> MOBY-dev at biomoby.org
> http://www.biomoby.org/mailman/listinfo/moby-dev
> 
> _______________________________________________
> MOBY-dev mailing list
> MOBY-dev at biomoby.org
> http://www.biomoby.org/mailman/listinfo/moby-dev
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Triples.html
URL: <http://lists.open-bio.org/pipermail/moby-dev/attachments/20050215/ebf2cf98/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: MobyObjectPrimitiveExtractor.html
URL: <http://lists.open-bio.org/pipermail/moby-dev/attachments/20050215/ebf2cf98/attachment-0001.ksh>