com.fasterxml.jackson.databind.ser.std

Class TokenBufferSerializer

java.lang.Object

com.fasterxml.jackson.databind.JsonSerializer<T>

com.fasterxml.jackson.databind.ser.std.StdSerializer<TokenBuffer>

com.fasterxml.jackson.databind.ser.std.TokenBufferSerializer

All Implemented Interfaces:

JsonFormatVisitable, SchemaAware, Serializable

public class TokenBufferSerializer
extends StdSerializer<TokenBuffer>

We also want to directly support serialization of TokenBuffer; and since it is part of core package, it can not implement JsonSerializable (which is only included in the mapper package)

See Also:

Serialized Form

Nested Class Summary

Nested classes/interfaces inherited from class com.fasterxml.jackson.databind.JsonSerializer

JsonSerializer.None

Field Summary

Fields inherited from class com.fasterxml.jackson.databind.ser.std.StdSerializer

_handledType

Constructor Summary

Constructors

Constructor and Description
TokenBufferSerializer()

Method Summary

Methods

Modifier and Type	Method and Description
void	acceptJsonFormatVisitor(JsonFormatVisitorWrapper visitor, JavaType typeHint) Default implementation specifies no format.
JsonNode	getSchema(SerializerProvider provider, Type typeHint) Default implementation simply claims type is "string"; usually overriden by custom serializers.
void	serialize(TokenBuffer value, com.fasterxml.jackson.core.JsonGenerator jgen, SerializerProvider provider) Method that can be called to ask implementation to serialize values of type this serializer handles.
void	serializeWithType(TokenBuffer value, com.fasterxml.jackson.core.JsonGenerator jgen, SerializerProvider provider, TypeSerializer typeSer) Implementing typed output for contents of a TokenBuffer is very tricky, since we do not know for sure what its contents might look like (or, rather, we do know when serializing, but not necessarily when deserializing!) One possibility would be to check the current token, and use that to determine if we would output JSON Array, Object or scalar value.

Methods inherited from class com.fasterxml.jackson.databind.ser.std.StdSerializer

createObjectNode, createSchemaNode, createSchemaNode, findConvertingContentSerializer, findPropertyFilter, getSchema, handledType, isDefaultSerializer, wrapAndThrow, wrapAndThrow

Methods inherited from class com.fasterxml.jackson.databind.JsonSerializer

getDelegatee, isEmpty, isEmpty, isUnwrappingSerializer, replaceDelegatee, unwrappingSerializer, usesObjectId

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

TokenBufferSerializer

public TokenBufferSerializer()

Method Detail

serialize

public void serialize(TokenBuffer value,
             com.fasterxml.jackson.core.JsonGenerator jgen,
             SerializerProvider provider)
               throws IOException,
                      com.fasterxml.jackson.core.JsonGenerationException

Description copied from class: JsonSerializer

Method that can be called to ask implementation to serialize values of type this serializer handles.

Specified by:

serialize in class StdSerializer<TokenBuffer>

Parameters:

value - Value to serialize; can not be null.

jgen - Generator used to output resulting Json content

provider - Provider that can be used to get serializers for serializing Objects value contains, if any.

Throws:

IOException

com.fasterxml.jackson.core.JsonGenerationException

serializeWithType

public final void serializeWithType(TokenBuffer value,
                     com.fasterxml.jackson.core.JsonGenerator jgen,
                     SerializerProvider provider,
                     TypeSerializer typeSer)
                             throws IOException,
                                    com.fasterxml.jackson.core.JsonGenerationException

Implementing typed output for contents of a TokenBuffer is very tricky, since we do not know for sure what its contents might look like (or, rather, we do know when serializing, but not necessarily when deserializing!) One possibility would be to check the current token, and use that to determine if we would output JSON Array, Object or scalar value. Jackson 1.5 did NOT include any type information; but this seems wrong, and so 1.6 WILL include type information.

Note that we just claim it is scalar; this should work ok and is simpler than doing introspection on both serialization and deserialization.

Overrides:

serializeWithType in class JsonSerializer<TokenBuffer>

Parameters:

value - Value to serialize; can not be null.

jgen - Generator used to output resulting Json content

provider - Provider that can be used to get serializers for serializing Objects value contains, if any.

typeSer - Type serializer to use for including type information

Throws:

IOException

com.fasterxml.jackson.core.JsonGenerationException

getSchema

public JsonNode getSchema(SerializerProvider provider,
                 Type typeHint)

Description copied from class: StdSerializer

Default implementation simply claims type is "string"; usually overriden by custom serializers.

Specified by:

getSchema in interface SchemaAware

Overrides:

getSchema in class StdSerializer<TokenBuffer>

Parameters:

provider - The serializer provider.

typeHint - A hint about the type.

Returns:

Json-schema for this serializer.

acceptJsonFormatVisitor

public void acceptJsonFormatVisitor(JsonFormatVisitorWrapper visitor,
                           JavaType typeHint)
                             throws JsonMappingException

Description copied from class: StdSerializer

Default implementation specifies no format. This behavior is usually overriden by custom serializers.

Specified by:

acceptJsonFormatVisitor in interface JsonFormatVisitable

Overrides:

acceptJsonFormatVisitor in class StdSerializer<TokenBuffer>

typeHint - Type of element (entity like property) being visited

Throws:

JsonMappingException