Re: Problems deserializing EOGenericRecords via WebServices
Re: Problems deserializing EOGenericRecords via WebServices
- Subject: Re: Problems deserializing EOGenericRecords via WebServices
- From: LD <email@hidden>
- Date: Tue, 18 Oct 2005 05:34:42 +1000
Hi there,
On 18/10/2005, at 12:17 AM, Riccardo De Menna wrote:
I was wondering if someone could help me shed some light on a
problem that has locked me for a while. Let me first say I'm no
expert on the subject and I'm a bit lost as I can't find any viable
documentation to help me out.
I'm working on a client/server webservice app that needs to pass
back and forth various EOEnterpriseObjects. For what I've
understood, WO should be able to serialize and deserialize them out
of the box. But I keep getting an error that I don't seem to
understand. Everything else (Strings, Arrays etc) works fine... but
as soon as I simply define a method that returns a
EOEnterpriseObject descendant I get:
javax.xml.rpc.ServiceException: Error processing WSDL document:
java.io.IOException: Type EOEnterpriseObject is referenced but not
defined.
Reason: Error processing WSDL document: java.io.IOException: Type
EOEnterpriseObject is referenced but not defined.
at org.apache.axis.client.Service.initService(Service.java:278)
at org.apache.axis.client.Service.<init>(Service.java:193)
at org.apache.axis.client.ServiceFactory.createService
(ServiceFactory.java:232)
at com.webobjects.webservices.client.WOWebService.axisService
(WOWebService.java:185)
at
com.webobjects.webservices.client.WOWebService.createCallForOperation(
WOWebService.java:235)
at com.webobjects.webservices.client.WOWebServiceClient.invoke
(WOWebServiceClient.java:482)
at CalculatorClient.invoke(CalculatorClient.java:51)
at Main.calculate(Main.java:46)
As an example, my server app has a method like the following in the
WS registered class (forgive my lack of imagination :) :
public EOGenericRecord test() {
return new EOGenericRecord();
}
Random thoughts/guesses...
1) try the full package/class path: i.e.,
public com.webobjects.eocontrol.EOGenericRecord test() {...}
2) Would you have any better luck using the other constructor, where
you provide the class description. Is that what it means by being
undefined perhaps...
return new EOGenericRecord
(EOClassDescription.classDescriptionForEntityName("Author"));
3) Make sure the entity type is understood by the client app.
with regards,
--
LD
_______________________________________________
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