|
Hi Ross,
Thank you for the response. There will be
predefined database queries but I don't think we want to expose the database
schema to the front-end developers. I think that most of these developers
will be more focused on the html rather than the database schema so we want to
make it as simple as possible for them to access the database. Note that
there will be database queries selecting data from the database and database
insert and update commands. But I think we want to shield all the SQL
statements from the front-end developers.
Dave
----- Original Message -----
Sent: Wednesday, May 05, 2004 11:41
AM
Subject: RE: question about database
result sets...
It
occurs to me that that EJBs were created to address exactly what you
describe. Though you could also use a web service as
well. The key item you leave out is, are the database queries
random queries or are they pre defined?
I am working with a software company that
develops in Java. Some of the functionality involves interaction with users
via the web. Some clients that use the software product would only
like the back-end code and would like to implement the look and feel of
their website on their own. In this case, we would like to provide a
middle-tier set of classes to "hand off" code to other developers at
clients.
I'd like to figure out the best way to implement
this middle-tier between back-end database processing and front-end GUI
code. The question is whether Axis is the proper tool.
More specifically, does Axis provide a way to
easily handle displaying, modifying and deleting data returned from a query
to a database where the query returns more than one row; i.e., a result
set? We would develop a middle-tier that would be responsible for
getting the data from the database and then returning it but then a
developer at a client would be responsible for displaying the data.
Because of this "hand off" we are looking for a smooth and easy
interface. Does Axis provide this type of easy
hand-off?
|
