Well, fancy scheduling API's aside, the action could launch a process via
the JDK's Runtime.exec() method. You can pass that parms and properties.
-Original Message-
From: José Gustavo Zagato [mailto:[EMAIL PROTECTED]
Sent: Friday, September 05, 2003 1:11 PM
To: 'Struts Users Mailing
José,
This is really a system design question rather than a Struts
specific question so I've add the [OT] to the subject. I've seen an
implementation similar to what you're asking about. I'm not sure if what I
can contribute will help you with your situation.
Something to keep
Thanks !!
Your Answer was really helpful for me !!
José Gustavo Zagato Rosa
System Analyst - Atos Origin
[EMAIL PROTECTED]
-Original Message-
From: Steve Hall [mailto:[EMAIL PROTECTED]
Sent: sexta-feira, 5 de setembro de 2003 16:54
To: 'Struts Users Mailing List'
Subject:
You may go with Quartz.
Where in your actions you just get user input and stores it (by Delegator / DAO) to
Quartz table.
Or you can start / run new thread / class that has implemented Runnable interface.
That up to your business logic.
Best Regards.
Michael.
-Original Message-
From:
4 matches
Mail list logo
