I'm probably going to make a few enemies here... Our company is actually considering moving away from Torque in favour of a JDO compliant persistence layer. There are several to choose from, and having a standard interface has very important advantages which I think we're all aware of.
We have been using standalone torque for several months without too many problems. The only major issue is memory problems with large datasets, but I believe that will be addressed in the next beta. If I started a new project however, I would not use torque. BTW, Castor is also not JDO compliant, despite the use of the acronym JDO. Have you evaluated any other persistence layers? I'm not aware of any open-source JDO compliant tools, but the costs of the commercial products is very small compared to the price of choosing the wrong product. The OJB jakarta project looks good, although according to the website is moving towards JDO compliance but is not quite there yet. Back to your original question, I think it sounds like a good concept, but axis is not even at the stage yet of interfacing directly into any existing classes, let alone torque classes. The persisted classes specified by JDO only have to implement a certain interface instead of having to extend a class as required by torque, which would make it much easier to implement. Martin Jericho ----- Original Message ----- From: "Andreas Leitner" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 09, 2002 2:40 AM Subject: augment torque schema with soap info ? > Hi, > > I recently stumbled over Torque. Although I have not tested it > extensivly, to me it looks like the one persistency layer I always > wanted. Looks like you did an awesome job guys! > > Now, what I would be interested is the following: > > A Schema file that servers three (or better four :) purposes: > *) Skeleton bean generation (Torque does it) > *) Serialiser for bean to DB > *) Serialiser for bean to to SOAP > *) Serialiser for bean to SOAP 2 (let me explain :) > > I'd like to build the following scenario: > > | DB | <-> | Java MiddleWare with Buissness Logic | <---SOAP---> | .NET > client| > > *) Which means the data is stored in a DB > *) It is retrieved and processed by a Java Application (probably an Axis > thingy) > *) A .NET client talks to the Axis thingy and visualizes the data, > allows modifications to the data and sends that data back to the Axis > server, which in return processes it and stores it in the DB > > > Now, if I would augment the tourque schema file with custom attributes > and elements that specify what and how to send the beans it already > generates over the wire, I could write my own generater which would > generate the neccessary client and server side proxies. The torque > generater I assume will gladly ignore my additional attributes and > elements. > > > Does that sound reasonable? > > > Also have there been non-Turbine projects completed who use Torque? How > stable is it at the moment? > > many thanks in advance, > Andreas > > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
