Sergey Beryozkin-5 wrote: > > This causes problems when doing non-Spring CXF deployments. > Generally, we should really try to keep the Spring related code in .spring > subpackages as it will make it simpler for CXF be integrated with other > similar frameworks or deployed in containers providing the optional Spring > support only. >
I wonder if we could just rename Spring to Banana and use Banana's JARs instead. Such a wrapping would allow us to use Spring to our heart's content while at the same time truthfully saying we're 100% Spring-free. (Or would we then need to worry about supporting non-Banana deployments? :) -- View this message in context: http://cxf.547215.n5.nabble.com/JMS-transport-strongly-depends-on-Spring-tp2262704p2264402.html Sent from the cxf-dev mailing list archive at Nabble.com.
