Supporting other java tracers

[GoogleCodeExporter]

What improvement do you want to Umple? Describe your vision of the new
functionality in as much detail as you can think of, including using
examples of code.

Right now, tracing in Umple supports two primitive tracers: Console and file. 
Console directs trace output to a standard error, while the later directs it to 
a file.

What difficulties (if any) would this new feature help you overcome?

How big, if any, do you expect the benefits of this to be to the software
engineering community?

What parts of the system (that you are aware of) would need to change?

Please use tags such as 'stateMachines', 'Tracing', etc. to help us
categorize this request.

Original issue reported on code.google.com by hjam...@gmail.com on 16 Jan 2014 at 3:57

[GoogleCodeExporter]

What improvement do you want to Umple? Describe your vision of the new
functionality in as much detail as you can think of, including using
examples of code.

Right now, tracing in Umple supports two primitive tracers: Console and file. 
Console directs trace output to a standard error, while the later directs it to 
a file.

It would be nice if other tracers is supported next to these primitive tracers. 
Suggested tracers are lttng and log4j.

[Syntax]

tracer log4j;
class Student
{
  Integer id;
  trace id;
}

What difficulties (if any) would this new feature help you overcome?
not that difficult if you are familiar with targeted tracer.

What parts of the system (that you are aware of) would need to change?
JET templates (code generation).

Original comment by hjam...@gmail.com on 16 Jan 2014 at 4:06

• Added labels: ucosp, Priority-Medium, tracing, associations
• Removed labels: ucops

[GoogleCodeExporter]

Adding missing difficulty and component tags.

Original comment by TimothyCLethbridge on 1 May 2014 at 2:07

• Changed state: Accepted
• Added labels: Component-SemanticsAndGen, Diffic-Med

[GoogleCodeExporter]

Original comment by TimothyCLethbridge on 5 Sep 2014 at 3:13

• Removed labels: ucosp