Home » Archived » Riena » IObjectTransaction.addReference()
IObjectTransaction.addReference() [message #1589] |
Mon, 19 May 2008 20:04 |
Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
the JavaDoc says:
Adds the reference to a child object simular to setReferenceObject with
the difference that the referenceName refers to an unsorted collection of
objects.
does this really mean, that you only support unsorted collections ?
no SortedSet, no List ?
thx for info
ekke
|
|
| |
Re: IObjectTransaction.addReference() [message #2806 is a reply to message #2754] |
Tue, 20 May 2008 16:05 |
Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
christian,
I think, at the moment I can live with these limitations -
if I found a situation where its really a stopper, I'll file a request.
So for now its the best I'll change some of my code-generation to use
also LinkedHashSet and ArrayList
ekke
|
|
|
Re: IObjectTransaction.addReference() [message #15679 is a reply to message #2806] |
Mon, 20 October 2008 10:34 |
Eclipse User |
|
|
|
Originally posted by: fdo.scodi.ch
Hello
Has there anything changed about this state?
I'm trying to transfer EMF objects with Riena, which works great. The only
problem is the usage of EObjectResolvingEList, which is used as soon as I
have a multi reference field.
Example:
public List<RoleRef> getRoles() {
if (roles == null) {
roles = new EObjectResolvingEList<RoleRef>(RoleRef.class, this,
BasicPackage.PERSON_BASIC__ROLES);
}
return roles;
}
Is it planned to fix this issue?
Thanks
Flavio
ekke wrote:
> christian,
> I think, at the moment I can live with these limitations -
> if I found a situation where its really a stopper, I'll file a request.
> So for now its the best I'll change some of my code-generation to use
> also LinkedHashSet and ArrayList
> ekke
|
|
|
Re: IObjectTransaction.addReference() [message #15707 is a reply to message #15679] |
Mon, 20 October 2008 12:38 |
Christian Campo Messages: 597 Registered: July 2009 |
Senior Member |
|
|
Hi Flavio,
your posting does not really state what "the issue" is. Being an EMF nerd its also not clear why your posted statment
should not work with Riena.
And other than that, ekke said he can live with the limitation. If you cant, please file a bugreport. Thats the way
things get done. A thread on the newsgroups help people to understand problems and exchange information. They usually
never get things done.
And you need to explain in the bugreport what goes wrong. You can also try to fix it yourself and attach a patch but
thats not a requirement. I am just trying to encourage you :-)
christian
Flavio Donzé schrieb:
> Hello
>
> Has there anything changed about this state?
> I'm trying to transfer EMF objects with Riena, which works great. The
> only problem is the usage of EObjectResolvingEList, which is used as
> soon as I have a multi reference field.
>
> Example: public List<RoleRef> getRoles() {
> if (roles == null) {
> roles = new EObjectResolvingEList<RoleRef>(RoleRef.class, this,
> BasicPackage.PERSON_BASIC__ROLES);
> }
> return roles;
> }
>
> Is it planned to fix this issue?
>
> Thanks
> Flavio
>
> ekke wrote:
>
>> christian,
>
>> I think, at the moment I can live with these limitations -
>> if I found a situation where its really a stopper, I'll file a request.
>
>> So for now its the best I'll change some of my code-generation to use
>> also LinkedHashSet and ArrayList
>
>> ekke
>
>
|
|
|
Re: IObjectTransaction.addReference() [message #16464 is a reply to message #15707] |
Tue, 21 October 2008 12:34 |
Eclipse User |
|
|
|
Originally posted by: fdo.scodi.ch
hey Christian
Sorry for not being so clear, I think I replied to the wrong post in the
first place.
I reported a bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=251501
Christian Campo wrote:
> Hi Flavio,
> your posting does not really state what "the issue" is. Being an EMF nerd
its also not clear why your posted statment
> should not work with Riena.
> And other than that, ekke said he can live with the limitation. If you cant,
please file a bugreport. Thats the way
> things get done. A thread on the newsgroups help people to understand
problems and exchange information. They usually
> never get things done.
> And you need to explain in the bugreport what goes wrong. You can also try
to fix it yourself and attach a patch but
> thats not a requirement. I am just trying to encourage you :-)
> christian
> Flavio Donzé schrieb:
>> Hello
>>
>> Has there anything changed about this state?
>> I'm trying to transfer EMF objects with Riena, which works great. The
>> only problem is the usage of EObjectResolvingEList, which is used as
>> soon as I have a multi reference field.
>>
>> Example: public List<RoleRef> getRoles() {
>> if (roles == null) {
>> roles = new EObjectResolvingEList<RoleRef>(RoleRef.class, this,
>> BasicPackage.PERSON_BASIC__ROLES);
>> }
>> return roles;
>> }
>>
>> Is it planned to fix this issue?
>>
>> Thanks
>> Flavio
>>
>> ekke wrote:
>>
>>> christian,
>>
>>> I think, at the moment I can live with these limitations -
>>> if I found a situation where its really a stopper, I'll file a request.
>>
>>> So for now its the best I'll change some of my code-generation to use
>>> also LinkedHashSet and ArrayList
>>
>>> ekke
>>
>>
|
|
| |
Re: IObjectTransaction.addReference() [message #571084 is a reply to message #2754] |
Tue, 20 May 2008 16:05 |
Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
christian,
I think, at the moment I can live with these limitations -
if I found a situation where its really a stopper, I'll file a request.
So for now its the best I'll change some of my code-generation to use
also LinkedHashSet and ArrayList
ekke
|
|
|
Re: IObjectTransaction.addReference() [message #576560 is a reply to message #2806] |
Mon, 20 October 2008 10:34 |
Eclipse User |
|
|
|
Originally posted by: fdo.scodi.ch
Hello
Has there anything changed about this state?
I'm trying to transfer EMF objects with Riena, which works great. The only
problem is the usage of EObjectResolvingEList, which is used as soon as I
have a multi reference field.
Example:
public List<RoleRef> getRoles() {
if (roles == null) {
roles = new EObjectResolvingEList<RoleRef>(RoleRef.class, this,
BasicPackage.PERSON_BASIC__ROLES);
}
return roles;
}
Is it planned to fix this issue?
Thanks
Flavio
ekke wrote:
> christian,
> I think, at the moment I can live with these limitations -
> if I found a situation where its really a stopper, I'll file a request.
> So for now its the best I'll change some of my code-generation to use
> also LinkedHashSet and ArrayList
> ekke
|
|
|
Re: IObjectTransaction.addReference() [message #576569 is a reply to message #15679] |
Mon, 20 October 2008 12:38 |
Christian Campo Messages: 597 Registered: July 2009 |
Senior Member |
|
|
Hi Flavio,
your posting does not really state what "the issue" is. Being an EMF nerd its also not clear why your posted statment
should not work with Riena.
And other than that, ekke said he can live with the limitation. If you cant, please file a bugreport. Thats the way
things get done. A thread on the newsgroups help people to understand problems and exchange information. They usually
never get things done.
And you need to explain in the bugreport what goes wrong. You can also try to fix it yourself and attach a patch but
thats not a requirement. I am just trying to encourage you :-)
christian
Flavio Donzé schrieb:
> Hello
>
> Has there anything changed about this state?
> I'm trying to transfer EMF objects with Riena, which works great. The
> only problem is the usage of EObjectResolvingEList, which is used as
> soon as I have a multi reference field.
>
> Example: public List<RoleRef> getRoles() {
> if (roles == null) {
> roles = new EObjectResolvingEList<RoleRef>(RoleRef.class, this,
> BasicPackage.PERSON_BASIC__ROLES);
> }
> return roles;
> }
>
> Is it planned to fix this issue?
>
> Thanks
> Flavio
>
> ekke wrote:
>
>> christian,
>
>> I think, at the moment I can live with these limitations -
>> if I found a situation where its really a stopper, I'll file a request.
>
>> So for now its the best I'll change some of my code-generation to use
>> also LinkedHashSet and ArrayList
>
>> ekke
>
>
|
|
|
Re: IObjectTransaction.addReference() [message #576666 is a reply to message #15707] |
Tue, 21 October 2008 12:34 |
Eclipse User |
|
|
|
Originally posted by: fdo.scodi.ch
hey Christian
Sorry for not being so clear, I think I replied to the wrong post in the
first place.
I reported a bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=251501
Christian Campo wrote:
> Hi Flavio,
> your posting does not really state what "the issue" is. Being an EMF nerd
its also not clear why your posted statment
> should not work with Riena.
> And other than that, ekke said he can live with the limitation. If you cant,
please file a bugreport. Thats the way
> things get done. A thread on the newsgroups help people to understand
problems and exchange information. They usually
> never get things done.
> And you need to explain in the bugreport what goes wrong. You can also try
to fix it yourself and attach a patch but
> thats not a requirement. I am just trying to encourage you :-)
> christian
> Flavio Donzé schrieb:
>> Hello
>>
>> Has there anything changed about this state?
>> I'm trying to transfer EMF objects with Riena, which works great. The
>> only problem is the usage of EObjectResolvingEList, which is used as
>> soon as I have a multi reference field.
>>
>> Example: public List<RoleRef> getRoles() {
>> if (roles == null) {
>> roles = new EObjectResolvingEList<RoleRef>(RoleRef.class, this,
>> BasicPackage.PERSON_BASIC__ROLES);
>> }
>> return roles;
>> }
>>
>> Is it planned to fix this issue?
>>
>> Thanks
>> Flavio
>>
>> ekke wrote:
>>
>>> christian,
>>
>>> I think, at the moment I can live with these limitations -
>>> if I found a situation where its really a stopper, I'll file a request.
>>
>>> So for now its the best I'll change some of my code-generation to use
>>> also LinkedHashSet and ArrayList
>>
>>> ekke
>>
>>
|
|
|
Goto Forum:
Current Time: Sat Oct 19 19:14:58 GMT 2024
Powered by FUDForum. Page generated in 0.04423 seconds
|