| AW: [mdt-bpmn2.dev] Multi-file support |
|
PS: The error originally is emitted by ECoreValidator. validateEReference_ConsistentOpposite(). You also see it if you
right-click in the ECore editor and choose “Validate”. Von:
mdt-bpmn2.dev-bounces@xxxxxxxxxxx [mailto:mdt-bpmn2.dev-bounces@xxxxxxxxxxx] Im
Auftrag von Hille-Doering, Reiner I have changed „transient“ together with resolveProxies, because
else opening .genmodel shows me the nasty error “The opposite of a
transient reference > must transient if it is proxy resolving”. Unfortunately you are right: setting “transient” to true on the
storage side has the effect that the reference is not serialized at all. I didn’t find a lot of information about the flags and there
conditions: General meaning of the flags: Discussion about the “transient resolve proxies issue”: http://dev.eclipse.org/newslists/news.eclipse.tools.emf/msg23116.html I really don’t know what to do here, except removing the non-storage
end of the association or some more in-depth tricks in our resource
implementation. Any ideas? Reiner. Von:
mdt-bpmn2.dev-bounces@xxxxxxxxxxx [mailto:mdt-bpmn2.dev-bounces@xxxxxxxxxxx] Im
Auftrag von Henning Heitkötter No problem, I think we didn't
duplicate any work ;-) 2010/8/23 Hille-Doering, Reiner <reiner.hille-doering@xxxxxxx> Hi Henning, wow, this is funny. You sent you mail almost
exactly in the moment when I wrote my other one J . Thanks to the work
again – I agree with your proposals. As I have already applied
some of the issues in your Excel, but not completely, I would ask you to update
it ones more to differentiate the fixed on non-fixed ones. And after you have
done your feature in the templates, we continue in a coordinated manner ;-) Regards, Reiner. Von: mdt-bpmn2.dev-bounces@xxxxxxxxxxx
[mailto:mdt-bpmn2.dev-bounces@xxxxxxxxxxx]
Im Auftrag von Henning Heitkötter
Hi
Reiner, 2010/8/21
Hille-Doering, Reiner <reiner.hille-doering@xxxxxxx> 2.
For all those
references, check if the target type is abstract. If yes, remove the abstract
flag. If you like you could extend your Excel to mark those cases. See
the attached document.
We
could add another details entry to the ExtendedMetadata of these classes (e.g.
abstract -> true). Additionally, I suggest to change the template
FactoryClass.javajet to the effect that the create method for originally
abstract classes does not appear in the interface Bpmn2Factory and is not
public in Bpmn2FactoryImpl. Thus it can be created during deserialization
(which calls EFactory.create(EClass)) but is somewhat hidden to users.
|