|Re: Error logging [message #1430641 is a reply to message #1430358]
||Wed, 24 September 2014 15:46
| Esteban Dugueperoux
Registered: July 2009
In which case you would like Sirius log? It is possible that in some
cases the odesign interpretation is incorrect and nothing is logged. If
you have found some of these case, you can raise a bugzilla with
reproduction data and scenario.
Which logging extension point are you talking about?
Le 24/09/2014 11:40, Felix Dorner a écrit :
> (I use the old Acceleo2 engine, maybe this has some impact, but I guess
> evaluation errors could be logged independently of the underlying engine)
> I always thought that Sirius was too silent about invalid expressions at
> I now found out that if I import the .odesign plugin into the runtime
> workspace, Sirius would create a marker on the relevant odesign object.
> For now I never had done that import, because it gave me weird results
> sometimes (Can't exactly remember), and also - this option will not be
> feasible once the product is deployed.
> So once I deploy my sirius application, theres no expression error
> logging whatsoever by default. Is that really desirable? I am aware of
> the logging extension point. The question is: Why does sirius itself not
> provide a default extension that logs to the error log?
Esteban Dugueperoux - Obeo
Need professional services for Sirius?
Powered by FUDForum
. Page generated in 0.02930 seconds