You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 16, 2019. It is now read-only.
I have many projects that are inside a symbolic directory link in Windows (e.g. C:\java_projects points to C:\users\username\documents\code) which was created using the windows cmd mklink /d .....
When running any project that is inside the symbolic link, Payara log says it can't find any of the classes that are inside that war and shows 404 for every page.
I confirmed the symbolic directory link is the problem by opening the project directly from its physical path instead of the symbolic link and the deploy worked without issue.
Before this, I was using Payara 4 as a "Glassfish" type server in Netbeans 8.2 (not using Payara plugin), and all the projects inside the symbolic links worked without any issue. This is why I'm reporting this bug, because it used to work.
I'm not sure if this is a plugin issue or an issue with the server itself, but it's definitely related to this: payara/Payara#2591
The text was updated successfully, but these errors were encountered:
I'm using:
I have many projects that are inside a symbolic directory link in Windows (e.g. C:\java_projects points to C:\users\username\documents\code) which was created using the windows cmd
mklink /d ....
.When running any project that is inside the symbolic link, Payara log says it can't find any of the classes that are inside that war and shows 404 for every page.
I confirmed the symbolic directory link is the problem by opening the project directly from its physical path instead of the symbolic link and the deploy worked without issue.
Before this, I was using Payara 4 as a "Glassfish" type server in Netbeans 8.2 (not using Payara plugin), and all the projects inside the symbolic links worked without any issue. This is why I'm reporting this bug, because it used to work.
I'm not sure if this is a plugin issue or an issue with the server itself, but it's definitely related to this: payara/Payara#2591
The text was updated successfully, but these errors were encountered: