Re: Followup2: Changed behaviour of Tomcat Deployment/Context/Lifecycle Manager concerning symbolic links

2019-03-08 Thread Mark Thomas
On 08/03/2019 11:59, Jäkel, Guido wrote: > Good news! > > I reverted the change and this solve my issue at once, i.e. all former > installed applications will start up as expected. > > So, please what was the reason or intention here to shift from getPath() to > getCanonicalPath() in case of

Configuring embedded Tomcat with @WebServlet annotations

2019-03-08 Thread Raffaele Sgarro
Hello all! How is one supposed to configure Tomcat (I'm on 9.x) to scan a given package looking for @WebServlet servlets? I cannot find any API and relevant examples in the Tomcat source. More insight: my app is currently packaged as a WAR and deployed to a running Tomcat instance. I want to buil

Followup2: Changed behaviour of Tomcat Deployment/Context/Lifecycle Manager concerning symbolic links

2019-03-08 Thread Jäkel , Guido
Good news! I reverted the change and this solve my issue at once, i.e. all former installed applications will start up as expected. So, please what was the reason or intention here to shift from getPath() to getCanonicalPath() in case of a link (detected by !file.isAbsolute() )? What's the

Followup: Changed behaviour of Tomcat Deployment/Context/Lifecycle Manager concerning symbolic links

2019-03-08 Thread Jäkel , Guido
or all other aspects greetings Guido >[...] >for deployment, with the newer Tomcat version I get the error > > 20190308-092433.557 ERROR [catalina-exec-38] [] [[/manager]] FAIL - > Application at context path [/foo] could not be >started > org.apache

Changed behaviour of Tomcat Deployment/Context/Lifecycle Manager concerning symbolic links

2019-03-08 Thread Jäkel , Guido
rom this, after establishing the link foo.war -> /some/fill/path/to/destination/bar.an_extension for deployment, with the newer Tomcat version I get the error 20190308-092433.557 ERROR [catalina-exec-38] [] [[/manager]] FAIL - Application at context path [/foo] could not be started