You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Akitoshi Yoshida (JIRA)" <ji...@apache.org> on 2015/12/01 15:33:11 UTC
[jira] [Closed] (CXF-6696) Java2WS - SEI - multiple classpaths
[ https://issues.apache.org/jira/browse/CXF-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Akitoshi Yoshida closed CXF-6696.
---------------------------------
Resolution: Invalid
For questions, please use CXF's users mailing list.
See more info at
https://cxf.apache.org/mailing-lists.html
> Java2WS - SEI - multiple classpaths
> -----------------------------------
>
> Key: CXF-6696
> URL: https://issues.apache.org/jira/browse/CXF-6696
> Project: CXF
> Issue Type: Bug
> Affects Versions: 3.1.4
> Reporter: Benjamin Kastelic
> Priority: Minor
>
> Greetings!
> First of all, this is more of a question than a bug. Here it goes.
> I'm working on a project, where the SEI class is in Maven module A, schema classes are in module B and the SEI interface is in module C. I am trying to generate a WSDL from the SEI class.
> I have run the java2ws plugin by setting the classpath to "moduleX/target/classes", but the plugin throws an error, that the classes from modules B and C cannot be loaded/found.
> Is this even supported or am I doing something wrong?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)