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

Bug 341411

Summary:

Move I/O classes to Java namespace

Product:

[Modeling] EMF

Reporter:

Kenn Hussey <Kenn.Hussey>

Component:

Core

Assignee:

Kenn Hussey <Kenn.Hussey>

Status:

CLOSED FIXED

QA Contact:

Severity:

enhancement

Priority:

CC:

Ed.Merks

Version:

2.7.0

Flags:

Kenn.Hussey: indigo+

Target Milestone:

RC1

Hardware:

OS:

Mac OS X - Carbon (unsup.)

Whiteboard:

Attachments:

Description	Flags
proposed patch	Kenn.Hussey: review?

Description Kenn Hussey

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

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

2011-05-11 12:07:11 EDT

This looks good to me.

Comment 3 Kenn Hussey

2011-05-12 11:23:07 EDT

The changes have been committed to CVS.

Comment 4 Ed Merks

2011-06-02 11:40:20 EDT

The fix is available in 3.7RC3 and later.