Hugo Ahlenius wrote:
One thing that I found really convenient in BlueDragon.Net was that it is
very easy to cycle and refresh a .Net application, even from the command
line - one just need to update the web.config file that sits in the root of
every application.

Couple of ways to accomplish this--one of course being to leverage the ability of your chosen servlet container/JEE server to reload specific web applications without rebooting the whole server. I will add a "reload configuration" option to the admin console, but the functionality you're describing in BD .NET is, I believe, actually part of .NET, not part of BD, because .NET (this is my understanding anyway) watches for changes to web.config and reloads the application when changes are made. In that sense this would be similar to reloading through your Java server, although the level of integration between BD .NET and .NET is higher than the level of integration between OpenBD and the (compared to .NET anyway) wild west of the Java world.

There's nothing exactly similar with OpenBD because changes to the xml config file aren't automagically seen by every Java server on which OpenBD might be deployed, but the capability to reload from the admin console, which really means reloading through the admin API, is certainly simple to add.

--
Matt Woodward
[EMAIL PROTECTED]
http://www.mattwoodward.com/blog

Please do not send me proprietary file formats such as Word, PowerPoint, etc. 
as attachments.
http://www.gnu.org/philosophy/no-word-attachments.html

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to