FUSE ESB v3.2 Release Notes

Added by Debbie Moynihan, last edited by Jonathan Anstey on Aug 01, 2007  (view change)

Release Notes - FUSE ESB - Version fuse-3.2.0.1 - August 1, 2007

Bug

  • ESB-4 - ServiceMix doesn't start correctly due to javax.management.MalformedObjectNameException
  • ESB-6 - Fixes to match newer Spring APIs when setting an object name.

Improvement

  • ESB-3 - Support specifing additional JNDI properties

Task

  • ESB-2 - Consumer Endpoint sets service/interface/uri on the message exchange while it has been already set earlier
  • ESB-7 - Update maven poms to use the new maven repository http://repo.open.iona.com/

Release Notes - FUSE ESB - Version fuse-3.2.0.0 - July 9, 2007

Bug

  • SM-331 - JabberComponentSupport attempts to create a jabber account every time on start
  • SM-470 - servicemix-http has no way to set a soap action
  • SM-750 - ClientFactory should implement java.io.Serializable
  • SM-828 - OutBinding doesn't allow for DeliveryChannel.accept()
  • SM-829 - Incorrect file encoding of created jbi.xml
  • SM-832 - Ws-Security signature does not work for outbound
  • SM-833 - into loan-broker-bpel sample - javax.jbi.messaging.MessagingException: Do not understand pattern: null
  • SM-835 - achetypes should not contain the <classpath/> tag inside the spring files
  • SM-839 - java.lang.IllegalStateException: Could not find valid implementation for: 2.0
  • SM-840 - JMS connections not close in servicemix-wsn2005
  • SM-841 - The servicemix-http provider endpoint does not properly handle web services that return faults with multiple elements in the detail section.
  • SM-842 - AuthenticationService set on the configuration is not used
  • SM-843 - The defaultMep attribute is missing on the jms endpoint in loan-broker-bpel demo
  • SM-845 - servicemix-quartz includes unneeded spring libraries
  • SM-846 - Call to default constructor of JBIContainer changes log4j log level
  • SM-847 - Old version of xml-apis in distribution
  • SM-849 - The web console fails when displaying an error
  • SM-850 - Error starting ServiceMix on AIX
  • SM-853 - NPE in DotViewFlowListener
  • SM-854 - LogService uses hard-coded path to the log4j.xml file
  • SM-858 - Unable to access a JBIContainer using the supplied component context in various endpoints (i.e. JSR181)
  • SM-860 - EndpointReferenceBuilder.getReference() should cache its DocumentBuilderFactory instance
  • SM-861 - servicemix-common does not properly set the correlationId for exchanges that are sent using sendSync
  • SM-862 - Possible problem when @WebMethod returns an empty string for the operation name
  • SM-863 - Generated ids are too long, it may cause problems when using them in databases as indexes
  • SM-866 - wsn-http-binding fails to start
  • SM-867 - Cannot add soap header in JSR181 component
  • SM-873 - servicemix-http does not return a valid fault when the xml is invalid
  • SM-874 - servicemix-http does not honor the soap version for certain kinds of faults
  • SM-878 - servicemix-bean is not include in the distribution
  • SM-879 - EIP XPath Splitter and Drools3.1 used together cause problems in xpath evaluation
  • SM-890 - Security Subject can not be propagated in servicemix-jsr181 when using the jsr181 proxies
  • SM-891 - Maven plugin should use finalName
  • SM-892 - ManagementContext.shutdown() calls wrong method to unregister MBeans
  • SM-893 - Messages lost under heavy load using JMSFlow
  • SM-895 - HttpConsumerEndpoint, security issue
  • SM-898 - soap2 unit tests fail with NullPointerException
  • SM-900 - WSDLFlattenner does not handle schemas inclusions
  • SM-902 - File Binding example error with JaxenStringXPathExpression
  • SM-904 - The jmx url is wrong if there are spaces at the end of the properties
  • SM-911 - JDBCComponent: The first column index is 1 in a result from sql query (non zero)
  • SM-914 - Exception upon generating a dot file from the apache-servicemix-web distribution in Tomcat
  • SM-921 - FTPClientPool does not have dataTimeout and controlEncoding properties.
  • SM-923 - NPE in the web console when viewing component with lightweight components deployed
  • SM-928 - ProviderProcessor leaks memory for https endpoints
  • SM-930 - ComponentListener does not get notified on Component uninstall
  • SM-931 - PMD/CheckStyle errors for servicemix-eip
  • SM-938 - Component updates (from the hot deployer) sometimes fail
  • SM-940 - OneWay operation are not supported
  • SM-941 - NPE in BeanComponent - checkEndOfRequest
  • SM-944 - IllegalStateException between servicemix-jms and servicemix-bean
  • SM-951 - Remove servicemix-sca which is hosted in tuscany and which is completely outdated
  • SM-952 - ClassLoaderXmlPreprocessor not able to load shared libraries from xbean.xml
  • SM-959 - ssl truststore is not set for unmanaged
  • SM-960 - JSR181 Orchestration sample doesn't work (Current state not START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE )
  • SM-963 - NullPointerExceptions during JMS component initialization
  • SM-966 - Consumer Endpoint sets service/interface/uri on the message exchange while it has been already set earlier
  • SM-969 - JBIMarshaler doesn't copy Subject from NormalizedMessage to SoapMessage
  • SM-972 - authenticationService is null - Several SA deployed on the same instance of Smx
  • SM-977 - wsdl-first example fails: XFireFault (could not unmarshal type)
  • SM-981 - Transaction Exception due to ServiceMix JMS Provider
  • SM-982 - memory leak in org.apache.servicemix.bean.BeanEndpoint
  • SM-984 - Two exchanges with the same dynamic endpoint processed at the same lead to an exception
  • SM-987 - Binding Component archetype - can't build
  • SM-991 - servicemix-saxon component lacks ServiceUnit analyzer which results in generating incomplete jbi.xml

Improvement

  • SM-510 - The servicemix-jms component should support the ability to set jms message properties
  • SM-557 - WSDL 1.1 message normalization for the servicemix-http component
  • SM-575 - servicemix-common base classes are not designed to support persistent deployments
  • SM-611 - Reduce non-optional core dependencies
  • SM-761 - JRuby support
  • SM-795 - HTTP headers attached as properties may cause requests to fail
  • SM-807 - Add jboss-service.xml to servicemix component so they can be properly deployed in jboss.
  • SM-810 - Create single complete ServiceMix Shared Library
  • SM-830 - Replace System.out printing with logger
  • SM-844 - Using Shared Libraries from LW SUs
  • SM-855 - Non concurrent processing of files in LW FilePoller
  • SM-865 - Remove jta and j2ee-connector from the mandatory dependencies when running an embedded ServiceMix instance
  • SM-869 - Avoid creating xml factories in jsr181
  • SM-870 - StaxSourceTransformer should reuse the XMLStreamReader when available
  • SM-871 - Optimize wsdl-first example
  • SM-876 - jmx.xml should use the jmx.url property
  • SM-877 - Bottleneck in SoapReader.readSoapUsingDom()
  • SM-883 - MBean registration in Websphere returns different objectName
  • SM-885 - WSA Epr are not recognized for namespaces other than http://www.w3.org/2005/08/addressing
  • SM-886 - Upgrade to saxon 9.9
  • SM-887 - The default value for the result property should be set back to 'dom'
  • SM-894 - Auto-create directory when file name contains subdirectories
  • SM-896 - Add a currentState on the component and ensure endpoints are correctly added / started at runtime
  • SM-903 - ServiceMix now requires java 5
  • SM-906 - extend ComponentSupport with methods to propagate the correlation id
  • SM-907 - Update to the latest version of the WS-Notification 1.3 spec
  • SM-908 - Upgrade to ActiveMQ 5.0
  • SM-909 - Upgrade to Geronimo 2.0
  • SM-912 - DOMStreamReader does not need to report namespaces as events
  • SM-913 - Improve archetypes and add a batch file for ease of use
  • SM-922 - When browsing for available services, existing urls should end with the needed '/' when displayed
  • SM-924 - Namespace support in servicemix-drools
  • SM-934 - change checkstyle line length to 140
  • SM-943 - Use a Calendar that displays nicely for the MessageExchange timestamp property
  • SM-965 - Allow use of -Dhost, -Dport, -Dusername and -Dpassword on jbi:projectDeploy
  • SM-986 - The maven jbi plugin should not fail it the SU jbi descriptor generation fails but only displays a warning

New Feature

  • SM-420 - Setting maximum memory
  • SM-532 - Allow easier deployment of endpoints using servicemix-common by splitting components from endpoints and put all endpoints together
  • SM-556 - CIMERO Eclipse plugin
  • SM-580 - Support for standard POST request from the provider.
  • SM-679 - Create a servicemix-ehcache standard JBI component
  • SM-724 - able to write marshaller for JBI components
  • SM-745 - Allow using Tibco for the JMSFlow
  • SM-826 - Add client for loan-broker-bpel
  • SM-834 - Provide File Marshalling for CSV/variable, fixed and heirarchial messages
  • SM-851 - Better soap / wsdl support
  • SM-856 - Add a marshaler to the servicemix-http component that handles Java serialization
  • SM-875 - TrueZIP binding component
  • SM-918 - Ability to reference Shared Libraries from Service Units
  • SM-926 - Add a standard JBI component for Velocity templates
  • SM-929 - eip message filter switch predicate where you can easily turn on/off the exchange flow depending on a property in a message filter
  • SM-939 - CXF based Service Engine and Bnding Component
  • SM-956 - Enhance jbi-maven-plugin to allow the use of a custom ServiceUnitAnalyzer
  • SM-985 - Allow additional beans to be injected in the rules definition from the xbean.xml

Task

  • SM-881 - Upgrade to xbean-spring 3.0
  • SM-901 - Upgrade to xfire 1.2.5
  • SM-946 - Upgrade loan-broker-bpel example to use Apache Ode
  • SM-992 - Fix XSD schema locations for use with plain spring

Known Installation Issues

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.