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

Romain Manni-Bucau closed TOMEE-1993.
-------------------------------------
       Resolution: Fixed
         Assignee: Romain Manni-Bucau
    Fix Version/s: 7.0.3

> When using symbolic links the @WebServlet is not processed
> ----------------------------------------------------------
>
>                 Key: TOMEE-1993
>                 URL: https://issues.apache.org/jira/browse/TOMEE-1993
>             Project: TomEE
>          Issue Type: Bug
>          Components: TomEE Core Server
>    Affects Versions: 7.0.2
>            Reporter: Violeta Georgieva
>            Assignee: Romain Manni-Bucau
>             Fix For: 7.0.3
>
>
> Hi,
> @WebServlet is not processed when the web app files are symbolic links, but 
> the root web app directory is not.
> The use case is the following:
> TomEE structure:
> {code}
> - TomEE root
> ...
>   - webapps
>     - myapp
>       content -> /some/other/location/...
> {code}
> When the root of the app (in my case my app dir is not a symbolic link) then
> the war path will point to the location under TomEE directory.
> https://github.com/apache/tomee/blob/master/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/Contexts.java#L62
> Later when processing the @WebServlet the actual file path will point to
> "/some/other/location/..." but the "info.name" will point to the location
> under TomEE directory.
> https://github.com/apache/tomee/blob/master/tomee/tomee-catalina/src/main/java/org/apache/catalina/startup/OpenEJBContextConfig.java#L569
> If I change the symbolic link to the following:
> {code}
> - TomEE root
> ...
>   - webapps
>     - myapp -> /some/other/location
>       content -> /some/other/location/...
> {code}
> Then everything is OK and the servlets are found.
> I'm reproducing this with TomEE 7.0.2 and I do not reproduce this behavior
> with TomEE 1.7.2
> Best Regards,
> Violeta Georgieva



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to