javax.persistence -- Cannot be resolved | Community
Skip to main content
New Participant
August 15, 2017
Solved

javax.persistence -- Cannot be resolved

  • August 15, 2017
  • 4 replies
  • 4040 views

There are unresolved issues

"javax.persistence -- Cannot be resolved

org.apache.commons.beanutils,version=[1.9,2) -- Cannot be resolved

org.hibernate -- Cannot be resolved

org.hibernate.cfg -- Cannot be resolved

org.hibernate.classic -- Cannot be resolved

org.hibernate.dialect -- Cannot be resolved

org.hibernate.dialect.function -- Cannot be resolved

org.hibernate.transform -- Cannot be resolved

"

when trying to do mvn install in 6.3. can anyone help to resolve these issues? Thanks, in-advance.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by smacdonald2008

Use AEM Dependency Finder to see if AEM has dependencies for OSGi bundles. For this package - there is no OSGi bunlde exporting this Java package:

http://localhost:4502/system/console/depfinder

See

4 replies

smacdonald2008
smacdonald2008Accepted solution
New Participant
August 15, 2017

Use AEM Dependency Finder to see if AEM has dependencies for OSGi bundles. For this package - there is no OSGi bunlde exporting this Java package:

http://localhost:4502/system/console/depfinder

See

New Participant
August 15, 2017

I accept for HIBERNATE dependencies but is it same for "javax.persistence" too

smacdonald2008
New Participant
August 15, 2017

Look at how we place the simple JSON JAR into an OSGi bundle by using the Eclipse plug-in project here: Scott's Digital Community: Submitting Adobe Experience Manager form data to custom Sling Servlets

smacdonald2008
New Participant
August 15, 2017

This looks like you are using APIs from Hibernate, etc that are not part of the Experience Manager OSGi service container. You need to get these Java APIs into an OSGi bundle and deploy the bundle to AEM.

One way you can do that is to wrap them into an Eclipse plug-in project.