I believe this only happens when you start the server. So to fully redeploy
a set of beans, you must restart the server.
Ejipt offers dynamic bean reloading (only when running in standalone mode),
but it is only of the bean class(es), not the home and remote
implementations.
Ejipt also offers redeployment of all jars via command line and JMC, which
does a full regeneration, recompile and redeploy of the app. But again,
this process updates deploy.properties and runtime.properties, but does not
copy runtime.properties or any jars from deploy/ to runtime/.
Scott Stirling
Allaire Corporation
http://www.allaire.com/developer/jrunreferencedesk/
> -----Original Message-----
> From: Jay Walters [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 26, 2001 4:34 PM
> To: JRun-Talk
> Subject: Jrun Question
>
>
> What event triggers the movement of the properties files and
> ejipt_*.jar
> files from the deploy directory to the runtime directory? I made some
> changes to my config via JMC and wound up needing to copy the
> property file
> over by hand.
>
> Cheers
> Jay Walters
> NetNumina Solutions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
