Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!rt.uk.eu.org!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Jeff Higgins Newsgroups: comp.lang.java.programmer Subject: Re: application server, just without the "web" part... Date: Sat, 17 May 2014 07:42:40 -0400 Organization: A noiseless patient Spider Lines: 44 Message-ID: References: <53740063$0$303$14726298@news.sunsite.dk> <5376b6f0$0$297$14726298@news.sunsite.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Sat, 17 May 2014 11:45:40 +0000 (UTC) Injection-Info: mx05.eternal-september.org; posting-host="6b9e92482af47766954d85fb77d372f5"; logging-data="15685"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+cUVvydVy0DS5LrroINL1JF3OYp2ZCzPE=" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.5.0 In-Reply-To: Cancel-Lock: sha1:O0AbRqGKosAPPQxXWW3bXWUg1LE= Xref: csiph.com comp.lang.java.programmer:28518 On 05/17/2014 05:46 AM, Andreas Leitgeb wrote: > Arne Vajhøj wrote: >> On 5/15/2014 10:32 AM, Andreas Leitgeb wrote: >>> Arne Vajhøj wrote: >>>> On 5/14/2014 3:16 PM, Andreas Leitgeb wrote: >>>>> Startup-time still isn't exactly Java's strong point,... >>>>> I'd like to consider some kind of application server, that would >>>>> run the actual java-code of any number of jobs (of one user) in one >>>>> jvm, and with an "interface", that would only allow that one user to >>>>> start new jobs. >>>> Why not run beanshell and run the classes from that. >>>> $ java -cp wherebshis:whereyourstuffis bsh.Interpreter >>>> bsh% somepackage.SomeClass.main(null); >>>> bsh% somepackage.SomeOtherClass.main(null); >>> I googled and found http://www.beanshell.org/javadoc/bsh/Interpreter.html >>> I'm not yet sure if this will help me with separating multiple >>> jobs running at the same time, but it might help me in my process >>> of incrementally implementing what I need. >> >> Now I am confused. >> >> You worry about the JVM startup time - implying that it is >> somewhat significant compared to job run time. >> But you want to run multiple jobs in parallel - implying that >> jobs run for a long time. > > There are short jobs, long jobs eventually spawning short > jobs while running. > > In principle I could distinguish them beforehand and only > use bean-shell for the short ones (running them serialized). > > However, I'm not sure if I can correctly predict it in > all cases, so I'm looking for a general solution that > won't require me to distinguish. > It's starting to sound like OSGI to me. OSGI Standard Services Or even a Business Process Management platform | framework