AW: [geclipse-dev] New Plug-In/New Problem Reporting Mechanism

["Stuempert, Mathias IWR" <mathias.stuempert@xxxxxxxxxx>]

Hi Ariel,

Well spotted, thanks. Already changed in SVN according to your proposal.

Cheers, Mathias

-----Ursprüngliche Nachricht-----
Von: geclipse-dev-bounces@xxxxxxxxxxx [mailto:geclipse-dev-bounces@xxxxxxxxxxx] Im Auftrag von Ariel Garcia
Gesendet: Freitag, 11. Januar 2008 12:15
An: Developer mailing list
Betreff: Re: [geclipse-dev] New Plug-In/New Problem Reporting Mechanism

Hi Mathias, all,

i've came across a small issue with the new problem reporting API.

There are two methods
  ReportingService.getSolution( String solutionID, String description)
  ReportingService.getSolution( String description, ISolver solver)

whose "default" call would be
  getSolution( "someID", null )
     to fetch an already defined solution from the extension point, w/o
     overwriting the solution's default description
  getSolution( "theDescription", null )
     to programmatically create a new _pasive_ solution

The problem is that in any case the compiler will complain of being unable 
to know which of the two methods he is supposed to use.

Of course writing something like
   String description = null;
   getSolution( "someID", description );
avoids the error, but it is not nice to have to do that, that case will be 
the most common one...

Therefore one proposal would be to change the second method to
   createSolution( String description, ISolver solver)
This would also make more evident that we are here creating a new ISolution 
which is not defined in the extension point.

Exactly the same problem happens with 
  getProblem( String "s", null, null, PluginID );
where "s" could be either description or problemID...

Comments?

Cheers, Ariel
_______________________________________________
geclipse-dev mailing list
geclipse-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/geclipse-dev