11

I am using ant wsimport to generate client stub from the wsdls. Also, I would like to generate client classes that implements Serializable. I would like to generate a different serialVersionUID for each class. I tried with the binding file that was shown below. But its generating same serialVersionUID for all the classes. Is there any way I can give my own serialVersionUID to each class?

<wsimport xendorsed="true" binding="binding.xml" debug="true" keep="true" 
verbose="false"  sourcedestdir="${generated}" wsdl="${src}${wsdl.file}"
wsdlLocation="${wsdl.file}">
</wsimport>

binding configuration

<bindings xmlns="http://java.sun.com/xml/ns/jaxb" version="2.0" xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <globalBindings>   
        <serializable uid="1" />        
    </globalBindings>    
</bindings>
Xstian
  • 8,184
  • 10
  • 42
  • 72
javageek
  • 111
  • 1
  • 3
  • Waitaminute... If you implement `Serializable` you are binding yourself for a contract for life; generating _random_ UUIDs? – fge Dec 15 '14 at 05:47
  • @fge The OP does not say he wants random `uid`s, the OP wants different `uid`s for different classes (i.e. not always the same/`1`). Theoretically it is possible to generate a `uid` based on the contents of the class. Different contents - different `uid`s. So the question makes sense to me. – lexicore Dec 15 '14 at 07:22
  • `` customization can only occur within your `` [see here](https://jaxb.java.net/jaxb20-ea/docs/vendorCustomizations.html). Anyway you can add a work around using binding for each element generated. – Xstian Dec 15 '14 at 09:19
  • 1
    why do they need to be unique? – jtahlborn Dec 21 '14 at 02:23
  • Possible duplicate of [How to generate a Java class which implements Serializable interface from xsd using JAXB?](http://stackoverflow.com/questions/1513972/how-to-generate-a-java-class-which-implements-serializable-interface-from-xsd-us) – OrangeDog Jan 03 '17 at 16:29

2 Answers2

3

Just for the record, there is no way to generate a unique serialVersionUID for each generated class because it doesn't make sense to do so.

Let me explain : A serialVersionUID represents a version of your class at a particular point in time. If you modify your class, your serialVersionUID should change. So when the JDK deserialize objects of the same class, it knows to which version of your class to deserialize it to.

In the case of JAXB, since you generate all your classes at once every time it doesn't make sense to version all the classes individually. Simply because they can only change as a group. (Unless you take them out of your target folder..)

I hope that makes a little bit more sense.

Tinou
  • 5,908
  • 4
  • 21
  • 24
2

This is the binding file we use, which does the trick for us.

<xs:schema elementFormDefault="qualified" version="1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
xmlns:xjc="http://java.sun.com/xml/ns/jaxb/xjc" jaxb:version="2.0"
jaxb:extensionBindingPrefixes="xjc">
<xs:annotation>
    <xs:appinfo>
        <jaxb:globalBindings>
            <xjc:serializable />
        </jaxb:globalBindings>
    </xs:appinfo>
</xs:annotation>

Cube
  • 21
  • 2
  • No, it’s not a complete schema, but the relevant bit to insert into your schema. At least, it did the trick to insert these lines into my WSDL file. – Michael Piefel Feb 01 '17 at 11:17