我正在使用jaxb从xml架构生成java类。 模式导入XMLSchema.xsd,其内容用作文档中的元素。
如果我分别删除了导入和对“xsd:schema”的引用,那么绑定编译器会成功生成类。 如果我不这样做会产生以下错误,如果我尝试仅从XMLSchema.xsd生成Java类,则会出现同样的错误!
> C:\Users\me>"%JAXB%/xjc" -extension -d tmp/uisocketdesc -p uis.jaxb uisocketdesc.xsd -b xml_binding_test.xml -b xml_binding_test_2.xml
-b xml_binding_test_3.xml
parsing a schema...
compiling a schema...
> [ERROR] A class/interface with the same name "uis.jaxb.ComplexType" is already in use. Use a class customization to resolve this conflict.
line 612 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] (Relevant to above error) another "ComplexType" is generated from here.
line 440 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] A class/interface with the same name "uis.jaxb.Attribute" is already in use. Use a class customization to resolve this conflict.
line 364 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] (Relevant to above error) another "Attribute" is generated from here.
line 1020 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] A class/interface with the same name "uis.jaxb.SimpleType" is already in use. Use a class customization to resolve this conflict.
line 2278 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] (Relevant to above error) another "SimpleType" is generated from here.
line 2222 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] A class/interface with the same name "uis.jaxb.Group" is already in use. Use a class customization to resolve this conflict.
line 930 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] (Relevant to above error) another "Group" is generated from here.
line 727 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] A class/interface with the same name "uis.jaxb.AttributeGroup" is already in use. Use a class customization to resolve this conflict.
line 1062 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] (Relevant to above error) another "AttributeGroup" is generated from here.
line 1026 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] A class/interface with the same name "uis.jaxb.Element" is already in use. Use a class customization to resolve this conflict.
line 721 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] (Relevant to above error) another "Element" is generated from here.
line 647 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] Two declarations cause a collision in the ObjectFactory class.
line 1020 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] (Related to above error) This is the other declaration.
line 364 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] Two declarations cause a collision in the ObjectFactory class.
line 2278 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] (Related to above error) This is the other declaration.
line 2222 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] Two declarations cause a collision in the ObjectFactory class.
line 930 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] (Related to above error) This is the other declaration.
line 727 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] Two declarations cause a collision in the ObjectFactory class.
line 440 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] (Related to above error) This is the other declaration.
line 612 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] Two declarations cause a collision in the ObjectFactory class.
line 1026 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] (Related to above error) This is the other declaration.
line 1062 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] Two declarations cause a collision in the ObjectFactory class.
line 647 of "http://www.w3.org/2001/XMLSchema.xsd"
> [ERROR] (Related to above error) This is the other declaration.
line 721 of "http://www.w3.org/2001/XMLSchema.xsd"
Failed to produce code.
答案 0 :(得分:18)
战斗这样的东西,对我而言,它是区分大小写的问题和元素和属性问题的同名(有时通过继承)。对于第二个问题,我正在使用包含以下内容的外部绑定文件:
<jaxb:bindings node="//xs:complexType[@name='AbstractGriddedSurfaceType']//xs:attribute[@name='rows']">
<jaxb:property name="rowCount"/>
</jaxb:bindings>
对于区分大小写的问题,您可以使用xjc参数 -XautoNameResolution ,maven版本为<args><arg>-B-XautoNameResolution</arg></args>
,但这不适用于包装器元素,因此对于这些,您需要编写jaxb如上所述的自定义,...如果你像我一样不幸:)你可能需要使用xsd的本地副本并手动修复重复。
修改强> 找到了区分大小写问题的另一种解决方案,其中重命名元素是不够的:
<jaxb:bindings node=".//xs:element[@name='imageDatum'][@type='gml:ImageDatumPropertyType']">
<jaxb:property name="imageDatumInst"/>
<jaxb:factoryMethod name="imageDatumInst" />
</jaxb:bindings>
祝你好运,希望这会有所帮助。
答案 1 :(得分:9)
您可以通过(至少)两种方法成功地让JAXB为XML Schema xsd生成代码。您遇到的问题源于某些模式类型和元素共享相同名称的事实。
第一个选项通过将一个或多个XML名称转换应用于生成的类名来避免名称冲突。以下是将执行此操作的外部绑定文件的示例:
<jxb:bindings version="2.1"
xmlns:jxb="http://java.sun.com/xml/ns/jaxb"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xjc="http://java.sun.com/xml/ns/jaxb/xjc"
jxb:extensionBindingPrefixes="xjc">
<jxb:globalBindings>
<xjc:simple/>
</jxb:globalBindings>
<jxb:bindings schemaLocation="XMLSchema.xsd">
<jxb:schemaBindings>
<jxb:nameXmlTransform>
<jxb:elementName suffix="Element"/>
</jxb:nameXmlTransform>
</jxb:schemaBindings>
</jxb:bindings>
</jxb:bindings>
这种方法有效(您可以应用其他可以正常工作的转换,但我在文档中一遍又一遍地看到这种技术),但我认为它会产生难看的结果。例如,在这种情况下,生成的类名为ElementElement
。
第二种方法使用xjc输出建议的类自定义。实际上,除了一个问题类之外的所有问题类都在相应的模式类型中设置了属性abstract="true"
。因此,使用“Abstract”前缀类名是有意义的,即AbstractElement
。剩下的Attribute
类不是抽象的,但名为xs:element
的{{1}}会生成一个空主体的扩展类。因此我称之为attribute
。这是我使用的外部绑定定义:
BaseAttribute
在我看来,这给出了更清晰的生成类名,并成功编译了模式。
我还建议对XMLSchema.xsd使用单独的编译并将其保存在jar文件中以备日后使用,以防在编译另一个模式时再次出现此问题。 this question的答案描述了如何。
答案 2 :(得分:4)
看起来您的架构已损坏。 XJC对这些事情非常挑剔,并且在其他工具可以通过的事情上失败。
我发现通过AlphaWorks Schema Quality Checker首先运行架构更容易,而不是挑选XJC的错误。这给出了一个很好的,人类可读的(好的,开发人员可读的,无论如何)错误输出。如果它通过了那个好的,那么你也有更好的机会通过XJC。
答案 3 :(得分:3)
另一种选择是删除-p
选项,以便在不同的包中生成类
答案 4 :(得分:2)
使用cxf从.wsdl生成对象时遇到了同样的问题。我的解决方案是使用-autoNameResolution作为错误消息建议。 Maven配置:
<wsdlOption>
<wsdl>${basedir}/test.wsdl</wsdl>
<extraargs>
<extraarg>-b</extraarg>
<extraarg>http://www.w3.org/2001/XMLSchema.xsd</extraarg>
<extraarg>-autoNameResolution</extraarg>
</extraargs>
<packagenames>
<packagename>test.wsdl</packagename>
</packagenames>
</wsdlOption>
答案 5 :(得分:0)
我试过以下,它对我有用:
<jxb:bindings schemaLocation="ClaimActivity-ACORD.xsd">
<jxb:schemaBindings>
<jxb:package name="x.x.x.x" />
</jxb:schemaBindings>
<jxb:bindings node="//xsd:complexType[@name='ConstructionType']">
<jxb:class name="AbstractConstructionType" />
</jxb:bindings>
<jxb:bindings node="//xsd:complexType[@name='ItemDefinitionType']">
<jxb:class name="AbstractItemDefinitionType" />
</jxb:bindings>
<jxb:bindings node="//xsd:complexType[@name='LocationType']">
<jxb:class name="AbstractLocationType" />
</jxb:bindings>
<jxb:bindings node="//xsd:complexType[@name='TaxFeeType']">
<jxb:class name="AbstractTaxFeeType" />
</jxb:bindings>
<jxb:bindings node="//xsd:complexType[@name='DeductibleType']">
<jxb:class name="AbstractDeductibleType" />
</jxb:bindings>
<jxb:bindings node="//xsd:complexType[@name='RegistrationType']">
<jxb:class name="AbstractRegistrationType" />
</jxb:bindings>
</jxb:bindings>
答案 6 :(得分:0)
我遇到了相同的错误,并完全删除了<generatePackage></generatePackage>
。这解决了我的问题。
答案 7 :(得分:-1)
您可以使用JDK1.6附带的xjc。您也可以尝试使用XML to Java,参考this article。