Thus, we’re proud to introduce zes3t (pronounced: zest!), a Python language, SOAP-based API for accessing Amazon’s S3 web service. Zes3t is still in its early stages, but is well-suited to administrative tasks. It very closely mimics Amazon’s own SOAP API, and the elegant, simple code base is well-documented and we’ve provided sample scripts to illustrate its usage. Zes3t is Free/Open Source software released under version 3 of the GNU LGPL.

Find out more about Zes3t on its project page:
https://createtank.org/projects/zes3t

xc : XmlConfiguration is now available under a triple license.
For your use, you may choose either the GNU General Public License [GPL], the GNU Lesser General Public License [LGPL], or the Apache License, Version 2.0.

Please check the main project site [http://xmlconfiguration.org/ ] for more details.

elemenope release 5.1 is a major feature release of the premier Open Source [FOSS] SOA and EAI Framework.

The following features/modifications are included:

• Addition of Enterprise XML-RPC Service Transport Protocol implementation — Embedded Jetty HTTP Server allows full enterprise capability in XML-RPC services with simplified deployment.
• Addition of Generic Filesystem Ingestion Operation implementation — Allows automated processing of files.
• All examples from elemenope User Guide Cookbook now within the standard configuration file
• ElemenopeStandardConfiguration — fixed broker and dispatcher initialization to allow 0 or 1 of each. Fixed default service/operation call to maintenance loop to fatal exit when throwable occurs within. Added capability to define more than one Broker for a service for use with web service implementations.
• XmlRpcDispatcher — changed default action when null payload is encountered. This allows call to default service/operation through XML-RPC, as this default call from w/in the maintenance loop always passes a null payload.

Download available here:
http://elemenope.org/downloads/5.1/

Release 1.1 of the elemenope User Guide coincides with this release and is available here: http://elemenope.org/doc/userguide/userguide-1.1.pdf

Please check the main project site [elemenope.org] for more details.

4.2rc2 includes the following new features:

• Synchronous JMS Connector family implementation.
  1. Allows one to configure synchronous communication via JMS queues.
  2. Offers generic persistent messaging in place of other synchronous communications.
• Web application download.
  1. We’ve included a webapp download for easy deployment of elemenope on your application server.

This is a release candidate issuance, and as such should not be considered stable. Some portions of the code within this release have not been completely tested.

Benefits and features provided by elemenopeâ„¢ framework:

• Transport abstraction – provides nearly unlimited scalability, as components may be connected in unexpected ways at a later date with no changes to code.
• Functional abstraction
  • Provides uniformity of functional code or business logic across the application or integration effort.
  • Provides for simplicity of interaction with subject matter experts [SME].
  • Provides ability to dynamically change the combinations of functional code units exposed as services under different transport protocols.
• Fault Tolerant/Fault Resilient messaging – Dispatcher Failover [DFO] provides ability to transparently failover from one transport protocol to another upon failure with no changes to the functional code or business logic.

Please check the main project site [elemenope.org] and/or the developer’s page for more details.

Version 4.1 includes the following new features:

• Full implementation of ElemenopeStartupServlet
  1. allows multiple configuration (initializationGroups) to be utilized within a single application server.
  2. Implementation of user level initialization within ElemenopeStartupServlet.
  3. Implementation of standard and user shutdown functionality within ElemenopeStartupServlet.

Benefits and features provided by elemenopeâ„¢ framework:

• Transport abstraction – provides nearly unlimited scalability, as components may be connected in unexpected ways at a later date with no changes to code.
• Functional abstraction
  • Provides uniformity of functional code or business logic across the application or integration effort.
  • Provides for simplicity of interaction with subject matter experts [SME].
  • Provides ability to dynamically change the combinations of functional code units exposed as services under different transport protocols.
• Fault Tolerant messaging – Dispatcher Failover [DFO] provides ability to transparently failover from one transport protocol to another upon failure with no changes to the functional code or business logic.

Please check the main project site [elemenope.org] and/or the developer’s page for more details.

Version 4.0 includes the following changes:

• Reorganization of base elemenope interfaces…
  1. Complete transmission protocol transparency
  2. Connector (connectivity implementor e.g. to JMS queue, web service, direct call, etc.)
  3. Broker (generic receipt functionality)
  4. Dispatcher (generic transmission functionality)
  5. Transaction (processing)
  6. ElemenopeConfiguration (configuration functionality)
  7. ElemenopeComponent (components with visibility [to all other components])
• New connectors
  1. Direct/Blocking call connector
  2. SOAP web services connector
• New Features
  1. Configurable Dispatcher failover
  2. Complete protocol transparency for transmission/receipt of messages

Newly added or enhanced benefits and features provided by elemenopeâ„¢ framework:

• Transport abstraction – provides nearly unlimited scalability, as components may be connected in unexpected ways at a later date with no changes to code.
• Functional abstraction
  • Provides uniformity of functional code or business logic across the application or integration effort.
  • Provides for simplicity of interaction with subject matter experts [SME].
  • Provides ability to dynamically change the combinations of functional code units exposed as services under different transport protocols.
• Fault Tolerant messaging – Dispatcher Failover [DFO] provides ability to transparently failover from one transport protocol to another upon failure with no changes to the functional code or business logic.

Please check the main project site [elemenope.org] and/or the developer’s page for more details.

v. 4.0rc1 includes the following changes:

• Reorganization of base elemenope interfaces…
  1. Complete transmission protocol transparency
  2. Connector (connectivity implementor e.g. to JMS queue, web service, direct call, etc.)
  3. Broker (generic receipt functionality)
  4. Dispatcher (generic transmission functionality)
  5. Transaction (processing)
  6. ElemenopeConfiguration (configuration functionality)
  7. ElemenopeComponent (components with visibility [to all other components])
• New connectors
  1. Direct/Blocking call connector
  2. SOAP web services connector
• New Features
  1. Configurable Dispatcher failover
  2. Complete protocol transparency for transmission/receipt of messages

Newly added or enhanced benefits and features provided by elemenopeâ„¢ framework:

• Transport abstraction – provides nearly unlimited scalability, as components may be connected in unexpected ways at a later date with no changes to code.
• Functional abstraction
  • Provides uniformity of functional code or business logic across the application or integration effort.
  • Provides for simplicity of interaction with subject matter experts [SME].
  • Provides ability to dynamically change the combinations of functional code units exposed as services under different transport protocols.
• Fault Tolerant messaging – Dispatcher Failover [DFO] provides ability to transparently failover from one transport protocol to another upon failure with no changes to the functional code or business logic.

Please check the main project site [elemenope.org] and/or the developer’s page for more details.

Release 3.0 includes the following changes:

• XML-RPC web services connectors!!!
• XML-RPC web services clients
• A simple C interface to MQSeries/WebsphereMQ
• Updated connector interfaces to complete JMS compliance
• Addition of Broker transaction type field position configuration

We Added XML-RPC web services connectors (both server and client). One can have multiple Web Services servers running, each with a configurable set of web services implementation classes, which can utilize all other objects within elemenope. One can also have multiple Web Services clients configured, which may be utilized by all senders and receivers within elemenope.

Altogether, this gives elemenope a list of features unmatched in the industry!

Please check the main project site [elemenope.createtank.com] and/or the developer’s page for more details.

Release 2.0 includes the following changes:

• Ability to utilize any JMS compliant Messaging Oriented Middleware [MOM]
• New JNDI connector set
• New JNDI example/setup
• Delimiters now configurable within Broker and Transaction classes
• Distribution script(s)

Please check the main project site [elemenope.createtank.com] and/or the developer’s page for more details.

createTank project elemenope release 1.1 includes the following changes:

• Improved build utilizing ANT (for framework, examples, and user classes)
• Rearranged directory structure
• Improved execution script
• Mild and general OO improvements
• Separation of XMLConfiguration utility into its own project [xmlconfiguration.createtank.com]
• Mild Javadoc corrections

Please check the main project site [elemenope.createtank.com] and/or the developer’s page for more details.