Release Features: Fabric3 1.5


Fabric3 1.5 contains a number of new features, enhancements and bug fixes. These are described below by theme.

Universal Application Deployment

  • Users can now transparently deploy applications across middleware hosts without application changes, including the Fabric3 runtime, Tomcat, WebLogic and even Ant and Maven!

    Advanced Clustering Support

  • Revamped the Fabric3 clustering implementation for better performance, reliability, and security.
  • Improved Fabric3's distributed architecture so that there no single point of failure.
  • Support for centralized and peer-based updates.
  • Ability to launch runtime instances and receive deployment updates without an active controller.
  • Transactional deployment - Fabric3 will automatically rollback a runtime to its last stable state on a failed deployment.
  • Ability to manually rollback a deployment.
  • Secure (HTTPS) artifact provisioning.
  • Support for pluggable recovery extensions.
  • Support for provisioning extensions from non-file system sources (e.g. cloud storage providers).

    WebLogic 10.3 Support

  • Fabric3 for WebLogic runtime leverages WebLogic's clustering, self-tuning, transaction, JMS and management capabilities.
  • Support for clustered SCA domains using direct integration with WebLogic's clustering infrastructure.
  • Support for deployment and undeployment of end-user applications without the need to restart WebLogic or Fabric3.
  • Support for deployment and undeployment of Fabric3 extensions without the need to restart WebLogic or Fabric3.
  • Direct integration with WebLogic self-tuning thread pools.
  • Automatic WebLogic DataSource discovery so end-user applications do not need to configure JNDI locations. DataSources created after an application has been deployed will also be discovered.
  • Direct integration with the WebLogic transaction manager.
  • JMS binding integration with WebLogic JMS.
  • Automatic discovery of WebLogic JMS queues and topics.
  • Integration with WebLogic JMX so that Fabric3 SCA components are automatically bound to WebLogic's clustered JMX server.
  • Integration with the Fabric3 command-line administration tool for deployment and monitoring.
  • Integration with WebLogic logging.

    Miscellaneous

  • Autowire optimizations to avoid duplicate wire commands
  • Fix bug where JPA resources were not properly disposed on composite undeploy, leading to potential memory leaks.

    Bug fixes

  • See JIRA for bug fixes: resolved issues
    •