-
Notifications
You must be signed in to change notification settings - Fork 491
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
Spring plugin doesn't work on wildfly 12 #269
Comments
When using exploded deployments, I see following errors during the hotswap:
The class in error is a superclass of a spring Component class being hotswapped, and is located in the jar under WEB-INF/lib |
golovlyev
pushed a commit
to golovlyev/HotswapAgent
that referenced
this issue
Aug 27, 2019
…rojects#269 issue fix from the HotswapAgent.
golovlyev
pushed a commit
to golovlyev/HotswapAgent
that referenced
this issue
Aug 28, 2019
…rojects#269 issue fix from the HotswapAgent.
aekrylov
pushed a commit
to Micord/HotswapAgent
that referenced
this issue
Aug 28, 2019
* WEBBPMNEXT-6025 removed custom spring plugin fix. Copied the HotswapProjects#269 issue fix from the HotswapAgent.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using hotswap agent 1.3.0 with Spring plugin enabled for war packaged web app on Wildfly 12. The agent is attached via the command line (i.e.
-XXaltjvm=dcevm -javaagent:%JBOSS_HOME%\bin\webbpm-hotswap-agent.jar"
). Classes are reloaded through JPDA. Core hotswap features work just fine, though the Spring plugin doesn't refresh components.Spring is initialized through
WebAppInitializer
s, with component scan enabled with annotations in config classes. I tried managed war and exploded deployments as well as unmanaged exploded deployment, neither of which works.On the app startup, i see warnings like that in Wildfly logs:
Is there something else I should do to make the plugin work?
The text was updated successfully, but these errors were encountered: