[news.eclipse.platform] [DataBinding] hibernate+spring+eclipse+databindi

[aappddeevv <aappddeevv@xxxxxxxxxxx>]

I am building a db intensive application with many data entry screens 
(i.e. implemented using eclipse managed forms).  I am also using eclipse 
databinding.  After adding validators to the bound fields of interest, I 
can track whether there are errors by using 
DataBindingContext.getValidationErrors() and tracking changes to the 
list.  I want to display validation errors from multiple contexts 
(corresponding to multiple data entry screens being open at the same 
time) in one view.  Similar to jgoodies validation, it would be nice to 
have a nice view factory for getting different display widgets.

I like ProblemView and would like to use something similar for 
consolidating errors into one view for all screens, etc.  That screen 
seems to be tied to IResources and Markers.  Does anyone have experience 
using IResources and Markers for data entry screens versus IResources 
like files and projects.  It appears that Resources are limited to 
files, folders and projects so my data entry screens do not fall into 
that category.  I also like the fact that the ProblemView feels much 
more decoupled in terms of workbench parts.  I have already done the 
obvious thing of creating a text area that shows validation messages 
when I receive a list changed event from the getValidationErrors() 
observable object--but I am looking for something that can integrate 
into the standard eclipse problem framework.


I need some design help for this. Any thoughts?  Should I just try to 
pretend that a file resource is equiv. to a data entry screen?