redhat-developer / redhat-developer/vscode-server-connector
servlet only works when deployed manually
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 59
- Forks
- 29
- Avg merge
- 19m
- Merged PRs (30d)
- 1
Description
I'm having an issue deploying a Spring servlet.
When I run mvn clean package and deploy the .war file manually on Wildfly10.x on VSCode on Windows, it works and I can access the application via localhost:8081/appURL. Then, under /deployment=myApp.war/subsystem=undertow/servlet=spring I can see my Servlet Class. I also get /deployment=myApp.war:
- Content: {"hash" => undefined}
- Owner:
- Persistent: true
However, when I add a exploded deployment from inside Red Hat Server Connector, I get a registered web context, but the application is not accessible. Then, I can't see my Servlet class, nothing under /deployment=myApp.war/subsystem=undertow. I get on /deployment=myApp.war:
- Content: {"archive" => false,"path" => "deployments\myApp.war","relative-to" => "jboss.server.base.dir"}
- Owner: ("subsystem" => "deployment-scanner") ("scanner" => "default")
- Persistent: false
On both situations I have a working and tested datasource running configured via standalone.xml
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the manually deployed WAR with the exploded deployment created through Red Hat Server Connector, using the reported WildFly deployment and Undertow states as the starting point. Reproduce the deployment on Windows with the stated VS Code and WildFly setup, then inspect the connector's deployment behavior and logs. Done means the exploded deployment registers the Spring servlet and serves the application like the manually deployed WAR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100