You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Andriy Redko (Jira)" <ji...@apache.org> on 2024/02/21 01:23:00 UTC

[jira] [Commented] (CXF-8956) include compiled WSDL in generated client

    [ https://issues.apache.org/jira/browse/CXF-8956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819031#comment-17819031 ] 

Andriy Redko commented on CXF-8956:
-----------------------------------

[~mirzac] so this functionality has been implemented to support, in particular, GraalVM native image packaging, please check out the documentation here [1] to find out the examples of how to capture generated classes and bundle them with your application.

[1] https://cxf.apache.org/docs/graalvm-support.html

> include compiled WSDL in generated client
> -----------------------------------------
>
>                 Key: CXF-8956
>                 URL: https://issues.apache.org/jira/browse/CXF-8956
>             Project: CXF
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Mirza
>            Priority: Minor
>
> When I generate my client-package from the WSDL file, runtime still needs access to WSDL file when accessing web service. This means I need to add WSDL file to resources, and it gets more complicated when additional XSD files are included in WSDL.
> I think many people would prefer to have "compiled" version od WSDL (not necessarily XML, maybe even JSON or whatever) inside generated Java client package. It could be separate .java file with single static String containing WSDL. This would be an option, like -embedWsdl. This would eliminate need for resource WSDL files and simplify pom.xml file client generation.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)