On Tue, Apr 21, 2009 at 11:39 PM, Ramkumar R <[email protected]> wrote: >> >> This would be ok for now, but the proper fix would be to have pojo >> related interfaces available in a separated module that could be >> exported via OSGi and used by all pojo related extensions (e.g java, >> ejb, spring). I have started doing that in implementation.pojo, but >> that still need some more work, and then migrate the related >> extensions to use it. > > Hi Luciano, > > That seems to be a good idea, as you said that would also benefit the jee > modules which also needs the java introspecting techniques. > > If you wish, I can go ahead and create a seperate module as you have > suggested. > As I am currently working in 2.x, there should not be any issue in taking > this up. >
I finally found the work I have initiated for implementation-pojo at [1]. I'd probably recommend renaming the module to something like core-pojo to avoid confusion with implementation-pojo sample that we have in 1.x. Note that the current changes I had to the pojo based extensions to use implementation-pojo is available as a patch in TUSCANY-2988 and you might need to review and complete it before applying these changes to avoid any breakage. [1] https://svn.apache.org/repos/asf/tuscany/java/sca-contrib/modules/implementation-pojo/ [2] https://issues.apache.org/jira/browse/TUSCANY-2988 -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/
