[deepamehta-devel] changing label config of existing topic type

[Jörg Richter]

Hi Robert,

> On 17 Jan 2017, at 18:57, Robert Schuster <robert.schuster.rs01 at gmail.com> wrote:
> 
> I tried to fix the Proposal type on my own and it seemed the following code would bring proper values to the "Include in Label" child of the association:
> 
> TopicType tt = dm4.getTopicType(NS("proposal"));
> tt.getAssocDef("dm4.datetime.date#dm4.events.from").getChildTopics().set("dm4.core.include_in_label", false);
> tt.getAssocDef("dm4.datetime.date#dm4.events.to").getChildTopics().set("dm4.core.include_in_label", false);

Your code looks good.

> In DM 4.8.4+4.8.5 this leads to a ClassCastException:
> 
> Caused by: java.lang.ClassCastException: de.deepamehta.core.impl.AssociationModelImpl cannot be cast to de.deepamehta.core.model.AssociationDefinitionModel
>     at de.deepamehta.core.impl.AssociationDefinitionModelImpl.postUpdate(AssociationDefinitionModelImpl.java:170)
>     at de.deepamehta.core.impl.DeepaMehtaObjectModelImpl.update(DeepaMehtaObjectModelImpl.java:400)
>     ... 31 more
> 
> Do you think this needs to be fixed in DM? Should I file a bug report?

Confirmed!
This is a bug in the DM Core.
Yes, please file a bug report.

We have 2 bugs now.
Consider filing 2 separate reports.
Both will be fixed in 4.8.6 then.

Thank you very much for reporting!

Cheers,
Jörg

-------------- n?chster Teil --------------
Ein Dateianhang mit Bin?rdaten wurde abgetrennt...
Dateiname   : signature.asc
Dateityp    : application/pgp-signature
Dateigr??e  : 496 bytes
Beschreibung: Message signed with OpenPGP using GPGMail
URL         : <http://lists.deepamehta.de/pipermail/devel-lists.deepamehta.de/attachments/20170118/753e38d9/attachment.sig>