Friday, 15 July 2011

java - Exclude certain WebApplicationInitializers in CloudFoundry WAR deploy -


This is a typical version of the question and a general version; I will ask it in both ways

Specific Questions

We have a traditional spring web application that integrates with Apache camel, which we have on cloud foundry Are pushing. It depends on a custom library that pulls in spring-cloud-security (and therefore, spring-boot-autoconfigure , among others) deployed on Cloud Foundry When doing, Java Autoreconfiguration WebApplicationInitializer s looks on the classpath and the search for which is the JerseyAutoConfiguration . When it specifically calls WebApplicationInitializer , we get annotation parsing errors, is there any way to leave it? @EnableAutoConfiguration (exit = ...) does not work because it is not happening automatically during the configuration phase. Java Autoreconfigure code (included through Java buildpack) to avoid implementing some WebApplicationInitializer

FAQ

Is there no way to tell by web.xml or any other feature? s?

If you deploy the app as executable instead of a war then there is no scanning WebApplicationInitializers (This is a spring thing, a buildpack does not matter).


No comments:

Post a Comment