Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 315444 - API for IStyleProcessor changed in bug 313652
Summary: API for IStyleProcessor changed in bug 313652
Status: RESOLVED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: 2.6.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 2.6.1   Edit
Assignee: Birt-Chart-inbox@eclipse.org CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-02 14:23 EDT by Kathy Chan CLA
Modified: 2010-06-12 04:57 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 Kathy Chan CLA 2010-06-02 14:23:13 EDT 
Just want to confirm that the API change for IStyleProcessor as a result of bug 313652 is intentional or not?

TPTP started noticing the problem when we picked up BIRT RC2 this week.  This resulted in a TPTP build break which we need to react to (TPTP bug 315200 has the detail on the problem caused by this change).  In short, the BIRT class that changed API (checked in on 05/19 for RC2) was: 

org.eclipse.birt.chart.style.IStyleProcessor 

A few methods such as processStyle, defaultBgColor, setDefaultBackgroundColor and getDefaultBackgroudColor were introduced. 

Just want to confirm that this change in API is intentional and is going to stay.  Since this API change is very late in the Helios cycle (after M7), we would appreciate if API changes are required late in the cycle is announced in the Eclipes Cross Project distribution list.  Thanks!
Comment 1 Yulin Wang CLA 2010-06-02 21:57:26 EDT 
The change is going to stay.
Could you customize your style processor by extending BaseStyleProcessor in the same package, rather than implementing IStyleProcessor? New base class will minimize the interface change.
Comment 2 Yulin Wang CLA 2010-06-12 04:57:04 EDT 
Set wontfix since this is must-change and user has a workaround.