Hi Mark;
* "WebBeans specification defines two runtime environment , Java SE environment via the "EJB Lite Container" and "Java EE" Application Server environment. Current specification says that implementation of the specification must be the integrated functionality of the Java EE Application Server.". Currently OpenWebBeans RI is written as plug-in model,(user have to manage configuration via ServletContextListener, Filter etc. in the web.xml), not an integrated functionality of the application server such as JBoss did. But we will talk with the Geronimo folks to integrate RI into the Geronimo Server runtime via our provided SPI that it has not done yet. * Currently OpenWebBeans RI does not support EJB and JMS WebBeans. 2- You are right. In fact we will able to expose some SPI as an extensions to the RI. One of the such an extension will be the "JNDI Naming Context" interface. For example, if user wish to use OpenWebBeans RI in Tomcat or his environment, he has to implement such an extension via SPI and configures the OpenWebBeans RI to use it, instead of using the default. For the time being RI implementation just binds the "javax.webbeans.Manager" object into the InitialContext as default. 3- OK. 4- You could definitely help on RI whatever you want to work on, lots of open slots are waiting for us :)) /Gurkan From: Mark Struberg <[email protected]> To: [email protected]; Gurkan Erdogdu <[email protected]> Sent: Tuesday, January 6, 2009 12:52:01 PM Subject: Re: CodingStyle question Hi Gurkan! ad 2) I know the JSR-299 spec says that WebBeans need at least an EJB lite container, but I personally don't see the point for this until now. Can't we simply store the Manager somewhere else if the InitialContext is immutable? Sure, there will be no EJB (and JMS) handling if we're running in this 'mode', but on the other hand this would make it a really lean solution with a small footprint. Gavins implementation is currently tied to JBoss (and later to other full J2EE servers), but what about a 'basic' solution? This comes down to whether OpenWebBeans is aimed for tomcat or for geronimo? ad 3) I'll debug through the tests. Maybe this is also due to the missing libraries. If I found them, I'll add them to the pom and provide the patch. LieGrue, strub ---------------------------------------------------------------- “Multiple exclamation marks are a sure sign of a diseased mind!” (Sir Terry Pratchett) --- Gurkan Erdogdu <[email protected]> schrieb am Mo, 5.1.2009: > Von: Gurkan Erdogdu <[email protected]> > Betreff: Re: CodingStyle question > An: [email protected] > CC: [email protected] > Datum: Montag, 5. Januar 2009, 20:55 > Hi Mark; > > Thanks for interest in OpenWebBeans and welcome :) > > As for errors, > > 2- Tomcat Context binding is read only, so you got > exception while binding Manager into the JNDI. But I > corrected this, instead of throwing exception, I simply logs > the error message. So, now it must be run smootly on Tomcat. > But for Tomcat or other not Java EE appliance application > servers, you have to include necessary Java EE jars, i.o.w > > WEB-INF/lib must contain the > > - JSF libraries and its dependencies > - JSF Facelet library > - webbeans-api > - webbeans- impl > - dom4j > - geronimo-ejb_3.0_spec-1.0-M1.jar > - geronimo-interceptor_3.0_spec-1.0.1.jar > - geronimo-jpa_3.0_spec-1.1.1.jar > - geronimo-jta_1.1_spec-1.1.1.jar > - javassist-3.8.0.GA.jar > - jsr250-api-1.0.jar > - log4j-1.2.14.jar > - scannotation-1.0.2.jar > > I also committed the log4j.properties to the > "samples" project src/main/resource to get logs > messages correctly. > > 3- Tests seems to be ok in my local.(Ubuntu 8.04, > jdk1.5.0_15-b04) > > Gurkan Erdogdu > > > > > > > ________________________________ > From: Mohammad Nour El-Din <[email protected]> > To: [email protected] > Sent: Monday, January 5, 2009 3:45:29 PM > Subject: Re: CodingStyle question > > Hi Mark... > > Thanks for your interest in OpenWebBeans :-). For the > coding > standards you can it here You can find our coding standards > here > http://incubator.apache.org/openwebbeans/eclipse-formatter.xml > . For > the errors I will check them max by tomorrow to see if I > have the same > errors on my machine. > > On Mon, Jan 5, 2009 at 2:51 PM, Mark Struberg > <[email protected]> wrote: > > Hi folks! > > > > First of all a big hands up for OpenWebBeans! > > > > I'm following this project since Matze made the > announcement on the myFaces list a few months ago and > I'm happy that the source finally found the way to the > official apache repo. > > > > Long story told short: > > 1.) what coding style will you use? Which tabsize, > spaces only, etc? Maybe we'll provide an idea and > eclipse prefs.xml? > > > > 2.) what appsrv are you testing your samples with? I > tried tomcat-6.0.14, tomcat-6.0.18 and jetty-6.1.14 and got > the following exceptions: > > jetty: > > 2009-01-05 13:15:24.018::WARN: Failed startup of > context > org.mortbay.jetty.plugin.jetty6pluginwebappcont...@13f4cf6f{/guess,/home/msx/develop/java/backwork/openwebbeans/samples/guess/src/main/webapp} > > > org.apache.webbeans.exception.WebBeansDeploymentException: > org.apache.webbeans.exception.WebBeansException: Unable to > bind object with name : java:comp/Manager > > at > org.apache.webbeans.config.WebBeansContainerDeployer.deploy(WebBeansContainerDeployer.java:110) > > ... > > Caused by: javax.naming.NamingException: This context > is immutable > > at > org.mortbay.naming.NamingContext.bind(NamingContext.java:324) > > at > org.mortbay.naming.NamingContext.bind(NamingContext.java:397) > > at > org.mortbay.naming.NamingContext.bind(NamingContext.java:417) > > at > org.mortbay.naming.java.javaRootURLContext.bind(javaRootURLContext.java:124) > > > > > > tomcat-6.0.18: > > SCHWERWIEGEND: Exception sending context initialized > event to listener instance of class > org.apache.webbeans.servlet.WebBeansConfigurationListener > > > org.apache.webbeans.exception.WebBeansDeploymentException: > org.apache.webbeans.exception.WebBeansException: Unable to > bind object with name : java:comp/Manager > > at > org.apache.webbeans.config.WebBeansContainerDeployer.deploy(WebBeansContainerDeployer.java:110) > > ... > > Caused by: javax.naming.NamingException: Context is > read only > > at > org.apache.naming.NamingContext.checkWritable(NamingContext.java:903) > > at > org.apache.naming.NamingContext.unbind(NamingContext.java:243) > > at > org.apache.naming.NamingContext.unbind(NamingContext.java:282) > > at > org.apache.naming.SelectorContext.unbind(SelectorContext.java:241) > > at > javax.naming.InitialContext.unbind(InitialContext.java:416) > > at > org.apache.webbeans.util.JNDIUtil.unbind(JNDIUtil.java:79) > > > > > > > > 3.) Just to make sure I'm working with the right > environment: currently a few tests do fail on my machine > (Fedora10, sun java x86_64 1.6.0_12-ea-b03): > > Failed tests: > > > testAroundInvokeWithSameMethodName(org.apache.webbeans.test.unittests.exception.ExceptionComponentTest) > > > nameSpacesNotDeclared(org.apache.webbeans.test.unittests.xml.XMLFieldTest) > > > testMultipleInterceptedComponent(org.apache.webbeans.test.unittests.intercept.EJBInterceptComponentTest) > > > testInterceptorWithSuperClassComponent(org.apache.webbeans.test.unittests.intercept.EJBInterceptComponentTest)
