[
https://issues.jboss.org/browse/JBIDE-19982?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-19982:
---------------------------------------------
Adding a class or changing structure of a class has always required restarting a module so
that wouldn't be a new thing.
are you *sure* server restarting is required and not just restart the module ? (right
click and restart, also we should actually ask you to restart when changing/adding a class
automatically)
Wildfly doesn't pick up batchlet classes in debug mode
------------------------------------------------------
Key: JBIDE-19982
URL:
https://issues.jboss.org/browse/JBIDE-19982
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: batch, server
Affects Versions: 4.3.0.Beta1
Reporter: Alexey Kazakov
It seems that wildfly 8.2. (or JBT server adapter?) doesn't support hot deployment
for batch application.
See steps to reproduce.
If I change job.xml then it works fine. But if I add some new classes which are
referenced from the job xml file then it doesn't it.
I see both the modified jbo xml files and new class file in
wildfly-8.2.0.Final/standalone/deployments/jboss-batch-processing.war folder but server
restarting is still required.
This is probably an upstream issue but we need to investigate this case and maybe
document it somehow if this is an expecting behavior.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)