Versions Compared

Old Version 3

changes.mady.by.user Guillaume Nodet

Saved on

compared with

New Version Current

changes.mady.by.user Guillaume Nodet

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

Web Application

Release notes

  • Bug
    • SM-410 - Component Uninstallation : ClassLoader not removed from JVM
    • SM-482 - Missing jars in the BPE component
    • SM-494 - Problems with JMSFlow and sendSync in start() callbacks.
    • SM-536 - The defaultMep is a mandatory attribute on consumer endpoints and should be checked
    • SM-559 - WSDL-First example in JBoss
    • SM-570 - HTTP connector can blow up while trying to report a problem
    • SM-571 - Memory leak in DeliveryChannelImpl
    • SM-572 - servicemix-wsn2005 always use the anonymous publisher
    • SM-576 - XBeanProcessor does not skip comments
    • SM-577 - JSR 181 fault message does not respect WSDL message fault definition
    • SM-583 - Jetty context Path verification
    • SM-584 - Servicemix archive for Jboss
    • SM-585 - Deadlock on BoundedLinkedQueue
    • SM-589 - The SourceTransformer should not log a warning when calling toResult with a null Source
    • SM-592 - notifier.run() missing from DefaultState
    • SM-593 - Jetty jars missing when running servicemix-web example
    • SM-597 - Drools xpath expression does not use the namespaces defined
    • SM-598 - MTOM attachments are not output by the jsr181 component
    • SM-599 - bridge sample client.html providing no status info
    • SM-600 - Compilation error in Geronimo ServiceMixGBean
    • SM-603 - NullPointerException at org.apache.servicemix.jms.standard.StandardConsumerProcessor.doStart(StandardConsumerProcessor.java:51)
    • SM-604 - Allow servicemix-http managed mode to dynamically determine the server, port, and context path it is running on when generating jsr181 WSDLs
    • SM-608 - Maven based examples should include the needed repositories
    • SM-610 - The ServiceAssembly mbean should return the names of the ServiceUnits
    • SM-621 - Issues with ServiceMix startup shell script on Solaris
    • SM-622 - JCAFlow with Howl Log throws STATUS_NO_TRANSACTION exception
    • SM-668 - JCAFlow should reject synchronous exchanges
    • SM-669 - Statistic file should be named stats.csv instead of stats.cvs
    • SM-674 - jbi:installComponent (and others) fails authentication against default SM container
    • SM-676 - In the instance2 of the ws-notification example, the org.apache.servicemix.tck.ReceiverComponent should be removed
    • SM-677 - FTP connection not recovered after ftp server failure/recovery
    • SM-678 - Jsr181Component not using SU classloader to load service interface
    • SM-691 - Client.html pages do not work in IE
    • SM-692 - http endpoint activation ordering
    • SM-697 - Using XSLT servicemix component causes a "java.io.IOException: Too many open files"
    • SM-700 - ClientFactory should log problems at warning level as they are not critical
    • SM-707 - Subscription Manager and Flow MBeans do not get unregistered.
    • SM-722 - ExtendedXMLStreamReader strips whitespaces, which breaks servicemix-http when a SOAP invocation contains whitespace nodes
    • SM-723 - ServiceMixClientFacade should not call "done" method
    • SM-727 - Schema Import problem in a WSDL which doesn't let the service to be doployed on Servicemix
    • SM-732 - Fault-messages cause JbiChannel to throw NullPointerException
    • SM-736 - JcaConsumerProcessor.start() fails after subsequent stop()
    • SM-738 - Invalid jbi.xml when using maven. no description element
    • SM-739 - wsdl for pojos exported by jsr181 endpoint is missing complextypes from other namespaces than the service itself
    • SM-742 - JdbcAuditor fails on JBoss
    • SM-743 - Deadlock in JBoss Deployer during shutdown
    • SM-746 - JettyContextManager does not set the truststore parameters for unmanaged ssl endpoints
    • SM-748 - Restart of ServiceUnits using PollingEndpoints fails
    • SM-754 - Issues with jsr181 proxies using jaxws + doc/lit wrapped
    • SM-757 - Pipeline throws NPE when configured in synchronous mode and an exchange in ERROR status is received
    • SM-758 - JBoss Deployer 3.0 Snapshot classloading issues
    • SM-759 - Error "Attempted read on closed stream" thrown from jsr181 proxies when dealing with streams
    • SM-763 - XPathPredicate should not copy the in message before processing it
    • SM-764 - Jsr181 does not respect the transaction semantic (sync + tx)
    • SM-765 - JCA provider should close the session after use
    • SM-766 - Error whit chracters latin1 when send message in JbiChannel. For example "á"
    • SM-771 - An IllegalStateException is generated when using an http provider endpoint when it is deployed using the Servicemix Web war (managed mode).
    • SM-775 - Positive preliminary response from server when using FTPSender to send multiple files
    • SM-778 - JCAFlow stopped working after updating to 3.1 snapshot
    • SM-779 - ISO-8859-1 characters are duplicated
    • SM-780 - Bug due to change in proxy support for http binding component
    • SM-781 - Re: Bug in ScritpComponent when using "script" attribute
    • SM-782 - Re-deploy with In-Only Mep
    • SM-783 - build fails under java 6
    • SM-785 - Error in method doGetIds in DefaultJDBCAdapter class
    • SM-791 - Problem packaging multiple service unit dependant from the same component
    • SM-793 - StandardProviderProcessor does not set exchange status to done for InOnly/RobustInOnly exchanges
    • SM-794 - jsr181 proxy does not throw faults correctly when used in jaxws mode
    • SM-798 - Cannot start Bridge-SA in Geronimo 1.1 + Servicemix 3.0.1 plugin
    • SM-801 - can not deploy bridge-sa in apache-servicemix-3.1-incubating-SNAPSHOT + Geronimo 1.2 Beta
    • SM-802 - Refactor the Auditor MBean interface to avoid method overloading (which cause problems with JMX)
    • SM-804 - Documentation for XPath Router is missing examples
    • SM-805 - Incompatible BPELWSDLLocator between wsdl4j-1.5.2 and wsdl4j-1.6.1
    • SM-808 - Remove Xalan dependency in SourceTransformer (was: Servicemix jboss deployer)
    • SM-813 - Unique Column Names for JdbcComponent
    • SM-814 - Remove the CONTENT_DOCUMENT_PROPERTY property in SourceTransformer to avoid using an old message when properties are forwarded between components
    • SM-816 - useless include log framwork into jboss deployer
    • SM-819 - Saxon NullPointerException at INFO level
    • SM-824 - Webconsole does not work in Internet Explorer 7

...