Re: Java extensions directory vs Excel generation

[Evan Harris <auctionitis@xxxxxxxxx>]

There's nothing "cup almost empty" about just stating a fact.

I can see how just kicking off multiple separate java instances gets rid of
the class path issue, so i have no problem with your solution, but the JVM
startup for each of those instances is an expensive and unavoidable side
effect.

On Tue, Jan 23, 2018 at 9:37 AM, Richard Schoen <
Richard.Schoen@xxxxxxxxxxxxxxx> wrote:

> Well that would be the cup almost empty way of looking at it.
>
> Don't knock it until you've tried it and actually deployed production
> processes with it 😊
>
> Or you can.....
>
> Regards,
> Richard Schoen
> Director of Document Management
> e. richard.schoen@xxxxxxxxxxxxxxx
> p. 952.486.6802
> w. helpsystems.com
> ------------------------------
>
> message: 3
> date: Mon, 22 Jan 2018 20:23:42 +0000
> from: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
> subject: RE: Java extensions directory vs Excel generation
>
> So you're starting a separate JVM for every call.  Then you can certainly
> use whatever Java properties you want.  You'll also have to suffer thru the
> JVM startup everytime.
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD