[MOBY-dev] splitting jmoby.jar

[Paul Gordon]

Hi Ediie,

Actually, I write clients, and use org.biomoby.shared.extended to 
type-check data, so yes a client may need these.  In my Seahawk 
application (which uses Java 1.5), these are the MOBY directories I 
imported from src/main/org/biomoby:

./client
./client/rdf
./client/rdf/vocabulary
./registry
./registry/definitions
./registry/definitions/types
./registry/properties
./service
./service/generated
./shared
./shared/data
./shared/dom
./shared/dom/wrappers
./shared/parser
./shared/extended
./shared/schema

If we are really interested in making truly lightweight JARs available,  
I may be able to help, should go to Java 1.5 sooner rather than later.  
I've made uncommitted changes to several classes so that MOBY doesn't 
absoluely require having the tulsoft, JDOM and ebi JARs around.  Seahawk 
packs everything it needs to call MOBY Central and remote services into 
a 2.5 MB JAR file (including the relevant classes from Axis, Xerces, 
Xalan, Commons Logging, etc., etc.)...

Regards,

Paul


> Hi Martin,
>
> Most likely all of the classes in the package 
> 	org.biomoby.client.ui, org.biomoby.client.rdf, org.biomoby.registry are
> not needed by clients writing services.
>
> Classes in the package org.biomoby.shared.extended are used for parsing RDF and
> are probably no use to clients.
>
> Eddie
>
>   
>> -----Original Message-----
>> From: Martin Senger [mailto:senger at ebi.ac.uk] 
>> Sent: Thursday, April 27, 2006 5:33 PM
>> To: Edward Kawas
>> Cc: Moby Developers
>> Subject: splitting jmoby.jar
>>
>> Eddie (and others),
>>    I think about making more (splitted) jar files, not only 
>> jmoby.jar. I would like to have a lightweight version of 
>> jmoby.jar that can be used for biomoby service providers (for 
>> those implementing a moby service in a different directory 
>> etc.). For normal jMoby users this would not be any change.
>>    Could you perhaps identify what which from your packages 
>> do not need to be for those who are writting service 
>> implementation? I will then update the build.xml. (Look there 
>> and you will see I have in mind: search for
>> jmoby-dashboard.)
>>    Think also about how many of these new jar files (and 
>> which ones) you will need to move to taverna (together with 
>> the lightweight jmoby.jar, of course).
>>
>>    Cheers,
>>    Martin
>>
>> --
>> Martin Senger
>>    email: martin.senger at gmail.com
>>    skype: martinsenger
>>
>>
>>     
>
> _______________________________________________
> MOBY-dev mailing list
> MOBY-dev at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/moby-dev
>