[jbossws-issues] [JBoss JIRA] Updated: (JBWS-3280) Avoid building Spring Bus when deployment has no spring descriptor

[Alessio Soldano (JIRA)]

     [ https://issues.jboss.org/browse/JBWS-3280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alessio Soldano updated JBWS-3280:
----------------------------------

    Fix Version/s:  jbossws-cxf-4.0


Scheduling for 4.0 as per discussion with Marius. Snowdrop is going to add some spring libs in the org.springframework.spring module, so the check on the availability of spring classes is not going to be valid one for deciding whether to use the spring bus or not.

> Avoid building Spring Bus when deployment has no spring descriptor
> ------------------------------------------------------------------
>
>                 Key: JBWS-3280
>                 URL: https://issues.jboss.org/browse/JBWS-3280
>             Project: JBoss Web Services
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf
>            Reporter: Alessio Soldano
>             Fix For:  jbossws-cxf-4.0
>
>
> The DescriptorDeploymentAspect currently relies on Spring availability in the classloader for deciding to generate a default jbossws-cxf.xml. Generally speaking, we should probably go the "Spring" way only when the deployment comes with a jbossws-cxf.xml (and spring is actually available ;-)), so the user explicitly asked for that.
> We might even evaluate changing the logic in JBossWSBusFactory to avoid using Spring when no spring descriptor is found (basically the same the CXF 2.4 SpringBusFactory does in public Bus createBus(String cfgFiles[], boolean includeDefaults) and we override in our JBossWS version of that factory).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira