What is this used for ? Looks a lot like a JNDI datasource name to me
Haha indeed I didn't think about that, thus I changed the value by the JNDI name in persistence.xml (since it should apply to both admin et wli applications)
The admin app is deploying but I cannot access the URL : localhost:8080/xa-cms-admin/
Here's the log for when I'm deploying the admin app only : onlyadmin - Pastebin.com
And here's the log when I'm deploying the admin and the wli app : both_apps - Pastebin.com
I think the problem comes from the fact that the admin app is dependant of the wli app but I didn't find a way to solve it yet and it's already time to leave the office.
Thank you for your help today, I hope we will be able to make it work soon.
EDIT : When I try to acces the admin's app URL I get this trace : tapestry_admin_app - Pastebin.com I don't really know if it means I have to migrate the admin with the help of Windup to make it work or if it is a completely different problem. I'll learn about tapestry to understand that better.
If you have any idea or need more infos about the wli app duplicate problem or the admin app URL/tapestry issue please do not hesitate to ask.
However it seems that Wildfly deployed the admin app to localhost:8080/ when I look into the trace : 11:19:32,511 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0021: Contexte web enregistré : /
I thought that if I didn't put a context it would deploy to the URL with the war's name but it seems I have to change that.
I still get a "forbidden" on localhost:8080 though.
Do you have a jboss-web.xml in your wars ?
Well not explicitely in my wars but I do have a jboss-web.xml in /WEB-INF directories :
<?xml version="1.0" encoding="UTF-8"?>
I think the fact both context root are not precised may lead to the duplicate exception since it may try to deploy admin and wli at the same URL, but I'm not sure about that, because I thought it was deployed at the URL which is the name of the war if you put "/" as context root.
So I deleted the two files and re-launched the server. The admin app is now bound to localhost:8080/xa-cms-admin/ just as you said and I have "Forbidden" displayed.
However the wli application still cannot be deployed, it's not the duplicate exception that was there before. Could you please take a look at the logs while I also investigate? : wli_exception - Pastebin.com
You have apache cxf jars files in your application which are in conflict with those provided by jboss eap
I've search on the internet to find solutions based on your advice and I applied one that almost works, it's the one proposed by Reto Hodel on this thread : Using CXF2.7.0 build with WAR in WildFly 10
Based on that, I created a jboss-deployment-structure.xml file in my WEB-INF folder. However I couldn't apply his second step because it was causing errors in my project's java resources.
After doing that I launched the server again and got these logs : wli_error_log - Pastebin.com
In the web management console both wars seem to be deployed. But at localhost:8080/xa-cms-wli/ I do not have "Forbidden" dsplayed (like for the admin app), instead there is the error trace that is at the end of the logs above.
Do you know another method to solve the problem of the cxf jars? Or maybe is it better to solve the errors in the logs?
Here is my pom file : pom_wli - Pastebin.com
and my jboss-deployment-structure.xml file : deployment-structure - Pastebin.com
1/ I don't think you need
in your pom.
2/ As I see it the problem seems to be in the ioc part of Tapestry which I don't know at all
I noticed too it was a problem between JBoss and Tapestry.
Thank you very much for all the help you brought on this thread.
I would like to ask you a question though, does the "Forbidden" displayed at the URI of the admin web app is a specific error? Or it is because I still have not adapted my source code to Wildfly with Windup ?