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

Bug 564986

Summary: [Passage] API revision | conditions | transport | xml
Product: [Technology] Passage Reporter: Elena Parovyshnaia <elena.parovyshnaya>
Component: APIAssignee: Elena Parovyshnaia <elena.parovyshnaya>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: 0.9.0   
Target Milestone: 1.0.0   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on:    
Bug Blocks: 564326    

Description Elena Parovyshnaia CLA 2020-07-06 13:48:26 EDT 
Current condistion transport for XML content type writes and read emf model XMI file. 

New interfaces for licensing conditions are not implanted into the model, thus only `read` part is implementd for `XmiConditionTransport` regitered for xml content type. 

Finc a way to implement writing to obsolete models as well. As new interfaces are equivalent to the asolete ones in ragards of actual data, this should be somehow feasible.
Comment 1 Elena Parovyshnaia CLA 2020-07-07 02:42:01 EDT 
It appeared on deeper analysis, that Transport actually do reading and writing in a severily different contexts:
  - we read conditions from existing license-like sources and are interested only in product usage demands
  - and we write conditions only on an emitted license persistence in the context of a license owning user and all the rest of stuff runtime is unaware of.

The decision has been taken to reduce 1.0 `ConditionTransport` interface to read functionality only and redesign writing part when it comes to  license writing.
Comment 2 Elena Parovyshnaia CLA 2020-07-07 03:17:26 EDT 
PR: https://github.com/eclipse-passage/passage/pull/291
Comment 3 Elena Parovyshnaia CLA 2020-07-07 03:56:01 EDT 
`ConditionTransport` in general has been cut to supplying reading facilities only.