"Online is just the icing." Right! The business logic of the application should be UI agnostic. The logic shouldn't know if it was invoked from a console application, a Swing gui app, or a web (Struts!) application. The business logic is (or should be) the same.
-----Original Message----- From: news [mailto:[EMAIL PROTECTED] Behalf Of Vic Cekvenich Sent: Monday, December 08, 2003 10:29 AM To: [EMAIL PROTECTED] Subject: Re: designing simple scheduler No, no that is not what we are saying. Just call the beans from your UI. In this case your UI is console. Same bean that you allready tested. Struts is the fastest way to develop that I know (15 years of IT for me) So your console app check the JavaMail and saves it or send it from db. Same beans and DB struts uses. So any mail shows up online. Batch/async is bread and butter of DP. Online is just the icing. .V Voinea, Marina wrote: > yes, calling APP layer API (beans) from the UI is OK. > I was thinking if it is possible the other way around : to somehow inform > the UI that soemthing happened on the backend and it has to display a > message accordingly. (kind of polling from UI to back end). The APP layer > bean triggering an event in UI application. Coud this be done? > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
