Apache Incubator OpenWebBeans M3 is Released

Discussions

News: Apache Incubator OpenWebBeans M3 is Released

  1. Apache Incubator OpenWebBeans M3 is Released (7 messages)

    This M3 release contains the parts of the specification that enables the developers to start and see more functional aspects of the JSR-299 than M2 release. Please look at the README M3 Release file to get more about release information. -------------------------------- OpenWebBeans M3 Release Features -------------------------------- - M3 Release Supports the followings ----------------------------------- * Managed Beans Support * Session Beans Support (via Embeddable OpenEJB container in Tomcat) * Producer Method Support * Producer Field Support * Java EE Resource Injection Support * JMS OpenWebBeans Support(OWB Specific) * Inheritance, Stereotype Inheritances * Specialization Support * Event Support * Decorator and Interceptor Support * Lookup and Dependency Injection Support * Java EE Plugin Support (via ServetContextListener interface) * Portable Integration Support This release also contains more sample applications including JMS and EJB usage with OWB. EJB is supported via embeddable Apache OpenEJB in Apache Tomcat. In addition to the implementation of the specification, the project aims to create a new set of Web Beans exposing functionality of other Apache Foundation projects. Feel free to ask any questions about the OpenWebBeans and M3-Release via our user forums. Download URL : ---------------- http://www.apache.org/dist/incubator/openwebbeans/ Project Main Site : -------------------- http://incubator.apache.org/openwebbeans/ User Forum : ------------------- openwebbeans-users at incubator dot apache dot org Developer Forum : ------------------- openwebbeans-dev at incubator dot apache dot org Wiki Page : ------------ http://cwiki.apache.org/OWB/ Blog Page : ------------ http://blogs.apache.org/OWB/ Gurkan Erdogdu OpenWebBeans Project
  2. org\apache\webbeans\context\type public enum ContextTypes { REQUEST(0), SESSION(1), APPLICATION(2), CONVERSATION(3), DEPENDENT(4); int name; ContextTypes(int name){ this.name = name; } public int getName() { return name; } public String getTypeName() { switch (getName()) { case 0: return "request"; case 1: return "session"; case 2: return "application"; case 3: return "conversation"; case 4: return "dependent"; } return null; } } How `name` can be an integer? What an purpose of switch if you can assign typeName in enum constructor? Saved on additional field in enum constant =)
  3. I have a doubt. Fron this: http://seamframework.org/WebBeans/WebBeansDevelopmentOverview the RI already has an Apache license. Why another implementation? What does the RI not doing right now? Regards
  4. Gabriel, A core value proposition for Java EE is that there are multiple compatible implementations available, each from a different group of people with different focus and characteristics. For example, Resin's implementation, CanDI focuses on a very small API with just basic DI capabilities, small foot-print and performance (mantras for Resin overall). We also expose all EJB annotations to managed beans that are not EJBs and will have some unique extensions of our own. Likewise, I imagine the Apache focus is on a development model that is based on an open source non-profit organization (which neither JBoss nor Caucho is) and exposing other Apache projects like Apache commons as JSR 299 pluggable extensions. Cheers, Reza ----------------------------------------------------------- Author, EJB 3 in Action Expert Group Member, EJB 3.1 and Java EE 6 Resin EJB 3.1 Lite Container Team Member
  5. Gurkan, Good work! It is especially good to see the OpenEJB/Tomcat integration. Are there any plans towards making this a pre-configured Java EE 6 Web Profile compatible stack? I think that would be a very compelling offering from Apache? Also, what other Apache projects are being exposed as extensions? Some part of Apache commons I hope? One interesting idea we are exploring in Resin/CanDI is exposing EJB annotations like @Lock, @TransactionAttribute, @Remote, @Schedule, @Asynchronous, etc into managed beans that are not EJBs. Do you guys have similar plans? Cheers, Reza ----------------------------------------------------------- Author, EJB 3 in Action Expert Group Member, EJB 3.1 and Java EE 6 Resin EJB 3.1 Lite Container Team Member
  6. Hi; Thanks a lot Reza. We have a plan to integrate OpenWebBeans into the Geronimo application server Java EE 6 Web Profile. For extensions that can be anything from any Apache projects like you said Apache Commons. We would like to implement some useful utility classes as managed beans that will be abstraction over those Apache Components. For example, implementing Http related managed beans on top of the Apache HttpComponents project, Log related managed beans on top of the Apache Logging, XML related managed beans on top of the Apache XML projects etc. OpenEJB + Tomcat + OpenWebBeans + OpenJPA + MyFaces combination are really killer and competitor for most of the Java Web Frameworks in the market :) Thanks again; --Gurkan
  7. Gurkan, I'll keep an eye on you guys and wish you the very best... Cheers, Reza ----------------------------------------------------------- Author, EJB 3 in Action Expert Group Member, EJB 3.1 and Java EE 6 Resin EJB 3.1 Lite Container Team Member
  8. OpenEJB + Tomcat + OpenWebBeans + OpenJPA + MyFaces combination are really killer and competitor for most of the Java Web Frameworks in the market :)
    Don't forget to throw Apache Harmony into that mix ;) It seriously sounds like a very interesting stack, but wouldn't OpenEJB + Tomcat + OpenWebBeans + OpenJPA + MyFaces 'simply' equal Apache Geronimo? Namewise, shouldn't MyFaces be called OpenFaces btw?