JSTL SQL calls don't conform to MVC principles in any way at all.

I'd suggest creating a business manager service in Spring which has access to the two DAOs and having a Struts action call a single method on that business manager. This one sounds like read only, but if you have write operations, this allows you to use Spring's declarative transaction handling to integrate both databases into a single transaction.

hope this helps...

        Joe


At 4:09 PM -0500 4/6/06, olonga henry wrote:
Using Struts-Spring-Hibernate:

I have a situation where I have to fetch a list of records from a table
'Ticket' (in database 1) in which a column is a employeeId so my action
class calls the service layer which in turns calls the DAO layer to get the
"Certain Tickets List".

Now, there is another table 'Employee' (in database 2) which contains
employeeId and employeeName columns.  In order to display the list of
tickets with the employee names (in place of the employee Ids), I could have
done a join if both the tables were in one database, which I cannot do in
this case.

I can make JSTL SQL calls to database 2 - Employee table to find the names
at the view layer.  But I would like to know if there are better
alternatives out there which confirm to MVC principles.

Thanx


--
Joe Germuska
[EMAIL PROTECTED] * http://blog.germuska.com
"You really can't burn anything out by trying something new, and
even if you can burn it out, it can be fixed.  Try something new."
        -- Robert Moog

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to