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 development 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? If not, is there another way we should develop this middle-tier? =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant archives, FAQs and Forums on JSPs can be found at: http://java.sun.com/products/jsp http://archives.java.sun.com/jsp-interest.html http://forums.java.sun.com http://www.jspinsider.com
