ppalaga commented on PR #2237: URL: https://github.com/apache/cxf/pull/2237#issuecomment-2621159402
> I found out that the issue is not happening in stock CXF where only `WrapperClassGenerator` is active. That one is using per service class loaders and it is thus able to provide multiple wrapper classes with the same FQ name. The issue only happens when there is a `GeneratedClassClassLoaderCapture` storing the classes per class name and a `WrapperClassLoader` using them and loading in flat class loader. Hm... when thinking of it more, another possible solution strategy could be to pass the service name to `GeneratedClassClassLoaderCapture`, let it store per service and make `WrapperClassLoader` also load the classes through per-service class loaders... I am not quite sure we should go that way, because it would be more complicated than the current solution. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
