Versions Compared

Old Version 1

changes.mady.by.user Freeman Fang

Saved on

compared with

New Version 2

changes.mady.by.user Freeman Fang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Linux/Mac OS X/Unix Downloads

Windows Downloads

...

Release notes

  • Bug
    • SM-854 - 331 - JabberComponentSupport attempts to create a jabber account every time on start
    • 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-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-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-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-923 - NPE in the web console when viewing component with lightweight components deployed
    • SM-928 - ProviderProcessor leaks memory for https endpoints
    • SM-938 - Component updates (from the hot deployer) sometimes fail
    • SM-940 - OneWay operation are not supported
    • SM-941 - NPE in BeanComponent - checkEndOfRequest
    • SM-951 - Remove servicemix-sca which is hosted in tuscany and which is completely outdated
  • Improvement
    • SM-611 - Reduce non-optional core dependencies
    • SM-795 - HTTP headers attached as properties may cause requests to fail
    • SM-830 - Replace System.out printing with logger
    • 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-889 - Add possibility to rename files after FTP upload
    • 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
    • LogService uses hard-coded path to the log4j.xml file
    • SM-937 - Poller polls subdirectory even though recursive is set to false
    • 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-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-982 - memory leak in org.apache.servicemix.bean.BeanEndpoint
    • SM-991 - servicemix-saxon component lacks ServiceUnit analyzer which results in generating incomplete jbi.xml
    • SM-1004 - File poller deletes files, even if errors occur while processing
    • SM-1006 - 0 byte files written when message contains invalid content
    • SM-1012 - Possible resource leak in FilePoller
    • SM-1014 - WSDL-first example fails javax.jbi.messaging.MessagingException: Do not understand pattern: null
    • SM-1016 - Environment Context ComponentMBeanImpl Removal
    • SM-1020 - Invalid query.xq generated by servicemix-saxon-xquery-service-unit archetype
    • SM-1023 - correlationId and senderEndpoint properties are not set on jsr181 (using the proxy) and jms consumer endpoints
    • SM-1024 - Archetype generates invalid brokerURL
    • SM-1026 - CorrelationId and senderEndpoint properties are not setted on the lightweigth components using the TransformComponentSupport
    • SM-1029 - Bug in HTTP BC when configuring managed keystore for SSL
    • SM-1043 - Poller sends invalid MessageExchange when file has been deleted
    • SM-1050 - Memory Leak in http consumer processor when using SSL
  • Improvement
    • 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
    • SM-1049 - Raise the number of http requests that can be send concurrently by servicemix-http
  • New Feature
    • SM-958 - Allow the connections element of the JBI.xml for a Service Assembly to be provided
    • SM-1045 - Servicemix tooling changes to generate JBISharedLibraryDescriptor
  • Task
    • SM-1028 - Ease the release process by avoiding manual changes in the source files
    Task
    • SM-901 - Upgrade to xfire 1.2.5
    • SM-916 - Upgrade to ActiveMQ 4.1.1
    • SM-946 - Upgrade loan-broker-bpel example to use Apache Ode

SVN Tag Checkout

Code Block
svn co http://svn.apache.org/repos/asf/incubator/servicemix/tags/servicemix-3.1.12/

Changelog

For a more detailed view of new features and bug fixes, see the changelog