Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-7797

EARContentsDeployer creates the wrong name for modules

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: 6.0.0.M2
    • Fix Version/s: 6.0.0.M3
    • Component/s: Deployers
    • Labels:
      None

      Description

      It passes the result of this calculation to ModuleMetaData.setFileName():

      private String earRelativePath(String earPath, String pathName)

      { StringBuilder tmp = new StringBuilder(pathName); tmp.delete(0, earPath.length()); return tmp.toString(); }

      That will include a leading /, e.g.

      foo.ear/bar.war

      will have a ModuleMetaData with name "/bar.war". It should be "bar.war".

      This impacts the processing done as part of JBAS-7644.

      EARStructure has the same flaw, but the "earRelativePath" is passed to VirtualFile.getChild(earRelativePath) which ignores the leading /.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  brian.stansberry Brian Stansberry
                  Reporter:
                  brian.stansberry Brian Stansberry
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: