Ulrich Mayring wrote:
Now, compose has to go and be replaced with service. Other than that I don't see much to be done. What lifecycle extensions would I gain by switching to Fortress?lifecycle extensions are a new, advanced feature you probably don't need reading that sample code.
http://avalon.apache.org/excalibur/fortress/lifecycle-extensions.html
As you can see, my ECM usage is very simple. Is it even worth to upgrade to Fortress and possibly go from "very simple" to "moderately complex"?I don't think fortress is much more complex than ECM. However, if your usage of ECM is not really going to grow much, you probably just want to keep using it until there is some feature you need that ECM doesn't provide and another container does.
with open source, it should IMHO also be fun :DI don't think it is wise at this point to make business decisions incorporating the "grand unified container" (codename: Spearhead) yet, unless you're actively involved in its development (in which case you would of course know or at least influence what it will end up as :D).Well, my project is OpenSource as well, so the business decision is up to the developer team and there's no boss, who can fire us :)
Me, I like working with new tech, the latest generation of everything, as it means dialogue with the developer is usually more fun. If you let that one weigh in, you will want to switch to fortress and then spearhead, or if that's too much work keep ecm and switch to spearhead.
cheers!
- Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
