servicemix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ge...@apache.org
Subject svn commit: r1383357 [2/3] - in /servicemix/website/trunk/src/main/webapp/downloads: ./ subprojects/
Date Tue, 11 Sep 2012 11:26:46 GMT
Modified: servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-components-2011.02.page
URL: http://svn.apache.org/viewvc/servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-components-2011.02.page?rev=1383357&r1=1383356&r2=1383357&view=diff
==============================================================================
--- servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-components-2011.02.page (original)
+++ servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-components-2011.02.page Tue Sep 11 11:26:45 2012
@@ -5,62 +5,62 @@ title: ServiceMix Components 2011.02
 h2. Release Notes: ServiceMix Components 2011.02
 
 *Bug*
-* [SMXCOMP-855|http://issues.apache.org/active/browse/SMXCOMP-855] - MessageExchange Leak in CXF SE Proxy Per-Request
-* [SMXCOMP-858|http://issues.apache.org/active/browse/SMXCOMP-858] - CXFSE Proxy  Doesn't Implement "propagateSubject" Setting
-* [SMXCOMP-866|http://issues.apache.org/active/browse/SMXCOMP-866] - HTTP Consumer timeout handling is incorrect
-* [SMXCOMP-876|http://issues.apache.org/active/browse/SMXCOMP-876] - servicemix-soap bundle is missing some necessary <Import-Package> and <Export-Package>
-* [SMXCOMP-878|http://issues.apache.org/active/browse/SMXCOMP-878] - ensure cxf bc consumer endpoint can publish wsdl
-* [SMXCOMP-886|http://issues.apache.org/active/browse/SMXCOMP-886] - <http:soap-consumer> config may fail to import xsd or wsdl files
-* [SMXCOMP-887|http://issues.apache.org/active/browse/SMXCOMP-887] - <http:soap-consumer> config may fail to import xsd or wsdl files in sub-directories
-* [SMXCOMP-891|http://issues.apache.org/active/browse/SMXCOMP-891] - Avoid adding commons-logging 1.0.3 to servicemix-shared
-* [SMXCOMP-896|http://issues.apache.org/active/browse/SMXCOMP-896] - CXF-BC will be blocked after handling some request when working in the async model
-* [SMXCOMP-897|http://issues.apache.org/active/browse/SMXCOMP-897] - ensure cxf servlet transport and cxf bc can share same bus out of box when deploy smx-cxf-bc in web container
-* [SMXCOMP-903|http://issues.apache.org/active/browse/SMXCOMP-903] - Sending unsubscribe can leave servicemix-wsn2005 threads hanging on sendSync()
-* [SMXCOMP-905|http://issues.apache.org/active/browse/SMXCOMP-905] - ensure DONE status is set when cxf bc consumer encounter soap fault and use synchronous="true"
-* [SMXCOMP-910|http://issues.apache.org/active/browse/SMXCOMP-910] - NPE Generated whenever a soap message is received that contains a namespace prefix but no namespace uri.
-* [SMXCOMP-912|http://issues.apache.org/active/browse/SMXCOMP-912] - servicemix-cxf-se OSGi header is incorrect
-* [SMXCOMP-914|http://issues.apache.org/active/browse/SMXCOMP-914] - servicemix-wsn2005 can't restart correctly when the dependency activemq-broker.xml bundle restart
-* [SMXCOMP-916|http://issues.apache.org/active/browse/SMXCOMP-916] - org.apache.servicemix.http.jetty.JCLLogger can't get initialized in OSGi container
-* [SMXCOMP-919|http://issues.apache.org/active/browse/SMXCOMP-919] - JMS soap endpoint tests failing
+* [SMXCOMP-855|http://issues.apache.org/jira/browse/SMXCOMP-855] - MessageExchange Leak in CXF SE Proxy Per-Request
+* [SMXCOMP-858|http://issues.apache.org/jira/browse/SMXCOMP-858] - CXFSE Proxy  Doesn't Implement "propagateSubject" Setting
+* [SMXCOMP-866|http://issues.apache.org/jira/browse/SMXCOMP-866] - HTTP Consumer timeout handling is incorrect
+* [SMXCOMP-876|http://issues.apache.org/jira/browse/SMXCOMP-876] - servicemix-soap bundle is missing some necessary <Import-Package> and <Export-Package>
+* [SMXCOMP-878|http://issues.apache.org/jira/browse/SMXCOMP-878] - ensure cxf bc consumer endpoint can publish wsdl
+* [SMXCOMP-886|http://issues.apache.org/jira/browse/SMXCOMP-886] - <http:soap-consumer> config may fail to import xsd or wsdl files
+* [SMXCOMP-887|http://issues.apache.org/jira/browse/SMXCOMP-887] - <http:soap-consumer> config may fail to import xsd or wsdl files in sub-directories
+* [SMXCOMP-891|http://issues.apache.org/jira/browse/SMXCOMP-891] - Avoid adding commons-logging 1.0.3 to servicemix-shared
+* [SMXCOMP-896|http://issues.apache.org/jira/browse/SMXCOMP-896] - CXF-BC will be blocked after handling some request when working in the async model
+* [SMXCOMP-897|http://issues.apache.org/jira/browse/SMXCOMP-897] - ensure cxf servlet transport and cxf bc can share same bus out of box when deploy smx-cxf-bc in web container
+* [SMXCOMP-903|http://issues.apache.org/jira/browse/SMXCOMP-903] - Sending unsubscribe can leave servicemix-wsn2005 threads hanging on sendSync()
+* [SMXCOMP-905|http://issues.apache.org/jira/browse/SMXCOMP-905] - ensure DONE status is set when cxf bc consumer encounter soap fault and use synchronous="true"
+* [SMXCOMP-910|http://issues.apache.org/jira/browse/SMXCOMP-910] - NPE Generated whenever a soap message is received that contains a namespace prefix but no namespace uri.
+* [SMXCOMP-912|http://issues.apache.org/jira/browse/SMXCOMP-912] - servicemix-cxf-se OSGi header is incorrect
+* [SMXCOMP-914|http://issues.apache.org/jira/browse/SMXCOMP-914] - servicemix-wsn2005 can't restart correctly when the dependency activemq-broker.xml bundle restart
+* [SMXCOMP-916|http://issues.apache.org/jira/browse/SMXCOMP-916] - org.apache.servicemix.http.jetty.JCLLogger can't get initialized in OSGi container
+* [SMXCOMP-919|http://issues.apache.org/jira/browse/SMXCOMP-919] - JMS soap endpoint tests failing
 
 *Improvement*
-* [SMXCOMP-857|http://issues.apache.org/active/browse/SMXCOMP-857] - ensure cxfse:proxy is thread safe to access requestcontext
-* [SMXCOMP-862|http://issues.apache.org/active/browse/SMXCOMP-862] - Upgrade to ActiveMQ 5.5.0
-* [SMXCOMP-863|http://issues.apache.org/active/browse/SMXCOMP-863] - Make allowsCoreThreadTimeOut name consistent across mbeans and properties
-* [SMXCOMP-867|http://issues.apache.org/active/browse/SMXCOMP-867] - servicemix-camel performance optimizations
-* [SMXCOMP-868|http://issues.apache.org/active/browse/SMXCOMP-868] - Align stax-api version
-* [SMXCOMP-870|http://issues.apache.org/active/browse/SMXCOMP-870] - upgrade to cxf 2.4.0
-* [SMXCOMP-879|http://issues.apache.org/active/browse/SMXCOMP-879] - cxf se endpoint should support configure JAXBDataBinding with extraClass
-* [SMXCOMP-880|http://issues.apache.org/active/browse/SMXCOMP-880] - Refactor servicemix-http component to avoid use of wrapper for locking
-* [SMXCOMP-881|http://issues.apache.org/active/browse/SMXCOMP-881] - Allow configuring HTTP consumer endpoint for handling late responses from the bus
-* [SMXCOMP-883|http://issues.apache.org/active/browse/SMXCOMP-883] - cxf bc consumer should be able to determine soap version from incoming message
-* [SMXCOMP-885|http://issues.apache.org/active/browse/SMXCOMP-885] - Dynamic Soap address in wsdl
-* [SMXCOMP-888|http://issues.apache.org/active/browse/SMXCOMP-888] - remove xmlschema from sharedlib
-* [SMXCOMP-889|http://issues.apache.org/active/browse/SMXCOMP-889] - use local copy of XSD for servicemix-soap2 to avoid test hang
-* [SMXCOMP-893|http://issues.apache.org/active/browse/SMXCOMP-893] - remove META-INF/cxf/cxf-extension-soap.xml from servicemix-cxf-se
-* [SMXCOMP-902|http://issues.apache.org/active/browse/SMXCOMP-902] - should be able to configure jaas domain name used in JbiJAASInterceptor
-* [SMXCOMP-906|http://issues.apache.org/active/browse/SMXCOMP-906] - servicemix-cxf-bc should use version range for javax.servlet package import
-* [SMXCOMP-911|http://issues.apache.org/active/browse/SMXCOMP-911] - Add shared-library bundles to JBI component bundle classloader
-* [SMXCOMP-915|http://issues.apache.org/active/browse/SMXCOMP-915] - Upgrade to Camel 2.8.3
+* [SMXCOMP-857|http://issues.apache.org/jira/browse/SMXCOMP-857] - ensure cxfse:proxy is thread safe to access requestcontext
+* [SMXCOMP-862|http://issues.apache.org/jira/browse/SMXCOMP-862] - Upgrade to ActiveMQ 5.5.0
+* [SMXCOMP-863|http://issues.apache.org/jira/browse/SMXCOMP-863] - Make allowsCoreThreadTimeOut name consistent across mbeans and properties
+* [SMXCOMP-867|http://issues.apache.org/jira/browse/SMXCOMP-867] - servicemix-camel performance optimizations
+* [SMXCOMP-868|http://issues.apache.org/jira/browse/SMXCOMP-868] - Align stax-api version
+* [SMXCOMP-870|http://issues.apache.org/jira/browse/SMXCOMP-870] - upgrade to cxf 2.4.0
+* [SMXCOMP-879|http://issues.apache.org/jira/browse/SMXCOMP-879] - cxf se endpoint should support configure JAXBDataBinding with extraClass
+* [SMXCOMP-880|http://issues.apache.org/jira/browse/SMXCOMP-880] - Refactor servicemix-http component to avoid use of wrapper for locking
+* [SMXCOMP-881|http://issues.apache.org/jira/browse/SMXCOMP-881] - Allow configuring HTTP consumer endpoint for handling late responses from the bus
+* [SMXCOMP-883|http://issues.apache.org/jira/browse/SMXCOMP-883] - cxf bc consumer should be able to determine soap version from incoming message
+* [SMXCOMP-885|http://issues.apache.org/jira/browse/SMXCOMP-885] - Dynamic Soap address in wsdl
+* [SMXCOMP-888|http://issues.apache.org/jira/browse/SMXCOMP-888] - remove xmlschema from sharedlib
+* [SMXCOMP-889|http://issues.apache.org/jira/browse/SMXCOMP-889] - use local copy of XSD for servicemix-soap2 to avoid test hang
+* [SMXCOMP-893|http://issues.apache.org/jira/browse/SMXCOMP-893] - remove META-INF/cxf/cxf-extension-soap.xml from servicemix-cxf-se
+* [SMXCOMP-902|http://issues.apache.org/jira/browse/SMXCOMP-902] - should be able to configure jaas domain name used in JbiJAASInterceptor
+* [SMXCOMP-906|http://issues.apache.org/jira/browse/SMXCOMP-906] - servicemix-cxf-bc should use version range for javax.servlet package import
+* [SMXCOMP-911|http://issues.apache.org/jira/browse/SMXCOMP-911] - Add shared-library bundles to JBI component bundle classloader
+* [SMXCOMP-915|http://issues.apache.org/jira/browse/SMXCOMP-915] - Upgrade to Camel 2.8.3
 
 *Task*
-* [SMXCOMP-852|http://issues.apache.org/active/browse/SMXCOMP-852] - Switch to use slf4j as logger (instead of commons-logging)
-* [SMXCOMP-859|http://issues.apache.org/active/browse/SMXCOMP-859] - Upgrade to Camel 2.7
-* [SMXCOMP-861|http://issues.apache.org/active/browse/SMXCOMP-861] - upgrade to cxf 2.3.3
-* [SMXCOMP-865|http://issues.apache.org/active/browse/SMXCOMP-865] - Update to CXF 2.4.0
-* [SMXCOMP-874|http://issues.apache.org/active/browse/SMXCOMP-874] - Upgrade to ServiceMix Specs 1.8.0
-* [SMXCOMP-875|http://issues.apache.org/active/browse/SMXCOMP-875] - Update to Camel 2.8.0
-* [SMXCOMP-882|http://issues.apache.org/active/browse/SMXCOMP-882] - Upgrade to Java Mail 1.4.4
-* [SMXCOMP-890|http://issues.apache.org/active/browse/SMXCOMP-890] - upgrade to cxf 2.4.1
-* [SMXCOMP-892|http://issues.apache.org/active/browse/SMXCOMP-892] - Upgrade to Groovy 1.8.0
-* [SMXCOMP-894|http://issues.apache.org/active/browse/SMXCOMP-894] - Upgrade to Quartz 1.8.5
-* [SMXCOMP-898|http://issues.apache.org/active/browse/SMXCOMP-898] - Upgrade to cxf 2.4.2
-* [SMXCOMP-899|http://issues.apache.org/active/browse/SMXCOMP-899] - upgrade to cxf 2.4.2
-* [SMXCOMP-900|http://issues.apache.org/active/browse/SMXCOMP-900] - Upgrade to Camel 2.8.1
-* [SMXCOMP-901|http://issues.apache.org/active/browse/SMXCOMP-901] - upgrade to cxf 2.4.3
-* [SMXCOMP-909|http://issues.apache.org/active/browse/SMXCOMP-909] - upgrade to spring 3.0.6
-* [SMXCOMP-913|http://issues.apache.org/active/browse/SMXCOMP-913] - upgrade to cxf 2.4.4
-* [SMXCOMP-920|http://issues.apache.org/active/browse/SMXCOMP-920] - upgrade to wss4j 1.6.3
+* [SMXCOMP-852|http://issues.apache.org/jira/browse/SMXCOMP-852] - Switch to use slf4j as logger (instead of commons-logging)
+* [SMXCOMP-859|http://issues.apache.org/jira/browse/SMXCOMP-859] - Upgrade to Camel 2.7
+* [SMXCOMP-861|http://issues.apache.org/jira/browse/SMXCOMP-861] - upgrade to cxf 2.3.3
+* [SMXCOMP-865|http://issues.apache.org/jira/browse/SMXCOMP-865] - Update to CXF 2.4.0
+* [SMXCOMP-874|http://issues.apache.org/jira/browse/SMXCOMP-874] - Upgrade to ServiceMix Specs 1.8.0
+* [SMXCOMP-875|http://issues.apache.org/jira/browse/SMXCOMP-875] - Update to Camel 2.8.0
+* [SMXCOMP-882|http://issues.apache.org/jira/browse/SMXCOMP-882] - Upgrade to Java Mail 1.4.4
+* [SMXCOMP-890|http://issues.apache.org/jira/browse/SMXCOMP-890] - upgrade to cxf 2.4.1
+* [SMXCOMP-892|http://issues.apache.org/jira/browse/SMXCOMP-892] - Upgrade to Groovy 1.8.0
+* [SMXCOMP-894|http://issues.apache.org/jira/browse/SMXCOMP-894] - Upgrade to Quartz 1.8.5
+* [SMXCOMP-898|http://issues.apache.org/jira/browse/SMXCOMP-898] - Upgrade to cxf 2.4.2
+* [SMXCOMP-899|http://issues.apache.org/jira/browse/SMXCOMP-899] - upgrade to cxf 2.4.2
+* [SMXCOMP-900|http://issues.apache.org/jira/browse/SMXCOMP-900] - Upgrade to Camel 2.8.1
+* [SMXCOMP-901|http://issues.apache.org/jira/browse/SMXCOMP-901] - upgrade to cxf 2.4.3
+* [SMXCOMP-909|http://issues.apache.org/jira/browse/SMXCOMP-909] - upgrade to spring 3.0.6
+* [SMXCOMP-913|http://issues.apache.org/jira/browse/SMXCOMP-913] - upgrade to cxf 2.4.4
+* [SMXCOMP-920|http://issues.apache.org/jira/browse/SMXCOMP-920] - upgrade to wss4j 1.6.3
 
 
 

Modified: servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-cxf-bc-2009.01.page
URL: http://svn.apache.org/viewvc/servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-cxf-bc-2009.01.page?rev=1383357&r1=1383356&r2=1383357&view=diff
==============================================================================
--- servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-cxf-bc-2009.01.page (original)
+++ servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-cxf-bc-2009.01.page Tue Sep 11 11:26:45 2012
@@ -1,69 +1,69 @@
----
-title: servicemix-cxf-bc 2009.01
-page_version: 1
-page_creator: gertvanthienen
-page_modifier: gertvanthienen
---- pipeline:conf
+---
+title: servicemix-cxf-bc 2009.01
+page_version: 1
+page_creator: gertvanthienen
+page_modifier: gertvanthienen
+--- pipeline:conf
 
 {excerpt}Release Notes - ServiceMix Components - Version servicemix-cxf-bc-2009.01{excerpt}
 
 
 *Bug*
-    * [SMXCOMP-111|http://issues.apache.org/active/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
-    * [SMXCOMP-113|http://issues.apache.org/active/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
-    * [SMXCOMP-181|http://issues.apache.org/active/browse/SMXCOMP-181] - MessageExchange (org.apache.cxf.transport.jbi.JBIDestination) not serializable
-    * [SMXCOMP-183|http://issues.apache.org/active/browse/SMXCOMP-183] - smx-cxf-bc provider throws NPE at JbiInWsdl1Interceptor.handleJBIFault(JbiInWsdl1Interceptor.java:237) 
-    * [SMXCOMP-186|http://issues.apache.org/active/browse/SMXCOMP-186] - Cxf BC Provider can't handle response soap message correctly if there is "whitespace" after <soap:Body> tag
-    * [SMXCOMP-188|http://issues.apache.org/active/browse/SMXCOMP-188] - CxfBcJmsTransaction*Test  hang
-    * [SMXCOMP-193|http://issues.apache.org/active/browse/SMXCOMP-193] - INFO: Interceptor has thrown exception, unwinding now org.w3c.dom.DOMException: HIERARCHY_REQUEST_ERR:
-    * [SMXCOMP-194|http://issues.apache.org/active/browse/SMXCOMP-194] - JBIOutInterceptor is not correctly handling outgoing WSA Headers
-    * [SMXCOMP-195|http://issues.apache.org/active/browse/SMXCOMP-195] - JMSBroker used in the test shouldn't setTmpDataDirectory as ./target which will break the release process
-    * [SMXCOMP-196|http://issues.apache.org/active/browse/SMXCOMP-196] - MessageExchange (org.apache.cxf.service.model.MessageInfo) not Serializable
-    * [SMXCOMP-197|http://issues.apache.org/active/browse/SMXCOMP-197] - OutOfMemoryException (PermGen) after redeploying servicemix-cxf* and servicemix-wsn2005
-    * [SMXCOMP-198|http://issues.apache.org/active/browse/SMXCOMP-198] - Provider fails to set proper ws-addressing To header on outbound messages
-    * [SMXCOMP-200|http://issues.apache.org/active/browse/SMXCOMP-200] - When using bufCfg, the file is not found correctly from a JBI SU deployed in Smx4
-    * [SMXCOMP-202|http://issues.apache.org/active/browse/SMXCOMP-202] - cxf bc provider and cxf se doesn't send DONE back when use oneway
-    * [SMXCOMP-203|http://issues.apache.org/active/browse/SMXCOMP-203] - cxf bc with ws-security can't work with enable JDBCAuditor
-    * [SMXCOMP-212|http://issues.apache.org/active/browse/SMXCOMP-212] - cxf-bc provider w/mtomEnabled=false talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading XMLStreamReader
-    * [SMXCOMP-213|http://issues.apache.org/active/browse/SMXCOMP-213] - servicemix-common and servicemix-cxf-bc component have servicemix-core dependency as provided which is only required as test dependency.
-    * [SMXCOMP-214|http://issues.apache.org/active/browse/SMXCOMP-214] - smx-cxf-bc consumer throws NPE in CxfBcConsumer.process() for one-way request where synchronous=false
-    * [SMXCOMP-215|http://issues.apache.org/active/browse/SMXCOMP-215] - Loading jax-ws-catalog.xml into servicemix-cxf-bc component
-    * [SMXCOMP-216|http://issues.apache.org/active/browse/SMXCOMP-216] - need add lock for DeliveryChannel of cxf bc consumer to handle multiple client invocation
-    * [SMXCOMP-458|http://issues.apache.org/active/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
-    * [SMXCOMP-461|http://issues.apache.org/active/browse/SMXCOMP-461] - Fix smx-cxf-bc consumer timeout property JavaDoc and code interpretation
-    * [SMXCOMP-470|http://issues.apache.org/active/browse/SMXCOMP-470] - we need cache attachment earlier when use ws-addressing and mtom
-    * [SMXCOMP-476|http://issues.apache.org/active/browse/SMXCOMP-476] - A CXF-BC provider used with WS-RM sends the CreateSequence request without SOAP envelope
-    * [SMXCOMP-478|http://issues.apache.org/active/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
+    * [SMXCOMP-111|http://issues.apache.org/jira/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
+    * [SMXCOMP-113|http://issues.apache.org/jira/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
+    * [SMXCOMP-181|http://issues.apache.org/jira/browse/SMXCOMP-181] - MessageExchange (org.apache.cxf.transport.jbi.JBIDestination) not serializable
+    * [SMXCOMP-183|http://issues.apache.org/jira/browse/SMXCOMP-183] - smx-cxf-bc provider throws NPE at JbiInWsdl1Interceptor.handleJBIFault(JbiInWsdl1Interceptor.java:237)
+    * [SMXCOMP-186|http://issues.apache.org/jira/browse/SMXCOMP-186] - Cxf BC Provider can't handle response soap message correctly if there is "whitespace" after <soap:Body> tag
+    * [SMXCOMP-188|http://issues.apache.org/jira/browse/SMXCOMP-188] - CxfBcJmsTransaction*Test  hang
+    * [SMXCOMP-193|http://issues.apache.org/jira/browse/SMXCOMP-193] - INFO: Interceptor has thrown exception, unwinding now org.w3c.dom.DOMException: HIERARCHY_REQUEST_ERR:
+    * [SMXCOMP-194|http://issues.apache.org/jira/browse/SMXCOMP-194] - JBIOutInterceptor is not correctly handling outgoing WSA Headers
+    * [SMXCOMP-195|http://issues.apache.org/jira/browse/SMXCOMP-195] - JMSBroker used in the test shouldn't setTmpDataDirectory as ./target which will break the release process
+    * [SMXCOMP-196|http://issues.apache.org/jira/browse/SMXCOMP-196] - MessageExchange (org.apache.cxf.service.model.MessageInfo) not Serializable
+    * [SMXCOMP-197|http://issues.apache.org/jira/browse/SMXCOMP-197] - OutOfMemoryException (PermGen) after redeploying servicemix-cxf* and servicemix-wsn2005
+    * [SMXCOMP-198|http://issues.apache.org/jira/browse/SMXCOMP-198] - Provider fails to set proper ws-addressing To header on outbound messages
+    * [SMXCOMP-200|http://issues.apache.org/jira/browse/SMXCOMP-200] - When using bufCfg, the file is not found correctly from a JBI SU deployed in Smx4
+    * [SMXCOMP-202|http://issues.apache.org/jira/browse/SMXCOMP-202] - cxf bc provider and cxf se doesn't send DONE back when use oneway
+    * [SMXCOMP-203|http://issues.apache.org/jira/browse/SMXCOMP-203] - cxf bc with ws-security can't work with enable JDBCAuditor
+    * [SMXCOMP-212|http://issues.apache.org/jira/browse/SMXCOMP-212] - cxf-bc provider w/mtomEnabled=false talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading XMLStreamReader
+    * [SMXCOMP-213|http://issues.apache.org/jira/browse/SMXCOMP-213] - servicemix-common and servicemix-cxf-bc component have servicemix-core dependency as provided which is only required as test dependency.
+    * [SMXCOMP-214|http://issues.apache.org/jira/browse/SMXCOMP-214] - smx-cxf-bc consumer throws NPE in CxfBcConsumer.process() for one-way request where synchronous=false
+    * [SMXCOMP-215|http://issues.apache.org/jira/browse/SMXCOMP-215] - Loading jax-ws-catalog.xml into servicemix-cxf-bc component
+    * [SMXCOMP-216|http://issues.apache.org/jira/browse/SMXCOMP-216] - need add lock for DeliveryChannel of cxf bc consumer to handle multiple client invocation
+    * [SMXCOMP-458|http://issues.apache.org/jira/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
+    * [SMXCOMP-461|http://issues.apache.org/jira/browse/SMXCOMP-461] - Fix smx-cxf-bc consumer timeout property JavaDoc and code interpretation
+    * [SMXCOMP-470|http://issues.apache.org/jira/browse/SMXCOMP-470] - we need cache attachment earlier when use ws-addressing and mtom
+    * [SMXCOMP-476|http://issues.apache.org/jira/browse/SMXCOMP-476] - A CXF-BC provider used with WS-RM sends the CreateSequence request without SOAP envelope
+    * [SMXCOMP-478|http://issues.apache.org/jira/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
 
 *Improvement*
-    * [SMXCOMP-9|http://issues.apache.org/active/browse/SMXCOMP-9] - if cxf endpoint use specific bus, then we should shutdown the bus cleanly when shutdown the  endpoint
-    * [SMXCOMP-115|http://issues.apache.org/active/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
-    * [SMXCOMP-116|http://issues.apache.org/active/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
-    * [SMXCOMP-184|http://issues.apache.org/active/browse/SMXCOMP-184] - Add "features" support from cxf to the smx-cxf-bc endpoint
-    * [SMXCOMP-185|http://issues.apache.org/active/browse/SMXCOMP-185] - CXF BC Provider using JMS Transport is not scalable (locks thread waiting for external service response)
-    * [SMXCOMP-190|http://issues.apache.org/active/browse/SMXCOMP-190] - Develop cxf-bc provider test case to verify that MTOM response is successfully handled regardless of mtomEnabled flag value
-    * [SMXCOMP-191|http://issues.apache.org/active/browse/SMXCOMP-191] - Develop test case to demonstrate and verify that smx-cxf-bc consumer endpoint with transactional JMS transport sends transactional exchange correctly
-    * [SMXCOMP-192|http://issues.apache.org/active/browse/SMXCOMP-192] - Excessive console output from cxfbc tests
-    * [SMXCOMP-204|http://issues.apache.org/active/browse/SMXCOMP-204] - cxf provider should be able to extract operationName based on payload and wsdl if using doc/literal style in case that no operationName bound to the MessageExchange
-    * [SMXCOMP-205|http://issues.apache.org/active/browse/SMXCOMP-205] - cxf-bc consumer should allow async sending of message exchanges to the NMR
-    * [SMXCOMP-206|http://issues.apache.org/active/browse/SMXCOMP-206] - ensure OASISCatalogManager is loaded before getting wsdl definition
-    * [SMXCOMP-207|http://issues.apache.org/active/browse/SMXCOMP-207] - remove unnecessary direct jaxws-api, jaxb dependency  from servicemix-cxf-se and servicemix-cxf-bc
-    * [SMXCOMP-208|http://issues.apache.org/active/browse/SMXCOMP-208] - remove unreachable code from JbiInInterceptor
-    * [SMXCOMP-450|http://issues.apache.org/active/browse/SMXCOMP-450] - CXF Binding Component ships with the generated code from the hello_world.wsdl
-    * [SMXCOMP-464|http://issues.apache.org/active/browse/SMXCOMP-464] - avoid adding xmlns for each element when using prefixes
+    * [SMXCOMP-9|http://issues.apache.org/jira/browse/SMXCOMP-9] - if cxf endpoint use specific bus, then we should shutdown the bus cleanly when shutdown the  endpoint
+    * [SMXCOMP-115|http://issues.apache.org/jira/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
+    * [SMXCOMP-116|http://issues.apache.org/jira/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
+    * [SMXCOMP-184|http://issues.apache.org/jira/browse/SMXCOMP-184] - Add "features" support from cxf to the smx-cxf-bc endpoint
+    * [SMXCOMP-185|http://issues.apache.org/jira/browse/SMXCOMP-185] - CXF BC Provider using JMS Transport is not scalable (locks thread waiting for external service response)
+    * [SMXCOMP-190|http://issues.apache.org/jira/browse/SMXCOMP-190] - Develop cxf-bc provider test case to verify that MTOM response is successfully handled regardless of mtomEnabled flag value
+    * [SMXCOMP-191|http://issues.apache.org/jira/browse/SMXCOMP-191] - Develop test case to demonstrate and verify that smx-cxf-bc consumer endpoint with transactional JMS transport sends transactional exchange correctly
+    * [SMXCOMP-192|http://issues.apache.org/jira/browse/SMXCOMP-192] - Excessive console output from cxfbc tests
+    * [SMXCOMP-204|http://issues.apache.org/jira/browse/SMXCOMP-204] - cxf provider should be able to extract operationName based on payload and wsdl if using doc/literal style in case that no operationName bound to the MessageExchange
+    * [SMXCOMP-205|http://issues.apache.org/jira/browse/SMXCOMP-205] - cxf-bc consumer should allow async sending of message exchanges to the NMR
+    * [SMXCOMP-206|http://issues.apache.org/jira/browse/SMXCOMP-206] - ensure OASISCatalogManager is loaded before getting wsdl definition
+    * [SMXCOMP-207|http://issues.apache.org/jira/browse/SMXCOMP-207] - remove unnecessary direct jaxws-api, jaxb dependency  from servicemix-cxf-se and servicemix-cxf-bc
+    * [SMXCOMP-208|http://issues.apache.org/jira/browse/SMXCOMP-208] - remove unreachable code from JbiInInterceptor
+    * [SMXCOMP-450|http://issues.apache.org/jira/browse/SMXCOMP-450] - CXF Binding Component ships with the generated code from the hello_world.wsdl
+    * [SMXCOMP-464|http://issues.apache.org/jira/browse/SMXCOMP-464] - avoid adding xmlns for each element when using prefixes
 
 
 *Task*
-    * [SMXCOMP-199|http://issues.apache.org/active/browse/SMXCOMP-199] - Upgrade to cxf 2.1.4
-    * [SMXCOMP-210|http://issues.apache.org/active/browse/SMXCOMP-210] - upgrade to CXF 2.1.3 release version
+    * [SMXCOMP-199|http://issues.apache.org/jira/browse/SMXCOMP-199] - Upgrade to cxf 2.1.4
+    * [SMXCOMP-210|http://issues.apache.org/jira/browse/SMXCOMP-210] - upgrade to CXF 2.1.3 release version
 
 *Test*
-    * [SMXCOMP-187|http://issues.apache.org/active/browse/SMXCOMP-187] - CxfBcJmsTest failure 
-    * [SMXCOMP-189|http://issues.apache.org/active/browse/SMXCOMP-189] - CxfBcJmsTransaction*Test is broken caused by recent change in cxf
-    * [SMXCOMP-201|http://issues.apache.org/active/browse/SMXCOMP-201] - changes in CXF-1946 cause CxfBCSEProviderSystemTest fail
-    * [SMXCOMP-209|http://issues.apache.org/active/browse/SMXCOMP-209] - test to ensure the different JMSConduit instance share share replyDest work correctly for cxf bc provider
-    * [SMXCOMP-211|http://issues.apache.org/active/browse/SMXCOMP-211] - test to guarantee conduit is created for each cxf bc provider endpoint but not per request
-    * [SMXCOMP-466|http://issues.apache.org/active/browse/SMXCOMP-466] - WS-RM : the CreateSequenceResponse body is void
-    * [SMXCOMP-477|http://issues.apache.org/active/browse/SMXCOMP-477] - CxfBcRMSequenceTest failed due to missing configuration file
+    * [SMXCOMP-187|http://issues.apache.org/jira/browse/SMXCOMP-187] - CxfBcJmsTest failure
+    * [SMXCOMP-189|http://issues.apache.org/jira/browse/SMXCOMP-189] - CxfBcJmsTransaction*Test is broken caused by recent change in cxf
+    * [SMXCOMP-201|http://issues.apache.org/jira/browse/SMXCOMP-201] - changes in CXF-1946 cause CxfBCSEProviderSystemTest fail
+    * [SMXCOMP-209|http://issues.apache.org/jira/browse/SMXCOMP-209] - test to ensure the different JMSConduit instance share share replyDest work correctly for cxf bc provider
+    * [SMXCOMP-211|http://issues.apache.org/jira/browse/SMXCOMP-211] - test to guarantee conduit is created for each cxf bc provider endpoint but not per request
+    * [SMXCOMP-466|http://issues.apache.org/jira/browse/SMXCOMP-466] - WS-RM : the CreateSequenceResponse body is void
+    * [SMXCOMP-477|http://issues.apache.org/jira/browse/SMXCOMP-477] - CxfBcRMSequenceTest failed due to missing configuration file
 
 

Modified: servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-cxf-se-2009.01.page
URL: http://svn.apache.org/viewvc/servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-cxf-se-2009.01.page?rev=1383357&r1=1383356&r2=1383357&view=diff
==============================================================================
--- servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-cxf-se-2009.01.page (original)
+++ servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-cxf-se-2009.01.page Tue Sep 11 11:26:45 2012
@@ -1,35 +1,35 @@
----
-title: servicemix-cxf-se 2009.01
-page_version: 1
-page_creator: gertvanthienen
-page_modifier: gertvanthienen
---- pipeline:conf
+---
+title: servicemix-cxf-se 2009.01
+page_version: 1
+page_creator: gertvanthienen
+page_modifier: gertvanthienen
+--- pipeline:conf
 
 {excerpt}Release Notes - ServiceMix Components - Version servicemix-cxf-se-2009.01{excerpt}
 
 
 *Bug*
-    * [SMXCOMP-111|http://issues.apache.org/active/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
-    * [SMXCOMP-113|http://issues.apache.org/active/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
-    * [SMXCOMP-181|http://issues.apache.org/active/browse/SMXCOMP-181] - MessageExchange (org.apache.cxf.transport.jbi.JBIDestination) not serializable
-    * [SMXCOMP-196|http://issues.apache.org/active/browse/SMXCOMP-196] - MessageExchange (org.apache.cxf.service.model.MessageInfo) not Serializable
-    * [SMXCOMP-197|http://issues.apache.org/active/browse/SMXCOMP-197] - OutOfMemoryException (PermGen) after redeploying servicemix-cxf* and servicemix-wsn2005
-    * [SMXCOMP-202|http://issues.apache.org/active/browse/SMXCOMP-202] - cxf bc provider and cxf se doesn't send DONE back when use oneway
-    * [SMXCOMP-458|http://issues.apache.org/active/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
-    * [SMXCOMP-478|http://issues.apache.org/active/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
+    * [SMXCOMP-111|http://issues.apache.org/jira/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
+    * [SMXCOMP-113|http://issues.apache.org/jira/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
+    * [SMXCOMP-181|http://issues.apache.org/jira/browse/SMXCOMP-181] - MessageExchange (org.apache.cxf.transport.jbi.JBIDestination) not serializable
+    * [SMXCOMP-196|http://issues.apache.org/jira/browse/SMXCOMP-196] - MessageExchange (org.apache.cxf.service.model.MessageInfo) not Serializable
+    * [SMXCOMP-197|http://issues.apache.org/jira/browse/SMXCOMP-197] - OutOfMemoryException (PermGen) after redeploying servicemix-cxf* and servicemix-wsn2005
+    * [SMXCOMP-202|http://issues.apache.org/jira/browse/SMXCOMP-202] - cxf bc provider and cxf se doesn't send DONE back when use oneway
+    * [SMXCOMP-458|http://issues.apache.org/jira/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
+    * [SMXCOMP-478|http://issues.apache.org/jira/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
 
 *Improvement*
-    * [SMXCOMP-115|http://issues.apache.org/active/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
-    * [SMXCOMP-116|http://issues.apache.org/active/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
-    * [SMXCOMP-207|http://issues.apache.org/active/browse/SMXCOMP-207] - remove unnecessary direct jaxws-api, jaxb dependency  from servicemix-cxf-se and servicemix-cxf-bc
-    * [SMXCOMP-242|http://issues.apache.org/active/browse/SMXCOMP-242] - support aegis databinding in cxf se
-    * [SMXCOMP-244|http://issues.apache.org/active/browse/SMXCOMP-244] - add simple frontend support in  cxf se
-    * [SMXCOMP-246|http://issues.apache.org/active/browse/SMXCOMP-246] - Add testContextInjectionRobustInOnly() test to CxfSeContextInjectionTest.java to verify robust-in-only mep is handled correctly
+    * [SMXCOMP-115|http://issues.apache.org/jira/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
+    * [SMXCOMP-116|http://issues.apache.org/jira/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
+    * [SMXCOMP-207|http://issues.apache.org/jira/browse/SMXCOMP-207] - remove unnecessary direct jaxws-api, jaxb dependency  from servicemix-cxf-se and servicemix-cxf-bc
+    * [SMXCOMP-242|http://issues.apache.org/jira/browse/SMXCOMP-242] - support aegis databinding in cxf se
+    * [SMXCOMP-244|http://issues.apache.org/jira/browse/SMXCOMP-244] - add simple frontend support in  cxf se
+    * [SMXCOMP-246|http://issues.apache.org/jira/browse/SMXCOMP-246] - Add testContextInjectionRobustInOnly() test to CxfSeContextInjectionTest.java to verify robust-in-only mep is handled correctly
 
 
 *Task*
-    * [SMXCOMP-199|http://issues.apache.org/active/browse/SMXCOMP-199] - Upgrade to cxf 2.1.4
-    * [SMXCOMP-210|http://issues.apache.org/active/browse/SMXCOMP-210] - upgrade to CXF 2.1.3 release version
+    * [SMXCOMP-199|http://issues.apache.org/jira/browse/SMXCOMP-199] - Upgrade to cxf 2.1.4
+    * [SMXCOMP-210|http://issues.apache.org/jira/browse/SMXCOMP-210] - upgrade to CXF 2.1.3 release version
 
 
 

Modified: servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-drools-2009.01.page
URL: http://svn.apache.org/viewvc/servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-drools-2009.01.page?rev=1383357&r1=1383356&r2=1383357&view=diff
==============================================================================
--- servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-drools-2009.01.page (original)
+++ servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-drools-2009.01.page Tue Sep 11 11:26:45 2012
@@ -1,21 +1,21 @@
----
-title: servicemix-drools 2009.01
-page_version: 1
-page_creator: gertvanthienen
-page_modifier: gertvanthienen
---- pipeline:conf
+---
+title: servicemix-drools 2009.01
+page_version: 1
+page_creator: gertvanthienen
+page_modifier: gertvanthienen
+--- pipeline:conf
 
 {excerpt}Release Notes - ServiceMix Components - Version servicemix-drools-2009.01{excerpt}
 
 
 *Bug*
-    * [SMXCOMP-111|http://issues.apache.org/active/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
-    * [SMXCOMP-113|http://issues.apache.org/active/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
-    * [SMXCOMP-247|http://issues.apache.org/active/browse/SMXCOMP-247] - ServiceMix Drools ignore the defaultTargetService attribute
-    * [SMXCOMP-458|http://issues.apache.org/active/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
-    * [SMXCOMP-478|http://issues.apache.org/active/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
+    * [SMXCOMP-111|http://issues.apache.org/jira/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
+    * [SMXCOMP-113|http://issues.apache.org/jira/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
+    * [SMXCOMP-247|http://issues.apache.org/jira/browse/SMXCOMP-247] - ServiceMix Drools ignore the defaultTargetService attribute
+    * [SMXCOMP-458|http://issues.apache.org/jira/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
+    * [SMXCOMP-478|http://issues.apache.org/jira/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
 
 *Improvement*
-    * [SMXCOMP-115|http://issues.apache.org/active/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
-    * [SMXCOMP-116|http://issues.apache.org/active/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
-    * [SMXCOMP-249|http://issues.apache.org/active/browse/SMXCOMP-249] - Setting XML Attributes in Messages & Auto Reply to support InOut w/o calling answer()/route() in .drl files
\ No newline at end of file
+    * [SMXCOMP-115|http://issues.apache.org/jira/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
+    * [SMXCOMP-116|http://issues.apache.org/jira/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
+    * [SMXCOMP-249|http://issues.apache.org/jira/browse/SMXCOMP-249] - Setting XML Attributes in Messages & Auto Reply to support InOut w/o calling answer()/route() in .drl files
\ No newline at end of file

Modified: servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-eip-2009.01.page
URL: http://svn.apache.org/viewvc/servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-eip-2009.01.page?rev=1383357&r1=1383356&r2=1383357&view=diff
==============================================================================
--- servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-eip-2009.01.page (original)
+++ servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-eip-2009.01.page Tue Sep 11 11:26:45 2012
@@ -1,35 +1,35 @@
----
-title: servicemix-eip 2009.01
-page_version: 1
-page_creator: gertvanthienen
-page_modifier: gertvanthienen
---- pipeline:conf
+---
+title: servicemix-eip 2009.01
+page_version: 1
+page_creator: gertvanthienen
+page_modifier: gertvanthienen
+--- pipeline:conf
 
 {excerpt}Release Notes - ServiceMix Components - Version servicemix-eip-2009.01{excerpt}
 
 
 *Bug*
-    * [SMXCOMP-44|http://issues.apache.org/active/browse/SMXCOMP-44] - EPI Content Enricher may not work if input content is a stream
-    * [SMXCOMP-111|http://issues.apache.org/active/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
-    * [SMXCOMP-113|http://issues.apache.org/active/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
-    * [SMXCOMP-119|http://issues.apache.org/active/browse/SMXCOMP-119] - LockManager impl causes memory leak in ServiceMix EIP
-    * [SMXCOMP-252|http://issues.apache.org/active/browse/SMXCOMP-252] - EIP Pipeline with "sendFaultsToTarget" = true does not copy properties and attachments to target ME "in" message for a fault
-    * [SMXCOMP-253|http://issues.apache.org/active/browse/SMXCOMP-253] - Content enricher does not handle StreamSources correctly
-    * [SMXCOMP-255|http://issues.apache.org/active/browse/SMXCOMP-255] - EIP wiretap should save operationname  by default
-    * [SMXCOMP-258|http://issues.apache.org/active/browse/SMXCOMP-258] - running servicemix-eip unit tests stalls intermittently
-    * [SMXCOMP-458|http://issues.apache.org/active/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
-    * [SMXCOMP-478|http://issues.apache.org/active/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
+    * [SMXCOMP-44|http://issues.apache.org/jira/browse/SMXCOMP-44] - EPI Content Enricher may not work if input content is a stream
+    * [SMXCOMP-111|http://issues.apache.org/jira/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
+    * [SMXCOMP-113|http://issues.apache.org/jira/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
+    * [SMXCOMP-119|http://issues.apache.org/jira/browse/SMXCOMP-119] - LockManager impl causes memory leak in ServiceMix EIP
+    * [SMXCOMP-252|http://issues.apache.org/jira/browse/SMXCOMP-252] - EIP Pipeline with "sendFaultsToTarget" = true does not copy properties and attachments to target ME "in" message for a fault
+    * [SMXCOMP-253|http://issues.apache.org/jira/browse/SMXCOMP-253] - Content enricher does not handle StreamSources correctly
+    * [SMXCOMP-255|http://issues.apache.org/jira/browse/SMXCOMP-255] - EIP wiretap should save operationname  by default
+    * [SMXCOMP-258|http://issues.apache.org/jira/browse/SMXCOMP-258] - running servicemix-eip unit tests stalls intermittently
+    * [SMXCOMP-458|http://issues.apache.org/jira/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
+    * [SMXCOMP-478|http://issues.apache.org/jira/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
 
 *Improvement*
-    * [SMXCOMP-115|http://issues.apache.org/active/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
-    * [SMXCOMP-116|http://issues.apache.org/active/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
-    * [SMXCOMP-261|http://issues.apache.org/active/browse/SMXCOMP-261] - set copyAttachments and copyProperties default value to true for ContentEnricher Pipeline and WireTap
+    * [SMXCOMP-115|http://issues.apache.org/jira/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
+    * [SMXCOMP-116|http://issues.apache.org/jira/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
+    * [SMXCOMP-261|http://issues.apache.org/jira/browse/SMXCOMP-261] - set copyAttachments and copyProperties default value to true for ContentEnricher Pipeline and WireTap
 
 *New Feature*
-    * [SMXCOMP-259|http://issues.apache.org/active/browse/SMXCOMP-259] - smx-eip AbstractAggregator should support boolean property "reportTimeoutAsErrors"
+    * [SMXCOMP-259|http://issues.apache.org/jira/browse/SMXCOMP-259] - smx-eip AbstractAggregator should support boolean property "reportTimeoutAsErrors"
 
 *Task*
-    * [SMXCOMP-256|http://issues.apache.org/active/browse/SMXCOMP-256] - Improve servicemix-eip schema documentation
+    * [SMXCOMP-256|http://issues.apache.org/jira/browse/SMXCOMP-256] - Improve servicemix-eip schema documentation
 
 
 

Modified: servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-file-2009.01.page
URL: http://svn.apache.org/viewvc/servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-file-2009.01.page?rev=1383357&r1=1383356&r2=1383357&view=diff
==============================================================================
--- servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-file-2009.01.page (original)
+++ servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-file-2009.01.page Tue Sep 11 11:26:45 2012
@@ -1,23 +1,23 @@
----
-title: servicemix-file 2009.01
-page_version: 1
-page_creator: gertvanthienen
-page_modifier: gertvanthienen
---- pipeline:conf
+---
+title: servicemix-file 2009.01
+page_version: 1
+page_creator: gertvanthienen
+page_modifier: gertvanthienen
+--- pipeline:conf
 
 {excerpt}Release Notes - ServiceMix Components - Version servicemix-file-2009.01{excerpt}
 
 
 *Bug*
-    * [SMXCOMP-52|http://issues.apache.org/active/browse/SMXCOMP-52] - smx-file async FilePollerEndpoint needs a throttling mechanism to avoid creating excessive numbers of open exchanges and overloading the nmr
-    * [SMXCOMP-111|http://issues.apache.org/active/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
-    * [SMXCOMP-113|http://issues.apache.org/active/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
-    * [SMXCOMP-119|http://issues.apache.org/active/browse/SMXCOMP-119] - LockManager impl causes memory leak in ServiceMix EIP
-    * [SMXCOMP-177|http://issues.apache.org/active/browse/SMXCOMP-177] - Using File Poller with Archive attribute fails when file with same name has been previously used
-    * [SMXCOMP-458|http://issues.apache.org/active/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
-    * [SMXCOMP-478|http://issues.apache.org/active/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
+    * [SMXCOMP-52|http://issues.apache.org/jira/browse/SMXCOMP-52] - smx-file async FilePollerEndpoint needs a throttling mechanism to avoid creating excessive numbers of open exchanges and overloading the nmr
+    * [SMXCOMP-111|http://issues.apache.org/jira/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
+    * [SMXCOMP-113|http://issues.apache.org/jira/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
+    * [SMXCOMP-119|http://issues.apache.org/jira/browse/SMXCOMP-119] - LockManager impl causes memory leak in ServiceMix EIP
+    * [SMXCOMP-177|http://issues.apache.org/jira/browse/SMXCOMP-177] - Using File Poller with Archive attribute fails when file with same name has been previously used
+    * [SMXCOMP-458|http://issues.apache.org/jira/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
+    * [SMXCOMP-478|http://issues.apache.org/jira/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
 
 *Improvement*
-    * [SMXCOMP-115|http://issues.apache.org/active/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
-    * [SMXCOMP-116|http://issues.apache.org/active/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
-    * [SMXCOMP-179|http://issues.apache.org/active/browse/SMXCOMP-179] - Add better documentation around attributes & elements for the servicemix-file component
\ No newline at end of file
+    * [SMXCOMP-115|http://issues.apache.org/jira/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
+    * [SMXCOMP-116|http://issues.apache.org/jira/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
+    * [SMXCOMP-179|http://issues.apache.org/jira/browse/SMXCOMP-179] - Add better documentation around attributes & elements for the servicemix-file component
\ No newline at end of file

Modified: servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-ftp-2009.01.page
URL: http://svn.apache.org/viewvc/servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-ftp-2009.01.page?rev=1383357&r1=1383356&r2=1383357&view=diff
==============================================================================
--- servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-ftp-2009.01.page (original)
+++ servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-ftp-2009.01.page Tue Sep 11 11:26:45 2012
@@ -1,26 +1,26 @@
----
-title: servicemix-ftp 2009.01
-page_version: 1
-page_creator: gertvanthienen
-page_modifier: gertvanthienen
---- pipeline:conf
+---
+title: servicemix-ftp 2009.01
+page_version: 1
+page_creator: gertvanthienen
+page_modifier: gertvanthienen
+--- pipeline:conf
 
 {excerpt}Release Notes - ServiceMix Components - Version servicemix-ftp-2009.01{excerpt}
 
 
 *Bug*
-    * [SMXCOMP-111|http://issues.apache.org/active/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
-    * [SMXCOMP-113|http://issues.apache.org/active/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
-    * [SMXCOMP-119|http://issues.apache.org/active/browse/SMXCOMP-119] - LockManager impl causes memory leak in ServiceMix EIP
-    * [SMXCOMP-458|http://issues.apache.org/active/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
-    * [SMXCOMP-478|http://issues.apache.org/active/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
+    * [SMXCOMP-111|http://issues.apache.org/jira/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
+    * [SMXCOMP-113|http://issues.apache.org/jira/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
+    * [SMXCOMP-119|http://issues.apache.org/jira/browse/SMXCOMP-119] - LockManager impl causes memory leak in ServiceMix EIP
+    * [SMXCOMP-458|http://issues.apache.org/jira/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
+    * [SMXCOMP-478|http://issues.apache.org/jira/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
 
 *Improvement*
-    * [SMXCOMP-115|http://issues.apache.org/active/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
-    * [SMXCOMP-116|http://issues.apache.org/active/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
-    * [SMXCOMP-173|http://issues.apache.org/active/browse/SMXCOMP-173] - Add "uploadPrefix" property to FtpSenderEndpoint
-    * [SMXCOMP-174|http://issues.apache.org/active/browse/SMXCOMP-174] - FTP poller should be able to archive files and autocreate directories if needed
-    * [SMXCOMP-175|http://issues.apache.org/active/browse/SMXCOMP-175] - Skipping file xxxxxxx: the file no longer exists on the server
+    * [SMXCOMP-115|http://issues.apache.org/jira/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
+    * [SMXCOMP-116|http://issues.apache.org/jira/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
+    * [SMXCOMP-173|http://issues.apache.org/jira/browse/SMXCOMP-173] - Add "uploadPrefix" property to FtpSenderEndpoint
+    * [SMXCOMP-174|http://issues.apache.org/jira/browse/SMXCOMP-174] - FTP poller should be able to archive files and autocreate directories if needed
+    * [SMXCOMP-175|http://issues.apache.org/jira/browse/SMXCOMP-175] - Skipping file xxxxxxx: the file no longer exists on the server
 
 
 

Modified: servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-http-2009.01.page
URL: http://svn.apache.org/viewvc/servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-http-2009.01.page?rev=1383357&r1=1383356&r2=1383357&view=diff
==============================================================================
--- servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-http-2009.01.page (original)
+++ servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-http-2009.01.page Tue Sep 11 11:26:45 2012
@@ -1,37 +1,37 @@
----
-title: servicemix-http 2009.01
-page_version: 1
-page_creator: gertvanthienen
-page_modifier: gertvanthienen
---- pipeline:conf
+---
+title: servicemix-http 2009.01
+page_version: 1
+page_creator: gertvanthienen
+page_modifier: gertvanthienen
+--- pipeline:conf
 
 {excerpt}Release Notes - ServiceMix Components - Version servicemix-http-2009.01{excerpt}
 
 
 *Bug*
-    * [SMXCOMP-111|http://issues.apache.org/active/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
-    * [SMXCOMP-113|http://issues.apache.org/active/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
-    * [SMXCOMP-160|http://issues.apache.org/active/browse/SMXCOMP-160] - When a SU is stopped on servicemix-http, pending exchanges are not processed correctly
-    * [SMXCOMP-161|http://issues.apache.org/active/browse/SMXCOMP-161] - running servicemix-http unit tests stalls intermittently
-    * [SMXCOMP-165|http://issues.apache.org/active/browse/SMXCOMP-165] - servicemix-http provider endpoint may convey incorrect http headers, leading to problems
-    * [SMXCOMP-172|http://issues.apache.org/active/browse/SMXCOMP-172] - Build problem: Incorrect parent pom version
-    * [SMXCOMP-458|http://issues.apache.org/active/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
-    * [SMXCOMP-469|http://issues.apache.org/active/browse/SMXCOMP-469] - Terminated exchanges are sometimes sent when handling an exception, leading to errors
-    * [SMXCOMP-478|http://issues.apache.org/active/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
+    * [SMXCOMP-111|http://issues.apache.org/jira/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
+    * [SMXCOMP-113|http://issues.apache.org/jira/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
+    * [SMXCOMP-160|http://issues.apache.org/jira/browse/SMXCOMP-160] - When a SU is stopped on servicemix-http, pending exchanges are not processed correctly
+    * [SMXCOMP-161|http://issues.apache.org/jira/browse/SMXCOMP-161] - running servicemix-http unit tests stalls intermittently
+    * [SMXCOMP-165|http://issues.apache.org/jira/browse/SMXCOMP-165] - servicemix-http provider endpoint may convey incorrect http headers, leading to problems
+    * [SMXCOMP-172|http://issues.apache.org/jira/browse/SMXCOMP-172] - Build problem: Incorrect parent pom version
+    * [SMXCOMP-458|http://issues.apache.org/jira/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
+    * [SMXCOMP-469|http://issues.apache.org/jira/browse/SMXCOMP-469] - Terminated exchanges are sometimes sent when handling an exception, leading to errors
+    * [SMXCOMP-478|http://issues.apache.org/jira/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
 
 *Improvement*
-    * [SMXCOMP-115|http://issues.apache.org/active/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
-    * [SMXCOMP-116|http://issues.apache.org/active/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
-    * [SMXCOMP-152|http://issues.apache.org/active/browse/SMXCOMP-152] - Add WSDL proxy in new HTTP endpoint
-    * [SMXCOMP-157|http://issues.apache.org/active/browse/SMXCOMP-157] - Update JettyContextManager to use QueuedThreadPool (BoundedThreadPool is deprecated)
-    * [SMXCOMP-164|http://issues.apache.org/active/browse/SMXCOMP-164] - servicemix-http consumer endpoints can not handle PUT and DELETE methods
-    * [SMXCOMP-168|http://issues.apache.org/active/browse/SMXCOMP-168] - servicemix-http component depends on servicemix-core for compilation which can be removed and the dependcy can be dropped down to test scope.
-    * [SMXCOMP-170|http://issues.apache.org/active/browse/SMXCOMP-170] - SoapEndpoint loadWsdl() does not support importing from relative paths
+    * [SMXCOMP-115|http://issues.apache.org/jira/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
+    * [SMXCOMP-116|http://issues.apache.org/jira/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
+    * [SMXCOMP-152|http://issues.apache.org/jira/browse/SMXCOMP-152] - Add WSDL proxy in new HTTP endpoint
+    * [SMXCOMP-157|http://issues.apache.org/jira/browse/SMXCOMP-157] - Update JettyContextManager to use QueuedThreadPool (BoundedThreadPool is deprecated)
+    * [SMXCOMP-164|http://issues.apache.org/jira/browse/SMXCOMP-164] - servicemix-http consumer endpoints can not handle PUT and DELETE methods
+    * [SMXCOMP-168|http://issues.apache.org/jira/browse/SMXCOMP-168] - servicemix-http component depends on servicemix-core for compilation which can be removed and the dependcy can be dropped down to test scope.
+    * [SMXCOMP-170|http://issues.apache.org/jira/browse/SMXCOMP-170] - SoapEndpoint loadWsdl() does not support importing from relative paths
 
 *New Feature*
-    * [SMXCOMP-155|http://issues.apache.org/active/browse/SMXCOMP-155] - Support WS-Addressing for the new http endpoints
-    * [SMXCOMP-166|http://issues.apache.org/active/browse/SMXCOMP-166] - servicemix-http: Support for "Content-Encoding: gzip" both on the consumer and the provider side
+    * [SMXCOMP-155|http://issues.apache.org/jira/browse/SMXCOMP-155] - Support WS-Addressing for the new http endpoints
+    * [SMXCOMP-166|http://issues.apache.org/jira/browse/SMXCOMP-166] - servicemix-http: Support for "Content-Encoding: gzip" both on the consumer and the provider side
 
 *Task*
-    * [SMXCOMP-154|http://issues.apache.org/active/browse/SMXCOMP-154] - Remove the HttpManagedServlet from servicemix-http, as it is duplicated by the one in apache-servicemix-web and introduce a strong dependency on servicemix-core
-    * [SMXCOMP-159|http://issues.apache.org/active/browse/SMXCOMP-159] - Upgrade to Jetty 6.1.12
\ No newline at end of file
+    * [SMXCOMP-154|http://issues.apache.org/jira/browse/SMXCOMP-154] - Remove the HttpManagedServlet from servicemix-http, as it is duplicated by the one in apache-servicemix-web and introduce a strong dependency on servicemix-core
+    * [SMXCOMP-159|http://issues.apache.org/jira/browse/SMXCOMP-159] - Upgrade to Jetty 6.1.12
\ No newline at end of file

Modified: servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-jms-2009.01.page
URL: http://svn.apache.org/viewvc/servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-jms-2009.01.page?rev=1383357&r1=1383356&r2=1383357&view=diff
==============================================================================
--- servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-jms-2009.01.page (original)
+++ servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-jms-2009.01.page Tue Sep 11 11:26:45 2012
@@ -1,35 +1,35 @@
----
-title: servicemix-jms 2009.01
-page_version: 1
-page_creator: gertvanthienen
-page_modifier: gertvanthienen
---- pipeline:conf
+---
+title: servicemix-jms 2009.01
+page_version: 1
+page_creator: gertvanthienen
+page_modifier: gertvanthienen
+--- pipeline:conf
 
 {excerpt}Release Notes - ServiceMix Components - Version servicemix-jms-2009.01{excerpt}
 
 
 *Bug*
-    * [SMXCOMP-111|http://issues.apache.org/active/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
-    * [SMXCOMP-113|http://issues.apache.org/active/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
-    * [SMXCOMP-126|http://issues.apache.org/active/browse/SMXCOMP-126] - JmsProviderEndpointTest hang
-    * [SMXCOMP-127|http://issues.apache.org/active/browse/SMXCOMP-127] - No rollback for failed InOnly exchange in JMS consumer endpoint
-    * [SMXCOMP-129|http://issues.apache.org/active/browse/SMXCOMP-129] - The "Content-Type" property is used in jms messages, but it is not compliant with the jms spec
-    * [SMXCOMP-131|http://issues.apache.org/active/browse/SMXCOMP-131] - Update servicemix-jms to use soap over jms spec property values
-    * [SMXCOMP-133|http://issues.apache.org/active/browse/SMXCOMP-133] - new smx-jms marshaler throws exception attempting to copy property "JbiConstants.DATESTAMP_PROPERTY_NAME" from NMR to JMS
-    * [SMXCOMP-138|http://issues.apache.org/active/browse/SMXCOMP-138] - smx-jms new, non-soap, in/out, provider/consumer endpoints do not pass JBI Faults correctly
-    * [SMXCOMP-140|http://issues.apache.org/active/browse/SMXCOMP-140] - smx-jms new, non-soap, in/out, provider/consumer endpoints do not pass JBI Errors correctly
-    * [SMXCOMP-141|http://issues.apache.org/active/browse/SMXCOMP-141] - smx-jms new, non-soap, in/out, provider/consumer endpoints do not pass JBI Attachments correctly
-    * [SMXCOMP-143|http://issues.apache.org/active/browse/SMXCOMP-143] - smx-jms old, non-soap, in/out, provider/consumer endpoints do not pass JBI Faults correctly
-    * [SMXCOMP-145|http://issues.apache.org/active/browse/SMXCOMP-145] - smx-jms provider should not create a temporary replyTo destination unless one is needed
-    * [SMXCOMP-458|http://issues.apache.org/active/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
-    * [SMXCOMP-478|http://issues.apache.org/active/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
+    * [SMXCOMP-111|http://issues.apache.org/jira/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
+    * [SMXCOMP-113|http://issues.apache.org/jira/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
+    * [SMXCOMP-126|http://issues.apache.org/jira/browse/SMXCOMP-126] - JmsProviderEndpointTest hang
+    * [SMXCOMP-127|http://issues.apache.org/jira/browse/SMXCOMP-127] - No rollback for failed InOnly exchange in JMS consumer endpoint
+    * [SMXCOMP-129|http://issues.apache.org/jira/browse/SMXCOMP-129] - The "Content-Type" property is used in jms messages, but it is not compliant with the jms spec
+    * [SMXCOMP-131|http://issues.apache.org/jira/browse/SMXCOMP-131] - Update servicemix-jms to use soap over jms spec property values
+    * [SMXCOMP-133|http://issues.apache.org/jira/browse/SMXCOMP-133] - new smx-jms marshaler throws exception attempting to copy property "JbiConstants.DATESTAMP_PROPERTY_NAME" from NMR to JMS
+    * [SMXCOMP-138|http://issues.apache.org/jira/browse/SMXCOMP-138] - smx-jms new, non-soap, in/out, provider/consumer endpoints do not pass JBI Faults correctly
+    * [SMXCOMP-140|http://issues.apache.org/jira/browse/SMXCOMP-140] - smx-jms new, non-soap, in/out, provider/consumer endpoints do not pass JBI Errors correctly
+    * [SMXCOMP-141|http://issues.apache.org/jira/browse/SMXCOMP-141] - smx-jms new, non-soap, in/out, provider/consumer endpoints do not pass JBI Attachments correctly
+    * [SMXCOMP-143|http://issues.apache.org/jira/browse/SMXCOMP-143] - smx-jms old, non-soap, in/out, provider/consumer endpoints do not pass JBI Faults correctly
+    * [SMXCOMP-145|http://issues.apache.org/jira/browse/SMXCOMP-145] - smx-jms provider should not create a temporary replyTo destination unless one is needed
+    * [SMXCOMP-458|http://issues.apache.org/jira/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
+    * [SMXCOMP-478|http://issues.apache.org/jira/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
 
 *Improvement*
-    * [SMXCOMP-115|http://issues.apache.org/active/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
-    * [SMXCOMP-116|http://issues.apache.org/active/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
-    * [SMXCOMP-136|http://issues.apache.org/active/browse/SMXCOMP-136] - smx-jms consumer endpoints should support maxConcurrentConsumers property from Spring JMS
-    * [SMXCOMP-148|http://issues.apache.org/active/browse/SMXCOMP-148] - Refactor JmsProviderEndpoint to not use reflection to call protected method on Spring JmsTemplate class
-    * [SMXCOMP-150|http://issues.apache.org/active/browse/SMXCOMP-150] - Added dependency to servicemix-jms POM to ensure that base endpoint properties are documented in the xbean generated XSD, Wiki, HTML
+    * [SMXCOMP-115|http://issues.apache.org/jira/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
+    * [SMXCOMP-116|http://issues.apache.org/jira/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
+    * [SMXCOMP-136|http://issues.apache.org/jira/browse/SMXCOMP-136] - smx-jms consumer endpoints should support maxConcurrentConsumers property from Spring JMS
+    * [SMXCOMP-148|http://issues.apache.org/jira/browse/SMXCOMP-148] - Refactor JmsProviderEndpoint to not use reflection to call protected method on Spring JmsTemplate class
+    * [SMXCOMP-150|http://issues.apache.org/jira/browse/SMXCOMP-150] - Added dependency to servicemix-jms POM to ensure that base endpoint properties are documented in the xbean generated XSD, Wiki, HTML
 
 
 

Modified: servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-jsr181-2009.01.page
URL: http://svn.apache.org/viewvc/servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-jsr181-2009.01.page?rev=1383357&r1=1383356&r2=1383357&view=diff
==============================================================================
--- servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-jsr181-2009.01.page (original)
+++ servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-jsr181-2009.01.page Tue Sep 11 11:26:45 2012
@@ -1,19 +1,19 @@
----
-title: servicemix-jsr181 2009.01
-page_version: 1
-page_creator: gertvanthienen
-page_modifier: gertvanthienen
---- pipeline:conf
+---
+title: servicemix-jsr181 2009.01
+page_version: 1
+page_creator: gertvanthienen
+page_modifier: gertvanthienen
+--- pipeline:conf
 
 {excerpt}Release Notes - ServiceMix Components - Version servicemix-jsr181-2009.01{excerpt}
 
 
 *Bug*
-    * [SMXCOMP-111|http://issues.apache.org/active/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
-    * [SMXCOMP-113|http://issues.apache.org/active/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
-    * [SMXCOMP-263|http://issues.apache.org/active/browse/SMXCOMP-263] - jsr181ServiceUnitAnalyser returns null channel while using jbi-maven-plugin to create service-unit decriptor which caues it to fail.
-    * [SMXCOMP-478|http://issues.apache.org/active/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
+    * [SMXCOMP-111|http://issues.apache.org/jira/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
+    * [SMXCOMP-113|http://issues.apache.org/jira/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
+    * [SMXCOMP-263|http://issues.apache.org/jira/browse/SMXCOMP-263] - jsr181ServiceUnitAnalyser returns null channel while using jbi-maven-plugin to create service-unit decriptor which caues it to fail.
+    * [SMXCOMP-478|http://issues.apache.org/jira/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
 
 *Improvement*
-    * [SMXCOMP-115|http://issues.apache.org/active/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
-    * [SMXCOMP-116|http://issues.apache.org/active/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
+    * [SMXCOMP-115|http://issues.apache.org/jira/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
+    * [SMXCOMP-116|http://issues.apache.org/jira/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2

Modified: servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-mail-2009.01.page
URL: http://svn.apache.org/viewvc/servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-mail-2009.01.page?rev=1383357&r1=1383356&r2=1383357&view=diff
==============================================================================
--- servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-mail-2009.01.page (original)
+++ servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-mail-2009.01.page Tue Sep 11 11:26:45 2012
@@ -1,27 +1,27 @@
----
-title: servicemix-mail 2009.01
-page_version: 1
-page_creator: gertvanthienen
-page_modifier: gertvanthienen
---- pipeline:conf
+---
+title: servicemix-mail 2009.01
+page_version: 1
+page_creator: gertvanthienen
+page_modifier: gertvanthienen
+--- pipeline:conf
 
 {excerpt}Release Notes - ServiceMix Components - Version servicemix-mail-2009.01{excerpt}
 
 
 *Bug*
-    * [SMXCOMP-3|http://issues.apache.org/active/browse/SMXCOMP-3] - servicemix-mail is not handling POP3 protocol correctly
-    * [SMXCOMP-111|http://issues.apache.org/active/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
-    * [SMXCOMP-113|http://issues.apache.org/active/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
-    * [SMXCOMP-458|http://issues.apache.org/active/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
-    * [SMXCOMP-472|http://issues.apache.org/active/browse/SMXCOMP-472] - ServiceMix-Mail broken in SMX4
-    * [SMXCOMP-478|http://issues.apache.org/active/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
-    * [SMXCOMP-481|http://issues.apache.org/active/browse/SMXCOMP-481] - connection not closed when error occurs on sendExchange
+    * [SMXCOMP-3|http://issues.apache.org/jira/browse/SMXCOMP-3] - servicemix-mail is not handling POP3 protocol correctly
+    * [SMXCOMP-111|http://issues.apache.org/jira/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
+    * [SMXCOMP-113|http://issues.apache.org/jira/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
+    * [SMXCOMP-458|http://issues.apache.org/jira/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
+    * [SMXCOMP-472|http://issues.apache.org/jira/browse/SMXCOMP-472] - ServiceMix-Mail broken in SMX4
+    * [SMXCOMP-478|http://issues.apache.org/jira/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
+    * [SMXCOMP-481|http://issues.apache.org/jira/browse/SMXCOMP-481] - connection not closed when error occurs on sendExchange
 
 *Improvement*
-    * [SMXCOMP-4|http://issues.apache.org/active/browse/SMXCOMP-4] - Apply xbean documentation recommendations to the servicemix-mail component
-    * [SMXCOMP-115|http://issues.apache.org/active/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
-    * [SMXCOMP-116|http://issues.apache.org/active/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
+    * [SMXCOMP-4|http://issues.apache.org/jira/browse/SMXCOMP-4] - Apply xbean documentation recommendations to the servicemix-mail component
+    * [SMXCOMP-115|http://issues.apache.org/jira/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
+    * [SMXCOMP-116|http://issues.apache.org/jira/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
 
 
 *Task*
-    * [SMXCOMP-2|http://issues.apache.org/active/browse/SMXCOMP-2] - Improve the mail component
+    * [SMXCOMP-2|http://issues.apache.org/jira/browse/SMXCOMP-2] - Improve the mail component

Modified: servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-osworkflow-2009.01.page
URL: http://svn.apache.org/viewvc/servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-osworkflow-2009.01.page?rev=1383357&r1=1383356&r2=1383357&view=diff
==============================================================================
--- servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-osworkflow-2009.01.page (original)
+++ servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-osworkflow-2009.01.page Tue Sep 11 11:26:45 2012
@@ -1,20 +1,20 @@
----
-title: servicemix-osworkflow 2009.01
-page_version: 1
-page_creator: gertvanthienen
-page_modifier: gertvanthienen
---- pipeline:conf
+---
+title: servicemix-osworkflow 2009.01
+page_version: 1
+page_creator: gertvanthienen
+page_modifier: gertvanthienen
+--- pipeline:conf
 
 {excerpt}Release Notes - ServiceMix Components - Version servicemix-osworkflow-2009.01{excerpt}
 
 
 *Bug*
-    * [SMXCOMP-111|http://issues.apache.org/active/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
-    * [SMXCOMP-113|http://issues.apache.org/active/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
-    * [SMXCOMP-458|http://issues.apache.org/active/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
-    * [SMXCOMP-478|http://issues.apache.org/active/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
+    * [SMXCOMP-111|http://issues.apache.org/jira/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
+    * [SMXCOMP-113|http://issues.apache.org/jira/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
+    * [SMXCOMP-458|http://issues.apache.org/jira/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
+    * [SMXCOMP-478|http://issues.apache.org/jira/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
 
 *Improvement*
-    * [SMXCOMP-115|http://issues.apache.org/active/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
-    * [SMXCOMP-116|http://issues.apache.org/active/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
+    * [SMXCOMP-115|http://issues.apache.org/jira/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
+    * [SMXCOMP-116|http://issues.apache.org/jira/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
 

Modified: servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-quartz-2009.01.page
URL: http://svn.apache.org/viewvc/servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-quartz-2009.01.page?rev=1383357&r1=1383356&r2=1383357&view=diff
==============================================================================
--- servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-quartz-2009.01.page (original)
+++ servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-quartz-2009.01.page Tue Sep 11 11:26:45 2012
@@ -1,21 +1,21 @@
----
-title: servicemix-quartz 2009.01
-page_version: 1
-page_creator: gertvanthienen
-page_modifier: gertvanthienen
---- pipeline:conf
+---
+title: servicemix-quartz 2009.01
+page_version: 1
+page_creator: gertvanthienen
+page_modifier: gertvanthienen
+--- pipeline:conf
 
 {excerpt}Release Notes - ServiceMix Components - Version servicemix-quartz-2009.01{excerpt}
 
 
 *Bug*
-    * [SMXCOMP-111|http://issues.apache.org/active/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
-    * [SMXCOMP-113|http://issues.apache.org/active/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
-    * [SMXCOMP-458|http://issues.apache.org/active/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
-    * [SMXCOMP-478|http://issues.apache.org/active/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
+    * [SMXCOMP-111|http://issues.apache.org/jira/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
+    * [SMXCOMP-113|http://issues.apache.org/jira/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
+    * [SMXCOMP-458|http://issues.apache.org/jira/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
+    * [SMXCOMP-478|http://issues.apache.org/jira/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
 
 *Improvement*
-    * [SMXCOMP-115|http://issues.apache.org/active/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
-    * [SMXCOMP-116|http://issues.apache.org/active/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
+    * [SMXCOMP-115|http://issues.apache.org/jira/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
+    * [SMXCOMP-116|http://issues.apache.org/jira/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
 
 

Modified: servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-saxon-2009.01.page
URL: http://svn.apache.org/viewvc/servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-saxon-2009.01.page?rev=1383357&r1=1383356&r2=1383357&view=diff
==============================================================================
--- servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-saxon-2009.01.page (original)
+++ servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-saxon-2009.01.page Tue Sep 11 11:26:45 2012
@@ -1,22 +1,22 @@
----
-title: servicemix-saxon 2009.01
-page_version: 1
-page_creator: gertvanthienen
-page_modifier: gertvanthienen
---- pipeline:conf
+---
+title: servicemix-saxon 2009.01
+page_version: 1
+page_creator: gertvanthienen
+page_modifier: gertvanthienen
+--- pipeline:conf
 
 {excerpt}Release Notes - ServiceMix Components - Version servicemix-saxon-2009.01{excerpt}
 
 
 *Bug*
-    * [SMXCOMP-111|http://issues.apache.org/active/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
-    * [SMXCOMP-113|http://issues.apache.org/active/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
-    * [SMXCOMP-458|http://issues.apache.org/active/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
-    * [SMXCOMP-478|http://issues.apache.org/active/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
+    * [SMXCOMP-111|http://issues.apache.org/jira/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
+    * [SMXCOMP-113|http://issues.apache.org/jira/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
+    * [SMXCOMP-458|http://issues.apache.org/jira/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
+    * [SMXCOMP-478|http://issues.apache.org/jira/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
 
 *Improvement*
-    * [SMXCOMP-115|http://issues.apache.org/active/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
-    * [SMXCOMP-116|http://issues.apache.org/active/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
+    * [SMXCOMP-115|http://issues.apache.org/jira/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
+    * [SMXCOMP-116|http://issues.apache.org/jira/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
 
 *New Feature*
-    * [SMXCOMP-223|http://issues.apache.org/active/browse/SMXCOMP-223] - Make Resources in ServiceMix-Saxon smart enough to reload themselves
+    * [SMXCOMP-223|http://issues.apache.org/jira/browse/SMXCOMP-223] - Make Resources in ServiceMix-Saxon smart enough to reload themselves

Modified: servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-script-2009.01.page
URL: http://svn.apache.org/viewvc/servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-script-2009.01.page?rev=1383357&r1=1383356&r2=1383357&view=diff
==============================================================================
--- servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-script-2009.01.page (original)
+++ servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-script-2009.01.page Tue Sep 11 11:26:45 2012
@@ -1,17 +1,17 @@
----
-title: servicemix-script 2009.01
-page_version: 1
-page_creator: gertvanthienen
-page_modifier: gertvanthienen
---- pipeline:conf
+---
+title: servicemix-script 2009.01
+page_version: 1
+page_creator: gertvanthienen
+page_modifier: gertvanthienen
+--- pipeline:conf
 {excerpt}Release Notes - ServiceMix Components - Version servicemix-script-2009.01{excerpt}
 
 
 *Bug*
-    * [SMXCOMP-111|http://issues.apache.org/active/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
-    * [SMXCOMP-113|http://issues.apache.org/active/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
-    * [SMXCOMP-478|http://issues.apache.org/active/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
+    * [SMXCOMP-111|http://issues.apache.org/jira/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
+    * [SMXCOMP-113|http://issues.apache.org/jira/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
+    * [SMXCOMP-478|http://issues.apache.org/jira/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
 
 *Improvement*
-    * [SMXCOMP-115|http://issues.apache.org/active/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
-    * [SMXCOMP-116|http://issues.apache.org/active/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
+    * [SMXCOMP-115|http://issues.apache.org/jira/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
+    * [SMXCOMP-116|http://issues.apache.org/jira/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2

Modified: servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-scripting-2009.01.page
URL: http://svn.apache.org/viewvc/servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-scripting-2009.01.page?rev=1383357&r1=1383356&r2=1383357&view=diff
==============================================================================
--- servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-scripting-2009.01.page (original)
+++ servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-scripting-2009.01.page Tue Sep 11 11:26:45 2012
@@ -1,21 +1,21 @@
----
-title: servicemix-scripting 2009.01
-page_version: 1
-page_creator: gertvanthienen
-page_modifier: gertvanthienen
---- pipeline:conf
+---
+title: servicemix-scripting 2009.01
+page_version: 1
+page_creator: gertvanthienen
+page_modifier: gertvanthienen
+--- pipeline:conf
 
 {excerpt}Release Notes - ServiceMix Components - Version servicemix-scripting-2009.01{excerpt}
 
 
 *Bug*
-    * [SMXCOMP-111|http://issues.apache.org/active/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
-    * [SMXCOMP-113|http://issues.apache.org/active/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
-    * [SMXCOMP-221|http://issues.apache.org/active/browse/SMXCOMP-221] - ServiceMix Scripting does not support all the features of the old one ( The lightweight )
-    * [SMXCOMP-458|http://issues.apache.org/active/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
-    * [SMXCOMP-478|http://issues.apache.org/active/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
+    * [SMXCOMP-111|http://issues.apache.org/jira/browse/SMXCOMP-111] - When deployed in Smx4, the JBI SUs do not have access to the whole JRE
+    * [SMXCOMP-113|http://issues.apache.org/jira/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
+    * [SMXCOMP-221|http://issues.apache.org/jira/browse/SMXCOMP-221] - ServiceMix Scripting does not support all the features of the old one ( The lightweight )
+    * [SMXCOMP-458|http://issues.apache.org/jira/browse/SMXCOMP-458] - Malformed manifest.mf  is generated for the servicemix-http bundle
+    * [SMXCOMP-478|http://issues.apache.org/jira/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
 
 *Improvement*
-    * [SMXCOMP-115|http://issues.apache.org/active/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
-    * [SMXCOMP-116|http://issues.apache.org/active/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
-    * [SMXCOMP-222|http://issues.apache.org/active/browse/SMXCOMP-222] - update to latest jsr223 api for servicemix-scripting
+    * [SMXCOMP-115|http://issues.apache.org/jira/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
+    * [SMXCOMP-116|http://issues.apache.org/jira/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
+    * [SMXCOMP-222|http://issues.apache.org/jira/browse/SMXCOMP-222] - update to latest jsr223 api for servicemix-scripting

Modified: servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-shared-2009.01.page
URL: http://svn.apache.org/viewvc/servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-shared-2009.01.page?rev=1383357&r1=1383356&r2=1383357&view=diff
==============================================================================
--- servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-shared-2009.01.page (original)
+++ servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-shared-2009.01.page Tue Sep 11 11:26:45 2012
@@ -1,26 +1,26 @@
----
-title: servicemix-shared 2009.01
-page_version: 1
-page_creator: gertvanthienen
-page_modifier: gertvanthienen
---- pipeline:conf
+---
+title: servicemix-shared 2009.01
+page_version: 1
+page_creator: gertvanthienen
+page_modifier: gertvanthienen
+--- pipeline:conf
 
 {excerpt}Release Notes - ServiceMix Components - Version servicemix-shared-2009.01{excerpt}
 
 
 *Bug*
-    * [SMXCOMP-113|http://issues.apache.org/active/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
-    * [SMXCOMP-226|http://issues.apache.org/active/browse/SMXCOMP-226] - AsyncBaseLifeCycle should catch all throwables when processing a given exchange
-    * [SMXCOMP-460|http://issues.apache.org/active/browse/SMXCOMP-460] - The TCCL is not set to the correct value after deploying a service unit
-    * [SMXCOMP-469|http://issues.apache.org/active/browse/SMXCOMP-469] - Terminated exchanges are sometimes sent when handling an exception, leading to errors
-    * [SMXCOMP-478|http://issues.apache.org/active/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
+    * [SMXCOMP-113|http://issues.apache.org/jira/browse/SMXCOMP-113] - Components jars should not include the jbi descriptor
+    * [SMXCOMP-226|http://issues.apache.org/jira/browse/SMXCOMP-226] - AsyncBaseLifeCycle should catch all throwables when processing a given exchange
+    * [SMXCOMP-460|http://issues.apache.org/jira/browse/SMXCOMP-460] - The TCCL is not set to the correct value after deploying a service unit
+    * [SMXCOMP-469|http://issues.apache.org/jira/browse/SMXCOMP-469] - Terminated exchanges are sometimes sent when handling an exception, leading to errors
+    * [SMXCOMP-478|http://issues.apache.org/jira/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
 
 *Improvement*
-    * [SMXCOMP-115|http://issues.apache.org/active/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
-    * [SMXCOMP-116|http://issues.apache.org/active/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
-    * [SMXCOMP-170|http://issues.apache.org/active/browse/SMXCOMP-170] - SoapEndpoint loadWsdl() does not support importing from relative paths
-    * [SMXCOMP-179|http://issues.apache.org/active/browse/SMXCOMP-179] - Add better documentation around attributes & elements for the servicemix-file component
-    * [SMXCOMP-225|http://issues.apache.org/active/browse/SMXCOMP-225] - Add additional Log output to the SimpleEndpoint methods
+    * [SMXCOMP-115|http://issues.apache.org/jira/browse/SMXCOMP-115] - Patch available for upgrading components to Spring 2.5.6
+    * [SMXCOMP-116|http://issues.apache.org/jira/browse/SMXCOMP-116] - Upgrade to spring osgi 1.2.0-m2
+    * [SMXCOMP-170|http://issues.apache.org/jira/browse/SMXCOMP-170] - SoapEndpoint loadWsdl() does not support importing from relative paths
+    * [SMXCOMP-179|http://issues.apache.org/jira/browse/SMXCOMP-179] - Add better documentation around attributes & elements for the servicemix-file component
+    * [SMXCOMP-225|http://issues.apache.org/jira/browse/SMXCOMP-225] - Add additional Log output to the SimpleEndpoint methods
 
 *New Feature*
-    * [SMXCOMP-155|http://issues.apache.org/active/browse/SMXCOMP-155] - Support WS-Addressing for the new http endpoints
\ No newline at end of file
+    * [SMXCOMP-155|http://issues.apache.org/jira/browse/SMXCOMP-155] - Support WS-Addressing for the new http endpoints
\ No newline at end of file

Modified: servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-smpp-2009.01.page
URL: http://svn.apache.org/viewvc/servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-smpp-2009.01.page?rev=1383357&r1=1383356&r2=1383357&view=diff
==============================================================================
--- servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-smpp-2009.01.page (original)
+++ servicemix/website/trunk/src/main/webapp/downloads/subprojects/servicemix-smpp-2009.01.page Tue Sep 11 11:26:45 2012
@@ -4,9 +4,9 @@ page_version: 1
 page_creator: gertvanthienen
 page_modifier: gertvanthienen
 --- pipeline:conf
-
-{excerpt}Release Notes - ServiceMix Components - Version servicemix-smpp-2009.01{excerpt}
-
-
-*Bug*
-    * [SMXCOMP-478|http://issues.apache.org/active/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle
+
+{excerpt}Release Notes - ServiceMix Components - Version servicemix-smpp-2009.01{excerpt}
+
+
+*Bug*
+    * [SMXCOMP-478|http://issues.apache.org/jira/browse/SMXCOMP-478] - OSGi bundles for components should not require the jaxp-ri bundle



Mime
View raw message