Comparison with Jackson
Juneau was developed independently from Jackson, but shares many of the same features and capabilities. Whereas Jackson was created to work primarily with JSON, Juneau was created to work for multiple languages. Therefore, the terminology and annotations in Juneau are similar, but language-agnostic.
The following charts describe equivalent features between the two libraries:
Jackson | Juneau |
---|---|
|
{@link oaj.annotation.Beanp @Beanp} |
|
{@link oaj.annotation.Beanp#name() @Beanp(name="*")} |
|
{@link oaj.annotation.BeanIgnore @BeanIgnore} |
{@link oaj.annotation.Bean#bpx @Bean(bpx="...")} | |
No equivalent annotation, but can be controlled via:
{@link oaj.BeanContext#BEAN_beanFieldVisibility BEAN_beanFieldVisibility} {@link oaj.BeanContext#BEAN_beanMethodVisibility BEAN_beanMethodVisibility} Future annotation support planned. |
|
|
{@link oaj.annotation.Beanc @Beanc} |
No equivalent.
Future support planned. |
|
|
Juneau uses swaps to convert non-serializable object to serializable forms:
{@link oaj.annotation.Swap @Swap} |
No equivalent annotation, but can be controlled via various settings:
{@link oaj.BeanContext} {@link oaj.serializer.Serializer} Future annotation support planned. |
|
{@link oaj.annotation.Bean#properties @Bean(bpi="...")}
{@link oaj.annotation.Bean#sort @Bean(sort=x)} |
|
|
Can be replicated using swaps with |