Merging JavaImplementationDefinition and JavaImplementation

[Jean-Sebastien Delfino <js...@apache.org>]

JavaImplementationDefinition currently extends JavaImplementationImpl 
and augments it with pointers to Java members and other useful info to 
have in the Java component implementation model.

Some of the runtime code currently depends on that implementation class 
and this is preventing me to use that code in the core-spring module, 
which I'm trying to use to validate the model changes I'm working on 
without having to change our whole runtime.

I don't think it's healthy to have the runtime code depend on such an 
implementation class, so I'm going to do the following:
- declare the public aspects of JavaImplementationDefinition in the 
JavaImplementation interface
- move its implementation to JavaImplementationImpl
- port the test cases and runtime code that currently depend on 
JavaImplementationDefinition to use the JavaImplementation interface.

It's going to take me a little bit of time to adjust the test cases, but 
I'm planning of having this done before the end of the day.

-- 
Jean-Sebastien


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org