I'm having an issue when I deploy a spring boot application in weblogic 12.2.1 through Eclipse Neon. This are the components
The error is:
weblogic.management.DeploymentException: java.lang.ClassNotFoundException: org.springframework.security.oauth2.client.token.AccessTokenRequest
at weblogic.application.internal.BaseDeployment.throwAppException(BaseDeployment.java:132)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:246)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:66)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:158)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:65)
Truncated. see log file for complete stacktrace
But I'm not using security in the application. If I run it as "Spring Boot App" the application runs.
I guess the problem is with weblogic, how can I solve it?
For anybody else hitting this, it appears this is a bug in Spring Boot (spring-boot-autoconfigure) induced by the Oracle WebLogic team's pesky adherence to the EE spec. See here for more info: https://github.com/spring-projects/spring-boot/issues/9441
The 1.5.5.RELEASE version of Spring Boot has this fixed. So if you're using gradle for example, changing your dependency as follows (and any other Spring Boot dependencies you have) should fix it:
compile "org.springframework.boot:spring-boot-autoconfigure:1.5.5.RELEASE"
I've just confirmed this works for me after getting the same problem.
Another guy here forced to deploy to weblogic :\
This is what I've done in order to fix the integration issue beetween weblogic, eclipse and spring-boot:
```
<dependency>
<groupId>org.springframework.security.oauth</groupId>
<artifactId>spring-security-oauth2</artifactId>
</dependency>
```
But after that, weblogic asked my user and password for every rest endpoint (not actuator ones)
So, here comes the second point:
```
@EnableAutoConfiguration(exclude = { org.springframework.boot.autoconfigure.security.SecurityAutoConfiguration.class
})
``` Hope it helps!
For me this exception disappeared when deployed the war file using the WebLogic console. Seems to be a bug in Eclipse-WebLogic integration.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With