Hi Nandika Since we have observed several issues with OpenJPA, we thought to replace it with EclipseLink. By doing that we can ship eclipselink since it's under eclipse license. Also we are making backend logic JPA compliance then we can use Hibernate as an option.
Note: since OpenJPA runtime enhancement doesn't work as expected currently both in SS and BPS, byte code enhancement done at build time, which means openjpa specific stuff added to entity classes at byte code level. Because of that we can't use same code base with eclipselink and Hibernate. But with EclipseLink and Hibernate run time enhancement happen properly, so same code base can be use with relevant libs. Currently we have done the R&D part and it's working fine. But if two projects use multiple libs for same purpose it won't be allowed. For that we (SS and BPS) need to come for an agreement that in future we will get rid of OpenJPA and replace with eclipselink (JPA and Hibernate complicance). So there should be at least red mine task for this in BPS side. SS team in a blocking state due to this. If BPS team can come to a conclusion regarding this it will be great help to continue work on SS road map. Cheers, Dhanuka *Dhanuka Ranasinghe* Senior Software Engineer WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 715381915
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
