Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It is possible to achieve this for this simple case without using a 3rd Party plugin using the <a href="http://docs.oracle.com/cd/E17802_01/webservices/webservices/docs/2.0/jaxb/vendorCustomizations.html" rel="nofollow" title="JAXB RI Vendor Extensions">JAXB RI Vendor Extensions</a> xjc:superInterface customization. It should be noted this approach will cause all generated classes to implement the interface. </p> <p>Example bindings file:</p> <pre><code>&lt;jxb:bindings version="1.0" 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"&gt; &lt;jxb:bindings schemaLocation="adult.xsd" node="/xs:schema"&gt; &lt;jxb:globalBindings&gt; &lt;xjc:superInterface name="com.example.model.Person"/&gt; &lt;/jxb:globalBindings&gt; &lt;/jxb:bindings&gt; &lt;/jxb:bindings&gt; </code></pre> <p>You then just need to run <a href="http://docs.oracle.com/cd/E17802_01/webservices/webservices/docs/1.6/jaxb/xjc.html" rel="nofollow">xjc</a> specifying the binding file and setting the -extension flag. Much quicker/simpler than bringing in JAXB2Basics!</p> <p>I was initially sceptical that this would work as the documentation states:</p> <blockquote> <p>The customization allows you to specify the fully qualified name of the Java interface that is to be used as the root interface of all the generated interfaces. This customization has no effect unless you are specifically generating interfaces with the globalBindings generateValueClass="false" switch.</p> </blockquote> <p>But when I tried it out with a bindings similar to the one above (without specifying generateValueClass="false", and generating classes, not interfaces), it gave me the output I required - all my generated classes implemented the common interface. </p>
    singulars
    1. This table or related slice is empty.
    1. POGenerating a JAXB class that implements an interface
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMalcolm Smith
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    1. COthis is not what the person asked (and usually, what most of the people want) as, as you said, this would make ALL the classes implement the same interface which is, most of the times, useless.
      singulars
      1. PO
      1. USClint Eastwood
    2. CONo, this is exactly what OP wanted; two schemas that generate two classes both implementing the same interface. It also happened to be a requirement I had in a real world project, so some times isn't useless at all. It is a fairly poorly documented area of JAXB, I don't think putting an example of its usage out there is a problem.
      singulars
      1. PO
      1. USMalcolm Smith
    3. COIf JAXB generates more than two classes, adding a global binding section using <xjc:superInterface> will result in ALL of the classes implementing the Person interface, which doesn't seem to be reasonable for a domain consisting of more than two classes where not all the objects are persons.
      singulars
      1. PO
      1. USClint Eastwood
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload