Hi Francesco, Thanks very much for your prompt reply.
Indeed, I have tried it once on Wildfly 26. before upgrading to wildfly 34 however I couldn't find customization options for wildfly 26. Let me explain : On the page https://syncope.apache.org/docs/3.0/getting-started.html#java-ee-container The container mentioned is indeed Wildfly26. However on the section about maven : https://syncope.apache.org/docs/3.0/getting-started.html#maven-project It is noted that : If no failures are encountered, your basic Apache Syncope project is now ready to go. *And Before actual deployment as executable or onto a Java EE container, you need to further check the Customization chapter of the Apache Syncope Reference Guide. <https://syncope.apache.org/docs/reference-guide.html> * And in this reference guide, the example for the JavaEE container is only for Wildfly 34. I suppose it is about the latest release of Syncope. So, If I am to go back to wildfly 26 again, where can I find the specific customization related to wildfly 26? Please advise Tarehe Alhamisi, 30 Jan 2025 saa 12:12 Francesco Chicchiriccò < ilgro...@apache.org> aliandika: > Hi Muleya, > Syncope 3.0 runs on Widfly 26; see > > https://syncope.apache.org/docs/3.0/getting-started.html#java-ee-container > > For Wildfly 34 you need Syncope 4.0; see > > https://syncope.apache.org/docs/4.0/getting-started.html#java-ee-container > > Hope this clarify. > Regards. > > On 30/01/25 17:06, Mukeya Kassindye wrote: > > Good day everyone, > > I’m trying to install Apache Syncope 3.0.10 on WildFly 34 (Java 17) using > Maven. The build process completes successfully, and there are no errors in > the WildFly logs. However, when I try to access the API endpoint, I > encounter the following issue: > > URL accessed: http://<server-ip>:8080/syncope/rest/openapi.json > > Error message: Failed to load API definition – Fetch error: Not Found > > What I’ve checked so far: > > 1. > > Deployment Status > > All WAR files (syncope.war, syncope-console.war, syncope-enduser.war, > syncope-wa.war) are successfully deployed. > > No errors in server.log. > 2. > > Configuration > > The core.properties file contains: > > server.servlet.contextPath=/syncope > > cxf.path=/rest > > WildFly is configured with a JNDI datasource for PostgreSQL, and > database connectivity works fine. > 3. > > Keymaster & Service Discovery > > keymaster.address is set to http://:8080/syncope/rest/keymaster > > Running curl -v http://:8080/syncope/rest/keymaster returns 404 NOT > found. > 4. > > Swagger & API Availability > > Swagger UI loads at http://:8080/syncope/, but the API definition is > missing. > > There is no /WEB-INF/classes/rest/ directory in the deployed WAR file. > > Questions: > > Should the /rest endpoint be generated automatically, or do I need to > configure something explicitly? > Is there a required dependency or configuration I might be missing for > Syncope’s REST API to work on WildFly? > Has anyone successfully deployed Syncope 3.0.x on WildFly and encountered > this issue? > > Any guidance would be greatly appreciated! > > What I Tried: > > - Checked WildFly logs (server.log) – No critical errors or deployment > failures. > - Verified database connectivity – PostgreSQL datasource is configured > via JNDI in standalone.xml, and the connection test from WildFly CLI was > successful. > - Verified configuration files (core.properties) > - Checked deployed WAR contents – The expected /WEB-INF/classes/rest/ > directory is missing inside syncope.war. > - Swagger UI loads, but the API definition /syncope/rest/openapi.json > is missing > > > I have posted this issue on stackoverflow as well : > https://stackoverflow.com/questions/79398728/issue-with-syncope-3-0-10-on-wildfly-failed-to-load-api-definition > > Best regards > > > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellencehttp://www.tirasa.net/ > > Member at The Apache Software Foundation > Syncope, Cocoon, Olingo, CXF, OpenJPA, > PonyMailhttp://home.apache.org/~ilgrosso/ > >
