Juergen,

In terms of persistence we are very tied to CDO. We have our own
HypergraphDb based repository (with LMDB/MDBX based store) with support for
model evolution, multi-tenant at rest encryption, using all the branching
and versioning parts of CDO, etc. For example we use CDO Remote queries to
leverage Hypergraph search to perform graph traversal and type based
querying.

So I guess in that realm we're deeply committed to that part of the stack.

In terms of special code generator, CDO is not impacting much. We have our
EObject that extends CDOObject and the rest of the generator is pretty
vanilla.

Alain


On Fri, Aug 10, 2018 at 4:12 AM Jürgen Albert via osgi-dev <
osgi-dev@mail.osgi.org> wrote:

> Alain,
>
> What kind of Persistence do you need? We have a MongoDB Persistence for
> EMF Models as well. This works with normal EObjects, that do not need a
> special code generator like CDO. There are a few other Document based DB
> (like couchDB)  extensions available as well.
>
> Jürgen.
>
> Am 09/08/2018 um 17:27 schrieb Alain Picard via osgi-dev:
>
> Mark,
>
> We have started to create our own extension of o.e.core.runtime with some
> extra portable stuff like ILog and others, would be interested in maybe
> sharing/contributing there.
>
> As for CDO, we should have to cross that bridge before October and will
> gladly share any changes needed in that regard.
>
> Cheers,
> Alain
>
> On Thu, Aug 9, 2018 at 11:14 AM Mark Hoffmann via osgi-dev <
> osgi-dev@mail.osgi.org> wrote:
>
>> 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
>> 'org.eclipse.core.runtime', because the Equinox supplement bundle was sadly
>> not enough.
>>
>> But it would be interesting for us to support CDO too. I think we meet
>> Eike Stepper, the CDO lead, in October at the ECE2018 and discuss this
>> topic with him.
>>
>> Mark
>>
>> Am 09.08.2018 um 17:02 schrieb Alain Picard via osgi-dev:
>>
>> Jurgen,
>>
>> This looks fantastic. Just out of curiosity, have you used it with CDO ?
>>
>> Alain
>>
>>
>> On Thu, Aug 9, 2018 at 10:11 AM Jürgen Albert via osgi-dev <
>> osgi-dev@mail.osgi.org> wrote:
>>
>>> It appears that we are too stupid to configure the project properly. You
>>> can get started with this:
>>> https://gitlab.com/gecko.io/geckoEMF/wikis/Get-started
>>>
>>>
>>> Am 09/08/2018 um 14:54 schrieb Alain Picard:
>>>
>>>
>>> On Thu, Aug 9, 2018 at 8:45 AM Jürgen Albert via osgi-dev <
>>> osgi-dev@mail.osgi.org> wrote:
>>>
>>>> Hi Alain,
>>>>
>>>> EMF does work without extension points, but in its current state needs
>>>> manual registration of you EPackages.
>>>>
>>> Ok that is the interesting part.
>>>
>>> The OSGi Compatibility option in the genmodel only defines the
>>>> org.eclipse.core.runtime as optional, which dues does not really solve
>>>> anything.
>>>>
>>> Agreed, not much.
>>>
>>>>
>>>> We have an extension for EMF that solves this issue. You can have EMF
>>>> with any framework you like and without extension points. Have a look here:
>>>> https://gitlab.com/gecko.io/geckoEMF
>>>>
>>> Gitlab is reporting an error " An error occurred while loading commit
>>> signature" and not getting that error with the other gecko.io project.
>>>
>>>
>>>>
>>>> If you have any questions, feel free to ask.
>>>>
>>>> Jürgen.
>>>>
>>>> Am 09/08/2018 um 11:12 schrieb Tim Ward:
>>>>
>>>>
>>>>
>>>> Begin forwarded message:
>>>>
>>>> *From: *Tim Ward <tim.w...@paremus.com>
>>>> *Subject: **Re: [osgi-dev] Eclipse Extension-points and EMF in OSGI*
>>>> *Date: *9 August 2018 at 10:02:50 BST
>>>> *To: *Alain Picard <pic...@castortech.com>, OSGi Developer Mail List <
>>>> osgi-dev@mail.osgi.org>
>>>> *Cc: *Scott Lewis <sle...@composent.com>
>>>>
>>>> I would expect that Mark Hoffman or Jürgen Albert might have some
>>>> useful pointers, I’m pretty sure that they’re heavy users of EMF.
>>>>
>>>> Best Regards,
>>>>
>>>> Tim
>>>>
>>>> On 9 Aug 2018, at 09:20, Alain Picard via osgi-dev <
>>>> osgi-dev@mail.osgi.org> wrote:
>>>>
>>>> Scott,
>>>>
>>>> I noticed the split of the o.e.core.runtime and am already using the
>>>> o.e.equinox.common + supplement and running some stuff like that with
>>>> Felix. But that part doesn't include of the support for extension points
>>>> that is in the other "half", hence my question.
>>>>
>>>> Alain
>>>>
>>>>
>>>> On Thu, Aug 9, 2018 at 12:18 AM Scott Lewis via osgi-dev <
>>>> osgi-dev@mail.osgi.org> wrote:
>>>>
>>>>> IOn 8/8/2018 7:43 AM, Alain Picard via osgi-dev wrote:
>>>>> > Working through our move from RCP to a generic OSGI solution, and I
>>>>> am
>>>>> > stuck with a couple of questions.
>>>>> >
>>>>> > There was an issue a while ago for EMF that resulted in a generation
>>>>> > setting to support generic OSGI frameworks and not only
>>>>> > Eclipse/Equinox. But the resulting bundles still have plugin.xml and
>>>>> > expose extension points. My understanding is that this part of
>>>>> Eclipse
>>>>> > is not covered in the portable part of o.e.core.runtime. We also
>>>>> have
>>>>> > a number of our own extension-points, some that we have already
>>>>> > converted and others that are still around.
>>>>> >
>>>>> > So anyone has successfully used EMF and/or Extension points outside
>>>>> of
>>>>> > a full Eclipse environment?
>>>>>
>>>>> Yes wrt extension registry/extension points.
>>>>>
>>>>> o.e.core.runtime is a split package, split between bundles
>>>>> o.e.equinox.common and o.e.equinox.registry
>>>>>
>>>>> I'm not sure of the justification for split packages, but I think it
>>>>> was
>>>>> done to maintain backward compatibility in eclipse plugins.
>>>>>
>>>>> The version I used was a few years ago, but at that time these two
>>>>> bundles...along with equinox...would run the extension registry (i.e.
>>>>> process extension points/extensions on startup).  AFAIK that's still
>>>>> the
>>>>> case.
>>>>>
>>>>> If you want to use a framework other than equinox, I know for certain
>>>>> that o.e.equinox.common works just fine on Felix...as long as one also
>>>>> includes this bundle [1].
>>>>>
>>>>> I don't think EMF requires anything in addition to o.e.equinox.common
>>>>> and o.e.equinox.registry but I'm not completely sure about that.
>>>>>
>>>>> Scott
>>>>>
>>>>> [1] org.eclipse.equinox.supplement  - available via equinox or maven
>>>>> central
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> OSGi Developer Mail List
>>>>> osgi-dev@mail.osgi.org
>>>>> https://mail.osgi.org/mailman/listinfo/osgi-dev
>>>>
>>>> _______________________________________________
>>>> OSGi Developer Mail List
>>>> osgi-dev@mail.osgi.org
>>>> https://mail.osgi.org/mailman/listinfo/osgi-dev
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Jürgen Albert
>>>> Geschäftsführer
>>>>
>>>> Data In Motion Consulting GmbH (haftungsbeschränkt)
>>>>
>>>> Kahlaische Str. 4
>>>> 07745 Jena
>>>>
>>>> Mobil:  0157-72521634
>>>> E-Mail: j.alb...@datainmotion.de
>>>> Web: www.datainmotion.de
>>>>
>>>> XING:   https://www.xing.com/profile/Juergen_Albert5
>>>>
>>>> Rechtliches
>>>>
>>>> Jena HBR 513025
>>>>
>>>> _______________________________________________
>>>> OSGi Developer Mail List
>>>> osgi-dev@mail.osgi.org
>>>> https://mail.osgi.org/mailman/listinfo/osgi-dev
>>>
>>>
>>> --
>>> Jürgen Albert
>>> Geschäftsführer
>>>
>>> Data In Motion Consulting GmbH (haftungsbeschränkt)
>>>
>>> Kahlaische Str. 4
>>> 07745 Jena
>>>
>>> Mobil:  0157-72521634
>>> E-Mail: j.alb...@datainmotion.de
>>> Web: www.datainmotion.de
>>>
>>> XING:   https://www.xing.com/profile/Juergen_Albert5
>>>
>>> Rechtliches
>>>
>>> Jena HBR 513025
>>>
>>> _______________________________________________
>>> OSGi Developer Mail List
>>> osgi-dev@mail.osgi.org
>>> https://mail.osgi.org/mailman/listinfo/osgi-dev
>>
>>
>>
>> _______________________________________________
>> OSGi Developer Mail 
>> listosgi-...@mail.osgi.orghttps://mail.osgi.org/mailman/listinfo/osgi-dev
>>
>>
>> --
>> Mark Hoffmann
>> M.A. Dipl.-Betriebswirt (FH)
>> Geschäftsführer
>>
>> Tel:    +49 3641 384 910 0
>> Mobil:  +49 175 701 2201
>> E-Mail: m.hoffm...@data-in-motion.biz
>> Web: www.datainmotion.de
>>
>> Data In Motion Consulting GmbH
>> Kahlaische Straße 4
>> 07745 Jena
>>
>> Geschäftsführer
>> Mark Hoffmann
>> Jürgen Albert
>>
>> Jena HRB 513025
>> Steuernummer 162/107/05779
>> USt-Id DE310002614
>>
>>
>>
>> _______________________________________________
>> OSGi Developer Mail List
>> osgi-dev@mail.osgi.org
>> https://mail.osgi.org/mailman/listinfo/osgi-dev
>
>
>
> _______________________________________________
> OSGi Developer Mail 
> listosgi-...@mail.osgi.orghttps://mail.osgi.org/mailman/listinfo/osgi-dev
>
>
> --
> Jürgen Albert
> Geschäftsführer
>
> Data In Motion Consulting GmbH (haftungsbeschränkt)
>
> Kahlaische Str. 4
> 07745 Jena
>
> Mobil:  0157-72521634
> E-Mail: j.alb...@datainmotion.de
> Web: www.datainmotion.de
>
> XING:   https://www.xing.com/profile/Juergen_Albert5
>
> Rechtliches
>
> Jena HBR 513025
>
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Reply via email to