This project provides a Reference Implementation for migrating existing Java EE applications from on-premise to cloud-based deployments, as well as migration to a microservices-based architecture.
The difference is not with regard to method or annotations in the code ... its openpa proprietary xml vs eclipselink proprietary ... you may also want to look at the help associated with those xml file warnings/errors as they may provide you with some hints on how to resolve these problems ... for instance, you may be able to use openjpa as an alternate jpa provider in jpa 2 and if so those proprietary annotations would be ok ...
btw to see the help in wamt select window => show view => other => help => help ... then whenever you click on one of the results in the eclipse "software analyzer results" tab you will see the help associated with that error in the help view ... if you then look at the help view and scroll down to the bottom of it you will see a "see also => detailed help" button. if you press on the "detailed help" button it will show you additional ideas on how to resolve that problem ... oft-times it shows several options for your consideration
The last error reported is about the JPA version used in our code. In the WebSphere Application Server V7.0 we are migrating our code from, we were using its Feature Pack for OSGI and JPA which comes with the JPA 2.0 version. In contrast, the WebSphere Application Server V9.0 which we want to migrate our code to uses JPA 2.1 where the provider has changed from being openJPA to eclipseLink. As a result, methods, annotations, etc are no longer valid or its behaviour has changed
Yes! The following is great!
Remember that our goal is to migrate our existing code/apps running on WebSphere Application Server V7.0 to run on a newer WebSphere Application Server version supported by WASaaS on Bluemix but with the minimum possible changes which is what the 'lift & shift' pattern consist of (modernization of your application, Java technologies wise, might be carried out on a later stage). Because of this, we can take advantage of the backwards compatibility on the JPA version and providers the new WebSphere Application Server V9.0 comes with and configure it to use JPA 2.0 so that we do not need to change anything in our app at all:
The difference is not with regard to method or annotations in the code ... its openpa proprietary xml vs eclipselink proprietary ... you may also want to look at the help associated with those xml file warnings/errors as they may provide you with some hints on how to resolve these problems ... for instance, you may be able to use openjpa as an alternate jpa provider in jpa 2 and if so those proprietary annotations would be ok ...
btw to see the help in wamt select window => show view => other => help => help ... then whenever you click on one of the results in the eclipse "software analyzer results" tab you will see the help associated with that error in the help view ... if you then look at the help view and scroll down to the bottom of it you will see a "see also => detailed help" button. if you press on the "detailed help" button it will show you additional ideas on how to resolve that problem ... oft-times it shows several options for your consideration
Yes! The following is great!