Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>They adhere to a clear <strong>specification</strong>.</p> <p>Thanks to this there are insanely a lot of tools to ease working with Javabeans (or just the other way round). There are tools which can autogenerate them based on some data in a certain flavor (<a href="http://xstream.codehaus.org/" rel="nofollow noreferrer">XML</a>, <a href="http://code.google.com/p/google-gson/" rel="nofollow noreferrer">JSON</a>, <a href="http://opencsv.sourceforge.net" rel="nofollow noreferrer">CSV</a>, <a href="http://www.vogella.de/articles/EclipseDali/article.html" rel="nofollow noreferrer">DDL</a>, etc) and/or vice versa, as well to read/manipulate/map them like <a href="http://commons.apache.org/beanutils/" rel="nofollow noreferrer">Commons BeanUtils</a>, <a href="http://dozer.sourceforge.net/" rel="nofollow noreferrer">Dozer</a>, <a href="http://ezmorph.sourceforge.net/" rel="nofollow noreferrer">EZMorph</a>, etcetera. Further there are a lot of MVC/ORM frameworks which works with Javabeans, like <a href="http://download.oracle.com/javaee/6/tutorial/doc/bnbpy.html" rel="nofollow noreferrer">JPA</a>, <a href="https://www.hibernate.org/" rel="nofollow noreferrer">Hibernate</a>, <a href="http://download.oracle.com/javaee/6/tutorial/doc/bnaph.html" rel="nofollow noreferrer">JSF</a>, <a href="http://www.springsource.org" rel="nofollow noreferrer">Spring</a>, etc. Even a bit decent IDE like Eclipse knows how to autogenerate Javabeans based on just some fields.</p> <p>It are the tools and frameworks around Javabeans which makes our life easier. It is the Javabeans specification which made those things exist.</p>
 

Querying!

 
Guidance

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