[MOBY-dev] bug report: jMoby Registry refers to default instead of accessing private

Edward Kawas edward.kawas at gmail.com
Mon Aug 10 13:58:39 UTC 2009


Hi Richard,

Are you running into this problem using MoSeS? You say composite MOBY
object, so does that mean you are using MobyComposite?

Did you try creating a Registry object that is primed with your registries
information?

Eddie

-----Original Message-----
From: moby-dev-bounces at lists.open-bio.org
[mailto:moby-dev-bounces at lists.open-bio.org] On Behalf Of Finkers, Richard
Sent: August-09-09 5:07 AM
To: moby-dev at lists.open-bio.org
Subject: [MOBY-dev] bug report: jMoby Registry refers to default instead of
accessing private

Hi All,

I am working on implementing an own moby client (based on the simpleclient
example / Java Moby API) in the backbone of my database system. For this, we
use a custom biomoby repository.

All goes fine (service lookup / service call) however in the default
situation I run into the following error while processing the XML:

Problem: org.biomoby.shared.MobyException: Attempted to build a composite
MOBY object from XML, but the tag (MeasurementSet) does not correspond to an
existing data type in the registry (default).  Please check the spelling and
capitalization of the XML tag, to match a registered data type.

This is logic since the object MeasurementSet was not registered in the
default (Calgary) registry but in our private project repository.

I was able to hack a work-around by changing the DEFAULT_ENDPOINT and
DEFAULT_NAMESPACE in the CentralImple.java class to the ENDPOINT and
NAMESPACE of my main (project) repository.

I was not able to trace back the origin of the bug (yet). Can any of you
help me with this?

Cheers,
Richard


_______________________________________________
MOBY-dev mailing list
MOBY-dev at lists.open-bio.org
http://lists.open-bio.org/mailman/listinfo/moby-dev




More information about the MOBY-dev mailing list