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

Bug 352881

Summary:	Make create operation streamable
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
Target Milestone:	1.5 M1
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:
Bug Depends on:
Bug Blocks:	311355

Description Holger Staudacher

2011-07-22 11:17:25 EDT

Currently the new method on the IClientObject creates a "create" operation. The create operation has a properties map. 

When you want to pass properties you have to create a map on the server side and pass this map to the IClientObject#new method. It would be much better to have something like this:

IClientObject obj = ...
obj.new( styles );
obj.setProperty....
obj.setProperty...

From a message point of view this should not create a "create" and "set" operation. This should create just a "create" operation and it should append the properties to the "create" operation's properties map. So, I think we should make the create operation streamable in the ProtocolMessageWriter.

Comment 1 Tim Buschtoens

2011-07-26 05:52:31 EDT

The client Protocol Processor now processes the "create" operation additinally as an "set" operation, supporting this feature.

Comment 2 Ralf Sternberg

2011-08-05 10:09:10 EDT

After some consideration, we decided to remove the properties parameter from IClientObject#create(). Properties are now set using IClientObject#setProperty(). Properties are appended to a preceding create operation.
Changes are in CVS HEAD.