cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Mathews (JIRA)" <>
Subject [jira] [Commented] (CXF-4487) cxf-codegen-plugin: Error resolving component warnings for imported types
Date Wed, 29 Aug 2012 13:53:08 GMT


Chris Mathews commented on CXF-4487:

Tested a number of different wsdls with 2.6.3-SNAPSHOT and it works perfectly. Awesome responsiveness,
thanks Dan!
> cxf-codegen-plugin: Error resolving component warnings for imported types
> -------------------------------------------------------------------------
>                 Key: CXF-4487
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: Tooling
>    Affects Versions: 2.6.2
>         Environment: Windows 7 x64
>            Reporter: Gert Driesen
>            Assignee: Daniel Kulp
>            Priority: Minor
>             Fix For: 2.6.3
>         Attachments:, cxf-codegen-plugin.log,
> As of CXF 2.6.2 (not sure about 2.6.1)), I get warnings for several types that have been
imported from an XSD.
> For example:
> WARNING: C:\cxf-plugin-issue\src\main\resources\Private\Acquittal\NisseAcquittal_V1.wsdl
[23,7]: src-resolve.4.2: Error resolving component 'meta:ApplHeaderStruct'. It was detected
that 'meta:ApplHeaderStruct' is in namespace '',
but components from this namespace are not referenceable from schema document 'file:/C:/cxf-plugin-issue/src/main/resources/Private/Acquittal/NisseAcquittal_V1.wsdl#types1'.
If this is the incorrect namespace, perhaps the prefix of 'meta:ApplHeaderStruct' needs to
be changed. If this is the correct namespace, then an appropriate 'import' tag should be added
to 'file:/C:/cxf-plugin-issue/src/main/resources/Private/Acquittal/NisseAcquittal_V1.wsdl#types1'.
> I get none of these warning when using CXF 2.5.4, and the WSDL and XSD are all valid.
> I'll attach a repro for this issue, and a log file (taken with level FINE).
> Just search for "src-resolve.4.2".
> Just use "mvn clean install" to reproduce the issue.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message