exception: org.apache.sling.ide.transport.RepositoryException - javax.jcr.RepositoryException: Bad Request]

rockie-rocafort

22-01-2019

Hello. I was able to start a server in my aem instance but when I verified if I update something in eclipse, if it will also be updated in crxde.. I've encountered this error:

1673550_pastedImage_0.png

Any help on how I can resolve this?

Thanks,

Rockie

Accepted Solutions (1)

Accepted Solutions (1)

Gaurav-Behl

MVP

23-01-2019

Follow these articles step by step -

AEM Developer Tools for Eclipse

  • Download and install Eclipse IDE for Java EE Developers. We currently support Eclipse Kepler or newer
  • We support AEM version 5.6.1 or newer
  • Configure your eclipse installation to ensure that you have at least 1 Giga bytes of Heap memory by editing your eclipse.ini configuration file as described in the Eclipse FAQ.

troubleshooting-

Apache Sling :: Sling IDE tooling for Eclipse User Guide

enable tracing to check logs

To do so, open the Eclipse preferences and navigate to General -> Tracing. Make sure that 'Enable tracing' is checked and all options under 'Sling IDE Tooling' are enabled.

How do I fix the error "Missing m2e incremental build support for generating the bundle manifest, co...

For further information on how to fix and configure the according maven plugins look at Incremental Builds in Sling IDE tooling for Eclipse.

Answers (8)

Answers (8)

rockie-rocafort

24-01-2019

Hello, I was able to make it work by using Eclipse IDE version 2018-09 M2 (4.9.0M2). I just did a simple import of my projects, Maven update, then clean install. I've tried adding a sample jsp file to my CRXDE and I was able to get it on Eclipse IDE by just selecting import to server. But when I make changes from Eclipse IDE, CRXDE doesn't update even I export it to server. The same error still displays...

rockie-rocafort

23-01-2019

I was able to check the Sling IDE tooling version and it's on 1.0.4 version. How can I change this to 1.0.2 so it will be compatible with my AEM 6.4? Is this the main reason of the error I'm encountering? Furthermore, I was also able to access the Eclipse Marketplace and install a plugin successfully.

As per checking with my network team, there's no corporate proxy or laptop's firewall. But I will try to set it up on a different machine and a different network by using a wifi or a vpn. I'll use Version: 2018-09 (4.9.0) for this. I'll update you afterwards.

Thank you,

Rockie

Gaurav-Behl

MVP

23-01-2019

If you search for 'org.apache.sling.tooling.support.install' or Apache Sling Tooling Support Install under /system/console/bundles, you should see the version

AEM 6.4 has sling tooling version 1.0.2  The reason behind it is that your sling tooling support version must match the AEM developer tool version otherwise it would not work.

Possible reasons for it to fail are mentioned in the last screenshot that you shared - m2e incremental support and other dependencies. Could you set it up on some other network and see if it works? It seems that there are restrictions on your corporate proxy (same pattern in the other tickets raised by you). Are you able to access Eclipse marketplace and install any plugin on this same network? If not, then your corporate proxy/windows firewall has restrictions in-place to block the downloads.

If you are able to make it work for /apps or for /content but not for /core then it becomes an issue with core bundle's pom.xml which can be fixed easily. The exception is probably because outgoing calls from eclipse are blocked by either firewall/proxy of your network.

Couple of approaches to proceed further -

1) Identify that corporate proxy or your laptop's firewall is the root cause. Open a ticket with your network team to find a solution

2) Try the setup on a different network (may be guest network or home network) where you've less restrictions.

3) Setup the eclipse installation on a different machine/different network and then port the eclipse/bundles including .m2 and .eclipse folders on this machine. It should be one time effort.

I'll check with your eclipse version 2018-12 (4.10.0) to see if I can reproduce the error.

Revert with your findings.

P.S.  I've same setup 1.0.2 that works on local AEM 6.4 without any issues. My configurations are

  • Eclipse Java EE IDE for Web Developers.
  • Version: 2018-09 (4.9.0)
  • Build id: 20180917-1800

rockie-rocafort

22-01-2019

AEM developer tool version: 1.2.0

Eclipse Version: 2018-12 (4.10.0)

Sling IDE tooling version: *how to check this one?

AEM Version: 6.4

Screenshot of AEM server configurations from eclipse:

1674138_pastedImage_7.png

Error trace when you click on Details button, right next to the OK button:

1674139_pastedImage_8.png

Steps that you performed to import/export the content

     Since this came from a different team, I was just given a zip file. What I did was just to extract the contents and import it in eclipse using "Existing Maven Projects" option.  I've encountered several errors during my import. You can check this thread for the history of errors I've encountered: For artifact {com.adobe.aem:uber-jar:null:jar}: The version cannot be empty. I've just added some additional dependencies in my parent pom.xml file then added the jars manually. I managed to fix the errors then encountered this: Project build error: Unresolveable build extension but was able to fix it again. I've added an AEM server and just updated the port. It started successfully with "Synchronized" tag indicated beside the content module. But as I was trying to update a jsp file in eclipse.. I encountered the said error. Btw, there was also no stack trace being printed in my eclipse console.

Furthermore, there are some errors in my eclipse problems tab:

1674239_pastedImage_13.png

smacdonald2008

22-01-2019

Please follow the WEEKEND tutorial and make sure that all software lines up with the version mentioned in the doc - Getting Started with AEM Sites - WKND Tutorial

As @gauravb10066713 mentions - looks like you may be using incompatible versions.

Gaurav-Behl

MVP

22-01-2019

could you share the following:

  • AEM developer tool version
  • eclipse version
  • sling IDE tooling version -- //check /system/console/bundles and find the jar version
  • AEM version
  • screenshot of AEM server configurations from eclipse
  • error trace when you click on Details button, right next to the OK button
  • steps that you performed to import/export the content