Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 4045358
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 20, 20262026-05-20T13:24:58+00:00 2026-05-20T13:24:58+00:00

I have an ear which currently works fine when deployed in JBoss 4.2.3. I

  • 0

I have an ear which currently works fine when deployed in JBoss 4.2.3. I am attempting to migrate to JBoss 5.0.1 but am getting the error ‘classpath module listed in application.xml is not a recognized deployment’.

Below is the struture of my ear:

              MyApp
                |       
                +- classpath
                |       
                +- lib
                |   |
                |   +- A.jar
                |   +- B.jar
                |   +- C.jar
                |
                +- META-INF 
                |   |
                |   +- application.xml
                |   +- jboss-app.xml
                |
                +- D.jar
                |
                *- E.jar
                |
                +- F.jar
                |
                +- myApp.war
                    |
                    +- WEB-INF
                    |
                    +- ....

Below is what I have in my application.xml:

<application>
  <display-name>MyApp</display-name>
  <module>
    <java>classpath</java>
  </module>
  <module>
    <java>lib/A.jar</java>
  </module>
  <module>
    <java>lib/B.jar</java>
  </module>
  <module>
    <java>D.jar</java>
  </module>

  ...      

  <module>
    <web>
      <web-uri>myApp.war</web-uri>
      <context-root>/WEB-INF</context-root>
    </web>
  </module>
</application>

As mentioned the current structure of my ear and the application.xml outlined above, all works fine in JBoss 4.2.3. However, when I deploy this is JBoss 5.1.0 it appears not to like the ‘classpath’ module defined in the application.xml.

Below is the full stack trace occuring:

17:02:09,767 WARN  [HDScanner] Scan failed
    org.jboss.deployers.spi.DeploymentException: Exception determining structure: AbstractVFSDeployment(MyApp.ear)
        at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
        at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:85)
        at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:1004)
        at org.jboss.deployers.plugins.main.MainDeployerImpl.determineDeploymentContext(MainDeployerImpl.java:440)
        at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:390)
        at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:300)
        at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.addDeployment(MainDeployerAdapter.java:86)
        at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:344)
        at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
        at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:662)
    Caused by: java.lang.RuntimeException: Error determining structure: MyApp.ear
        at org.jboss.deployment.EARStructure.determineStructure(EARStructure.java:293)
        at org.jboss.deployers.vfs.plugins.structure.StructureDeployerWrapper.determineStructure(StructureDeployerWrapper.java:73)
        at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl.doDetermineStructure(VFSStructuralDeployersImpl.java:196)
        at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl.determineStructure(VFSStructuralDeployersImpl.java:221)
        at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:77)
        ... 16 more
    Caused by: java.lang.RuntimeException: classpath module listed in application.xml is not a recognized deployment, .ear: MyApp.ear
        at org.jboss.deployment.EARStructure.determineStructure(EARStructure.java:277)
        ... 20 more

I’m tearing my hair out with this one! Any help would be greatly appreciated.

Thanks

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-20T13:24:59+00:00Added an answer on May 20, 2026 at 1:24 pm

    The good news is that JBoss 5.x automatically adds any JARs in lib to the EAR’s classpath, so you don’t actually need to specify them in the application.xml.

    For your classpath directory, you’ll have to rename that to classpath.jar, and then 5.x should accept it.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a web application which deploys fine as an ear file. But when
We have an enterprise application (deployed as an ear) is a batch processor which
I have a J2EE app deployed as an EAR file, which in turn contains
I have created an EAR project in Eclipse to be deployed on JBoss. In
I'm using JBoss 4.2.3, EJB2, XDoclet and have deployed one EAR with the EJBs
I have an EAR module which contian ejb client, structs web module and webservice
I have service classes which are deployed in an EAR with no WAR or
I have an old J2EE application (J2EE 1.3), which packages into an EAR, and
I have a trouble deploying an ear in jboss under eclipse. I got a
I have an application ear which I am trying to deploy into Oracle Weblogic

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.