Prevent JAXB from creating JAXBElements

I had some annoying trouble with updating JAXB1.0 code into JAXB2.0 code, among which the one of the things is the generation og JAXBElements instead normal type, like JAXBElements instead of simple double.
This is due to fact that JAXB wants to define cases of elements in XSD with minOccurs="0" and nillable="true". If you don't care about such issue, then you can prevent JAXB from creating the JAXBElements in a following way:

Add to your command line generation -b addCFG.xjb
where addCFG.xjb is this file:
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
jaxb:version="2.0">



source:

Comments

Post a Comment

Popular posts from this blog

Exporting Skype Chat/Skype Contacts to csv file using the shell script and sqlite3 (usually already installed on mac)

Edit: a very first draft version of Skype Exporter have been made and released. https://github.com/renesto/SkypeExportSwift/releases check it, and report any issues to renesto-at-gmail.com I heard there are not so many nice ways to get the chat history from skype, so I came across a page of one guy who shows a way to open the sql chat history database and delete all conversations. I thought to make something more from that idea (as delete chat history is now one of the options in skype) Create a file exportFromSkype.sh place either this text: sqlite3 -batch "$HOME/Library/Application Support/Skype/$1/main.db" < <EOF .mode csv .output $2.csv select * from Messages where dialog_partner = '$2'; .output stdout .exit EOF now make the script executable by running chmod +x exportFromSkype.sh now, when you want to export some chat history from certain person, you can do it by: sh exportFromSkype.sh your_skype_name your_friends_skype_name and i...
Read more

Javascript comparison operators

I came across very nice short explanation of the differences between == and === comparison operators. I have copied this into my blog just in case the post gets deleted from stackoverflow for whatever reason. The identity (===) operator behaves identically to the equality (==) operator except no type conversion is done, and the types must be the same to be considered equal. Reference: Javascript Tutorial: Comparison Operators The == operator will compare for equality after doing any necessary type conversions . The === operator will not do the conversion, so if two values are not the same type === will simply return false. It's this case where === will be faster, and may return a different result than ==. In all other cases performance will be the same. To quote Douglas Crockford's excellent JavaScript: The Good Parts , JavaScript has two sets of equality operators: === and !== , and their evil twins == and != . The good ones work the way you would expect. ...
Read more

trim() not supported by IE7 and IE8

Funny fact, trim function is not supported by IE7 and IE8. Ok, it is supported, but through jQuery trim function. So, when you have something like this: jQuery(...).attr().trim() , this trim() function stops having any relation to jQuery, as the attr() would return String type, which method would be then trim(). Since IE7 and IE8 do not support trim() method within String type, you should use instead jQuery.trim(jQuery(...).attr()) or if you don't wanna use jQuery (whyyyy?), you can simply implement the trim function youself. if(typeof String.prototype.trim !== 'function') { String.prototype.trim = function() { return this.replace(/^\s+|\s+$/g, ''); } } http://www.blogger.com/img/blank.gif source 1 source 2
Read more