[jira] Updated: (SMXCOMP-771) Upgrade to Spring 3.0.3.RELEASE

["Gert Vanthienen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/SMXCOMP-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gert Vanthienen updated SMXCOMP-771:
------------------------------------

    Attachment: SMXCOMP-771-servicemix-bean.diff

Attaching a diff to get the servicemix-bean tests passing again.

Most of it is just adding the correct namespace declarations, however Spring validation also seems to disallow some syntax that used to be allowed, e.g.
{noformat}
-          <bean:component searchPackages="org.apache.servicemix.bean.beans"/>
+          <bean:component>
+            <bean:searchPackages>
+              <value>org.apache.servicemix.bean.beans</value>
+            </bean:searchPackages>
+          </bean:component>
{noformat}

Not sure this will be a problem for normal JBI deployment since we're our abstract xbean deployer has validation disabled, but it might bite people that use pure Spring deployments (as in ServiceMix 4).  Perhaps we should change the XBean generated schema to explicitly allow the use of attributes in this situation?

> Upgrade to Spring 3.0.3.RELEASE
> -------------------------------
>
>                 Key: SMXCOMP-771
>                 URL: https://issues.apache.org/activemq/browse/SMXCOMP-771
>             Project: ServiceMix Components
>          Issue Type: Task
>          Components: servicemix-bean, servicemix-camel, servicemix-common, servicemix-cxf-bc, servicemix-cxf-se, servicemix-drools, servicemix-eip, servicemix-exec, servicemix-file, servicemix-ftp, servicemix-http, servicemix-jms, servicemix-jsr181, servicemix-ldap, servicemix-mail, servicemix-osworkflow, servicemix-quartz, servicemix-rmi, servicemix-saxon, servicemix-script, servicemix-scripting, servicemix-shared, servicemix-smpp, servicemix-snmp, servicemix-soap, servicemix-soap2, servicemix-truezip, servicemix-validation, servicemix-vfs, servicemix-wsn2005, servicemix-xmpp
>            Reporter: Gert Vanthienen
>             Fix For: servicemix-ldap-2010.02, servicemix-pdfcomposer-2010.02, servicemix-rmi-2010.02, servicemix-bean-2010.02, servicemix-camel-2010.02, servicemix-cxf-bc-2010.02, servicemix-cxf-se-2010.02, servicemix-drools-2010.02, servicemix-eip-2010.02, servicemix-exec-2010.02, servicemix-file-2010.02, servicemix-ftp-2010.02, servicemix-http-2010.02, servicemix-jms-2010.02, servicemix-jsr181-2010.02, servicemix-mail-2010.02, servicemix-osworkflow-2010.02, servicemix-quartz-2010.02, servicemix-saxon-2010.02, servicemix-script-2010.02, servicemix-scripting-2010.02, servicemix-shared-2010.02, servicemix-smpp-2010.02, servicemix-snmp-2010.02, servicemix-truezip-2010.02, servicemix-validation-2010.02, servicemix-vfs-2010.02, servicemix-wsn2005-2010.02, servicemix-xmpp-2010.02
>
>         Attachments: SMXCOMP-771-component-pom.diff, SMXCOMP-771-servicemix-bean.diff, SMXCOMP-771-servicemix-jms.diff, SMXCOMP-771-shared.diff
>
>
> In order to be able to migrate ServiceMix 4 to Spring 3, we should start by upgrading the components.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.