BEA purchases NitroX producer M7

Home

News: BEA purchases NitroX producer M7

  1. BEA purchases NitroX producer M7 (10 messages)

    At BEA World, BEA announced that they have acquired NitroX vendor M7 to "accelerate the delivery of BEA developer tools on the Eclipse Tools Framework."

    This fits in well with BEA's announcement earlier in the year to deliver WebLogic Workshop on the Eclipse framework, and BEA VP of product marketing Bill Roth commented that the two products will likely merge features (in "What does the acquistion of M7 mean to BEA?"). NitroX provides a set of plugins to provide JSF, JSP, and Hibernate capabilities to Eclipse, and BEA will have a development platform that is able to target a wide range of application servers, including Geronimo, JBoss, and WebSphere.

    Additional reporting can be found in BEA embraces Eclipse, acquires M7.

    Threaded Messages (10)

  2. BEA purchases NitroX producer M7[ Go to top ]

    I thinks it´s a good notice for Eclipse Project and BEA. It seems that BEA has avoided to be bought by Oracle or another big comany.
    That´s great for enterprise application server market.

    Joserra
    Najaraba(Modelos de Neocio basados en sw. libre)
  3. BEA purchases NitroX producer M7[ Go to top ]

    I thinks it´s a good notice for Eclipse Project and BEA.

    I'am not to unhappy about this either. Now there are two players that deliver the whole thing. I'am not such a great fan of the other player. I think nitrox is a much more inspired tool. Some tools are "designed" to much. I grew up in a city that was designed from scratch, man what a dump it became.
  4. NitroX and Spring[ Go to top ]

    NitroX/Eclipse purchase and Spring support are some great moves on the part of BEA. They are looking more and more developer friendly.
  5. BEA purchases NitroX producer M7[ Go to top ]

    Seems like they are listening to developers. BEA needs to come out with a strong Eclipse-based tools offering to support their 9,0 app server and value-added apps on top (portal, integration, and new esb). It will be compared to WSAD immediately. It has to be as good or better than what they have done with Workshop.

    I was expecting their initial Eclipse plugins to be buggy. This compenates.
  6. Vendor Lockin[ Go to top ]

    The only reason we chose not to use Weblogic Workshop is because it was non trivial to write pure j2ee code without including BEA controls.

    I hope they won't screw Nitro up.
  7. Vendor Lockin - where?[ Go to top ]

    Check out Apache Beehive and XMLBeans. BEA has opensourced all these Workshop value-adds (XMLBeans, pageflows, controls, web service annotations). These have been out for a while actually. EJBGen has been available for a while too. And there is always XDoclet. Workshop generates Ant scripts so you have no tool lock-in.
  8. BEA purchases NitroX producer M7[ Go to top ]

    Seems like they are listening to developers.

    yeah as the other doesn't and never will. I hope BEA will blow them away forever.
  9. BEA purchases NitroX producer M7[ Go to top ]

    Actually, Workshop is a great tool for building portals and integration application. In my opinion, its NOT a java IDE.

    With this acquisition, I guess BEA is trying to get some good eclipse developers who will port the Workshop framework to Eclipse. It would indeed be awesome to have features of both Workshop and Eclipse in the same IDE.

    But what does this mean for IntelliJ IDEA ?
  10. BEA purchases NitroX producer M7[ Go to top ]

    Actually, Workshop is a great tool for building portals and integration application. In my opinion, its NOT a java IDE.With this acquisition, I guess BEA is trying to get some good eclipse developers who will port the Workshop framework to Eclipse. It would indeed be awesome to have features of both Workshop and Eclipse in the same IDE.But what does this mean for IntelliJ IDEA ?

    Workshop 8.1 was about making J2EE easier, but it sacrificed portability to get there. It was also not based on Eclipse, which is what everyone now prefers.

    Since then we've made a few announcements about the Workshop strategy to overcome some of these hurdles.

    First, we put the Workshop framework into Apache under the project name Beehive so the source is available to anyone who wants it.

    http://beehive.apache.org/

    It's been ported to Tomcat and a few other app servers to show cross platform support.

    Second, BEA joined Eclipse as a strategic level board member is heading up the Web Tools project.

    Finally, with M7 and internally developed plug ins we will roll out a new version of Workshop that brings them all together into a single IDE, with support for Beehive, Spring, Hibernate, JSF, etc.

    The execs have been saying that support for non-WebLogic app servers will continue, so this should address the portability issue.

    Eric- BEA
  11. BEA purchases NitroX producer M7[ Go to top ]

    Workshop 8.1 was about making J2EE easier, but it sacrificed portability to get there. It was also not based on Eclipse, which is what everyone now prefers.

    IMHO the problem with Workshop was not that it was "not based in Eclipse". It was that the development team apparently did not believe that you need a solid editor framework to actually reap the benefits of the various features it offers. There was just too much impedance mismatch going between two different - very memory hungy - tools you essentially still needed to do anything meaningful. Now that apparently has been understood so I am looking forward of getting all the nice features of Workshop combined with a solid Editor (and a solid IDE). Actually I find it a bit sad that BEA jumped on the Eclipse bandwagon. I still think IDEA is a superior IDE and BEA embracing (or indeed buying) IDEA would have created a bit of more and more missed competition in the IDE space.