class import issues in one module to another module in AEM 6.3

Are you getting log error messages? Can you post them please.

One thing in AEM 6.3 is this code by defaul will not work:

ResourceResolver resourceResolver = resolverFactory.getAdministrativeResourceResolver(null);

Another issue is you should rebuild your OSGi bundles using AEM UBER 6.3 JAR file.

Lakshmi,

   Can you share your error log as a file ? Still I have put some effort copying the above log and check for the issues, I do see a lot of issues in the code. Are you sure you have done all the primary check for moving code to 6.3 ?

Please see the below error line

Error 1

Error 2

Error 3

Error 4

          Please find my observations and recommendations

• Can you check the logs and see if you are using any deprecated items in your code.
• Will it be possible for you to change your JSP's to .html files?
• Can you create a fresh project using archetype 10 or 11 in Maven or using AEM Developer tool plugin in Eclipse and compare all the pom.xml and make sure you have all the attributes needed for your classes to get exported properly. If your bundle is active then either your classes are not exported properly for sling to refer them properly. You can click the bundle and check the exported packages section and see if your classes are exported properly

     PS:-  Migration from 6.0 to 6.3 won't be a plug and play even if you are able to build the bundle successfully. Just make sure to nail down the error logs and see if everything looks good.

Thanks Veena for the update.

not able to attach complete error.log file. Please let me know the steps to attach the file. and no we can't convert the jsps to html.

Thanks,

Lakshmi Raghava Reddy M.

Agree with Veene comments. You basically need to rebuild your components for 6.3 using the latest 6.3 UBER and development tools. Tyring to drop in stuff that worked in 6.1 into 6.3 does not always work. There are changes in Java lib versions, etc,