Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [gemini-dev] bean definition profiles support in gemini blueprint
Hi Glyn, Jan

Thanks for your responses!

Jan,

My problem was not with the xml file, but with the context that is created automatically by the extender. I wonder how can I specify the active profiles to use when my META-INF/spring/*.xml files are parsed and deployed? Do you have an answer?

Glyn,

Thanks for the point, I'll see what I can do. Although could you please clarify your phrase "if you can make the change so that it also works with Spring framework 3.0.x"? I think that if it is Srping 3.0.x the xml definition itself would not match the xsd schema if I use profiles. Did you mean maybe that it should be an optional functionality that works if spring is >= 3.1 and just does nothing if spring is < 3.1 ?

Thanks in advance,
Alexander Shutyaev


2013/1/21 Jan Stamer <J.Stamer@xxxxxxxxxxxxxxxxxxxx>
Hi Alexander,

actually you can use profiles along with Gemini Blueprint without problems. We are doing just that in our project.
The trick is to use the Spring 3.1 namespace and not the Blueprint one.

If you have questions feel free to contact me!

Bye,
Jan

From: gemini-dev-bounces@xxxxxxxxxxx [gemini-dev-bounces@xxxxxxxxxxx] on behalf of Glyn Normington [gnormington@xxxxxxxxxx]
Sent: Monday, January 21, 2013 3:16 PM
To: Gemini and sub-projects developer discussions
Subject: Re: [gemini-dev] bean definition profiles support in gemini blueprint

Hi Alexander

Responses inline.

Regards,
Glyn
On 21 Jan 2013, at 13:53, Alexander Shutyaev wrote:

Hi all!

Is there any support for Bean Definition Profiles [1] in gemini blueprint project?

No.

If yes, how can I specify the active profiles to use when my META-INF/spring/*.xml files are parsed and deployed? If no, then maybe you can show me some entry point in the current source code, so I can implement this support and share it. Our app really needs this. :)

I'm afraid I don't have the Gemini Blueprint codebase in my head - I'm really only a caretaker project lead currently. But I would start with the ContextLoaderListener class as the entry point for the extender and go from there.

If you do implement support, please bear in mind that not all users will necessarily want to pre-req. Spring framework 3.1, so if you can make the change so that it also works with Spring framework 3.0.x, so much the better. We are currently aiming to release Gemini Blueprint 2.0 around March, so that might be a good vehicle to carry your changes.

_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev


_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev


Back to the top