Re: Web Services, Flex and RPC Fault from complex types
Re: Web Services, Flex and RPC Fault from complex types
- Subject: Re: Web Services, Flex and RPC Fault from complex types
- From: Lachlan Deck <email@hidden>
- Date: Thu, 11 Oct 2007 07:18:06 +1000
On 10/10/2007, at 11:38 PM, Francis Labrie wrote:
Thomas wrote:
Thanks for your help, Francis.
It's true that the WSDL refers to EOGenericRecord but does not
define it:
<complexType abstract="true"
name="_Product"><complexContent><extension
base="tns4:EOGenericRecord">
I previously saw your article about SOAP serialisers, and must
confess I still don't understand how to use it after re-reading
it. I don't have any custom serialisers, so where would I put your
writeSchema() code fragment?
One thing you can try is to use Axis 1.0 instead of 1.1: IIRC, one
colleague got this kind of missing type definition using Axis 1.1.
Anyway, personnally I can't get WebObjects 5.3.x to use reliably
other Axis 1.1+, so I always use 1.0. To to so, you must replace
both files:
/Library/WebObjects/Extensions/axis.jar
/Library/WebObjects/Extensions/axis-ant.jar
I do the same as Mike, utilising simple classes that simply define
the properties I want exposed (no need for setters/getters, KVC does
it all on my end, and soap generates the getters/setters on the other
end).
However, I did find that to avoid the undefined type thing, I'd
generate the WSDL with Axis 1.0... but at deployment time (to
properly support attachments) utilising 1.1 worked whereas 1.0 was
problematic.
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden