JAXB XJC compiler disregarding mixed=true on XML Schema documents

Question

XJC seems to be completely ignoring mixed=\"true\" on my XML Schema elements thereby not allowing me to extract text content. From the sample XML below, I need to b

Answer 1

http://blogs.oracle.com/mgrebac/entry/handling_extended_mixed_content_in

This worked! Just create a binding file like so:

<?xml version="1.0" encoding="UTF-8"?>
<jaxb:bindings
 xmlns:jaxb="http://java.sun.com/xml/ns/jaxb" jaxb:version="2.0"
 xmlns:xjc= "http://java.sun.com/xml/ns/jaxb/xjc" jaxb:extensionBindingPrefixes="xjc">
  <jaxb:globalBindings generateMixedExtensions="true"/>
</jaxb:bindings>

Then use the -b parameter on the command line with the way you usually do it.

Answer 2

After more research I could do nothing but conclude it was a bug which I filed. It was acknowledged as JAXB issue #792.

Answer 3

Years pass by, but this scheme keeps troubling people! I've been struggling with this same XSD (HL7) for the past few days, especially for handling the mixed content element types.

My initial requirment was the opposite of the original poster, as I needed to write simple text inside a mixed element. But I must be able to also read such content, so I applied the same solution suggested in another reply, that is creating a custom binding file and using it in Eclipse's "JAXB Classes from Schema" wizard. In that case you can specifically choose which binding file(s) to use in one of the wizard's dialogs.

As a result, classes are generated with a List<Serializable> content whenever a mixed element type is found. It gets a bit tricky to extract the single piece of information you actually need, but at least you're sure you can programatically access anything that's present in an XML file adhering that XSD.

You can even navigate into more complex mixed contents such as:

<v3:name>
    <v3:given>Sample Given Name</v3:given>
    <v3:family>Sample Family Name</v3:family>
</v3:name>

Where name is defined as such (I removed content not useful for this example from the original XSD):

<xs:complexType name="EN" mixed="true">
    <xs:complexContent>
        <xs:sequence>
            <xs:choice minOccurs="0" maxOccurs="unbounded">
                <xs:element name="delimiter" type="en.delimiter"/>
                <xs:element name="family" type="en.family"/>
                <xs:element name="given" type="en.given"/>
                <xs:element name="prefix" type="en.prefix"/>
                <xs:element name="suffix" type="en.suffix"/>
            </xs:choice>
        </xs:sequence>
    </xs:complexContent>
</xs:complexType>

Types en.family, en.given and such are mixed themselves (and for our purpose we don't need to know anything else).

So, when you access name's content, its List<Serializable> will be composed of:

1. a String, being the blanks between <v3:name> and <v3:given>
2. an EnGiven element
3. a String, being the blanks between </v3:given> and <v3:family>
4. an EnFamily element
5. a String, being the blanks between </v3:family> and </v3:name>

EnGiven and EnFamily's content will be each made of a single String, respectively "Sample Given Name" and "Sample Family Name". Again, it is a bit tricky, and you have probably have to put some logic to handle the specific cases, but you can manage it this way.

By the way, populating an element is trivial: just add a String to the desired List<Serializable> content.