Forum Discussion
CWalker
Occasional Contributor
Hi Rao,
I think this is a libraries problem, that the WAR is relying on some JARs available in Tomcat that aren't available or accessible in WildFly. web.xml is standard across all Java EE Servlet Containers, so a WAR ought to be portable.
I'm coding the mocks with Resteasy instead of exporting Virts and deploying to WildFly.
Thanks for responding,
Carl
nmrao
8 years agoChampion Level 3
May be I was wrong on that web.xml thing. Certainly you are true that it can be related to libraries. What if you include those libraries into war and retry deploying? I know it is trial and error and could be time taking. But once you know what is needed, then probably you could create script to make to changes to work with wildfly automatically deployable war.
Related Content
- 6 years agoenkeleda2006
- 8 years agoframe2
- 9 months agoLuukdb