Hi,
compilation caching is definitely on the "todo list", it's not as straightforward as
saving raw classes (the Orion JSP classes are dynamic in a sense) but it's
doable and will be done. Hang in there :)
/Magnus Stenman, the Orion team
(PS. Orion has been designed to "never (need to) be restarted", ie it should be
able to dynamically update anything, but we still agree that there's a need
for this features. DS)
----- Original Message -----
From: Darren Gibbons <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 07, 1999 1:49 AM
Subject: Caching of JSP files
> Hi all,
>
> I've downloaded and tested various versions of the Orion application server
> over the past couple of months, and I've been impressed with what I've seen
> so far. I've been primarily using the JSP + beans side of things.
>
> Most JSP engines I've used (JRun, Weblogic, GNUJSP) do a
> .jsp->.xml->.java->.class conversion to the .jsp file the first time it is
> accessed. Subsequent calls are much faster, because the engine can just
> pick up the compiled classes and run them, even after a reboot of the
> server.
>
> It doesn't appear that Orion saves these .class files to disk (at least I
> wasn't able to find them). Experience seems to back this theory up, as the
> initial lag the first time a .jsp file is run seems to happen every time the
> server is shut down and restarted.
>
> Is there an option I can set to save these files to disk?
>
> Thanks,
>
> Darren.
>
> PS Great to see the mailing list up and running!
>
> --
> Darren Gibbons [EMAIL PROTECTED]
> OpenRoad Communications ph: 604.681.0516
> Internet Application Development fax: 604.681.0916
> Vancouver, B.C. http://www.openroad.ca
