[MOBY] Re: [MOBY-l] A Java web service problem

[Viji]

Hi Michael,

Wish you feel the best.

Below is the link that will take you to my posting (on Feb 10th in 
moby-l mailing list) on the sample java source code for registering and 
retrieving a moby compliant service.

http://open-bio.org/pipermail/moby-l/2004-February/000757.html

If this doesn't work, get back to me and I can send you.

Hope I can help you.

Regards
Viji
Michael Gruenberger wrote:

>Hi Mark and Martin and Viji,
>
>thanks for all your suggestions and sorry for the delay in getting back
>to you (I've been in hospital for the last few days).
>
>I have reset my service to output the XML as String (but without the
>CDATA, because it doesn't seem to make a difference). My service seems
>to be receiving the GOid's from MOBY, so I don't think the input is the
>problem. I haven't used AXIS monitor yet, but I'll give it a try in the
>next few days to see if there are any error messages (there aren't any
>in the error logs).
>
>Viji, do you mind sending me some example code you are using for your
>services, then I should be able to copy your style and adjust it for my
>service?!
>
>Cheers,
>
>Michael.
>
>On Thu, 2004-03-04 at 15:47, Mark Wilkinson wrote:
>  
>
>>my messages are encoded as:
>>
>>xsi:type = http://schemas.xmlsoap.org/soap/encoding/base64
>>
>>your messages are encoded as:
>>
>>xsi:type = http://www.w3.org/2001/XMLSchema/base64Binary
>>
>>That is likely the source of the problem.
>>
>>Interestingly, soap:base64 is defined as:
>>
>><xs:simpleType name="base64">
>><xs:restriction base="xs:base64Binary"/>
>></xs:simpleType>
>>
>>So it shouldn't *really* make a difference.  I might jot a quick note to
>>Paul Kulchenko later today to ask him if this is a bug in SOAP Lite, or
>>if the payload really does have to be defined by a soap encoding
>>data-type rather than directly as an XML Schema data-type.
>>
>>In the meantime, perhaps you should do as Martin suggests and switch
>>back to regular strings... interestingly, Viji's services pass their
>>output as 
>>
>>xsi:type=http://www.w3.org/2001/XMLSchema/string
>>
>>i.e. the SOAP Body data-type is defined by an XML schema, rather than a
>>SOAP encoding style, so it seems more and more like the problem we are
>>seeing is a bug in SOAP::Lite...
>>
>>Michael, can you put your services back to the state they were in when
>>you were passing your data as string so that I can look at the output
>>again?
>>
>>Thanks!
>>
>>Mark
>>
>>    
>>
>
>  
>