geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (GERONIMO-5583) Same Web Context-Paths in two EBA don't conflict after deployment
Date Sun, 12 Sep 2010 05:18:32 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jarek Gawor resolved GERONIMO-5583.
-----------------------------------

    Resolution: Invalid

This is working as described in the specification. There should be a warning message logged
about the web context path collision. The colliding bundle is queued and will be deployed
once the bundle that's currently deployed with the given context path is undeployed.


> Same Web Context-Paths in two EBA don't conflict after deployment
> -----------------------------------------------------------------
>
>                 Key: GERONIMO-5583
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5583
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Aries
>    Affects Versions: 3.0
>         Environment: OS:winXP
> JDK: 1.6.0_21
>            Reporter: viola.lu
>            Priority: Minor
>             Fix For: 3.0
>
>
> 1.Build Aries sample, deploy its blog sample EBA: blog-jdbc-eba, and blog-jpa-eba to
server, 
> 2.Both ebas contains the sample web.jar file, same Web-ContextPath: /blog, but no conflict
error, and i can access the app via http://localhost:8080/blog/.
> Not sure which one is called. There should web-contextpath check, if one already exists,
should report errors.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message