On Mon, Feb 28, 2011 at 04:36, Antoine Sabot-Durand
<antoine@sabot-durand.net> wrote:
Totally agree with Emmanuel. Having some kind of CMS "stub" would be a great asset for Seam. It's something that often lack in small project. In my shop the only answer to this issue is to build all these project that need a light CMS around a portal (mostly Liferay :-( ). It's overkill.
Perhaps it's beyond Seam mission, but I think that high level tools like a CMS, a wiki (what happened (or didn't happened) to wiki example in Seam 2 was very frustrating for me) or something original like Tohu can make the difference in a framework choice.
You should probably split this discussion off into a separate thread so it doesn't get mixed up with the topic at hand. I'll mention briefly here that the demise of Seam Wiki was largely because it was buried in the Seam 2 codebase. We've solved that problem universally by having independent module repositories and by not using the archaic subversion repo model.
In fact, if you want to start any CDI/Seam module/example/integration, you can do so by just setting it up anywhere in
github.com and saying "here's my module and it rules" and then we can assimilate you :) hehehe That's open source in it's truest sense.
-Dan