What AOP really does for JBoss

I mentioned some time ago that i really like that the JBoss people were trying to do more than just implementing the J2EE standards. Too often people complain that open source is just copying existing stuff, and that there is no innovation in open source. So I’m glad to see JBoss trying to innovate.

However, I also know that out of ten so called innovations nine will probably fail, and only one will really prove worthwhile. And after reading this thread on the serverside, I’m not so sure JBoss’ so called AOP implementation is going to be that one worthwhile innovation. But i don’t want them to stop. They have to either be extremely successful, or fail misserably, but we need to get this sorted out. And when it proves to be a success, i guess it’ll end up in more EJB containers, and even the j2ee specs.

But i think for production environment i really don’t want to use a playground for innovative ideas, which means that i’ll probably look elsewhere for a production level j2ee server (jonas, openejb, apache j2ee/geronimo?)…

blog comments powered by Disqus