This is a very specific situation - you have 2 heterogeneous databases, that can't be joined, right? I'm talking by my own little experience with this type of thing, it's best to you work with a search engine in a heterogeneous environment like yours. Something like Lucene is good (both Hibernate and Spring support it). Because, if you have to keep SQL to query this 2 databases, you'll have to write a DAO for each (TicketDAO and EmployeeDAO), and do the transactional stuff in your Business Object.
I hope that it could help you Rafael Mauricio Nami 2006/4/7, olonga henry <[EMAIL PROTECTED]>: > Rick, I am not trying to be an a**ss, but what he talked about is the most > basic stuff to any programmer. That's what I was pointing towards. Even > you > admitted later that you were replying without getting complete hold of the > subject matter. > "... although I wasn't following the thread that closely and missed about > the different databases. I'll just shut up and let smarter people > answer. (I will almost bet though that hibernate isn't helping the > situation.)" > Just wanted to know if other fellow programmers know of any good design > patters regarding this. > > > On 4/7/06, Rick Reumann <[EMAIL PROTECTED]> wrote: > > > > olonga henry wrote the following on 4/7/2006 11:33 AM: > > > Larry, person who talks about Spring, Hibernate and struts and know > > about > > > JTA certainly knows that a database is a collection of tables. > > > > You don't have to be an a**ss when someone is just trying to get > > clarification. Good luck getting help from people here. > > > > Man, what has this list come to these days:) > > > > -- > > Rick > > http://www.learntechnology.net > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > >
