Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF » [CDO] Validation problem markers
[CDO] Validation problem markers [message #934026] Fri, 05 October 2012 15:22 Go to next message
Christian W. Damus is currently offline Christian W. Damus
Messages: 802
Registered: July 2009
Senior Member
Hi,

EMF-based applications typically use Eclipse workspace markers to
present validation problems in the Problems view and in the editor (the
label decorator uses the trace from the marker to the offending
object's URI). This works great for the generated editors using
workspace resources.

However, in a CDO world, resources don't live in the workspace and
workspace metadata such as problem markers do not apply. Has anyone
provided an alternative mechanism for tracking and presenting problems
in the CDO context? I could imagine something as simple as a problem
model that annotates elements simply by referencing them; it could be
persisted anywhere, but would probably not make sense in to share in
the repository. Label decorations would be straight-forward, but the
standard Problems view is marker-driven so presumably some new view
would be needed for validation problems.

Thanks,

Christian
Re: [CDO] Validation problem markers [message #934073 is a reply to message #934026] Fri, 05 October 2012 16:21 Go to previous messageGo to next message
Eike Stepper is currently offline Eike Stepper
Messages: 5545
Registered: July 2009
Senior Member
Hi Christian,

I know of no effort in that direction. It would certainly be cool to reuse the Problems view but I also don't see how to
provide those darned IResources to the markers API.

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper


Am 05.10.2012 17:22, schrieb Christian W. Damus:
> Hi,
>
> EMF-based applications typically use Eclipse workspace markers to present validation problems in the Problems view and
> in the editor (the label decorator uses the trace from the marker to the offending object's URI). This works great
> for the generated editors using workspace resources.
>
> However, in a CDO world, resources don't live in the workspace and workspace metadata such as problem markers do not
> apply. Has anyone provided an alternative mechanism for tracking and presenting problems in the CDO context? I could
> imagine something as simple as a problem model that annotates elements simply by referencing them; it could be
> persisted anywhere, but would probably not make sense in to share in the repository. Label decorations would be
> straight-forward, but the standard Problems view is marker-driven so presumably some new view would be needed for
> validation problems.
>
> Thanks,
>
> Christian
>
Re: [CDO] Validation problem markers [message #934081 is a reply to message #934073] Fri, 05 October 2012 16:31 Go to previous messageGo to next message
Christian W. Damus is currently offline Christian W. Damus
Messages: 802
Registered: July 2009
Senior Member
Thanks, Eike.

If nobody else responds with any pointers, then I shall probably wind
up contributing a solution, myself. Would such a thing be welcome in
CDO?

cW


On 2012-10-05 16:21:31 +0000, Eike Stepper said:

> Hi Christian,
>
> I know of no effort in that direction. It would certainly be cool to
> reuse the Problems view but I also don't see how to provide those
> darned IResources to the markers API.
>
> Cheers
> /Eike
>
> ----
> http://www.esc-net.de
> http://thegordian.blogspot.com
> http://twitter.com/eikestepper
>
>
> Am 05.10.2012 17:22, schrieb Christian W. Damus:
>> Hi,
>>
>> EMF-based applications typically use Eclipse workspace markers to
>> present validation problems in the Problems view and in the editor (the
>> label decorator uses the trace from the marker to the offending
>> object's URI). This works great for the generated editors using
>> workspace resources.
>>
>> However, in a CDO world, resources don't live in the workspace and
>> workspace metadata such as problem markers do not apply. Has anyone
>> provided an alternative mechanism for tracking and presenting problems
>> in the CDO context? I could imagine something as simple as a problem
>> model that annotates elements simply by referencing them; it could be
>> persisted anywhere, but would probably not make sense in to share in
>> the repository. Label decorations would be straight-forward, but the
>> standard Problems view is marker-driven so presumably some new view
>> would be needed for validation problems.
>>
>> Thanks,
>>
>> Christian
Re: [CDO] Validation problem markers [message #934086 is a reply to message #934081] Fri, 05 October 2012 16:36 Go to previous message
Eike Stepper is currently offline Eike Stepper
Messages: 5545
Registered: July 2009
Senior Member
Am 05.10.2012 18:31, schrieb Christian W. Damus:
> Thanks, Eike.
>
> If nobody else responds with any pointers, then I shall probably wind up contributing a solution, myself. Would such
> a thing be welcome in CDO?
Most welcome! Let me know if you need help...

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper


>
> cW
>
>
> On 2012-10-05 16:21:31 +0000, Eike Stepper said:
>
>> Hi Christian,
>>
>> I know of no effort in that direction. It would certainly be cool to reuse the Problems view but I also don't see how
>> to provide those darned IResources to the markers API.
>>
>> Cheers
>> /Eike
>>
>> ----
>> http://www.esc-net.de
>> http://thegordian.blogspot.com
>> http://twitter.com/eikestepper
>>
>>
>> Am 05.10.2012 17:22, schrieb Christian W. Damus:
>>> Hi,
>>>
>>> EMF-based applications typically use Eclipse workspace markers to present validation problems in the Problems view
>>> and in the editor (the label decorator uses the trace from the marker to the offending object's URI). This works
>>> great for the generated editors using workspace resources.
>>>
>>> However, in a CDO world, resources don't live in the workspace and workspace metadata such as problem markers do not
>>> apply. Has anyone provided an alternative mechanism for tracking and presenting problems in the CDO context? I
>>> could imagine something as simple as a problem model that annotates elements simply by referencing them; it could be
>>> persisted anywhere, but would probably not make sense in to share in the repository. Label decorations would be
>>> straight-forward, but the standard Problems view is marker-driven so presumably some new view would be needed for
>>> validation problems.
>>>
>>> Thanks,
>>>
>>> Christian
>
>
Previous Topic:[JET]JETEmitter Problem when running workspace
Next Topic:RCP Build Failed - Could not create feature
Goto Forum:
  


Current Time: Sat Oct 25 07:12:50 GMT 2014

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

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