[Swagger UI]: no service was found
See original GitHub issueDear, I have 4 resources, a basic auth, and a cxf soap endpoint on the same project of my 4 rest resources. --> I got a “no service was found” white page 😦 do you have an idea of the problem plz ? bellow all my screenshots
Expected behavior: On other project I don’t have the problem, and in this project, when I go to localhost:8080/q/swagger-ui I expected the same behavior of swagger-ui displaying
Actual behavior: I got a “no service was found” on my swagger-ui but I don’t understand why …
Configuration
# Set up the users and roles using properties files
quarkus.security.users.file.enabled=true
quarkus.security.users.file.users=users.properties
quarkus.security.users.file.roles=roles.properties
quarkus.security.users.file.realm-name=Company
quarkus.security.users.file.plain-text=true
quarkus.http.auth.policy.role-employee.roles-allowed=employee
quarkus.http.auth.permission.roles.paths=/q/*
quarkus.http.auth.permission.roles.policy=role-employee
quarkus.cxf.endpoint."/dalkia-ticket-loader".published-endpoint-url=http://localhost:8080/dalkia-ticket-loader
quarkus.cxf.endpoint."/dalkia-ticket-loader".implementor=fr.dalkia.ticketloader.services.front.soap.RequestUpdateServiceImpl
quarkus.smallrye-openapi.path=/swagger
quarkus.swagger-ui.always-include=true
quarkus.swagger-ui.display-request-duration=true
quarkus.swagger-ui.with-credentials=true
quarkus.swagger-ui.doc-expansion=full
quarkus.swagger-ui.theme=original
Screenshots
(If applicable, add screenshots to help explain your problem.)
Environment (please complete the following information):
OpenJDK Runtime Environment GraalVM CE 21.0.0.2 (build 11.0.10+8-jvmci-21.0-b06) Linux adrien 5.4.0-67-generic #75-Ubuntu SMP Fri Feb 19 18:03:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 20.04.2 LTS Quarkus version: 1.12.1.Final Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: /home/adrien/.sdkman/candidates/maven/current Java version: 11.0.10, vendor: GraalVM Community, runtime: /home/adrien/.sdkman/candidates/java/21.0.0.2.r11-grl Default locale: fr_FR, platform encoding: UTF-8 OS name: “linux”, version: “5.4.0-67-generic”, arch: “amd64”, family: “unix”
**bellow all attached screen
**
Issue Analytics
- State:
- Created 2 years ago
- Comments:15 (11 by maintainers)
ok thank @shumonsharif it’s work properly now 😃 because I didn’t think to aggregate the both URL for soap endpoint. You can close de ticket. BTW after trying with “quarkus.cxf.path=/” I realized that can request on “http://localhost:8080**//**dalkia-ticket-loader” … I tried to put:
quarkus.cxf.path= quarkus.cxf.endpoint.“/dalkia-ticket-loader”.implementor=fr.dalkia.ticketloader.services.front.soap.RequestUpdateServiceImpl quarkus.resteasy.path=/services
In order to keep retrocompatibility with ours old calling URL like http://localhost:8080/dalkia-ticket-loader by hope that the URL will be construct with http://localhost:8080/ + “” + “/dalkia-ticket-loader” but not really work … it’s just too bad for this last case not to be able to keep my url. Maybe a point of improvement to think about 😃
But for now @phillip-kruger @shumonsharif you can close the ticket, thank 😃 @shumonsharif I don’t forget to produce a hello-world from wsdl case, for the Quarkus-Cxf Quarkiverse !
Yes anything that reproduce the issue