Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF » [CDO]: CDO Resource Launcher
[CDO]: CDO Resource Launcher [message #422580] Wed, 10 September 2008 07:22 Go to next message
Andre Dietisheim is currently offline Andre DietisheimFriend
Messages: 131
Registered: July 2009
Senior Member
Hi ViK!

I tested this stuff yesterday and I got everything rolling fine (I use a
ganymede ide, cdo/net4j bundles from cvs and a target platform built a
month ago).
I really like the idea and I think its even better than to provide a
preferences page as I wanted in bug 242230 (it's more flexible). Let me
try to sum up what could be done to this. I'd be happy to provide stuff
here:

- component to display cdo launcher files in a common navigator
- wizards to create launcher files
- launch compare view to compare 2 resources
- any further ideas?

Cheers
André
Re: [CDO]: CDO Resource Launcher [message #422581 is a reply to message #422580] Wed, 10 September 2008 09:38 Go to previous messageGo to next message
Victor Roldan Betancort is currently offline Victor Roldan BetancortFriend
Messages: 524
Registered: July 2009
Senior Member
Hi André,

> I tested this stuff yesterday and I got everything rolling fine (I use a
> ganymede ide, cdo/net4j bundles from cvs and a target platform built a
> month ago).

Great that everything worked fine :D

> I really like the idea and I think its even better than to provide a
> preferences page as I wanted in bug 242230 (it's more flexible).

I agree in the part of having a server page preferences. Indeed, I've
already have a preferences page for our product, where you store just
repository URIs. This central place for URIs is then used in wizards,
allowing the user to choose a repository.

So, I agree that we could store Session information in a preferences
page, but I find storing Views (or Transactions or Audits) a bit
redundant, since that information is already stored in a launcher model.

Furthermore, the ideas described in the bug (the drop down menu and
such) also somehow collide with the idea of the launcher. The main idea
of the launcher was to allow the user having a file in the common
navigator representing a model stored in a CDO Server, trying to imitate
the "models as files". Of course, the 242230 would be a great
enhancement, but would give the same functionality for something that
the launcher already does: two ways to do the same thing.

Let me
> try to sum up what could be done to this. I'd be happy to provide stuff
> here:
>
> - component to display cdo launcher files in a common navigator

What do you mean here? The launcher is a file, so it will already be
showed up as an IFile in the navigator.

> - wizards to create launcher files

The wizard would allow you to select sessions (Repository URI) from the
registry, right?

> - launch compare view to compare 2 resources

Great! This will imply working on EMF Compare integration with CDO.
Shouldn't be a prob, just passing teh 2 root objects to compare. Eike
told me that the server might need some cache tweaking ...
Any comments, Eike?

> - any further ideas?

Not at the time, but I'm sure plenty will eventually emerge :)

>
> Cheers
> André

Cheers!
ViK
Re: [CDO]: CDO Resource Launcher [message #422582 is a reply to message #422581] Wed, 10 September 2008 09:52 Go to previous messageGo to next message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6468
Registered: July 2009
Senior Member
Víctor Roldán Betancort schrieb:
> [...]
>> I really like the idea and I think its even better than to provide a
>> preferences page as I wanted in bug 242230 (it's more flexible).
> I agree in the part of having a server page preferences. Indeed, I've
> already have a preferences page for our product, where you store just
> repository URIs. This central place for URIs is then used in wizards,
> allowing the user to choose a repository.
The term "server preferences" always confuses me because we really mean
client side preferences. Can we call it "session preferences"?

> So, I agree that we could store Session information in a preferences
> page, but I find storing Views (or Transactions or Audits) a bit
> redundant, since that information is already stored in a launcher model.
Isn't that true for session properties as well?

> Furthermore, the ideas described in the bug (the drop down menu and
> such) also somehow collide with the idea of the launcher. The main
> idea of the launcher was to allow the user having a file in the common
> navigator representing a model stored in a CDO Server, trying to
> imitate the "models as files". Of course, the 242230 would be a great
> enhancement, but would give the same functionality for something that
> the launcher already does: two ways to do the same thing.
I think the whole *preferences* idea collides with the launcher model.
Both approaches support infrastructure creation from information
persistent somewhere on the client. Only the exact location of the
persistent information differs: Workspace vs. PreferencePage.

With the wizards you talked about available we could perhaps implement
the PreferencePage-based approach by using the launcher model
internally. What do you think?

> [...]
>> - wizards to create launcher files
> The wizard would allow you to select sessions (Repository URI) from
> the registry, right?
No, I think the wizards would support the creation of configuration data
for the various components.
With the launcher model (which also represents a form of a registry) we
don't need the registries anymore.

>
>> - launch compare view to compare 2 resources
>
> Great! This will imply working on EMF Compare integration with CDO.
> Shouldn't be a prob, just passing teh 2 root objects to compare. Eike
> told me that the server might need some cache tweaking ...
> Any comments, Eike?
Hmm, I can't remember anymore and I don't see the relation. You must
help me ;-)

Cheers
/Eike


Re: [CDO]: CDO Resource Launcher [message #422583 is a reply to message #422582] Wed, 10 September 2008 10:25 Go to previous messageGo to next message
Victor Roldan Betancort is currently offline Victor Roldan BetancortFriend
Messages: 524
Registered: July 2009
Senior Member
Eike,
comments below

Eike Stepper escribió:
> Víctor Roldán Betancort schrieb:
>> [...]
>>> I really like the idea and I think its even better than to provide a
>>> preferences page as I wanted in bug 242230 (it's more flexible).
>> I agree in the part of having a server page preferences. Indeed, I've
>> already have a preferences page for our product, where you store just
>> repository URIs. This central place for URIs is then used in wizards,
>> allowing the user to choose a repository.
> The term "server preferences" always confuses me because we really mean
> client side preferences. Can we call it "session preferences"?

Agree! I also like to call it "CDO repository preferences". But let's go
on with "session preferences" :P

>> So, I agree that we could store Session information in a preferences
>> page, but I find storing Views (or Transactions or Audits) a bit
>> redundant, since that information is already stored in a launcher model.
> Isn't that true for session properties as well?

Yes, but I see the session preferences more like a little help for
wizards: If a session preferences doesn't exist, the user would have to
write the repository URI in a wizard each time they want a retrieve a
resource from the same repository. Instead, having a session
preferences, the user only needs to choose it from a dialog.
Furthermore, with the new patch of "query resources", the user doesn't
need to enter the resource path either: he would be also able to choose
the resource from a dialog as well.

At the end, the generated CDOLauncher would contain all the information
needed to open a session/view/transaction/audit over a resource.

>
>> Furthermore, the ideas described in the bug (the drop down menu and
>> such) also somehow collide with the idea of the launcher. The main
>> idea of the launcher was to allow the user having a file in the common
>> navigator representing a model stored in a CDO Server, trying to
>> imitate the "models as files". Of course, the 242230 would be a great
>> enhancement, but would give the same functionality for something that
>> the launcher already does: two ways to do the same thing.
> I think the whole *preferences* idea collides with the launcher model.
> Both approaches support infrastructure creation from information
> persistent somewhere on the client. Only the exact location of the
> persistent information differs: Workspace vs. PreferencePage.

Sure, both collide, but I think we could get the most of both.
The model approach has two additional advantage: the launcher is
shareable among clients, and is easily shown in the navigator as a file,
behaving like a "direct link" to the resource. The preference page
configuration is not shareable, and we would need work how to show
preferences data as a IResource in the navigator (I really think is a
cool idea having it in the navigator) :(

> With the wizards you talked about available we could perhaps implement
> the PreferencePage-based approach by using the launcher model
> internally. What do you think?

But we would loose a good point of the model approach, which is having
it in the common navigator.

>
>> [...]
>>> - wizards to create launcher files
>> The wizard would allow you to select sessions (Repository URI) from
>> the registry, right?
> No, I think the wizards would support the creation of configuration data
> for the various components.
> With the launcher model (which also represents a form of a registry) we
> don't need the registries anymore.

Ok, I get your point now. I think having the model as a registry is a
nice idea, but I still miss the good feature of having it in the common
navigator. If you find a way to workaround that, I'll agree. Otherwise,
I will agree as well, it's you project, your decisions :P :P

And don't forget also the "shareable" feature of the original approach.
I guess the "registry model" could also be shareable.

>
>>
>>> - launch compare view to compare 2 resources
>>
>> Great! This will imply working on EMF Compare integration with CDO.
>> Shouldn't be a prob, just passing teh 2 root objects to compare. Eike
>> told me that the server might need some cache tweaking ...
>> Any comments, Eike?
> Hmm, I can't remember anymore and I don't see the relation. You must
> help me ;-)

You suggested that the object graph could end up being loaded totally...
And I think the same as well. That could be kind of inefficient for the
CDO Server.

>
> Cheers
> /Eike
Re: [CDO]: CDO Resource Launcher [message #422584 is a reply to message #422583] Wed, 10 September 2008 10:45 Go to previous messageGo to next message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6468
Registered: July 2009
Senior Member
Víctor Roldán Betancort schrieb:
> [...]
>>> So, I agree that we could store Session information in a preferences
>>> page, but I find storing Views (or Transactions or Audits) a bit
>>> redundant, since that information is already stored in a launcher
>>> model.
>> Isn't that true for session properties as well?
>
> Yes, but I see the session preferences more like a little help for
> wizards: If a session preferences doesn't exist, the user would have
> to write the repository URI in a wizard each time they want a retrieve
> a resource from the same repository. Instead, having a session
> preferences, the user only needs to choose it from a dialog.
I'm not sure if I understand completely. The repository information
would be in a file. So for a combo box (or similar) we'd only need a
mechanism to determine all such files, right?


> Furthermore, with the new patch of "query resources", the user doesn't
> need to enter the resource path either: he would be also able to
> choose the resource from a dialog as well.
>
> At the end, the generated CDOLauncher would contain all the
> information needed to open a session/view/transaction/audit over a
> resource.
>
>>
>>> Furthermore, the ideas described in the bug (the drop down menu and
>>> such) also somehow collide with the idea of the launcher. The main
>>> idea of the launcher was to allow the user having a file in the
>>> common navigator representing a model stored in a CDO Server, trying
>>> to imitate the "models as files". Of course, the 242230 would be a
>>> great enhancement, but would give the same functionality for
>>> something that the launcher already does: two ways to do the same
>>> thing.
>> I think the whole *preferences* idea collides with the launcher
>> model. Both approaches support infrastructure creation from
>> information persistent somewhere on the client. Only the exact
>> location of the persistent information differs: Workspace vs.
>> PreferencePage.
>
> Sure, both collide, but I think we could get the most of both.
> The model approach has two additional advantage: the launcher is
> shareable among clients, and is easily shown in the navigator as a
> file, behaving like a "direct link" to the resource. The preference
> page configuration is not shareable, and we would need work how to
> show preferences data as a IResource in the navigator (I really think
> is a cool idea having it in the navigator) :(
Please note that a preference page is not required to store the
configuration values in an IPreferenceStore!
We can also use the launcher model files if we store them somewhere in
the configuration area.
Then we can reuse not only the persistent format and save/load
implementation but also the wizards that create the files and their
content...

>
>> With the wizards you talked about available we could perhaps
>> implement the PreferencePage-based approach by using the launcher
>> model internally. What do you think?
>
> But we would loose a good point of the model approach, which is having
> it in the common navigator.
No, this approach would still be fully included.

>
>>
>>> [...]
>>>> - wizards to create launcher files
>>> The wizard would allow you to select sessions (Repository URI) from
>>> the registry, right?
>> No, I think the wizards would support the creation of configuration
>> data for the various components.
>> With the launcher model (which also represents a form of a registry)
>> we don't need the registries anymore.
>
> Ok, I get your point now. I think having the model as a registry is a
> nice idea, but I still miss the good feature of having it in the
> common navigator. If you find a way to workaround that, I'll agree.
> Otherwise, I will agree as well, it's you project, your decisions :P :P
I don't see the problem. It's "just" an EMF model, i.e. a forrest of
EObjects. We should care from where these were loaded.

>
> And don't forget also the "shareable" feature of the original
> approach. I guess the "registry model" could also be shareable.
You mean being able to share, let's say, a configured connector instance
among multiple sessions?
All this is still in the launcher model.
I only recommend to reuse this cool model for the implementation of the
preference pages, together with a different storage location (maybe just
a URIHandler is needed to redirect I/O).

>
>>
>>>
>>>> - launch compare view to compare 2 resources
>>>
>>> Great! This will imply working on EMF Compare integration with CDO.
>>> Shouldn't be a prob, just passing teh 2 root objects to compare.
>>> Eike told me that the server might need some cache tweaking ...
>>> Any comments, Eike?
>> Hmm, I can't remember anymore and I don't see the relation. You must
>> help me ;-)
>
> You suggested that the object graph could end up being loaded totally...
> And I think the same as well. That could be kind of inefficient for
> the CDO Server.
While completly loading the compared resources is more than probable, I
don't see a way to prevent that.
They are loaded because their content is needed, right?

Cheers
/Eike


Re: [CDO]: CDO Resource Launcher [message #422585 is a reply to message #422584] Wed, 10 September 2008 10:47 Go to previous messageGo to next message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6468
Registered: July 2009
Senior Member
A correction:

>>
>> Ok, I get your point now. I think having the model as a registry is a
>> nice idea, but I still miss the good feature of having it in the
>> common navigator. If you find a way to workaround that, I'll agree.
>> Otherwise, I will agree as well, it's you project, your decisions :P :P
> I don't see the problem. It's "just" an EMF model, i.e. a forrest of
> EObjects. We should care from where these were loaded.
We should *not* care from where these were loaded.


Re: [CDO]: CDO Resource Launcher [message #422586 is a reply to message #422584] Wed, 10 September 2008 13:58 Go to previous messageGo to next message
Victor Roldan Betancort is currently offline Victor Roldan BetancortFriend
Messages: 524
Registered: July 2009
Senior Member
The design for new approach is described at:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=246623

Mark, is the new approach ok for you?

> While completly loading the compared resources is more than probable, I
> don't see a way to prevent that.
> They are loaded because their content is needed, right?

Yes. Further experimentation would reveal us if tweaking is needed.

Cheers.
ViK.
Re: [CDO]: CDO Resource Launcher [message #422588 is a reply to message #422586] Wed, 10 September 2008 14:25 Go to previous messageGo to next message
Mark Geib is currently offline Mark GeibFriend
Messages: 432
Registered: July 2009
Senior Member
ViK,

This sounds fine to me, no concerns.

Mark.


Víctor Roldán Betancort wrote:
> The design for new approach is described at:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=246623
>
> Mark, is the new approach ok for you?
>
>> While completly loading the compared resources is more than probable,
>> I don't see a way to prevent that.
>> They are loaded because their content is needed, right?
>
> Yes. Further experimentation would reveal us if tweaking is needed.
>
> Cheers.
> ViK.
Re: [CDO]: CDO Resource Launcher [message #422589 is a reply to message #422586] Wed, 10 September 2008 14:37 Go to previous messageGo to next message
Victor Roldan Betancort is currently offline Victor Roldan BetancortFriend
Messages: 524
Registered: July 2009
Senior Member
> Mark, is the new approach ok for you?
Sorry, meant André, although Mark has probably things to say as well! :)
Re: [CDO]: CDO Resource Launcher [message #422591 is a reply to message #422581] Wed, 10 September 2008 17:53 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: andras.okros.optxware.com

Hello Victor,

Maybe I do something wrong, but I only see the root elements in the
resource after loading it (no attributes, or anything else). The editor
I use is good (a CDO enhanced one), because it works with my own plain
xml file based loader well.

Thanks in advance if you have some ideas, what can be wrong. (I use the
CDO version 1.0.0.v200806180411) Let me know, if you need some more
information about this.

Best regards,
András

Víctor Roldán Betancort írta:
> Hi André,
>
>> I tested this stuff yesterday and I got everything rolling fine (I use
>> a ganymede ide, cdo/net4j bundles from cvs and a target platform built
>> a month ago).
>
> Great that everything worked fine :D
>
> Cheers!
> ViK
Re: [CDO]: CDO Resource Launcher [message #422593 is a reply to message #422591] Wed, 10 September 2008 18:11 Go to previous messageGo to next message
Victor Roldan Betancort is currently offline Victor Roldan BetancortFriend
Messages: 524
Registered: July 2009
Senior Member
Hi András,

> Maybe I do something wrong, but I only see the root elements in the
> resource after loading it (no attributes, or anything else). The editor
> I use is good (a CDO enhanced one), because it works with my own plain
> xml file based loader well.

Uhm, strange...

Are you sure you are using the generated enhanced editor? I mean, you
properly set the generated ID in the launcher model attribute
"editorId", right? (it's, by default, the same as the original editor
ID, but ended in "enhanced", if I recall correctly. you can see it in
the plugin.xml at the extensions tab).

Could you try to launch the resource using CDOEditor instead? (its ID is
"org.eclipse.emf.cdo.ui.CDOEditor") and see if you get the same behaviour?

> Thanks in advance if you have some ideas, what can be wrong. (I use the
> CDO version 1.0.0.v200806180411) Let me know, if you need some more
> information about this.

That's almost the Ganymede's code, I believe (CDO project page shows
"200806241000" available to download. Mark was also experiencing some
problems with the initial Ganymede release. I'm not sure about what
could be happening... I always suggest to try out the HEAD code...

I haven't tried out yet the launcher with Ganymede release.
I'll go on with it tomorrow and let you now know :D

Cheers,
ViK.
Re: [CDO]: CDO Resource Launcher [message #422611 is a reply to message #422593] Thu, 11 September 2008 09:58 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: andras.okros.optxware.com

Hi Vik,

The launcher has the same behaviour with the CDOEditor
(org.eclipse.emf.cdo.ui.CDOEditor).

I haven't tried it out with the HEAD, however I get it working by
inserting the
session.getPackageRegistry().putEPackage(OurModelPackage.eIN STANCE);
code into the CDOEditorLauncher. Although it is not a good general approach.

Maybe the Automatic Package Registry doesn't works well? Do you have any
tips?

Cheers,
András


Víctor Roldán Betancort írta:
> Hi András,
>
>> Maybe I do something wrong, but I only see the root elements in the
>> resource after loading it (no attributes, or anything else). The
>> editor I use is good (a CDO enhanced one), because it works with my
>> own plain xml file based loader well.
>
> Uhm, strange...
>
> Are you sure you are using the generated enhanced editor? I mean, you
> properly set the generated ID in the launcher model attribute
> "editorId", right? (it's, by default, the same as the original editor
> ID, but ended in "enhanced", if I recall correctly. you can see it in
> the plugin.xml at the extensions tab).
>
> Could you try to launch the resource using CDOEditor instead? (its ID is
> "org.eclipse.emf.cdo.ui.CDOEditor") and see if you get the same behaviour?
>
>> Thanks in advance if you have some ideas, what can be wrong. (I use
>> the CDO version 1.0.0.v200806180411) Let me know, if you need some
>> more information about this.
>
> That's almost the Ganymede's code, I believe (CDO project page shows
> "200806241000" available to download. Mark was also experiencing some
> problems with the initial Ganymede release. I'm not sure about what
> could be happening... I always suggest to try out the HEAD code...
>
> I haven't tried out yet the launcher with Ganymede release.
> I'll go on with it tomorrow and let you now know :D
>
> Cheers,
> ViK.
Re: [CDO]: CDO Resource Launcher [message #422612 is a reply to message #422611] Thu, 11 September 2008 10:14 Go to previous messageGo to next message
Victor Roldan Betancort is currently offline Victor Roldan BetancortFriend
Messages: 524
Registered: July 2009
Senior Member
Hi András,

I've already tried out in a clean Ganymede release, and everything seems
to work fine for me :S

Just detected a small bug that triggers the launching once the wizard
creates an instance, since by default the wizard tries to open the
editor, and in this case, it finds the "launch" action as default action
(dunno why... maybe setting content-type priority to low...)

If it works that way for you, it means the auto-registry is not
registering your model properly. Some of the reasons could be:

- The model code is not native (although I believe dynamic mode should
work).

- (most probably) The model is not registered in the EMF registry. Are
you running the launcher file in the same workspace where the model's
code is located? Have you tried running the launcher in a
runtime-workbench? (run -> run-as -> Eclipse Application)

HTH,
ViK.

András Ökrös escribió:
> Hi Vik,
>
> The launcher has the same behaviour with the CDOEditor
> (org.eclipse.emf.cdo.ui.CDOEditor).
>
> I haven't tried it out with the HEAD, however I get it working by
> inserting the
> session.getPackageRegistry().putEPackage(OurModelPackage.eIN STANCE);
> code into the CDOEditorLauncher. Although it is not a good general
> approach.
>
> Maybe the Automatic Package Registry doesn't works well? Do you have any
> tips?
>
> Cheers,
> András
>
>
> Víctor Roldán Betancort írta:
>> Hi András,
>>
>>> Maybe I do something wrong, but I only see the root elements in the
>>> resource after loading it (no attributes, or anything else). The
>>> editor I use is good (a CDO enhanced one), because it works with my
>>> own plain xml file based loader well.
>>
>> Uhm, strange...
>>
>> Are you sure you are using the generated enhanced editor? I mean, you
>> properly set the generated ID in the launcher model attribute
>> "editorId", right? (it's, by default, the same as the original editor
>> ID, but ended in "enhanced", if I recall correctly. you can see it in
>> the plugin.xml at the extensions tab).
>>
>> Could you try to launch the resource using CDOEditor instead? (its ID
>> is "org.eclipse.emf.cdo.ui.CDOEditor") and see if you get the same
>> behaviour?
>>
>>> Thanks in advance if you have some ideas, what can be wrong. (I use
>>> the CDO version 1.0.0.v200806180411) Let me know, if you need some
>>> more information about this.
>>
>> That's almost the Ganymede's code, I believe (CDO project page shows
>> "200806241000" available to download. Mark was also experiencing some
>> problems with the initial Ganymede release. I'm not sure about what
>> could be happening... I always suggest to try out the HEAD code...
>>
>> I haven't tried out yet the launcher with Ganymede release.
>> I'll go on with it tomorrow and let you now know :D
>>
>> Cheers,
>> ViK.
Re: [CDO]: CDO Resource Launcher [message #422613 is a reply to message #422612] Thu, 11 September 2008 10:24 Go to previous messageGo to next message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6468
Registered: July 2009
Senior Member
Guys,

We could add to the launcher model to be able to configure packages to
register with the session.
What do you think?

Cheers
/Eike


Víctor Roldán Betancort schrieb:
> Hi András,
>
> I've already tried out in a clean Ganymede release, and everything
> seems to work fine for me :S
>
> Just detected a small bug that triggers the launching once the wizard
> creates an instance, since by default the wizard tries to open the
> editor, and in this case, it finds the "launch" action as default
> action (dunno why... maybe setting content-type priority to low...)
>
> If it works that way for you, it means the auto-registry is not
> registering your model properly. Some of the reasons could be:
>
> - The model code is not native (although I believe dynamic mode should
> work).
>
> - (most probably) The model is not registered in the EMF registry. Are
> you running the launcher file in the same workspace where the model's
> code is located? Have you tried running the launcher in a
> runtime-workbench? (run -> run-as -> Eclipse Application)
>
> HTH,
> ViK.
>
> András Ökrös escribió:
>> Hi Vik,
>>
>> The launcher has the same behaviour with the CDOEditor
>> (org.eclipse.emf.cdo.ui.CDOEditor).
>>
>> I haven't tried it out with the HEAD, however I get it working by
>> inserting the
>> session.getPackageRegistry().putEPackage(OurModelPackage.eIN STANCE);
>> code into the CDOEditorLauncher. Although it is not a good general
>> approach.
>>
>> Maybe the Automatic Package Registry doesn't works well? Do you have
>> any tips?
>>
>> Cheers,
>> András
>>
>>
>> Víctor Roldán Betancort írta:
>>> Hi András,
>>>
>>>> Maybe I do something wrong, but I only see the root elements in the
>>>> resource after loading it (no attributes, or anything else). The
>>>> editor I use is good (a CDO enhanced one), because it works with my
>>>> own plain xml file based loader well.
>>>
>>> Uhm, strange...
>>>
>>> Are you sure you are using the generated enhanced editor? I mean,
>>> you properly set the generated ID in the launcher model attribute
>>> "editorId", right? (it's, by default, the same as the original
>>> editor ID, but ended in "enhanced", if I recall correctly. you can
>>> see it in the plugin.xml at the extensions tab).
>>>
>>> Could you try to launch the resource using CDOEditor instead? (its
>>> ID is "org.eclipse.emf.cdo.ui.CDOEditor") and see if you get the
>>> same behaviour?
>>>
>>>> Thanks in advance if you have some ideas, what can be wrong. (I use
>>>> the CDO version 1.0.0.v200806180411) Let me know, if you need some
>>>> more information about this.
>>>
>>> That's almost the Ganymede's code, I believe (CDO project page shows
>>> "200806241000" available to download. Mark was also experiencing
>>> some problems with the initial Ganymede release. I'm not sure about
>>> what could be happening... I always suggest to try out the HEAD code...
>>>
>>> I haven't tried out yet the launcher with Ganymede release.
>>> I'll go on with it tomorrow and let you now know :D
>>>
>>> Cheers,
>>> ViK.


Re: [CDO]: CDO Resource Launcher [message #422614 is a reply to message #422613] Thu, 11 September 2008 10:39 Go to previous messageGo to next message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6468
Registered: July 2009
Senior Member
--> https://bugs.eclipse.org/bugs/attachment.cgi?id=112298


Eike Stepper schrieb:
> Guys,
>
> We could add to the launcher model to be able to configure packages to
> register with the session.
> What do you think?
>
> Cheers
> /Eike
>
>
> Víctor Roldán Betancort schrieb:
>> Hi András,
>>
>> I've already tried out in a clean Ganymede release, and everything
>> seems to work fine for me :S
>>
>> Just detected a small bug that triggers the launching once the wizard
>> creates an instance, since by default the wizard tries to open the
>> editor, and in this case, it finds the "launch" action as default
>> action (dunno why... maybe setting content-type priority to low...)
>>
>> If it works that way for you, it means the auto-registry is not
>> registering your model properly. Some of the reasons could be:
>>
>> - The model code is not native (although I believe dynamic mode
>> should work).
>>
>> - (most probably) The model is not registered in the EMF registry.
>> Are you running the launcher file in the same workspace where the
>> model's code is located? Have you tried running the launcher in a
>> runtime-workbench? (run -> run-as -> Eclipse Application)
>>
>> HTH,
>> ViK.
>>
>> András Ökrös escribió:
>>> Hi Vik,
>>>
>>> The launcher has the same behaviour with the CDOEditor
>>> (org.eclipse.emf.cdo.ui.CDOEditor).
>>>
>>> I haven't tried it out with the HEAD, however I get it working by
>>> inserting the
>>> session.getPackageRegistry().putEPackage(OurModelPackage.eIN STANCE);
>>> code into the CDOEditorLauncher. Although it is not a good general
>>> approach.
>>>
>>> Maybe the Automatic Package Registry doesn't works well? Do you have
>>> any tips?
>>>
>>> Cheers,
>>> András
>>>
>>>
>>> Víctor Roldán Betancort írta:
>>>> Hi András,
>>>>
>>>>> Maybe I do something wrong, but I only see the root elements in
>>>>> the resource after loading it (no attributes, or anything else).
>>>>> The editor I use is good (a CDO enhanced one), because it works
>>>>> with my own plain xml file based loader well.
>>>>
>>>> Uhm, strange...
>>>>
>>>> Are you sure you are using the generated enhanced editor? I mean,
>>>> you properly set the generated ID in the launcher model attribute
>>>> "editorId", right? (it's, by default, the same as the original
>>>> editor ID, but ended in "enhanced", if I recall correctly. you can
>>>> see it in the plugin.xml at the extensions tab).
>>>>
>>>> Could you try to launch the resource using CDOEditor instead? (its
>>>> ID is "org.eclipse.emf.cdo.ui.CDOEditor") and see if you get the
>>>> same behaviour?
>>>>
>>>>> Thanks in advance if you have some ideas, what can be wrong. (I
>>>>> use the CDO version 1.0.0.v200806180411) Let me know, if you need
>>>>> some more information about this.
>>>>
>>>> That's almost the Ganymede's code, I believe (CDO project page
>>>> shows "200806241000" available to download. Mark was also
>>>> experiencing some problems with the initial Ganymede release. I'm
>>>> not sure about what could be happening... I always suggest to try
>>>> out the HEAD code...
>>>>
>>>> I haven't tried out yet the launcher with Ganymede release.
>>>> I'll go on with it tomorrow and let you now know :D
>>>>
>>>> Cheers,
>>>> ViK.


Re: [CDO]: CDO Resource Launcher [message #422615 is a reply to message #422613] Thu, 11 September 2008 10:46 Go to previous messageGo to next message
Victor Roldan Betancort is currently offline Victor Roldan BetancortFriend
Messages: 524
Registered: July 2009
Senior Member
Eike,

It's a great idea :D I think this feature would be necessary if
auto-registry is set to off, and would be equivalent to the help
provided by the Package Manager Dialog in the Session View.

However, to allow the new model referencing, we would need to add a new
multi-valued EReference to EObjects, that would be in turn the EPackages
to register. However, I always find problematic having a model that
contains references/attributes to EObjects.

Alternatives?

Cheers,
ViK.

Eike Stepper escribió:
> Guys,
>
> We could add to the launcher model to be able to configure packages to
> register with the session.
> What do you think?
>
> Cheers
> /Eike
>
>
> Víctor Roldán Betancort schrieb:
>> Hi András,
>>
>> I've already tried out in a clean Ganymede release, and everything
>> seems to work fine for me :S
>>
>> Just detected a small bug that triggers the launching once the wizard
>> creates an instance, since by default the wizard tries to open the
>> editor, and in this case, it finds the "launch" action as default
>> action (dunno why... maybe setting content-type priority to low...)
>>
>> If it works that way for you, it means the auto-registry is not
>> registering your model properly. Some of the reasons could be:
>>
>> - The model code is not native (although I believe dynamic mode should
>> work).
>>
>> - (most probably) The model is not registered in the EMF registry. Are
>> you running the launcher file in the same workspace where the model's
>> code is located? Have you tried running the launcher in a
>> runtime-workbench? (run -> run-as -> Eclipse Application)
>>
>> HTH,
>> ViK.
>>
>> András Ökrös escribió:
>>> Hi Vik,
>>>
>>> The launcher has the same behaviour with the CDOEditor
>>> (org.eclipse.emf.cdo.ui.CDOEditor).
>>>
>>> I haven't tried it out with the HEAD, however I get it working by
>>> inserting the
>>> session.getPackageRegistry().putEPackage(OurModelPackage.eIN STANCE);
>>> code into the CDOEditorLauncher. Although it is not a good general
>>> approach.
>>>
>>> Maybe the Automatic Package Registry doesn't works well? Do you have
>>> any tips?
>>>
>>> Cheers,
>>> András
>>>
>>>
>>> Víctor Roldán Betancort írta:
>>>> Hi András,
>>>>
>>>>> Maybe I do something wrong, but I only see the root elements in the
>>>>> resource after loading it (no attributes, or anything else). The
>>>>> editor I use is good (a CDO enhanced one), because it works with my
>>>>> own plain xml file based loader well.
>>>>
>>>> Uhm, strange...
>>>>
>>>> Are you sure you are using the generated enhanced editor? I mean,
>>>> you properly set the generated ID in the launcher model attribute
>>>> "editorId", right? (it's, by default, the same as the original
>>>> editor ID, but ended in "enhanced", if I recall correctly. you can
>>>> see it in the plugin.xml at the extensions tab).
>>>>
>>>> Could you try to launch the resource using CDOEditor instead? (its
>>>> ID is "org.eclipse.emf.cdo.ui.CDOEditor") and see if you get the
>>>> same behaviour?
>>>>
>>>>> Thanks in advance if you have some ideas, what can be wrong. (I use
>>>>> the CDO version 1.0.0.v200806180411) Let me know, if you need some
>>>>> more information about this.
>>>>
>>>> That's almost the Ganymede's code, I believe (CDO project page shows
>>>> "200806241000" available to download. Mark was also experiencing
>>>> some problems with the initial Ganymede release. I'm not sure about
>>>> what could be happening... I always suggest to try out the HEAD code...
>>>>
>>>> I haven't tried out yet the launcher with Ganymede release.
>>>> I'll go on with it tomorrow and let you now know :D
>>>>
>>>> Cheers,
>>>> ViK.
Re: [CDO]: CDO Resource Launcher [message #422616 is a reply to message #422614] Thu, 11 September 2008 10:48 Go to previous messageGo to next message
Victor Roldan Betancort is currently offline Victor Roldan BetancortFriend
Messages: 524
Registered: July 2009
Senior Member
Ok, through URI's

You don't even give me time to answer to your post xD

:)

Eike Stepper escribió:
> --> https://bugs.eclipse.org/bugs/attachment.cgi?id=112298
>
>
> Eike Stepper schrieb:
>> Guys,
>>
>> We could add to the launcher model to be able to configure packages to
>> register with the session.
>> What do you think?
>>
>> Cheers
>> /Eike
>>
>>
>> Víctor Roldán Betancort schrieb:
>>> Hi András,
>>>
>>> I've already tried out in a clean Ganymede release, and everything
>>> seems to work fine for me :S
>>>
>>> Just detected a small bug that triggers the launching once the wizard
>>> creates an instance, since by default the wizard tries to open the
>>> editor, and in this case, it finds the "launch" action as default
>>> action (dunno why... maybe setting content-type priority to low...)
>>>
>>> If it works that way for you, it means the auto-registry is not
>>> registering your model properly. Some of the reasons could be:
>>>
>>> - The model code is not native (although I believe dynamic mode
>>> should work).
>>>
>>> - (most probably) The model is not registered in the EMF registry.
>>> Are you running the launcher file in the same workspace where the
>>> model's code is located? Have you tried running the launcher in a
>>> runtime-workbench? (run -> run-as -> Eclipse Application)
>>>
>>> HTH,
>>> ViK.
>>>
>>> András Ökrös escribió:
>>>> Hi Vik,
>>>>
>>>> The launcher has the same behaviour with the CDOEditor
>>>> (org.eclipse.emf.cdo.ui.CDOEditor).
>>>>
>>>> I haven't tried it out with the HEAD, however I get it working by
>>>> inserting the
>>>> session.getPackageRegistry().putEPackage(OurModelPackage.eIN STANCE);
>>>> code into the CDOEditorLauncher. Although it is not a good general
>>>> approach.
>>>>
>>>> Maybe the Automatic Package Registry doesn't works well? Do you have
>>>> any tips?
>>>>
>>>> Cheers,
>>>> András
>>>>
>>>>
>>>> Víctor Roldán Betancort írta:
>>>>> Hi András,
>>>>>
>>>>>> Maybe I do something wrong, but I only see the root elements in
>>>>>> the resource after loading it (no attributes, or anything else).
>>>>>> The editor I use is good (a CDO enhanced one), because it works
>>>>>> with my own plain xml file based loader well.
>>>>>
>>>>> Uhm, strange...
>>>>>
>>>>> Are you sure you are using the generated enhanced editor? I mean,
>>>>> you properly set the generated ID in the launcher model attribute
>>>>> "editorId", right? (it's, by default, the same as the original
>>>>> editor ID, but ended in "enhanced", if I recall correctly. you can
>>>>> see it in the plugin.xml at the extensions tab).
>>>>>
>>>>> Could you try to launch the resource using CDOEditor instead? (its
>>>>> ID is "org.eclipse.emf.cdo.ui.CDOEditor") and see if you get the
>>>>> same behaviour?
>>>>>
>>>>>> Thanks in advance if you have some ideas, what can be wrong. (I
>>>>>> use the CDO version 1.0.0.v200806180411) Let me know, if you need
>>>>>> some more information about this.
>>>>>
>>>>> That's almost the Ganymede's code, I believe (CDO project page
>>>>> shows "200806241000" available to download. Mark was also
>>>>> experiencing some problems with the initial Ganymede release. I'm
>>>>> not sure about what could be happening... I always suggest to try
>>>>> out the HEAD code...
>>>>>
>>>>> I haven't tried out yet the launcher with Ganymede release.
>>>>> I'll go on with it tomorrow and let you now know :D
>>>>>
>>>>> Cheers,
>>>>> ViK.
Re: [CDO]: CDO Resource Launcher [message #422619 is a reply to message #422616] Thu, 11 September 2008 11:30 Go to previous messageGo to next message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6468
Registered: July 2009
Senior Member
Víctor Roldán Betancort schrieb:
> Ok, through URI's
>
> You don't even give me time to answer to your post xD
You'll need this time to implement the model that I designed! ;-)

>
> :)
>
> Eike Stepper escribió:
>> --> https://bugs.eclipse.org/bugs/attachment.cgi?id=112298
>>
>>
>> Eike Stepper schrieb:
>>> Guys,
>>>
>>> We could add to the launcher model to be able to configure packages
>>> to register with the session.
>>> What do you think?
>>>
>>> Cheers
>>> /Eike
>>>
>>>
>>> Víctor Roldán Betancort schrieb:
>>>> Hi András,
>>>>
>>>> I've already tried out in a clean Ganymede release, and everything
>>>> seems to work fine for me :S
>>>>
>>>> Just detected a small bug that triggers the launching once the
>>>> wizard creates an instance, since by default the wizard tries to
>>>> open the editor, and in this case, it finds the "launch" action as
>>>> default action (dunno why... maybe setting content-type priority to
>>>> low...)
>>>>
>>>> If it works that way for you, it means the auto-registry is not
>>>> registering your model properly. Some of the reasons could be:
>>>>
>>>> - The model code is not native (although I believe dynamic mode
>>>> should work).
>>>>
>>>> - (most probably) The model is not registered in the EMF registry.
>>>> Are you running the launcher file in the same workspace where the
>>>> model's code is located? Have you tried running the launcher in a
>>>> runtime-workbench? (run -> run-as -> Eclipse Application)
>>>>
>>>> HTH,
>>>> ViK.
>>>>
>>>> András Ökrös escribió:
>>>>> Hi Vik,
>>>>>
>>>>> The launcher has the same behaviour with the CDOEditor
>>>>> (org.eclipse.emf.cdo.ui.CDOEditor).
>>>>>
>>>>> I haven't tried it out with the HEAD, however I get it working by
>>>>> inserting the
>>>>> session.getPackageRegistry().putEPackage(OurModelPackage.eIN STANCE);
>>>>> code into the CDOEditorLauncher. Although it is not a good general
>>>>> approach.
>>>>>
>>>>> Maybe the Automatic Package Registry doesn't works well? Do you
>>>>> have any tips?
>>>>>
>>>>> Cheers,
>>>>> András
>>>>>
>>>>>
>>>>> Víctor Roldán Betancort írta:
>>>>>> Hi András,
>>>>>>
>>>>>>> Maybe I do something wrong, but I only see the root elements in
>>>>>>> the resource after loading it (no attributes, or anything else).
>>>>>>> The editor I use is good (a CDO enhanced one), because it works
>>>>>>> with my own plain xml file based loader well.
>>>>>>
>>>>>> Uhm, strange...
>>>>>>
>>>>>> Are you sure you are using the generated enhanced editor? I mean,
>>>>>> you properly set the generated ID in the launcher model attribute
>>>>>> "editorId", right? (it's, by default, the same as the original
>>>>>> editor ID, but ended in "enhanced", if I recall correctly. you
>>>>>> can see it in the plugin.xml at the extensions tab).
>>>>>>
>>>>>> Could you try to launch the resource using CDOEditor instead?
>>>>>> (its ID is "org.eclipse.emf.cdo.ui.CDOEditor") and see if you get
>>>>>> the same behaviour?
>>>>>>
>>>>>>> Thanks in advance if you have some ideas, what can be wrong. (I
>>>>>>> use the CDO version 1.0.0.v200806180411) Let me know, if you
>>>>>>> need some more information about this.
>>>>>>
>>>>>> That's almost the Ganymede's code, I believe (CDO project page
>>>>>> shows "200806241000" available to download. Mark was also
>>>>>> experiencing some problems with the initial Ganymede release. I'm
>>>>>> not sure about what could be happening... I always suggest to try
>>>>>> out the HEAD code...
>>>>>>
>>>>>> I haven't tried out yet the launcher with Ganymede release.
>>>>>> I'll go on with it tomorrow and let you now know :D
>>>>>>
>>>>>> Cheers,
>>>>>> ViK.


Re: [CDO]: CDO Resource Launcher [message #422641 is a reply to message #422612] Thu, 11 September 2008 16:00 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: andras.okros.optxware.com

Hi ViK, Eike,

The extension of the launcher model sounds great :).


My test-model is not native (emm.. I don't know how can it be :) ). I
run the launcher in a runtime-workbench, the model code (with the
launcher's code) is in the host eclipse. I tried to put the model code
in the runtime-workbench as well, but it didn't helped.

Maybe there is something wrong with the EMF registry config? I didn't
done anything to it, I think the generator created the extension
automatically (org.eclipse.emf.ecore.generated_package).

Thanks in advance if you have any suggestions. I'll keep on trying for
sure, and let you know if I found the cause.

Best regards,
András


Víctor Roldán Betancort írta:
> Hi András,
>
> I've already tried out in a clean Ganymede release, and everything seems
> to work fine for me :S
>
> Just detected a small bug that triggers the launching once the wizard
> creates an instance, since by default the wizard tries to open the
> editor, and in this case, it finds the "launch" action as default action
> (dunno why... maybe setting content-type priority to low...)
>
> If it works that way for you, it means the auto-registry is not
> registering your model properly. Some of the reasons could be:
>
> - The model code is not native (although I believe dynamic mode should
> work).
>
> - (most probably) The model is not registered in the EMF registry. Are
> you running the launcher file in the same workspace where the model's
> code is located? Have you tried running the launcher in a
> runtime-workbench? (run -> run-as -> Eclipse Application)
>
> HTH,
> ViK.
Re: [CDO]: CDO Resource Launcher [message #422644 is a reply to message #422641] Thu, 11 September 2008 16:12 Go to previous messageGo to next message
Victor Roldan Betancort is currently offline Victor Roldan BetancortFriend
Messages: 524
Registered: July 2009
Senior Member
András,

> My test-model is not native (emm.. I don't know how can it be :) ).

Sorry, I meant CDO Native :P Otherwise, you'll be using dynamic mode.
(works fine but with some drawbacks)
For this, you have to create a new .genmodel with configured
specifically for CDO. This is can be done using a wizard contributed by
CDO in the EMF Model project. Take a look at:

http://wiki.eclipse.org/Preparing_EMF_Models_for_CDO

Maybe this could help with you problem :)

> I run the launcher in a runtime-workbench, the model code (with the
> launcher's code) is in the host eclipse. I tried to put the model code
> in the runtime-workbench as well, but it didn't helped.

You were already doing it in the right way, son forget about my second
hypothesis :P

> Maybe there is something wrong with the EMF registry config? I didn't
> done anything to it, I think the generator created the extension
> automatically (org.eclipse.emf.ecore.generated_package).

Yes, and that's fine. So I think the EMF registry has nothing to do with
your problem.

Maybe dynamic mode is related with your problem. I'll try to reproduce
your problem with a non-native model.

> Thanks in advance if you have any suggestions. I'll keep on trying for
> sure, and let you know if I found the cause.

Thanks!
ViK
Re: [CDO]: CDO Resource Launcher [message #422647 is a reply to message #422644] Thu, 11 September 2008 17:03 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: andras.okros.optxware.com

Vik,

First, thanks for the fast answer!

Ok I understand now the CDO Native stuff. My model is CDO Native then
:). On the host eclipse the CDO Sessions view says, that this model is
?/Dynamic (Registry/Repository). After opening a resource it became
Dynamic both. The general cdo editor works just fine here.

In the runtime eclipse I never tried out the CDO Session view until now.
The package manager says its Native/Dynamic, but after the first start,
it bacame Dynamic both. Starting the general editor from here produces
the same problem, that the launcher, the editor doesn't recognize my
package at all.. (So after all, it seems that this problem has nothing
to do with your launcher, or enhanced editor :)

Thanks,
András

Víctor Roldán Betancort írta:
> András,
>
>> My test-model is not native (emm.. I don't know how can it be :) ).
>
> Sorry, I meant CDO Native :P Otherwise, you'll be using dynamic mode.
> (works fine but with some drawbacks)
> For this, you have to create a new .genmodel with configured
> specifically for CDO. This is can be done using a wizard contributed by
> CDO in the EMF Model project. Take a look at:
>
> http://wiki.eclipse.org/Preparing_EMF_Models_for_CDO
>
> Maybe this could help with you problem :)
>
>> I run the launcher in a runtime-workbench, the model code (with the
>> launcher's code) is in the host eclipse. I tried to put the model code
>> in the runtime-workbench as well, but it didn't helped.
>
> You were already doing it in the right way, son forget about my second
> hypothesis :P
>
>> Maybe there is something wrong with the EMF registry config? I didn't
>> done anything to it, I think the generator created the extension
>> automatically (org.eclipse.emf.ecore.generated_package).
>
> Yes, and that's fine. So I think the EMF registry has nothing to do with
> your problem.
>
> Maybe dynamic mode is related with your problem. I'll try to reproduce
> your problem with a non-native model.
>
>> Thanks in advance if you have any suggestions. I'll keep on trying for
>> sure, and let you know if I found the cause.
>
> Thanks!
> ViK
Re: [CDO]: CDO Resource Launcher [message #422649 is a reply to message #422647] Thu, 11 September 2008 18:10 Go to previous messageGo to next message
Victor Roldan Betancort is currently offline Victor Roldan BetancortFriend
Messages: 524
Registered: July 2009
Senior Member
András,

> First, thanks for the fast answer!

You are welcome!


> Ok I understand now the CDO Native stuff. My model is CDO Native then
> :). On the host eclipse the CDO Sessions view says, that this model is
> ?/Dynamic (Registry/Repository). After opening a resource it became
> Dynamic both. The general cdo editor works just fine here.

Yes, this is the expected behaviour. The model is not registered in the
EMF Registry, since the plugin's extension points are not exposed to the
workbench.

> In the runtime eclipse I never tried out the CDO Session view until now.
> The package manager says its Native/Dynamic, but after the first start,
> it bacame Dynamic both. Starting the general editor from here produces
> the same problem, that the launcher, the editor doesn't recognize my
> package at all.. (So after all, it seems that this problem has nothing
> to do with your launcher, or enhanced editor :)

Yes, it seems is a problem related with your model.
Usually, if everything is fine, it appears to me as "Native/Static".

It seems that your registry recognizes properly the model's code as
native. I can't really say why, after opening a resource, it turns into
"Dynamic" both. Have you tried creating a new resource, instead of
opening an already existing one in the CDO Server repository? Maybe the
problem is the stored instance that you are trying to open?

>
> Thanks,
> András
>
> Víctor Roldán Betancort írta:
>> András,
>>
>>> My test-model is not native (emm.. I don't know how can it be :) ).
>>
>> Sorry, I meant CDO Native :P Otherwise, you'll be using dynamic mode.
>> (works fine but with some drawbacks)
>> For this, you have to create a new .genmodel with configured
>> specifically for CDO. This is can be done using a wizard contributed
>> by CDO in the EMF Model project. Take a look at:
>>
>> http://wiki.eclipse.org/Preparing_EMF_Models_for_CDO
>>
>> Maybe this could help with you problem :)
>>
>>> I run the launcher in a runtime-workbench, the model code (with the
>>> launcher's code) is in the host eclipse. I tried to put the model
>>> code in the runtime-workbench as well, but it didn't helped.
>>
>> You were already doing it in the right way, son forget about my second
>> hypothesis :P
>>
>>> Maybe there is something wrong with the EMF registry config? I didn't
>>> done anything to it, I think the generator created the extension
>>> automatically (org.eclipse.emf.ecore.generated_package).
>>
>> Yes, and that's fine. So I think the EMF registry has nothing to do
>> with your problem.
>>
>> Maybe dynamic mode is related with your problem. I'll try to reproduce
>> your problem with a non-native model.
>>
>>> Thanks in advance if you have any suggestions. I'll keep on trying
>>> for sure, and let you know if I found the cause.
>>
>> Thanks!
>> ViK
Re: [CDO]: CDO Resource Launcher [message #422733 is a reply to message #422591] Mon, 15 September 2008 15:31 Go to previous message
Eclipse UserFriend
Originally posted by: andras.okros.optxware.com

An update to the CDO 2.0 HEAD code solved the problem.

Cheers,
András

András Ökrös írta:
> Hello Victor,
>
> Maybe I do something wrong, but I only see the root elements in the
> resource after loading it (no attributes, or anything else). The editor
> I use is good (a CDO enhanced one), because it works with my own plain
> xml file based loader well.
>
> Thanks in advance if you have some ideas, what can be wrong. (I use the
> CDO version 1.0.0.v200806180411) Let me know, if you need some more
> information about this.
>
> Best regards,
> András
>
> Víctor Roldán Betancort írta:
>> Hi André,
>>
>>> I tested this stuff yesterday and I got everything rolling fine (I
>>> use a ganymede ide, cdo/net4j bundles from cvs and a target platform
>>> built a month ago).
>>
>> Great that everything worked fine :D
>>
>> Cheers!
>> ViK
Previous Topic:[Teneo] Different generation using opposite
Next Topic:Teneo Hibernate Dialect must be explicitly set
Goto Forum:
  


Current Time: Tue Jan 28 06:19:52 GMT 2020

Powered by FUDForum. Page generated in 0.02738 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top