Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 351947

Summary:	Make Protocol API public
Product:	[RT] RAP	Reporter:	Holger Staudacher <holger.staudacher>
Component:	RWT	Assignee:	Project Inbox <rap-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	tbuschto
Version:	1.5	Keywords:	api
Target Milestone:	2.0
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:	351948
Bug Blocks:	311355

Description Holger Staudacher

2011-07-13 07:09:25 EDT

Before we can call the protocol implementation finished we need to move the Protocol API to a public package.

Comment 1 Tim Buschtoens

2011-07-13 08:00:33 EDT

I would wait with this until we use the protocol at least for a few widgets. There's a chance (though unlikely) we might have to change something.

Comment 2 Holger Staudacher

2011-07-13 08:26:09 EDT

I would even go further. I think this should be the last task to fix before we can mark bug 311355 as fixed.

Comment 3 Holger Staudacher

2012-02-21 05:49:32 EST

As all widgets are converted to use the protocol, I think we can make the API public because it disturbs Custom Widget Developer a lot when using the API which is still internal. Also I think bug 311355 can be closed.

Comment 4 Ralf Sternberg

2012-02-21 10:26:06 EST

Agree for IClientObject.
Disagree with the methods currently available on the ClientObjectFactory. At least the methods getForDisplay() and getForGC() should not be public, getForWidget() could be encapsulated by WidgetLCAUtil. Tim came up with the idea to provide only one method getForObject(), which I like a lot.

I'd also suggest a central object id provider to replace the widget id generator.

Comment 5 Ralf Sternberg

2012-04-30 11:50:17 EDT

Holger and me made good progress on ClientObjectFactory, ClientObjectAdapter, etc.
However, since we're long past the API freeze, and don't have much time left to make any corrections, we should keep this API internal for 1.5.

Comment 6 Ralf Sternberg

2013-03-07 09:22:17 EST

The Remote API has been introduced in RAP 2.0. See package org.eclipse.rap.rwt.remote.