I think that, we are trying to implement the specification as a whole and indeed this specification is defined for using it in the Java EE 6.0 application servers or EJB 3.1 lite containers in Java SE environment. And I said before, one of the compelling requirement of the specification is that it must be the integrated functionality of the Java EE 6.0 servers. So somehow modularity depends on the how we integrate OpenWebBeans into the application server via SPI.
In fact, OWB will just define the SPI for the environment it runs, this maybe the java web server like Tomcat or full Java EE application server like GlassFish. For example, If the Tomcat does not depends on the EJB, it does not implement the EJB stuff SPI. we may think about the modularity after the M1 release in more detail. /Gurkan ________________________________ From: Mark Struberg <[email protected]> To: [email protected] Sent: Sunday, January 11, 2009 10:35:41 AM Subject: Re: WebBeans 'light' > (read the EG list. Funny to read, these days...) Yes, they _have_to_ take care about EJB because WebBeans (or whatever they finally may call it) also has to work in the most complex environment. But that should not hinder us from designing OpenWebBeans modulary. This would make OpenWebBeans much more versatile. Still more than 70% of the projects I know do NOT use EJB at all. And this are not only small projects. Sometimes it's easier to scale out (not scale up, but out (split of the concerns each server does)!) if you only have a thin layer which does exactly what you like. LieGrue, strub --- Matthias Wessendorf <[email protected]> schrieb am So, 11.1.2009: > Von: Matthias Wessendorf <[email protected]> > Betreff: Re: WebBeans 'light' > An: [email protected] > Datum: Sonntag, 11. Januar 2009, 3:38 > I like beeing not heavyweight, even if the "light" > term isn't > (eventually) not making it to the final spec. > (read the EG list. Funny to read, these days...) > > -M > > On Sat, Jan 10, 2009 at 11:45 AM, Mark Struberg > <[email protected]> wrote: > > Hi! > > > > I know the WebBeans spec is demanding either a full > EJB server or at least an EJB light container. > > > > But if someone (like me) likes to NOT use EJB at all, > and also no JMS, then WebBeans might still be very > interesting in combination with a small standalone servlet > engine like tomcat or jetty + JSF for the frontend + JPA for > ORM. > > > > What about this combination? Do we like to modularize > OpenWebBeans in a way that a scaled down approach would work > also? > > > > I'm not sure if this is possible without > infringing the spec or if this is implementable at all. > WDYT? > > > > LieGrü, > > strub > > > > > > > > > > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf
