Unable to validate node types since project ... is not associated with a server or the server is not started. | Community
Skip to main content
A
alexr21
New Participant
February 3, 2018
Solved

Unable to validate node types since project ... is not associated with a server or the server is not started.

  • February 3, 2018
  • 16 replies
  • 4177 views

I am getting this error which is described in one of the AEM tutorials

Getting Started with AEM Sites Part 2 - Creating a Base Page and Template

Unfortunately, the suggested fix does not work:

  • First issue is, Eclipse does not allow removing Dynamic Web Module through the UI.

  • Second issue is, if you forcibly remove it by editing /ui.apps/.settings/org.eclipse.wst.common.project.facet.core.xml, the actual problem is still not solved.

Any other ideas?

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 alexr21

The problem appears to be gone after the following updates are applied. The archetype has a lot of outdated references:

  • maven-sling-plugin 2.2.0 -> 2.3.4
  • htl-maven-plugin 1.0.6 -> 1.1.2
  • maven-bundle-plugin 3.3.0 -> 3.5.0
  • Do not upgrade: content-package-maven-plugin - stay on 0.5.1, because 1.0.2 causes other problems
  • Eclipse Sling IDE Tools 1.1.0 -> 1.2.0
  • Eclipse Neon.3 vs Oxygen doesn't seem to matter

16 replies

Daniel_Gordon
Daniel_Gordon
Employee
February 13, 2018

Thanks alexr2​!

A
alexr21Author
New Participant
February 9, 2018

hi dgordon86​, we were experiencing this issue in our own project and updating the dependencies fixed it. The project was created by a colleague using the Maven aem-project-archetype version 12.

Here's the top-level pom.xml, the version which works fine: [XML] <?xml version="1.0" encoding="UTF-8"?> <!-- | Copyright 2015 Adobe Systems I - Pastebin.com

Daniel_Gordon
Daniel_Gordon
Employee
February 9, 2018

alexr2​ to clarify, did updating those dependencies in WKND pom.xml fix the issue? Or were you experiencing this issue in your own project and updating those dependencies fixed it? You mention "the archetype has a lot outdated references" is that when creating a project using Lazybones or the using the Maven aem-project-archetype? Do you mind posting the relevant pom.xmls? Thanks!

smacdonald2008
smacdonald2008
New Participant
February 8, 2018

Thanks for posting this - i have asked the author of this doc to look at making possible updates based on your post.

A
alexr21AuthorAccepted solution
New Participant
February 8, 2018

The problem appears to be gone after the following updates are applied. The archetype has a lot of outdated references:

  • maven-sling-plugin 2.2.0 -> 2.3.4
  • htl-maven-plugin 1.0.6 -> 1.1.2
  • maven-bundle-plugin 3.3.0 -> 3.5.0
  • Do not upgrade: content-package-maven-plugin - stay on 0.5.1, because 1.0.2 causes other problems
  • Eclipse Sling IDE Tools 1.1.0 -> 1.2.0
  • Eclipse Neon.3 vs Oxygen doesn't seem to matter
smacdonald2008
smacdonald2008
New Participant
February 6, 2018

Setup the project - as described in the Lazybone article.

Then switch to AEM Perspective. THen you can click on a location in the JCR and add a new node:

I created a new node of type nt:folder

When i run Maven from Eclipse - the node is imported into AEM,

Try to re-install the AEM DEV tool in Neon eclipse. It works.

A
alexr21Author
New Participant
February 5, 2018

I verified the content sync points to src/main/content/jcr_root and org.eclipse.wst.common.project.facet.core.xml contains the same entries (except my Java version = 1.8).

A
alexr21Author
New Participant
February 5, 2018

Ratna Kumar​ thank you for your comments however please note the problem that I'm having is not with creating the project and deploying it, the issue specifically is inability to use "Create Node" within Eclipse. This is a developer productivity issue affecting our entire team, as it forces us to go into CRX/DE to create nodes and then import them back into Eclipse. The error is in our real project, but it's the same as shown in the tutorial.

A
alexr21Author
New Participant
February 5, 2018

smacdonald2008​, thank you for your comment regarding "successfully deploy using Eclipse NEON and the LazyBone", unfortunately this is not the key issue for me. I want to be able to create JCR Nodes in Eclipse. The error occurs when you context-click on a folder within Eclipse and attempt to create a JCR Node, exactly as described in the tutorial, except that the solution from the tutorial does not work.

A
alexr21Author
New Participant
February 5, 2018

I am using Neon.3

Show more replies
Terms & ConditionsAccessibility statement

Loading footer...