Databases
StackOverflow2013
Postsdbo
POXML schema method naming inconsistency
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POXML schema method naming inconsistency
    primarykey
    data
    text
    <p>I am hoping someone has experienced this issue and can maybe shed some light.</p> <p>I have an xml schema and an ant build file. The output .java files differ when I run ant on Windows versus Mac, even if I am using the same jaxb-xjc.jar to do the xml-compiling. The Windows side is naming the "getter" methods for attributes as "getX". The Mac side wants to name them "isX". Anyone experience anything like this before and/or have a solution? This is consistent between Windows Vista &amp; 7 doing this the one way and Mac OSX 10.6 &amp; 10.7 (untested on Mac OSX 10.8) doing it the other.</p> <p>----edit----</p> <p>I'll attach some of the code from the ant build.xml file.</p> <p>Telling it what the xjc is.</p> <pre><code>&lt;taskdef name="xjc" classname="com.sun.tools.xjc.XJCTask"&gt; &lt;classpath refid="classpath"/&gt; &lt;/taskdef&gt; </code></pre> <p>Here is the 'actual' compiling:</p> <p> Compiling the automaton schema </p> <pre><code> &lt;echo&gt;Compiling old automaton schema&lt;/echo&gt; &lt;xjc schema="${oldxml-schema}" destdir="${src.dir}" package="${oldxml.package}"&gt; &lt;produces dir="${oldxml-gen.dir}" includes="**/*.java"/&gt; &lt;/xjc&gt; &lt;echo&gt;Compiling the plugin schema&lt;/echo&gt; &lt;mkdir dir="${plugin-gen.dir}" /&gt; &lt;xjc schema="${plugin-schema}" destdir="${src.dir}" package="${plugin.package}"&gt; &lt;produces dir="${plugin-gen.dir}" includes="**/*.java"/&gt; &lt;/xjc&gt; &lt;echo&gt;Compiling the pluginDesumaSide schema&lt;/echo&gt; &lt;mkdir dir="${pluginDesumaSide-gen.dir}" /&gt; &lt;xjc schema="${pluginDesumaSide-schema}" destdir="${src.dir}" package="${pluginDesumaSide.package}"&gt; &lt;produces dir="${pluginDesumaSide-gen.dir}" includes="**/*.java"/&gt; &lt;/xjc&gt; &lt;/target&gt; </code></pre> <p>All targets (by that I mean anything mentioned like ${}) are defined and every links and compiles right except for Mac naming the 'getter' methods as 'is' methods for variables. They are boolean attributes that do have defaults if non-specified.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJonathan Leffler
    1. USLan
    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. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COPlease include more information. What tool are you using with this XML Schema? It appears you are generating code?
      singulars
      1. POXML schema method naming inconsistency
      1. USJohn Saunders
    2. COWhat versions of the JDK are you using?
      singulars
      1. POXML schema method naming inconsistency
      1. USBlaise Doughan
    3. CO@JohnSaunders BlaiseDoughan The inconsistency has been spotted with Java 1.6.23, 1.6.26 for Mac & Windows and the Windows running 1.7.? generates getX functions. I am using the jaxb-xjc.jar binding compiler. When I run java -jar jaxb-xjc.jar -version it responds "hudson-jaxb-ri-2.1-661". I am using the schema to generate classes which are later used to 'load' xml files for the program.
      singulars
      1. POXML schema method naming inconsistency
      1. USLan
 

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