Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Sirius » Error logging
Error logging [message #1430358] Wed, 24 September 2014 09:40 Go to next message
Felix Dorner is currently offline Felix DornerFriend
Messages: 295
Registered: March 2012
Senior Member
Hi,

(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
runtime.

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?

Thanks,
Felix
Re: Error logging [message #1430641 is a reply to message #1430358] Wed, 24 September 2014 15:46 Go to previous messageGo to next message
Esteban Dugueperoux is currently offline Esteban DugueperouxFriend
Messages: 472
Registered: July 2009
Senior Member
Hi Felix,

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?

Best Regards.

Le 24/09/2014 11:40, Felix Dorner a écrit :
> Hi,
>
> (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
> runtime.
>
> 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?
>
> Thanks,
> Felix



--
Esteban Dugueperoux - Obeo

Need professional services for Sirius?
http://www.obeodesigner.com/sirius
Re: Error logging [message #1430667 is a reply to message #1430641] Wed, 24 September 2014 16:27 Go to previous message
Felix Dorner is currently offline Felix DornerFriend
Messages: 295
Registered: March 2012
Senior Member
On 24/09/2014 17:46, Esteban Dugueperoux wrote:
> Hi Felix,
>
> 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?

It is org.eclipse.sirius.runtimeLogger. It's being consumed in
RuntimeLoggerManager.
Previous Topic:unable to apply Viewpoints for modeling project
Next Topic:Layout configuration
Goto Forum:
  


Current Time: Mon Mar 30 16:47:33 GMT 2020

Powered by FUDForum. Page generated in 0.02930 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top