Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341411 - Move I/O classes to Java namespace
Summary: Move I/O classes to Java namespace
Status: CLOSED FIXED
Alias: None
Product: EMF
Classification: Modeling
Component: Core (show other bugs)
Version: 2.7.0   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: RC1   Edit
Assignee: Kenn Hussey CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-30 14:29 EDT by Kenn Hussey CLA
Modified: 2011-06-02 11:40 EDT (History)
1 user (show)

See Also:
Kenn.Hussey: indigo+

Attachments
proposed patch (41.04 KB, patch)
2011-03-30 16:15 EDT, Kenn Hussey CLA 		Kenn.Hussey: review?
Details | Diff
View All 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 Kenn Hussey CLA 2011-03-30 14:29:44 EDT 
The I/O classes in the GWT runtime should be moved to a Java namespace (i.e., java.io) to ease maintenance of multiple EMF runtimes and so that different implementations of the associated APIs (e.g., URIConverter, URIHandler) can be provided for multiple runtime platforms seamlessly (using the same API).

The idea here is to use package replacement so that a Javascript version of the classes is used on the client while the "standard" versions are used on the server. This is the same approach that GWT itself uses to emulate classes from the standard Java library.
Comment 1 Kenn Hussey CLA 2011-03-30 16:15:50 EDT 
Created attachment 192223 [details]
proposed patch

Here is a patch which refactors the I/O classes as suggested. Ed, please review when you get a chance.
Comment 2 Ed Merks CLA 2011-05-11 12:07:11 EDT 
This looks good to me.
Comment 3 Kenn Hussey CLA 2011-05-12 11:23:07 EDT 
The changes have been committed to CVS.
Comment 4 Ed Merks CLA 2011-06-02 11:40:20 EDT 
The fix is available in 3.7RC3 and later.