The next version of dbXML (1.5) will be ported from the Juggernaut
server framework to Avalon. From a very high level, it looks like it
should be fairly easy, but I was wondering if anybody has run into any
gotchas porting between server frameworks.
I guess I am chief porter for the mo ;-)
Static is the killer. I guess only beginners make that mistake. No singletons needed for Avalon/phoenix.
Yes, it's read only. One day it will be updatable. For now, perhaps seperate logically into your own interal services (and one or more blocks that deliver than service). What you could do in one DbXmlConfiguration service (and it's DefaultDbXmlConfiguration block) is copy stuff from the read only Configuration (from assembly.xml) and write immediately to the persistence store. Charles' SimpleServer demo uses the persistence store. When the writable configuration arrives, you could change (hopefully) the block only. You et the functioanly you require immediately though.My one concern is the configuration system. Avalon's configuration interfaces seem to be read-only, but our server needs to maintain its own configuration on disk. Are there additional interfaces in Avalon for managing 'writable' configurations?
Also, is Tomcat 4 running on top of Avalon? I had heard rumblings to this degree, but can't confirm it from looking at the distro.
Not yet. Marketing campaign to begin soon....
Welcome aboard, by the way.
Regards,
- Paul H
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
