jbi4corba release 0.7.3 - fixes and easier ORB config

Discussions

News: jbi4corba release 0.7.3 - fixes and easier ORB config

  1. Jbi4Corba is a JBI compliant Binding Component. It allows to map a CORBA service as an internal JBI endpoint. This is simply done by deploying into a JBI ESB a service unit containing the IDL defining the CORBA service, no coding is required. Having an internal JBI endpoint opens a wide spectrum of possibilities because the endpoint can participate to the message streams and the orchestrations that take place inside the ESB. For example the endpoint could be externally exposed as a SOAP/HTTP Webservice. This release is mainly a bugfix release. We have one new important feature: the addition of a jacorb shared library. The component uses this library when jacorb is configured as the ORB to be used, so there's no need to install jacorb runtime in the ESB libraries. The shared library is mandatory even if jacorb is not used. So please remember to install it before installing the component. please find more information on jbi4corba website: http://jbi4corba.sourceforge.net/ or on OpenESB web site http://wiki.open-esb.java.net/Wiki.jsp?page=CORBABC Message was edited by: staff
  2. 1. its corba related 2. its still version 0.x.x Yawn ! :0
  3. It's a nice option for integrating legacy systems into modern Java environments. Who cares about the version numbers as long as it does the job? Armin Wallrab, SOPERA GmbH
  4. It's a nice option for integrating legacy systems into modern Java environments. Who cares about the version numbers as long as it does the job?

    Armin Wallrab, SOPERA GmbH
    There are many ways to integrate legacy systems into java systems and Corba isnt just the one. Corba is rather the solution from last decade. And you seem to be ignorant of the fact that version numbering has been used to reflect the quality and stability of a product for a long time. so dont try to show off that version muber doenst matter, IT DOES and always will to most normal people. On the other hand if you claim that quality of this software is and can "get the job done", then why not call it version 1.0. ????? why not follow the industry standard ? Anyway .. its not worthy of any more comments .. :)
  5. Yeah, except to mention there are hundreds of applications still using CORBA *and* generating revenue and the need to integrate them with other systems through an SOA infrastructure like an ESB can be a very real requirement.