Re: designing simple scheduler
With a layered MVC application you can re-use beans outside of Struts. Have cron call beans application. I do. .V Raman wrote: Hello, I am using struts/beans in my application. I want a scheduler kind of thing that after regular interval of time should check the db and send mails. I want some suggestions regarding running it on red hat linux and way to go for this. Cheers, Raman Garg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: designing simple scheduler
Hi, search the mail archive. This thread was discussed about one or two weeks ago. Regards, Markus Hello, I am using struts/beans in my application. I want a scheduler kind of thing that after regular interval of time should check the db and send mails. I want some suggestions regarding running it on red hat linux and way to go for this. Cheers, Raman Garg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: designing simple scheduler
Vic, can you please explain a bit more how do you reuse your beans ? (and have cron job call yor application - you know the idea of separating layers, how is your architecture like now ?) (we would need something similar...) Thanks, M. -Original Message- From: Vic Cekvenich [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2003 6:29 AM To: [EMAIL PROTECTED] Subject: Re: designing simple scheduler With a layered MVC application you can re-use beans outside of Struts. Have cron call beans application. I do. .V Raman wrote: Hello, I am using struts/beans in my application. I want a scheduler kind of thing that after regular interval of time should check the db and send mails. I want some suggestions regarding running it on red hat linux and way to go for this. Cheers, Raman Garg - 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]
RE: designing simple scheduler
how to reuse beans? You should be making your beans without any thought of the web whatsoever. THEN your Actions can calls your beans. This way, the Actions are clients of your API. By having an API containing business logic (instead of business logic in your actions), you promote reuse. An additional benefit of this type of bean design is that you can test it automatedly (JUnit!) without having Tomcat or servlet container running. The Action, in this case, is the glue connecting all your business logic (beans). Replace the glue with another type of glue and you can reuse your business components anywhere. -Original Message- From: Voinea, Marina [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2003 9:19 AM To: 'Struts Users Mailing List' Subject: RE: designing simple scheduler Vic, can you please explain a bit more how do you reuse your beans ? (and have cron job call yor application - you know the idea of separating layers, how is your architecture like now ?) (we would need something similar...) Thanks, M. -Original Message- From: Vic Cekvenich [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2003 6:29 AM To: [EMAIL PROTECTED] Subject: Re: designing simple scheduler With a layered MVC application you can re-use beans outside of Struts. Have cron call beans application. I do. .V Raman wrote: Hello, I am using struts/beans in my application. I want a scheduler kind of thing that after regular interval of time should check the db and send mails. I want some suggestions regarding running it on red hat linux and way to go for this. Cheers, Raman Garg - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: designing simple scheduler
Turansky, Mark wrote: how to reuse beans? You should be making your beans without any thought of the web whatsoever. THEN your Actions can calls your beans. This way, the Actions are clients of your API. By having an API containing business logic (instead of business logic in your actions), you promote reuse. An additional benefit of this type of bean design is that you can test it automatedly (JUnit!) without having Tomcat or servlet container running. The Action, in this case, is the glue connecting all your business logic (beans). Replace the glue with another type of glue and you can reuse your business components anywhere. +1 You should be making your beans without any thought of the web whatsoever An additional benefit of this type of bean design is that you can test it +1 And to underline the obvios Struts is MVC implementation. The benefit of MVC is MVC layers. Then you can call your application (Yes, you can write console applications in Java, and re-use your Mail beans ) like this in bsh: while true do $JAVA_HOME/bin/java -classpath $CLASSPATH com.async.run sleep 100 done Else... you did not do MVC Struts... oops. hth, .V -Original Message- From: Voinea, Marina [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2003 9:19 AM To: 'Struts Users Mailing List' Subject: RE: designing simple scheduler Vic, can you please explain a bit more how do you reuse your beans ? (and have cron job call yor application - you know the idea of separating layers, how is your architecture like now ?) (we would need something similar...) Thanks, M. -Original Message- From: Vic Cekvenich [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2003 6:29 AM To: [EMAIL PROTECTED] Subject: Re: designing simple scheduler With a layered MVC application you can re-use beans outside of Struts. Have cron call beans application. I do. .V Raman wrote: Hello, I am using struts/beans in my application. I want a scheduler kind of thing that after regular interval of time should check the db and send mails. I want some suggestions regarding running it on red hat linux and way to go for this. Cheers, Raman Garg - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: designing simple scheduler
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? -Original Message- From: Turansky, Mark [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2003 9:57 AM To: Struts Users Mailing List Subject: RE: designing simple scheduler how to reuse beans? You should be making your beans without any thought of the web whatsoever. THEN your Actions can calls your beans. This way, the Actions are clients of your API. By having an API containing business logic (instead of business logic in your actions), you promote reuse. An additional benefit of this type of bean design is that you can test it automatedly (JUnit!) without having Tomcat or servlet container running. The Action, in this case, is the glue connecting all your business logic (beans). Replace the glue with another type of glue and you can reuse your business components anywhere. -Original Message- From: Voinea, Marina [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2003 9:19 AM To: 'Struts Users Mailing List' Subject: RE: designing simple scheduler Vic, can you please explain a bit more how do you reuse your beans ? (and have cron job call yor application - you know the idea of separating layers, how is your architecture like now ?) (we would need something similar...) Thanks, M. -Original Message- From: Vic Cekvenich [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2003 6:29 AM To: [EMAIL PROTECTED] Subject: Re: designing simple scheduler With a layered MVC application you can re-use beans outside of Struts. Have cron call beans application. I do. .V Raman wrote: Hello, I am using struts/beans in my application. I want a scheduler kind of thing that after regular interval of time should check the db and send mails. I want some suggestions regarding running it on red hat linux and way to go for this. Cheers, Raman Garg - 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] - 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]
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]
RE: designing simple scheduler
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]
RE: designing simple scheduler
This probably goes without saying, but in addition to being UI agnostic, your business logic should also be datastore agnostic. To be truly abstract, it should be as easy to move your backend from RDBMS to LDAP or XML as it is to move the UI from Web to GUI to Console. Ian Turansky, Mark [EMAIL PROTECTED]To: Struts Users Mailing List [EMAIL PROTECTED] rm.com cc: Subject: RE: designing simple scheduler 12/08/2003 11:05 AM Please respond to Struts Users Mailing List 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] This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
