-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please add HowTo configure wicket-spring-boot with Standalone Tomcat to documentation #115
Comments
|
Well, first of all I thought that I'm not using "pure" Spring Boot application, but Wicket one, so I started carefully looking for the information on your page. Then I was googling around for "spring boot standalone tomcat", but everything suggested extending
"Modify your Application entry-point class" (which occured to be not true... And point 1. is also not required - works fine for me without changint it). Because my Application class was already extending |
have you changed anything? |
Sorry I thought that you've already provided the solution... |
I don't know how to help here. Maybe it helps to point you to my code (which is mostly working). |
I already found the solution while I was creating this request. |
Ah ok, sorry... I've missunterstood this request. I may also add a working example in the example repository. |
Great ideal! |
You don't have to extend SpringBootServletInitializer. See the simple-war example. You only have to mark the spring-boot-starter-tomcat as provided. Only if you want to configure specific behaviour - see simple-war-websocket. |
I'm affraid you are wrong. I tried it with
it started to work - this was the only change between working and not working solution. And you can also put:
for the (a little bit) more secure app |
Hmm, but I could run it without extending SpringBootServletInitializer. See https://github.com/MarcGiffing/wicket-spring-boot-examples/tree/master/simple-war[simple-war]. Maybe you should provide a pull request for the documentation which I can take :) |
Running the app works fine indeed, but if you create |
That would be great. You can also update the Readme accordingly. Yes you can add a standalone SpringBootServletInitializer. Thanks! |
I have similar issue. My app is extended WicketBootSecuredWebApplication and has @SpringBootApplication on it. if I remove @SpringBootApplication annotation from MyApplication I am getting If I put @SpringBootApplication annotation on both of them I am getting multiple endpoints If I leave @SpringBootApplication annotation only on WarInitializer I am getting this How did you make it work with both WicketBootSecuredWebApplication and in tomcat. |
I have standalone Tomcat and I wanted to deploy created war with wicket-spring-boot on it.
After hours of struggling I finally found this example and basicaly I ended up with:
WicketApplication.class
and that's it....
The text was updated successfully, but these errors were encountered: