Agree, Pax Spring (or whatever) could make sense. Just wonder if a lot
of people would use it.
Regards
JB
On 11/16/2015 09:03 AM, Sobkowiak Krzysztof wrote:
Hi
I'm not sure how many people need this, but it shouldn't be too difficult to
take the Spring DM sources and adjust them for Spring 4? If many people need
this and want to
volunteer perhaps it's worth to start a small project (PAX, or separate project
in Github), which develops the Spring integration based on Spring DM code base.
Regards
Krzysztof
On 16.11.2015 08:04, Jean-Baptiste Onofré wrote:
Hi Raul,
I don't think just extending the version range should be enough as the Spring API
changed between 3 & 4.
Yes, spring-* "project" should work in aries-blueprint in term of beans.
However, the namespace handler won't unfortunately :(
Regards
JB
On 11/14/2015 01:11 PM, Raul Kripalani wrote:
On Sat, Nov 14, 2015 at 6:21 AM, Jean-Baptiste Onofré <j...@nanthrax.net>
wrote:
spring-dm is dead, and the last Spring version supported is Spring 3.
Yep, I know. I wondered if it would make sense to release spring-dm bundles
opening the version range to cover Spring 4 – for folks how still want to
run this set up. I know there's no guarantee it'll work with newer
versions, but right now we don't even know.
Actually, the "replacement" of spring-dm is blueprint, so, just use
aries-blueprint.
Is it possible to use Spring modules like spring-cache, spring-tx, etc.
with a context loaded via aries-blueprint? This is the use case I'd like to
cover.
Regards,
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
