Unable to compile class for JSP: An error occurred at line: 6 in the generated java file Only a type can be imported. | Community
Skip to main content
suvasishm
suvasishm
New Participant
June 13, 2016
Solved

Unable to compile class for JSP: An error occurred at line: 6 in the generated java file Only a type can be imported.

  • June 13, 2016
  • 13 replies
  • 10146 views

Problem:

On Author http://<host:port>/projects.html getting the following error after AEM 6.1 SP1 installation:

Unable to compile class for JSP: An error occurred at line: 6 in the generated java file Only a type can be imported. com.adobe.cq.experiencelog.ExperienceLogConfig resolves to a package An error occurred at line: 24 in the jsp file: /libs/cq/experiencelog/components/head/head.jsp ExperienceLogConfig cannot be resolved to a type
 

On Publish http://<host:port>/content/geometrixx-outdoors/en.html getting the following error after SP1 installation:
Unable to compile class for JSP: An error occurred at line: 6 in the generated java file Only a type can be imported. com.adobe.granite.contexthub.api.ContextHub resolves to a package An error occurred at line: 54 in the jsp file: /libs/granite/contexthub/components/contexthub/contexthub.jsp ContextHub cannot be resolved to a type

Pretty much similar errors. Need help fixing the problem.

Observation while debugging:

a) On both the environments Adobe Granite ContextHub Commons(com.adobe.granite.contexthub.commons) and Adobe CQ Experience Log Client Bundlecom.adobe.cq.cq-experiencelog bundles are in "installed" state. 

In fact on author, Bundle information: 455 bundles in total, 418 bundles active, 8 active fragments, 29 bundles installed 

and on publish Bundle information: 451 bundles in total, 415 bundles active, 8 active fragments, 28 bundles installed. 

So a large number of bundles are in "installed" state.

b) In the log:

13.06.2016 06:35:38.310 *ERROR* [qtp1771211259-95655] org.apache.felix.http.jetty %bundles.pluginTitle: Cannot start (org.osgi.framework.BundleException: Unresolved constraint in bundle com.adobe.cq.cq-experiencelog [459]: Unable to resolve 459.0: missing requirement [459.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.experiencelog)(version>=1.0.0)(!(version>=2.0.0))))
org.osgi.framework.BundleException: Unresolved constraint in bundle com.adobe.cq.cq-experiencelog [459]: Unable to resolve 459.0: missing requirement [459.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.experiencelog)(version>=1.0.0)(!(version>=2.0.0)))


Please suggest solution to fix the problem.

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 suvasishm

Steps that fixed the issue for me courtesy Daycare support.

1. Stopped Region Digraph (org.eclipse.equinox.region) bundle. Not used in 6.1.

2. Restart the instance

3. Clear the compiled classes using http://<host>:<port>/system/console/slingjsp

13 replies

Show previous replies
Peter_Puzanovs
Peter_Puzanovs
New Participant
June 14, 2016

Try going into: http://{ip}:{port}/system/console/bundles

Search for Adobe CQ Experience Log Client Bundle com.adobe.cq.cq-experiencelog

Would assume it is in the Stopped state, try pressing on the start button.

At the same time look through the error.log, do you see any problems there?

 

Regards,

Peter

suvasishm
suvasishmAuthor
New Participant
June 14, 2016

Tried with several restart. Same result. As many as 28 or 29 bundles remaining in "installed" state.

smacdonald2008
smacdonald2008
New Participant
June 13, 2016

If your bundles are not in an active state - there is a bigger issue.  Try restarting AEM to see if the bundles become active. 

Terms & ConditionsAccessibility statement

Loading footer...