blocks|key|209602|text|试试这个。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|209603|<xs:element+name="usage-auth-rate-charge">
++++<xs:complexType>
++++++++<xs:sequence>
++++++++++++<xs:element+name="service-id"+type="xs:string"/>
++++++++</xs:sequence>
++++++++<xs:attribute+name="chosen"+type="xs:boolean"+use="required"/>
++++</xs:complexType>
</xs:element>|code-block|syntax|javascript|209604|我发现了你的问题，因为我正在寻找如何做你正在做的完全相反的事情。我有一个布尔属性，它只会生成将该属性作为原始布尔值的代码。为了让jaxb将这个属性作为布尔对象而不是布尔原语生成，我在xsd中删除了属性定义中的use=“use=”部分。|209605|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Try this...

<pre><code>&lt;xs:element name="usage-auth-rate-charge"&gt;
 &lt;xs:complexType&gt;
 &lt;xs:sequence&gt;
 &lt;xs:element name="service-id" type="xs:string"/&gt;
 &lt;/xs:sequence&gt;
 &lt;xs:attribute name="chosen" type="xs:boolean" use="required"/&gt;
 &lt;/xs:complexType&gt;
&lt;/xs:element&gt;
</code></pre>

I found your question as I was looking how to do the exact opposite thing you were doing. I had a boolean attribute that would only generate code that had the attribute as a primitive boolean value. To make jaxb generate this attribute as a Boolean object instead of a boolean primitive, I just removed the use="required" portion of my attribute's definition in the xsd.

blocks|key|3062259|text|问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3062260|获取Boolean而不是boolean的原因是您的元素定义中包含了minOccurs="0"。将为缺少的元素存储null值。|offset|length|style|CODE|3062261|<xs:element+name="pricepoint_custom_fields_required"+type="xs:boolean"+minOccurs="0"/>|code-block|syntax|javascript|3062262|解决方案应该是什么|3062263|解决方案应该是一个外部绑定文件，该文件指示应该对可选值使用原语类型(请参阅JAXB+2.2规范的7.5.1节)。|3062264|<?xml+version="1.0"+encoding="UTF-8"?>
<jaxb:bindings
++++xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
++++version="2.1">
++++<jaxb:globalBindings+optionalProperty="primitive"/>
</jaxb:bindings>|3062265|外部绑定文件是使用XJC的-b选项指定的。|3062266|xjc+-b+binding.xml+my-schema.xsd|3062267|为什么该解决方案不起作用|3062268|已打开以下错误来跟踪optionalProperty="primitive"的问题。|3062269|3062270|https://github.com/javaee/jaxb-v2/issues/510|unordered-list-item|3062271|https://github.com/javaee/jaxb-v2/issues/926|3062272|3062273|解决方法|3062274|如果您不喜欢在JAXB中生成类的方式，那么可以自己创建一个类，并让JAXB将其作为模式的一部分引入到类生成中。|3062275|binding.xml|BOLD|3062276|<jxb:bindings+
++++xmlns:xs="http://www.w3.org/2001/XMLSchema"
++++xmlns:jxb="http://java.sun.com/xml/ns/jaxb"
++++version="2.1">

++++<jxb:bindings+schemaLocation="my-schema.xsd">
++++++++<jxb:bindings+node="//xs:element[@name='usage-auth-rate-charge']/complexType">
++++++++++++<jxb:class+ref="com.example.foo.UsageAuthRateCharge"/>
++++++++</jxb:bindings>
++++</jxb:bindings>
</jxb:bindings>|3062277|UsageAuthRateCharge|3062278|用你想要的方法创建这个类。|3062279|XJC调用|3062280|在XJC调用中使用-b标志来指定binding.xml文件|3062281|xjc+-b+binding.xml+my-schema.xsd|3062282|3062283|更新|3062284|3062285|我真正希望的是，读者中可能有一位是jaxb开发团队的成员，他可以用jaxb轻松地完成更改。用户archenroot在他对jaxb问题927+(926的副本)的评论中提供了一个可能的解决方案，这使我认为对于合适的人来说，修复jaxb将是一项简单的工作。|blockquote|3062286|3062287|3062288|我是的领导。我已经联系了负责JAXB参考实现的同事(他们也为Oracle工作)。以下是我从他们那里得到的回复：|3062289|我在主干中测试过|3062290|+--问题确实存在。我将检查代码修复它有多容易。|3062291|3062292|3062293|希望你能得到这个问题的真正解决方案。|3062294|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|2|7|C|7|X|D|1K|4|0|0|0|0|0|D|2|0|0|0|A|S|0|0|0|18|0|0|0|18|1|0|0|0|0|0|B|0|0|0|J|0|0|0|5|0|9|2|G|B|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|2H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2I|8|@$D|2J|E|2K|F|G]|$D|2L|E|2M|F|G]|$D|2N|E|2O|F|G]|$D|2P|E|2Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|2R|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|2S|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|2T|8|@]|9|@]|A|$]]|$1|Q|3|R|5|J|7|2U|8|@]|9|@]|A|$K|L]]|$1|S|3|T|5|6|7|2V|8|@$D|2W|E|2X|F|G]]|9|@]|A|$]]|$1|U|3|V|5|J|7|2Y|8|@]|9|@]|A|$K|L]]|$1|W|3|X|5|6|7|2Z|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|30|8|@$D|31|E|32|F|G]]|9|@]|A|$]]|$1|10|3|-4|5|6|7|33|8|@]|9|@]|A|$]]|$1|11|3|12|5|13|7|34|8|@]|9|@$D|35|E|36|1|37]]|A|$]]|$1|14|3|15|5|13|7|38|8|@]|9|@$D|39|E|3A|1|3B]]|A|$]]|$1|16|3|-4|5|6|7|3C|8|@]|9|@]|A|$]]|$1|17|3|18|5|6|7|3D|8|@]|9|@]|A|$]]|$1|19|3|1A|5|6|7|3E|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|3F|8|@$D|3G|E|3H|F|1D]]|9|@]|A|$]]|$1|1E|3|1F|5|J|7|3I|8|@]|9|@]|A|$K|L]]|$1|1G|3|1H|5|6|7|3J|8|@$D|3K|E|3L|F|1D]]|9|@]|A|$]]|$1|1I|3|1J|5|6|7|3M|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|6|7|3N|8|@$D|3O|E|3P|F|1D]]|9|@]|A|$]]|$1|1M|3|1N|5|6|7|3Q|8|@$D|3R|E|3S|F|G]|$D|3T|E|3U|F|G]]|9|@]|A|$]]|$1|1O|3|1P|5|J|7|3V|8|@]|9|@]|A|$K|L]]|$1|1Q|3|-4|5|6|7|3W|8|@]|9|@]|A|$]]|$1|1R|3|1S|5|6|7|3X|8|@]|9|@]|A|$]]|$1|1T|3|-4|5|6|7|3Y|8|@]|9|@]|A|$]]|$1|1U|3|1V|5|1W|7|3Z|8|@]|9|@]|A|$]]|$1|1X|3|-4|5|6|7|40|8|@]|9|@]|A|$]]|$1|1Y|3|-4|5|6|7|41|8|@]|9|@]|A|$]]|$1|1Z|3|20|5|6|7|42|8|@]|9|@]|A|$]]|$1|21|3|22|5|6|7|43|8|@]|9|@]|A|$]]|$1|23|3|24|5|1W|7|44|8|@]|9|@]|A|$]]|$1|25|3|-4|5|6|7|45|8|@]|9|@]|A|$]]|$1|26|3|-4|5|6|7|46|8|@]|9|@]|A|$]]|$1|27|3|28|5|6|7|47|8|@]|9|@]|A|$]]|$1|29|3|-4|5|6|7|48|8|@]|9|@]|A|$]]]|2A|$2B|$5|2C|2D|2E|A|$2F|12]]|2G|$5|2C|2D|2E|A|$2F|15]]]]

<h2>Problem</h2>

The reason you are getting <code>Boolean</code> instead of <code>boolean</code> is that you have <code>minOccurs="0"</code> in your element definition. A <code>null</code> value will be stored for an absent element.

<pre><code>&lt;xs:element name="pricepoint_custom_fields_required" type="xs:boolean" minOccurs="0"/&gt;
</code></pre>

<h2>What the Solution Should Be</h2>

The solution should be an external binding file that indicates that a primitive type should be used for optional values (see section 7.5.1 of the JAXB 2.2 specification).

<pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;jaxb:bindings
 xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
 version="2.1"&gt;
 &lt;jaxb:globalBindings optionalProperty="primitive"/&gt;
&lt;/jaxb:bindings&gt;
</code></pre>

The external binding file is specified using the <code>-b</code> option with XJC.

<pre><code>xjc -b binding.xml my-schema.xsd
</code></pre>

<h2>Why That Solution Does Not Work</h2>

The following bugs have been opened to track the issue with <code>optionalProperty="primitive"</code>.

<ul>
<li><a href="https://github.com/javaee/jaxb-v2/issues/510" rel="noreferrer">https://github.com/javaee/jaxb-v2/issues/510</a></li>
<li><a href="https://github.com/javaee/jaxb-v2/issues/926" rel="noreferrer">https://github.com/javaee/jaxb-v2/issues/926</a></li>
</ul>

<h2>Workaround</h2>

If you don't like the way a class is generated in JAXB, then you can create a class yourself and have JAXB pull it in as part of the schema to class generation.

binding.xml

<pre><code>&lt;jxb:bindings 
 xmlns:xs="http://www.w3.org/2001/XMLSchema"
 xmlns:jxb="http://java.sun.com/xml/ns/jaxb"
 version="2.1"&gt;

 &lt;jxb:bindings schemaLocation="my-schema.xsd"&gt;
 &lt;jxb:bindings node="//xs:element[@name='usage-auth-rate-charge']/complexType"&gt;
 &lt;jxb:class ref="com.example.foo.UsageAuthRateCharge"/&gt;
 &lt;/jxb:bindings&gt;
 &lt;/jxb:bindings&gt;
&lt;/jxb:bindings&gt;
</code></pre>

UsageAuthRateCharge

Create this class with the methods as you want them.

XJC Call

Use the <code>-b</code> flag on the XJC call to specify the <code>binding.xml</code> file

<pre><code>xjc -b binding.xml my-schema.xsd
</code></pre>

<hr>

<h2>UPDATE</h2>

<blockquote>
 What I was really hoping was that one of the readers might be a jaxb
 dev team member who could do the change easily in jaxb. User
 archenroot offered a possible solution in his comments on jaxb issue
 927 (a duplicate of 926) which leads me to think that for the right
 person, it would be a simple job to fix jaxb
</blockquote>

I'm the <a href="http://www.eclipse.org/eclipselink/moxy.php" rel="noreferrer">EclipseLink JAXB (MOXy)</a> lead. I have reached out to my colleagues who do the JAXB reference implementation (they also work for Oracle). Below is the reply I got from them:

<blockquote>
 I’ve tested in trunk - and the problem exists.
 I’ll check code how easy is to fix it.
</blockquote>

Hopefully you will be able to get a real fix for this issue.

blocks|key|210054|text|只是为了让它完整|type|unstyled|depth|inlineStyleRanges|entityRanges|data|210055|type="xs:boolean"+minOccurs="0"+maxOccurs="1"+++++++++++++++++++==+Boolean+value+(object)

type="xs:boolean"+minOccurs="0"+maxOccurs="1"+nillable="true"+++==+JAXBElement<Boolean>+value+(object)

type="xs:boolean"+minOccurs="1"+maxOccurs="1"+++++++++++++++++++==+boolean+value+(primitive)

type="xs:boolean"+minOccurs="1"+maxOccurs="1"+nillable="true"+++==+Boolean+value+(object)|code-block|syntax|javascript|210056|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Just to make it complete

<pre><code>type="xs:boolean" minOccurs="0" maxOccurs="1" == Boolean value (object)

type="xs:boolean" minOccurs="0" maxOccurs="1" nillable="true" == JAXBElement&lt;Boolean&gt; value (object)

type="xs:boolean" minOccurs="1" maxOccurs="1" == boolean value (primitive)

type="xs:boolean" minOccurs="1" maxOccurs="1" nillable="true" == Boolean value (object)
</code></pre>

I'm migrating a project from JAXB 1.0 to JAXB 2.1 and I'm having problems with the datatype mapping.

I'm using the Ant xjc binding compiler, and I've successfully configured the global bindings such that (for example) xs:date maps to java.util.Calendar.

However I'm getting generated methods which return <code>Boolean</code>, whereas I want <code>boolean</code>.

Here is the complex type:

<pre><code>&lt;xs:element name="usage-auth-rate-charge"&gt;
 &lt;xs:complexType&gt;
 &lt;xs:sequence&gt;
 &lt;xs:element name="service-id" type="xs:string"/&gt;
 &lt;xs:element name="pricepoint_custom_fields_required" type="xs:boolean" minOccurs="0"/&gt;
 &lt;/xs:sequence&gt;
 &lt;/xs:complexType&gt;
&lt;/xs:element&gt;
</code></pre>

And the generated class looks like this:

<pre><code>public class UsageAuthRateCharge {
........
public Boolean isPricepointCustomFieldsRequired() {
 return pricepointCustomFieldsRequired;
}
</code></pre>

The problem is that although boxing will work, if the supplied XML doesn't contain a value for <code>pricepoint_custom_fields_required</code>, the class's Boolean field is null, instead of false. So I get NullPointerExceptions when doing something like this:

<pre><code>methodWhichTakesPrimitiveBooleanArg(myUsageAuthRateChargeInstance.isPricepointCustomFieldsRequired());
</code></pre>

because it tries to unbox the Boolean passed in - except it's null.

 
I can't change the schema, and I can't adjust all the client code to do the null checks.

I've set the optionalProperty attribute in my binding.xml as follows:

<pre><code>&lt;globalBindings optionalProperty="primitive"&gt;
</code></pre>

In the spec, it says: "If the attribute’s value is "primitive", it binds as it did in JAXB 1.0"

Yet this is clearly not happening.

How can I solve this problem?

UPDATE:

This is now fixed in jaxb 2.2.9:
<a href="https://java.net/jira/browse/JAXB/fixforversion/16850" rel="nofollow noreferrer">https://java.net/jira/browse/JAXB/fixforversion/16850</a>

JAXB compiler is binding xs:boolean to Java Boolean wrapper class, instead of boolean primitive type

编译器

我正在将一个项目从JAXB 1.0迁移到JAXB 2.1，但在数据类型映射方面遇到了问题。我使用的是Ant xjc绑定编译器，并且我已经成功地配置了全局绑定，使(例如) xs:date映射到java.util.Calendar。然而，我得到的是返回Boolean的生成方法，而我想要的是boolean。下面是复杂类型：<...

问JAXB编译器正在将xs:boolean绑定到Java布尔包装类，而不是布尔原语类型
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问JAXB编译器正在将xs:boolean绑定到Java布尔包装类，而不是布尔原语类型EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问JAXB编译器正在将xs:boolean绑定到Java布尔包装类，而不是布尔原语类型
EN