Hi Alain,
Am 09.08.2018 um 14:54 schrieb Alain Picard via osgi-dev:
On Thu, Aug 9, 2018 at 8:45 AM Jürgen Albert via osgi-dev
mailto:osgi-dev@mail.osgi.org>> wrote:
Hi Alain,
EMF does work without extension points, but in its current state
needs manual registration of you
Alain,
no, we don't use CDO and didn't tried it. The only thing, that can make
it not work are the Require-Bundle declarations in the CDO stuff.
We experienced some problems, because of this, with QVT and EMF Compare.
We created a workaround bundle with the symbolic name
Hi all,
Carsten Ziegeler pointed us to the Configuration Plugin Services, that
are part of the ConfigurationAdmin specification. Together with the
Configurator specification, it could be possible to do that substitution
in such an plugin.
Regards,
Mark
Am 20.08.2018 um 17:56 schrieb
Hi Reza,
for OSGi is in our opinion the best approach for any software, thats
needs to extensible or customizable. We use OSGi in desktop fat clients
(Eclipse RCP) as well as in the backend and even on embedded devices.
The main success factor for us are all the specifications, that cover
May you try this:
public class PromiseExample {
PushStreamProvider psp = null;
SimplePushEventSource ses = null;
public static void main(String[] args) {
new PromiseExample().start();
}
private void start() {
// Begin delivery when someone is listening
Hi, it depends on what you want to do.We use pure Lucene a search backend, that
is heavily customized to the customers needs. This especially belongs to the
data model he uses. For that we OSGi fied the Lucene stuff, because it is not
OSGi ready. This can be easily done, except some split
We use the Zookeeper together with the ConfigAdmin, to share
configurations. With the configuration plugin of the config admin, you
can substitute the configuration or extend it with information from an
alternative source.
In Zookeeper you can have global, configurations or create
Hi Stephen,
1. Maven is very popular. So using maven makes it easy for a large
audience to adopt OSGi. When there is an integration for the right build
tool, people tend to rather try things out, then if they have to "learn"
a new build tool.
2. You can also use gradle. We use only gradle
Hi Markus,
the JaxRs API uses exactly this pattern of a @GET annotated resource
with the corresponding @Produces annotation to provide SSE.
But this constellation doesn't follow the ordinary request-response
behavior. The connection between the sender and receiver stays open. It
is a
Hi Markus,
at first the SseEventSink is auto-closable. It can also be closed from a
client side
https://javaee.github.io/javaee-spec/javadocs/javax/ws/rs/sse/SseEventSink.html
So in the examples from chapter 9.3 the usage of the sink is put in an
try-statement, which auto-closes
Hi Alain,
a little bit late but maybe some side notes to EMF and OSGi. EMF is not
thread-safe. May it be possible that you share one ResourceSet/Resource
over many Prototype instances?
This is in general not a good idea. In case you use EMF with Equinox,
you should give each prototype
Hoffmann via osgi-dev
mailto:osgi-dev@mail.osgi.org>> wrote:
Hi Alain,
a little bit late but maybe some side notes to EMF and OSGi. EMF
is not thread-safe. May it be possible that you share one
ResourceSet/Resource over many Prototype instances?
This is in general not
2020 at 05:35, Mark Hoffmann via osgi-dev wrote:
Hi Stefan,I believe Optionals are not optimal for that.If a service is removed,
you would need a new empty optional instance. Optionals doesn't support to hold
a state.The state is in the component, not the Optional instance. References
are static
t are Optional I like Stefan's suggestion and I disagree
with some specific points made by Mark... responses line below.On Wed, 23 Sep
2020 at 05:35, Mark Hoffmann via osgi-dev wrote:
Hi Stefan,I believe Optionals are not optimal for that.If a service is removed,
you would need a new empty option
below.On Wed, 23 Sep
2020 at 05:35, Mark Hoffmann via osgi-dev wrote:
Hi Stefan,I believe Optionals are not optimal for that.If a service is removed,
you would need a new empty optional instance. Optionals doesn't support to hold
a state.The state is in the component, not the Optional instance
Hi Stefan,I believe Optionals are not optimal for that.If a service is removed,
you would need a new empty optional instance. Optionals doesn't support to hold
a state. In addition to that you don't have callbacks where to get notified
about adding, modifying or removing a service. I could
OSGi
Fellow and CTO of the OSGi Alliance // mobile: +1 386 848
3788hargr...@us.ibm.com
- Original message -From: Mark Hoffmann via osgi-dev
Sent by: osgi-dev-boun...@mail.osgi.orgTo: Neil
Bartlett Cc: OSGi Developer Mail List
Subject: [EXTERNAL] Re: [osgi-dev] SCR:
ServiceI
r. Michael Bolle, Dr. Christian Fischer,
Dr. Stefan Hartung,
Dr. Markus Heyn, Harald Kröger, Christoph Kübel, Rolf Najork, Uwe Raschke,
Peter Tyroller
Von:
osgi-dev-boun...@mail.osgi.org
Im Auftrag von Mark Hoffmann via osgi-dev
Gesendet: Mittwoch, 23. September 2020 06:35
An: Stefan Bisc
18 matches
Mail list logo
