Discussions

News: Business Integration at ObjectWeb: Portal, CMS, BPEL

  1. James Niccolai wrote a story in InfoWeek about 3 new projects donated to the ObjectWeb code base:

    "The ObjectWeb Consortium added portal, content, and business process management elements to the stack of open source middleware projects it promotes, potentially providing businesses with access to cheaper technology, members of the group announced Tuesday.

    The three projects are an enterprise portal contributed by eXo Platform SARL; the Byline collaborative content management tool formerly known as Red Hat CCM, contributed by Red Hat; and MOBE, a business process execution engine with support for the BPEL (Business Process Execution Language) specification, developed by Dutch company eMaxx. ObjectWeb first announced plans to add MOBE to the software stack in September.

    ObjectWeb is probably best known for its involvement with Jonas, the open source J2EE (Java 2 Enterprise Edition) application server, but its work encompasses around 50 open source projects including workflow utilities and message-oriented middleware."

    Byline, the content management software contributed by Red Hat, is the result of years of experience developing data-centric web applications for enterprise clients.

    eXo Platform is an innovative open-source enterprise portal solution built on the top of the Java(tm) Server Faces (JSF) web layer, one of the first to implement the portlet API (JSR 168), receiving certification of compliance from Sun Microsystems in December 2003.

    MOBE (MidOffice BPEL Engine) is a business process execution engine compliant with the OASIS standard BPEL (Business Process Execution Language).

    http://www.infoworld.com/article/04/11/16/HNobjectweb_1.html

    Threaded Messages (5)

  2. eXo Platform[ Go to top ]

    Coming with that move we have released an updated release candidate named RC-OW which comes with many new features and bug fixes such as:

    * Enhanced forum portlet and mail portlet
    * Improve the configuration service to support values-param, value-param, properties-param, object-param. Move the default configuration to its own jar file and the admin can override the service configuration in the portal/WEB-INF/conf/configuration.xml
    * Relational database workspace container and repository manager for JCR (done)
    * Extension of the JCRExplorer portlet to visualised specific info from the JCR API (done)
    * Add the default LDAP implementation of organization service
    * And many moreā€¦

    For more details on the changes: http://www.exoplatform.com/portal/faces/public/exo/home/community/wiki?portal:componentId=wiki&portal:type=render&portal:isSecure=false&action=view&topic=Main.rc-ow

    We are currently working on upgrading the documentationn.

    And more links in the press:

    Press release
    * Business wire: http://home.businesswire.com/portal/site/google/index.jsp?ndmViewId=news_view&newsId=20041116005081&newsLang=en
    * InfoWorld x2: http://www.infoworld.com/article/04/11/16/HNexoplatform_1.html
    * NewsForge: http://trends.newsforge.com/article.pl?sid=04/11/16/063214
  3. Well done[ Go to top ]

    I benjamin,
    This is a great news, iv'e been watching your portal for a while and i love the architecture and double license scheme.
    Keep it up!
  4. Well done[ Go to top ]

    Thanks you,

    Have a look at the new release on ObjectWeb forge, the new multiportal instances configuration stuff is simply wonderfull :)

    Benjamin
    http://www.exoplatform.com
  5. Why you choosed Objectweb ?
  6. Why ObjectWeb[ Go to top ]

    Actually ObjectWeb was the natural choice for many reasons.

    -Middleware is becoming a commodity and vendors are now making more business revenues on higher level stacks such as Portal, CMS and BPEL; but the lower stack is also a necessity. So it was a natural choice for us to join ObjectWeb, and it was a natural choice for ObjectWeb to welcome us.

    -ObjectWeb executive commitee has a deep knowledge of the Portal and CMS market including all the standards in that field which we also promote. So we both had the same strategy and vison on where to go, how to get there and how to work together for the benefit of all the consortium members, and more important, for the benefit of our users (and customers for eXo Platform SARL).

    -ObjectWeb already contains one of the most extensive of Open Source midddleware projects including JOnAS, JORAM, c-JDBC and many more in the J2EE 1.4 space... with products at least as good as the JBoss ones for example and ahead Apache right now.

    -It is a consortium of institutions and companies which all together define the global strategy. Each company is then free to make the business it wants on top of the projects hosted there and get the support of the other members. This is clearly the difference between ObjectWeb and other OpenSource organisations such as Apache and JBoss.

    -The companies network is large and we have - as eXo Platform SARL - good commercial contacts with the consortium members.

    -The proposed license types are LGPL/GPL which is also our type of license.

    -All in one, it allows us to have a broader visibility and to offer an integrated application suite platform on top of ObjectWeb projects and to "feed" the community and its members. Of course the project will always stay modular and will not be tied to any particular application server.

    The ObjectWeb is now hosting the largest suite of J2EE components and is defenitely an alternative to commercial suite such as Oracle, BEA or IBM ones.

    Hope it answers your question.

    Benjamin
    http://www.exoplatform.com

    PS : another press link, http://www.ebizq.net/news/5348.html