1. Hi!!

    I could deploy my SOAP WS war. But I can’t see the WSDL in JBoss EAP.

    When I go to Runtime -> Standalone Server -> Subsystems-> Web Services. I don’t have any endpoint

    1. Author

      Could you provide more information? How does your setup like? Is it a Spring Boot app with JBoss configuration?

  2. Hi,
    I’m trying to get some configuration per environment (qa, pre and production), but I do not know where I should make the changes so that they can be read from some .properties file outside the war.
    Do you have any idea?

    1. Author

      I guess you already use profiles and the part you’re missing is described here. You can choose what to do among those options, but I recommend you to pack the profiles’ application.properties within the war, and pass any “secret values” such as passwords by using environment variables (e.g. SERVER_PORT environment variable will override server.port in application.properties).

  3. Thanks for the “extends SpringBootServletInitializer” part. This helped me further.

  4. Hii,

    I followed ur post to deploy springBootApp to Jboss, but it giving error. My application is working fine with tomacat. but it giving error when trying to deploy JBOSS.
    The error as follows::Caused by: org.springframework.context.ApplicationContextException: Unable to start embedded container; nested exception is org.springframework.context.ApplicationContextException: Unable to start EmbeddedWebApplicationContext due to missing EmbeddedServletContainerFactory bean.

    Looking for your reply.

    1. Author

      Could you share your Application class? But it could be a JBoss configuration problem of the classpath, since it’s working fine with Tomcat (I guess not the embedded one).

    2. My application class is as below:
      import org.springframework.boot.SpringApplication;
      import org.springframework.boot.autoconfigure.SpringBootApplication;
      import org.springframework.boot.builder.SpringApplicationBuilder;
      import org.springframework.boot.context.web.SpringBootServletInitializer;

      public class Application extends SpringBootServletInitializer
      protected SpringApplicationBuilder configure(SpringApplicationBuilder application) {
      return application.sources(Application.class);

      public static void main(String[] args)
      SpringApplication.run(Application.class, args);

      When i deployed the application on Jboss 6.4, i am not getting above mentioned problem. but, my application is still not running. when i am trying to run “http://localhost:8080/greeting” not getting any output …

      Looking for ur reply

  5. Hello

    I followed your tutorial to deploy the Spring Boot App of mine to Jboss but it doesn’t work. My Spring Boot App works fine with embedded tomcat but when I try to deploy it to external Tomcat or Jboss as a .war it always give me HTTP Status 404 .

    With embedded tomcat this URL works: localhost:8080/employees but when I deploy to external Tomcat or Jboss none of the below URL works for me:

    Looking for your reply. Thanks in advance.

    1. Author

      Hi Ankit,
      Do you have your source code in GitHub so I can have a look? Actually that could be caused by many reasons…

  6. So I don’t know why, I did a re-fresh on the project and re-published the war on wildfly and now everything works! I guess there was something old cached somewhere.

    Thanks for the good tutorial. Took me a while to find something up to date and simple like this to get me going.

    1. Author

      Thanks for your comment George, I´m glad you found the solution!

  7. I started off with a default spring boot application with hello world example and added your modifications. It builds and the war file is produced and deployed on WildFly 9.x but the application spits out a “Not Found” error when accessing it (http://localhost:8080/demo/greeting/?name=george)

    I’m using STS 3.7.1 RELEASE with WildFly 9.x

    Any idea what could be causing this? I’m not supposed to have a web.xml correct?


This site uses Akismet to reduce spam. Learn how your comment data is processed.