You should design objects that map your data, and return an array of them. In my opinion, to respect a good design principle, your web-service should call some kind of 'business service', and only this service should be aware of your data representation in the database, directly (using sql), or through a data mapping layer (tool or ejb entities). I generally build my web services as a j2ee endpoint ejb, over another internal business ejb that handles data. It's just my opinion...
-- Ephemeris Lappis >>> -----Message d'origine----- >>> De : Gregory G Carter [mailto:[EMAIL PROTECTED] >>> Envoy� : vendredi 18 mars 2005 18:39 >>> � : [email protected] >>> Objet : JDBC Service >>> >>> >>> Hello, >>> >>> I have Axis up and running, and have done some examples but I am >>> really interested to know how I can return a JDBC result set from a web >>> service, and what exactly is involved in the client end. >>> >>> Has anyone attempted to obtain result sets of JDBC queries from a web >>> service? >>> >>> -gc
