[jboss-jira] [JBoss JIRA] (WFLY-4402) Fails to load JAX-RS Application class if deployment runtime name is changed

[Abhijit Sarkar (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045992#comment-13045992 ] 

Abhijit Sarkar edited comment on WFLY-4402 at 3/4/15 12:15 AM:
---------------------------------------------------------------

[~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.

Edit: In order to attach the screenshot, I'm having to reopen the issue. Feel free to close if you've followed the steps and didn't see the error.


was (Author: abhi0123):
[~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)