[jboss-user] [JBoss Seam] - Dropping clean MC support was a Bad Thing :(

przemjaskier do-not-reply at jboss.com
Mon Jul 9 08:11:49 EDT 2007


After struggling with 1.3->2.0 migration for couple of days (no success) I want 
to share my objections on last Seam changes. I admire Seam team work and am working with the bleeding edge versions of Seam since a long long time. 
Forgive me if I'm sounding a little bit harsh and disappointed, but I am recently frustrated by the changes I see.

Env: Apache 6.0.13.

Having MC support I could:
1. Create my own, custom Microcontainer bootstrap class, feeding it with hand-picked, programmatically-defined xml bean descriptors, creating two separate flavours "test" and "production". It could be simply bootstrapped no matter of environment, servler container or not. Small, robust, elegant.
2. Can run advanced test harness without relying on deployers magic, totally out of a servlet container.
3. Microcontainer was a small, almost-clean jar, and it's classpath dependencies were rational and manageable.
4. You can have best-of-breed integration of JBoss managed datasource, JTA etc. with clean, well-grained configuration.

Now, the Embedded approach.. geez...

1. You got a 13 MB ball with a chain - is you look into it's contents it looks like a pure mess... What is the idea of having such "all" tarBALL with some magic and esoteric versions of half of the javax.* APIs dropped into it. Come on, it's Maven time now...
2. Even if I know that there is an old-good MC beneath all these things, it has been obscured by a mass of deployment descriptors and redundant dependencies.
3. JBossE is in beta stage, almost undecummented(???) and all optimization
hinst provided here http://www.jboss.com/index.html?module=bb&op=viewtopic&t=111734
are nothing comparing to the ability to selectively spawn selected services as it was possible in Seam 1.x.
It's not the case of blubbering about "lightweightness" of anything... It's about creating clean, robust and manageable development/production platform with Seam.

With MC I could have simple, small,  manageable JTA environment for Seam, and was thinking about migrating to JBoss AS someday, when the phase of rapid development of my application ends... 
I would prefer my previous MC-driven setup, even trying (with no success) to get Spring-bound Postgres DS + Spring-bound Hibernate SessionFactory to work with Seam 2.0 like posted here:

I've invested in my project a lot of time and hoped for a stable Seam environment for a long-running development process... Now I'm a little bit confused :(.

Best regards,

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4061948#4061948

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4061948

More information about the jboss-user mailing list