no, we did a detour providing our own pojos that contain only serializable data and are handled by axis. before sending data to the client we copy values from cayenne-objects to our pojos using reflection. i did not like this approach, but it had the advantage, that we could easily strip out some data, that we didnt want to send to the user but internally using with cayenne.
-----Ursprüngliche Nachricht----- Von: Kevin Menard [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 7. Juni 2007 22:39 An: [email protected] Betreff: RE: Cayenne Generated Classes in Web Service API Hi Peter, > -----Original Message----- > From: Peter Schröder [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 07, 2007 11:45 AM > To: [email protected] > Subject: AW: Cayenne Generated Classes in Web Service API > > hi michael, > > we did some basic testing on sending cayenne classes via axis 1.4. > that didnt really work out, because persistent objects > provide references to unserializable objects. > i think that this might be handled by a custom > de-/serializer, but we did no further investigation. Did you try the XML encoder/decoder provided by Cayenne? This should make mapping data objects to XML fairly straightforward. -- Kevin
