3
EDIT Guys I managed to solve, I was missing point my application to my virtual server, thank you.
I uploaded an application on the server today and glassfish is not taking the context of the application alone for example to access I’m having to put : www.bla.com/Customer service.
<glassfish-web-app>
<context-root>/Atendimento</context-root>
<parameter-encoding default-charset="UTF-8" />
<property name="alternatedocroot_1" value="from=/backgrounds/* dir=e:\HRatendimento\imagens\" />
<property name="alternatedocroot_2" value="from=/logos/* dir=e:\HRatendimento\imagens\" />
<property name="alternatedocroot_3" value="from=/gerais/* dir=e:\HRatendimento\imagens\" />
<property name="alternatedocroot_4" value="from=/anexos/* dir=e:\HRatendimento\imagens\" />
<property name="alternatedocroot_5" value="from=/usuarios/* dir=e:\HRatendimento\imagens\" />
<property name="alternatedocroot_6" value="from=/licenca/* dir=e:\HRatendimento\" />
<property name="alternatedocroot_7" value="from=/manuais/* dir=e:\HRatendimento\" />
And on the glassfish I left the contextRoot as /Atendimento
.
Does anyone have any idea what it might be?
Try editing the context root on the console (port 4848). If it doesn’t work take a screen from the settings on the console and show from your
glassfish-web.xml
(all the content as well as the folder in which it is located). If the goal is to play at the root of the site, just set the context-root to/
.– Anthony Accioly
@Anthonyaccioly again helping me, so this application worked smoothly, I made this deploy today and it happened, because I did not change these settings
– Wellington Avelino
I get it. Just so I can help you better. The goal is to eliminate
/Atendimento
and publish at the root? Or is to stay where you are only some problem is happening?– Anthony Accioly
Yes publish at the root
– Wellington Avelino