JRun 3.1 is not the same as JRun 3.01. Not sure if you're interested in
moving to JRun 3.1, but if you do (it's a free upgrade), you'll find that
developing web-apps is _much_ easier as everything is hot deployable and
redeployable.
Scott
> -----Original Message-----
> From: Haseltine, Celeste [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 02, 2001 11:32 AM
> To: JRun-Talk
> Subject: RE: bean newbie question
>
>
> Scott,
>
> We have never been able to get JRUN to reload a Java class
> bean dynamically.
> We have used both JRUN 3.0 and 3.01. Perhaps it is because
> we usually do
> not need to change the JSP that the bean is referenced in,
> only the bean
> class itself. Since we run into so many problems during development,
> particularly when uploading new/modified code to a
> development server, that
> I have made it a procedural requirement to delete all the
> compiled servelets
> from the Allaire/JRUN/server subdirectory, and restart the
> server when the
> weekly upload is made. This has allieviated many headaches
> for us and our
> testing department.
>
> If there is a better way to do this with JRUN 3.01, I would
> be interested in
> obtaining that information.
>
> Celeste
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
