Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 348915 - [remoteservices] change async interface message
Summary: [remoteservices] change async interface message
Status: RESOLVED FIXED
Alias: None
Product: ECF
Classification: RT
Component: ecf.remoteservices (show other bugs)
Version: 3.5.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.5.2   Edit
Assignee: ecf.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-09 11:11 EDT by Scott Lewis CLA
Modified: 2011-06-13 06:21 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Lewis CLA 2011-06-09 11:11:55 EDT 
When no async interface is available, the remote service implementation presents a warning message...for example

> [log;+0100 2011.06.09
> 12:16:36:888;INFO;org.eclipse.ecf.remoteservice;org.eclipse.core.runtime.Status[plugin=org.eclipse.ecf.remoteservice;code=0;message=No
> async remote service interface found with name=com.example.foo.IFooAsync for
> proxy service class=com.example.foo.IFoo;severity2;exception=null;children=[]]]

This warning message should not be presented by default.

Originally reported via bug 348872.
Comment 1 Markus Kuppe CLA 2011-06-09 12:07:15 EDT 
Instead of removing it completely, I'd suggest to downgrade it to INFO and regard it as async advertisement for users that (yet) don't use it.
Comment 2 Scott Lewis CLA 2011-06-09 14:32:08 EDT 
Changing bug title to reflect comment 1.
Comment 3 Scott Lewis CLA 2011-06-09 17:52:58 EDT 
As per comment 1, changed status level to 'INFO' (from WARNING) and pushed to master.  Resolving as fixed.
Comment 4 Alex Blewitt CLA 2011-06-13 06:18:55 EDT 
ECF is way too noisy on its log messages. This really isn't going to help adoption; the problem is that it's printing anything at all which most people won't care about.

The bug was 'stop logging this message', not just 'reduce its priority'.
Comment 5 Alex Blewitt CLA 2011-06-13 06:21:46 EDT 
Added bug 349173 since I can't re-open this bug.