[jboss-jira] [JBoss JIRA] Closed: (JBMICROCONT-104) DeploymentContext shortName for jar is messed up as well as url

Scott M Stark (JIRA) jira-events at lists.jboss.org
Thu Mar 15 23:40:32 EDT 2007


     [ http://jira.jboss.com/jira/browse/JBMICROCONT-104?page=all ]

Scott M Stark closed JBMICROCONT-104.
-------------------------------------

    Fix Version/s:  JBossMC_2_0_0 Beta3
                       (was: JBossMC_2_0_0_CR1)
       Resolution: Done
         Assignee: Scott M Stark

There are now getSimpleName() and getRelativePath() methods that provide short deployment oriented names.


> DeploymentContext shortName for jar is messed up as well as url
> ---------------------------------------------------------------
>
>                 Key: JBMICROCONT-104
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-104
>             Project: JBoss MicroContainer
>          Issue Type: Bug
>          Components: VFS
>            Reporter: Bill Burke
>         Assigned To: Scott M Stark
>             Fix For:  JBossMC_2_0_0 Beta3
>
>
> The DeploymentContext.getName() ends up being the full URL of a JAR
> if you have a JAR file within a directory, its name is
> jar:file:/.../foo.jar!/
> Shouldn't this be a "short" name?  My bet this has something to do with how the URL is messed up too for VirtualFiles that are JARs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list