On Wed, 24 Jul 2002 07:25, Jason van Zyl wrote: > Is there any reason in particular things like Sevak go into Phoenix and > aren't just normal components?
No particular reason. I am not sure it uses any specific phoenix features at this stage. > I want a servlet container component but > I'm not running phoenix. Looking at it I could easily strip out phoenix > references and make it work in fortress or my tweety mutant. should be easy enough. > Is there any reason there couldn't be phoenix wrappers for things like > Sevak. Sevak in particular seems out of place because as something like > Sevak might be assembled into something larger to form an application > but isn't an application itself. Most phoenix specific components (most of cornerstone and apps) will eventually be merged back into excalibur as regular components. If you have a particular need for one of them then we can do it earlier rather than later. > Will the common metadata/containerkit work allow for there to be more > standard components? Yep. It is currently on hold until * xdoclet does a release * more of merlin/fortress is experimented with * Peter finishes up config/management stuff I have already converted all the cornerstone and a chunk of excalibur components (mainly the ones that were inherited from cocoon). I can upload the changes, however be warned that things are likely to change a bit and the process involves binding to xdoclet even though that is massively in flux. If you don't mind that I will upload as I have time (maybe sunday/monday). -- Cheers, Peter Donald *------------------------------------------------* | The student who is never required to do what | | he cannot do never does what he can do. | | - John Stuart Mill | *------------------------------------------------* -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
