Well I worked with WebObjects for about a year now and I recently switched
to jrun for another project.
In terms of beans and recompilation, here's my take on it:
(assuming that your beans are placed in /WEB-INF/classes for your
particular app)
- if you use the bean directly from a jsp page, tough luck - you
won't be able to reload the bean unless you restart the server
- if you use the bean in a servlet, you can reload it through this
not so obvious procedure: recompile or touch the servlet java file. This
will cause jrun to reload the servlet next time you use it and with it any
beans it uses
About "ChangeNotification" - that framework is needed in WO because WO keeps
this interesting object cache of all db rows that people requested. That's
why if an app modifies the db, it is necessary to let other apps that the db
changed and that their cache is not up to date anymore.
Jrun does not have this caching mechanism. All sql calls go directly to the
db (through jdbc) so any changes are visible immediately.
In terms of sessions, I don't know that much about them since right now I'm
only working on a single app. I am not sure how sessions are treated across
apps - my guess is that each jrun app would create its own sessions. Jrun
implements very closely the 2.2 servlet spec - so whatever is provided for
in there, jrun will do.
Cristian
------------------------------
>
> Date: Thu, 01 Feb 2001 08:40:33 -0700
> From: "Kimball" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: A few questions about Jrun vs. WebObjects
> Message-ID: <[EMAIL PROTECTED]>
>
> Does anyone out there have any experience with WebObjects and
> Jrun? We are
> currently using WebObjects to develop large scale web apps, but are
> considering other alternatives, namely Jrun. I have been
> playing with it
> for a few days now, and have a few questions:
> Is there a way to avoid the need to restart the default
> server whenever
> I re-compile a bean? It would be nice if I could somehow
> flush the working
> cache of the server, so that it would be forced to load the
> new version of
> my bean... But I have found none yet.
> In WebObjects, there is a framework called
> "ChangeNotification" that
> basically allows 2 separate apps to use the same database, and not get
> confused... App 1 can save new data to a table that app2 is currently
> looking at, and app2 will automatically know about the new
> data, and it will
> be accessible real time. It also keeps the 2 apps from
> overwriting data in
> the db. Is there a way to do such a thing in Jrun? We use
> Oracle for the
> db.
> Session tracking in WebObjects is very robust. With it,
> you can have a
> user enter an app, invoke a session, get directed to another
> app, invoke
> another session, then return to the first app, and still have
> their session
> active... all cookieless. (for example, an online bookstore that has
> different apps for the different sections of the store...
> mystery, fiction,
> non-fiction etc.. all have their own session tracking info,
> but the main
> session from the master app follows the user around effortlessly.
> WebObjects does this with tracking at the session level and at the
> application level.... anyone know how to do this in Jrun?
> Will the session
> beans that I have been reading a little about do it?
>
> Thanks in advance for any help anyone can provide.
>
> -Kimball Larsen
>
>
>
> Click HERE to get this card For your own FREE card, click here
>
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Structure your ColdFusion code with Fusebox. Get the official
> book at http://www.fusionauthority.com/bkinfo.cfm
>
> ------------------------------
>
> End of JRun-Talk-List V1 #119
> *****************************
> Archives: http://www.mail-archive.com/[email protected]/
> Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
>
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
