From: Aplaws D. L. <apl...@li...> - 2009-05-24 11:30:02
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7407192 By: shawnlane I think the problem for APLAWS is it has been abandoned by Redhat. The original architecture suited Redhat, designed to make money from services support. It was never designed from the ground up as an open source solution, first it only had Oracle support for example and Resin as the application server, plus a proprietary build system and RPM deployments . By removing the need for Resin, Oracle, Perl and building like a normal JEE application then this is a good move. However I think it is too late. The outside world things are moving on, specifications for content repositories that APLAWS does not have for example. I know a number of local authorities are looking at WCM from another perspective, they need a product that can deliver their services and is supported more easily that APLAWS but has a minimum 5 year product life cycle. I think APLAWS does work and is good for content management, but it does not meet what end users are expecting in 2009. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |