Hi Saminathan,

We are not looking at scheduler...

We have some existing batch programs - the business logic presently lies in
the Stored Procedure. We want to re-engineer the application so that some
part of it can be also used for online computation. Since the web
application is using J2EE platform we thought that it would be better if we
can re-devlop the batch component so that they are accessible from both
batch as well as online.

Regards,
Milind




                    Saminathan
                    Balasundaram             To:     [EMAIL PROTECTED]
                    <saminathan@HUGHE        cc:
                    STELE.COM>               Subject:     Re: Batch Programs
                    Sent by: A
                    mailing list for
                    Enterprise
                    JavaBeans
                    development
                    <EJB-INTEREST@JAV
                    A.SUN.COM>


                    11/13/2002 09:28
                    PM
                    Please respond to
                    saminathan






Milind

If am not mistaken,Is it some thing like scheduler?

 If you are interested in some kind of scheduler,there is a Component
called Quartz available
as an open source,you can down load from sourceforge.net.

Thanks and Regards
Saminathan.


----- Original Message -----
From: Joe Schell <[EMAIL PROTECTED]>
Date: Tuesday, November 12, 2002 3:33 am
Subject: Re: Batch Programs

> Milind Kulkarni wrote:
> >
> > We are in the process of developing a set of batch programs.
> Currently > all the batch programs are developed in Oracle PL /
> SQL and we
> > want to migrate them to Java environment. Has anybody worked on
> > the similar assignment? What are the major issues involved. It
> > would be great,  if somebody can point out some resources for
> > batch processing.
>
> To restate....
>
> You have a number of processes, written in some combination of stored
> procedures and perhaps straight SQL, which you are going to entirely
> re-write in Java and run outside of the database (ie not using "Java
> stored procedures".)
>
> Then I can think of one immediate and very obvious impact.
>
> Unless the existing SQL code is extremely inefficient your new
> code in
> Java will be significantly slower.  It would be hard to imagine it not
> being at least twice as slow.  It wouldn't surprise me if it is 10
> timesslower.  And it could be as much as 100 to 1000 times slower,
> dependingon exactly what you are doing and the amount of data that
> is involved.
>
>
========================================================================
===
> To unsubscribe, send email to [EMAIL PROTECTED] and include in
> the body
> of the message "signoff EJB-INTEREST".  For general help, send
> email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
>

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to