Run as Spring Boot App failed in eclipse

Camunda 7 Topics Discussion & Questions
1

I am trying to create a spring boot camunda application. I am able to compile, but when i ran i am getting the class not found exception.

springbootmavenarchetype
springbootmavenarchetype960×540 5.62 KB
pom.xml (6.3 KB)

Caused by: java.io.FileNotFoundException: class path resource [org/springframework/web/servlet/config/annotation/WebMvcConfigurerAdapter.class] cannot be opened because it does not exist
at org.springframework.core.io.ClassPathResource.getInputStream(ClassPathResource.java:172) ~[spring-core-4.3.11.RELEASE.jar:4.3.11.RELEASE]
at org.springframework.core.type.classreading.SimpleMetadataReader.(SimpleMetadataReader.java:50) ~[spring-core-4.3.11.RELEASE.jar:4.3.11.RELEASE]
at org.springframework.core.type.classreading.SimpleMetadataReaderFactory.getMetadataReader(SimpleMetadataReaderFactory.java:98) ~[spring-core-4.3.11.RELEASE.jar:4.3.11.RELEASE]
at org.springframework.boot.type.classreading.ConcurrentReferenceCachingMetadataReaderFactory.createMetadataReader(ConcurrentReferenceCachingMetadataReaderFactory.java:89) ~[spring-boot-1.5.7.RELEASE.jar:1.5.7.RELEASE]
at org.springframework.boot.type.classreading.ConcurrentReferenceCachingMetadataReaderFactory.getMetadataReader(ConcurrentReferenceCachingMetadataReaderFactory.java:76) ~[spring-boot-1.5.7.RELEASE.jar:1.5.7.RELEASE]
at org.springframework.core.type.classreading.SimpleMetadataReaderFactory.getMetadataReader(SimpleMetadataReaderFactory.java:93) ~[spring-core-4.3.11.RELEASE.jar:4.3.11.RELEASE]
at org.springframework.context.annotation.ConfigurationClassParser.asSourceClass(ConfigurationClassParser.java:693) ~[spring-context-4.3.11.RELEASE.jar:4.3.11.RELEASE]
at org.springframework.context.annotation.ConfigurationClassParser$SourceClass.getSuperClass(ConfigurationClassParser.java:857) ~[spring-context-4.3.11.RELEASE.jar:4.3.11.RELEASE]
at org.springframework.context.annotation.ConfigurationClassParser.doProcessConfigurationClass(ConfigurationClassParser.java:328) ~[spring-context-4.3.11.RELEASE.jar:4.3.11.RELEASE]
at org.springframework.context.annotation.ConfigurationClassParser.processConfigurationClass(ConfigurationClassParser.java:245) ~[spring-context-4.3.11.RELEASE.jar:4.3.11.RELEASE]
at org.springframework.context.annotation.ConfigurationClassParser.processImports(ConfigurationClassParser.java:606) ~[spring-context-4.3.11.RELEASE.jar:4.3.11.RELEASE]
… 15 common frames omitted

2

Do you build camunda-spring-boot from github sources or do you use a certain version dependency?

3

I configured eclipse with remote camunda catalog for downloading archetypes.

https://app.camunda.com/nexus/content/repositories/camunda-bpm/.

Please do let me know if you need more info.

4

I never worked with the archetypes, so I would if possible have to see the code (maybe you can provide a minimal failing example on github) or the exact version of starter, camunda, spring , archetype and java you are using to reproduce.

5

I sent you the screen shot of archetype of starter.

Windows 10 Pro 64 bit.
Eclipse Oxygen 64 Bit
Java 1.8.171 64 bit.

6

In your screenshot it looks like you are trying to use 7.8.2.
This would mean you are trying to use the enterprise version of camunda.
Have you configured your maven correctly so that it has access to the private repositories for the EE?

https://docs.camunda.org/get-started/apache-maven/#enterprise-edition-1

7

I am pulling it from nexus as i configured remote catalog in eclipse. I thought 7.8.2 was the latest version shown in archetype.

8

You are right, you were referring to the Archetype Version not Camunda BPM dependencies.

Have you changed anything in the pom.xml after creating the project using the maven archetype?
Is Eclipse showing any errors?
Can you verify that all dependencies have been downloaded successfully?

9

I am able to compile code sucessfully, there are no errors. build was successful. It downloaded all the dependencies from pom.xml, i did not make a change in pom.xml

Only problem is that when i run the application as Spring Boot application, it throws an error.

10