Re: [henshin-dev] Attribute default value "null" check

[Johannes Tietje <johannes.tietje@xxxxxxxxxxxxxxxxx>]

Hello,

thank you for your fast reply, I was able to build the rules correctly
with your "workaround".

Greets,
Johannes

Am Montag, den 04.04.2011, 10:51 +0200 schrieb Enrico Biermann: 
> Hello Johannes,
> 
> I was able to reproduce the bug and will fix it soon. In the meantime,
> if you want to check for the value "null" of an attribute during
> matching, you can use attribute conditions if you want to check for null:
> - Assign a parameter (lets say x) to the attribute
> - Define an attribute condition x == null for the rule
> 
> Regards,
> Enrico
> 
> On 04.04.2011 10:31, Johannes Tietje wrote:
> > Hello,
> >
> > I recently created a set of Henshin rules operating on a Ecore model
> > with an object (Transition) whose attributes (action, trigger) are of
> > type String and have a default value of "null". 
> >
> > How do I specify that an objects attribute is assigned with "null"
> > without receiving a NullPointerException (which comes up when the rule
> > matcher tries to match the LHS to the model, i guess)?
> >
> > Kind regards,
> > Johannes
> >
> >
> > _______________________________________________
> > henshin-dev mailing list
> > henshin-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/henshin-dev
> _______________________________________________
> henshin-dev mailing list
> henshin-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/henshin-dev