Inconsistent endpoint paths generation

[ecabrerar]

Hi all...

We notice sometimes openapi generated the endpoint paths like we are expecting, but sometimes generate the path without the JAX-RS Application prefix.

For example:
Our JAX-RS services use the prefix servicios, we are expecting paths like '/servicios/xxxx/xxx'

/servicios/aplicacion/version (when is ok)
/aplicacion/version (when is wrong)

Application Server: WildFly Full 24.0.1.Final
Microprofile:
microprofile-openapi-api : 3.0
microprofile-config-api: 3.0.1

openapi-failed.txt
openapi-ok.txt

[MikeEdgar]

@ecabrerar can you share a simple reproducer app?

[ecabrerar]

I could not reproduce it with a single maven project. I'm using openapi with a multi-module maven project. I did try to structure a reproducer app with multiple maven modules like the real project, but it was not posible to reproduce it.

After removing some old Java EE dependencies of the project, we have some improve, the paths are generated like we are expecting most of the time. I'll let you know if I can reproduce the same situation with a reproducer app or find a solution.

Thanks for your quick response!.

[MikeEdgar]

@ecabrerar you don't possibly have multiple Application classes do you?

[ecabrerar]

We don't notice there are two Application class in the core module.

The first one:
@ApplicationPath("servicios")
public class ApplicationServicesPath extends Application{

}

And the second one:
public final class RestConfiguration extends Application{
@OverRide
public Set<Class<?>> getClasses() {

}

}

In the last one, they use a ServiceLoader to load all classes with @path annotations.

Now, I could reproduce the same behaviour with a reproducer app.

Thank you for your help!.

[codespearhead]

@ecabrerar I'm not sure I understand your last message. Does that mean the problem is solved?

If so, can you mark this discussion as answered so that it doesn't show up in the discussion tab as unanswered?