[
https://issues.jboss.org/browse/WFLY-4402?page=com.atlassian.jira.plugin....
]
Abhijit Sarkar commented on WFLY-4402:
--------------------------------------
[~swd847] There appears to be a not-so-obvious disconnect between what we're doing.
Just humor me and please try the following steps exactly as laid out.
# Download 8.2.0.Final if you don't already have it.
# Start it with `standalone.sh`.
# Log into the management console (requires creating an admin user but you already know
that).
# Starting from "create deployment", upload the war file attached. Change the
runtime name and check the enable box. Before you hit the save button, the screen should
look like the attached screenshot (if I can attach it, not sure, as the ticket has been
closed).
# Look at the console for errors.
Fails to load JAX-RS Application class if deployment runtime name is
changed
----------------------------------------------------------------------------
Key: WFLY-4402
URL:
https://issues.jboss.org/browse/WFLY-4402
Project: WildFly
Issue Type: Bug
Components: Class Loading
Affects Versions: 8.2.0.Final
Environment: Oracle JDK 1.8.0_25
Reporter: Abhijit Sarkar
Assignee: David Lloyd
Priority: Critical
Attachments: availability-service-0.0.1-SNAPSHOT.war
If the runtime name is modified during deployment, it fails with a
{{ClassNotFoundException}}. The runtime name determines the context root so in most
practical cases, it'd be different from the archive name. Seems related to WFLY-1521
which was closed.
{code}
wildfly-server-8.2.0.Final.jar:8.2.0.Final]
... 5 more
Caused by: java.lang.ClassNotFoundException:
name.abhijitsarkar.microservices.availability.AvailabilityApp from [Module
"deployment.availability-service:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213)
[jboss-modules.jar:1.3.3.Final]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)