package com.fasterxml.jackson.annotation;

import java.lang.annotation.ElementType;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;

/**
 * Marker annotation that indicates that the annotated method or field is to be
 * ignored by introspection-based
 * serialization and deserialization functionality. That is, it should
 * not be consider a "getter", "setter" or "creator".
 *<p>
 * In addition, starting with Jackson 1.9, if this is the only annotation
 * associated with a property, it will also cause cause the whole
 * property to be ignored: that is, if setter has this annotation and
 * getter has no annotations, getter is also effectively ignored.
 * It is still possible for different accessors to use different
 * annotations; so if only "getter" is to be ignored, other accessors
 * (setter or field) would need explicit annotation to prevent
 * ignoral (usually {@link JsonProperty}).
 * <p>
 * For example, a "getter" method that would otherwise denote
 * a property (like, say, "getValue" to suggest property "value")
 * to serialize, would be ignored and no such property would
 * be output unless another annotation defines alternative method to use.
 *<p>
 * Before version 1.9, this annotation worked purely on method-by-method (or field-by-field)
 * basis; annotation on one method or field did not imply ignoring other methods
 * or fields. However, with version 1.9 and above, annotations associated
 * with various accessors (getter, setter, field, constructor parameter) of
 * a logical property are combined; meaning that annotations in one (say, setter)
 * can have effects on all of them (if getter or field has nothing indicating
 * otherwise).
 *<p>
 * Annotation is usually used just a like a marker annotation, that
 * is, without explicitly defining 'value' argument (which defaults
 * to <code>true</code>): but argument can be explicitly defined.
 * This can be done to override an existing JsonIgnore by explicitly
 * defining one with 'false' argument.
 *<p>
 * Annotation is similar to {@link javax.xml.bind.annotation.XmlTransient} 
 */
@Target({ElementType.ANNOTATION_TYPE, ElementType.METHOD, ElementType.CONSTRUCTOR, ElementType.FIELD})
@Retention(RetentionPolicy.RUNTIME)
@JacksonAnnotation
public @interface JsonIgnore
{
    /**
     * Optional argument that defines whether this annotation is active
     * or not. The only use for value 'false' if for overriding purposes
     * (which is not needed often); most likely it is needed for use
     * with "mix-in annotations" (aka "annotation overrides").
     * For most cases, however, default value of "true" is just fine
     * and should be omitted.
     */
    boolean value() default true;
}

@@ -251,728 +251,888 @@
 the 
-annotated method or field is to be%0A * ignored by introspection-based%0A * serialization and deserialization functionality. That is, it should%0A * not be consider a %22getter%22, %22setter%22
+logical property that%0A * the accessor (field, getter/setter method or Creator parameter%0A * %5Bof %7B@link JsonCreator%7D-annotated constructor or factory method%5D)%0A * is to be ignored by introspection-based%0A * serialization and deserialization functionality.%0A * Annotation only needs to be added to one of the accessors (often%0A * getter method, but may be setter, field
  or 
-%22
 creator
-%22.%0A *%3Cp%3E%0A * In addition, starting with Jackson 1.9, if this is the only annotation%0A * associated with a property, it will also cause cause the whole%0A * property to be ignored: that is, if setter has this annotation and%0A * getter has no annotations, getter is also effectively ignored.%0A * It is still possible for different accessors to use different
+ parameter),%0A * if the complete removal of the property is desired.%0A * However: if only particular accessor is to be ignored (for example,%0A * when ignoring one of potentially conflicting setter methods),%0A * this can be done by annotating other not-to-be-ignored accessors%0A * with %7B@link JsonProperty%7D (or its equivalents). This is considered
 %0A * 
-annotations; so if only %22getter%22 is to be ignored, other accessors%0A * (setter or field) would need explicit annotation to prevent%0A * ignoral (usually %7B@link JsonProperty%7D).
+so-called %22split property%22 case and allows definitions of%0A * %22read-only%22 (read from input into POJO) and %22write-only%22 (write%0A * in output but ignore on output)
 %0A *
- 
 %3Cp%3E%0A
@@ -1407,502 +1407,252 @@
 %0A * 
-Before version 1.9, this annotation worked purely on method-by-method (or field-by-field)%0A * basis; annotation on one method or field did not imply ignoring other methods%0A * or fields. However, with version 1.9 and above, annotations associated%0A * with various accessors (getter, setter, field, constructor parameter) of%0A * a logical property are combined; meaning that annotations in one (say, setter)%0A * can have effects on all of them (if getter or field has nothing indicating%0A * otherwise)
+When ignoring the whole property, the default behavior if encountering%0A * such property in input is to ignore it without exception; but if there%0A * is a %7B@link JsonAnySetter%7D it will be called instead. Either way,%0A * no exception will be thrown
 .%0A *
@@ -1901,16 +1901,17 @@
 xisting 
+%60
 JsonIgno
@@ -1912,16 +1912,17 @@
 onIgnore
+%60
  by expl
@@ -1969,91 +1969,69 @@
 ment
-.%0A *%3Cp%3E%0A * Annotation is similar to %7B@link javax.xml.bind.annotation.XmlTransient%7D 
+: either in a sub-class, or by%0A * using %22mix-in annotations%22.
 %0A */

Improve `@JsonIgnore` javadocs