felix-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré ...@nanthrax.net>
Subject Re: Enterprise business domain using DS - is it good idea?
Date Mon, 20 Jul 2015 11:25:03 GMT

Good point actually Carstens !

Sent from my Samsung device

-------- Original message --------
From: Carsten Ziegeler <cziegeler@apache.org> 
Date: 20/07/2015  12:39  (GMT+01:00) 
To: users@felix.apache.org, Alex Sviridov <ooo_saturn7@mail.ru> 
Subject: Re: Enterprise business domain using DS - is it good idea? 

And I think another important point is, it's not one *or* the other. You
can start with whatever you think is more suitable and if you find out
you need features from the other for something, just use it for that.
The great thing here is, you're developing services which interact with
each other through the service registry. It doesn't matter what you use
to implement them. They all work nicely together
Of course, usually dev teams try to focus on a single way to do things
(which is preferable of course), but you're not bound to this.

For example, we are usually developing everything with DS, but in some
cases we go directly with the framework API.


Am 20.07.15 um 08:25 schrieb Achim Nierbeck:
> Hi Alex,
> may I answer a couple of your questions.
> 1) it's Apache Aries, not Felix :-)
> 2) I think Christian Schneider worked on something similar transforming JEE
> Annotations to a blueprint structure, but I'm not sure how
> "production-ready" it is, as I never used it. But I'm sure he'll give some
> feedback.
> 3) Haven't seen any yet
> 4) If you take a look at the samples around Apache Karaf you'll find lots
> of Blueprint related samples [1]
> Regarding Blueprint/DS discussion, as usual you'll always find something
> that fits your needs better.
> Sometimes DS is just enough sometimes you'll need to extend something and
> find that blueprint is suited better.
> Especially the namespace handling in Blueprint brings another positive
> "side-effect", you'll be able to extend the
> blueprint mechanism with something like a authentication mechanism on
> method level, with your own
> Namespace handler an a InstanceListener. Similar to the way the
> transactions are declared in blueprint beans.
> regards, Achim

Carsten Ziegeler
Adobe Research Switzerland

To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message