com.google.protobuf.compiler

Class PluginProtos.CodeGeneratorResponse.File

java.lang.Object

com.google.protobuf.AbstractMessageLite<MessageType,BuilderType>

com.google.protobuf.GeneratedMessageLite<PluginProtos.CodeGeneratorResponse.File,PluginProtos.CodeGeneratorResponse.File.Builder>

com.google.protobuf.compiler.PluginProtos.CodeGeneratorResponse.File

All Implemented Interfaces:

PluginProtos.CodeGeneratorResponse.FileOrBuilder, MessageLite, MessageLiteOrBuilder

Enclosing class:

PluginProtos.CodeGeneratorResponse

public static final class PluginProtos.CodeGeneratorResponse.File
extends GeneratedMessageLite<PluginProtos.CodeGeneratorResponse.File,PluginProtos.CodeGeneratorResponse.File.Builder>
implements PluginProtos.CodeGeneratorResponse.FileOrBuilder

 Represents a single generated file.
 

Protobuf type google.protobuf.compiler.CodeGeneratorResponse.File

Nested Class Summary

Nested Classes

Modifier and Type	Class and Description
static class	PluginProtos.CodeGeneratorResponse.File.Builder Represents a single generated file.

Nested classes/interfaces inherited from class com.google.protobuf.GeneratedMessageLite

GeneratedMessageLite.DefaultInstanceBasedParser<T extends GeneratedMessageLite<T,?>>, GeneratedMessageLite.ExtendableBuilder<MessageType extends GeneratedMessageLite.ExtendableMessage<MessageType,BuilderType>,BuilderType extends GeneratedMessageLite.ExtendableBuilder<MessageType,BuilderType>>, GeneratedMessageLite.ExtendableMessage<MessageType extends GeneratedMessageLite.ExtendableMessage<MessageType,BuilderType>,BuilderType extends GeneratedMessageLite.ExtendableBuilder<MessageType,BuilderType>>, GeneratedMessageLite.ExtendableMessageOrBuilder<MessageType extends GeneratedMessageLite.ExtendableMessage<MessageType,BuilderType>,BuilderType extends GeneratedMessageLite.ExtendableBuilder<MessageType,BuilderType>>, GeneratedMessageLite.GeneratedExtension<ContainingType extends MessageLite,Type>, GeneratedMessageLite.MergeFromVisitor, GeneratedMessageLite.MethodToInvoke, GeneratedMessageLite.SerializedForm, GeneratedMessageLite.Visitor

Field Summary

Fields

Modifier and Type	Field and Description
static int	CONTENT_FIELD_NUMBER
static int	INSERTION_POINT_FIELD_NUMBER
static int	NAME_FIELD_NUMBER

Fields inherited from class com.google.protobuf.GeneratedMessageLite

memoizedSerializedSize, unknownFields

Fields inherited from class com.google.protobuf.AbstractMessageLite

memoizedHashCode

Method Summary

Modifier and Type	Method and Description
protected Object	dynamicMethod(GeneratedMessageLite.MethodToInvoke method, Object arg0, Object arg1) A method that implements different types of operations described in GeneratedMessageLite.MethodToInvoke.
String	getContent() The file contents.
ByteString	getContentBytes() The file contents.
static PluginProtos.CodeGeneratorResponse.File	getDefaultInstance()
String	getInsertionPoint() If non-empty, indicates that the named file should already exist, and the content here is to be inserted into that file at a defined insertion point.
ByteString	getInsertionPointBytes() If non-empty, indicates that the named file should already exist, and the content here is to be inserted into that file at a defined insertion point.
String	getName() The file name, relative to the output directory.
ByteString	getNameBytes() The file name, relative to the output directory.
int	getSerializedSize() Get the number of bytes required to encode this message.
boolean	hasContent() The file contents.
boolean	hasInsertionPoint() If non-empty, indicates that the named file should already exist, and the content here is to be inserted into that file at a defined insertion point.
boolean	hasName() The file name, relative to the output directory.
static PluginProtos.CodeGeneratorResponse.File.Builder	newBuilder()
static PluginProtos.CodeGeneratorResponse.File.Builder	newBuilder(PluginProtos.CodeGeneratorResponse.File prototype)
static PluginProtos.CodeGeneratorResponse.File	parseDelimitedFrom(InputStream input)
static PluginProtos.CodeGeneratorResponse.File	parseDelimitedFrom(InputStream input, ExtensionRegistryLite extensionRegistry)
static PluginProtos.CodeGeneratorResponse.File	parseFrom(byte[] data)
static PluginProtos.CodeGeneratorResponse.File	parseFrom(byte[] data, ExtensionRegistryLite extensionRegistry)
static PluginProtos.CodeGeneratorResponse.File	parseFrom(ByteString data)
static PluginProtos.CodeGeneratorResponse.File	parseFrom(ByteString data, ExtensionRegistryLite extensionRegistry)
static PluginProtos.CodeGeneratorResponse.File	parseFrom(CodedInputStream input)
static PluginProtos.CodeGeneratorResponse.File	parseFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)
static PluginProtos.CodeGeneratorResponse.File	parseFrom(InputStream input)
static PluginProtos.CodeGeneratorResponse.File	parseFrom(InputStream input, ExtensionRegistryLite extensionRegistry)
static Parser<PluginProtos.CodeGeneratorResponse.File>	parser()
void	writeTo(CodedOutputStream output) Serializes the message and writes it to output.

Methods inherited from class com.google.protobuf.GeneratedMessageLite

dynamicMethod, dynamicMethod, emptyBooleanList, emptyDoubleList, emptyFloatList, emptyIntList, emptyLongList, emptyProtobufList, equals, getDefaultInstanceForType, getParserForType, hashCode, isInitialized, isInitialized, makeImmutable, makeImmutable, mergeLengthDelimitedField, mergeUnknownFields, mergeVarintField, mutableCopy, mutableCopy, mutableCopy, mutableCopy, mutableCopy, mutableCopy, newBuilderForType, newRepeatedGeneratedExtension, newSingularGeneratedExtension, parseDelimitedFrom, parseDelimitedFrom, parseFrom, parseFrom, parseFrom, parseFrom, parseFrom, parseFrom, parseFrom, parseFrom, parsePartialFrom, parseUnknownField, toBuilder, toString

Methods inherited from class com.google.protobuf.AbstractMessageLite

addAll, checkByteStringIsUtf8, toByteArray, toByteString, writeDelimitedTo, writeTo

Methods inherited from class java.lang.Object

clone, finalize, getClass, notify, notifyAll, wait, wait, wait

Methods inherited from interface com.google.protobuf.MessageLiteOrBuilder

getDefaultInstanceForType, isInitialized

Field Detail

NAME_FIELD_NUMBER

public static final int NAME_FIELD_NUMBER

See Also:

Constant Field Values

INSERTION_POINT_FIELD_NUMBER

public static final int INSERTION_POINT_FIELD_NUMBER

See Also:

Constant Field Values

CONTENT_FIELD_NUMBER

public static final int CONTENT_FIELD_NUMBER

See Also:

Constant Field Values

Method Detail

hasName

public boolean hasName()

 The file name, relative to the output directory.  The name must not
 contain "." or ".." components and must be relative, not be absolute (so,
 the file cannot lie outside the output directory).  "/" must be used as
 the path separator, not "\".
 If the name is omitted, the content will be appended to the previous
 file.  This allows the generator to break large files into small chunks,
 and allows the generated text to be streamed back to protoc so that large
 files need not reside completely in memory at one time.  Note that as of
 this writing protoc does not optimize for this -- it will read the entire
 CodeGeneratorResponse before writing files to disk.
 

optional string name = 1;

Specified by:

hasName in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder

getName

public String getName()

 The file name, relative to the output directory.  The name must not
 contain "." or ".." components and must be relative, not be absolute (so,
 the file cannot lie outside the output directory).  "/" must be used as
 the path separator, not "\".
 If the name is omitted, the content will be appended to the previous
 file.  This allows the generator to break large files into small chunks,
 and allows the generated text to be streamed back to protoc so that large
 files need not reside completely in memory at one time.  Note that as of
 this writing protoc does not optimize for this -- it will read the entire
 CodeGeneratorResponse before writing files to disk.
 

optional string name = 1;

Specified by:

getName in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder

getNameBytes

public ByteString getNameBytes()

 The file name, relative to the output directory.  The name must not
 contain "." or ".." components and must be relative, not be absolute (so,
 the file cannot lie outside the output directory).  "/" must be used as
 the path separator, not "\".
 If the name is omitted, the content will be appended to the previous
 file.  This allows the generator to break large files into small chunks,
 and allows the generated text to be streamed back to protoc so that large
 files need not reside completely in memory at one time.  Note that as of
 this writing protoc does not optimize for this -- it will read the entire
 CodeGeneratorResponse before writing files to disk.
 

optional string name = 1;

Specified by:

getNameBytes in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder

hasInsertionPoint

public boolean hasInsertionPoint()

 If non-empty, indicates that the named file should already exist, and the
 content here is to be inserted into that file at a defined insertion
 point.  This feature allows a code generator to extend the output
 produced by another code generator.  The original generator may provide
 insertion points by placing special annotations in the file that look
 like:
   @@protoc_insertion_point(NAME)
 The annotation can have arbitrary text before and after it on the line,
 which allows it to be placed in a comment.  NAME should be replaced with
 an identifier naming the point -- this is what other generators will use
 as the insertion_point.  Code inserted at this point will be placed
 immediately above the line containing the insertion point (thus multiple
 insertions to the same point will come out in the order they were added).
 The double-@ is intended to make it unlikely that the generated code
 could contain things that look like insertion points by accident.
 For example, the C++ code generator places the following line in the
 .pb.h files that it generates:
   // @@protoc_insertion_point(namespace_scope)
 This line appears within the scope of the file's package namespace, but
 outside of any particular class.  Another plugin can then specify the
 insertion_point "namespace_scope" to generate additional classes or
 other declarations that should be placed in this scope.
 Note that if the line containing the insertion point begins with
 whitespace, the same whitespace will be added to every line of the
 inserted text.  This is useful for languages like Python, where
 indentation matters.  In these languages, the insertion point comment
 should be indented the same amount as any inserted code will need to be
 in order to work correctly in that context.
 The code generator that generates the initial file and the one which
 inserts into it must both run as part of a single invocation of protoc.
 Code generators are executed in the order in which they appear on the
 command line.
 If |insertion_point| is present, |name| must also be present.
 

optional string insertion_point = 2;

Specified by:

hasInsertionPoint in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder

getInsertionPoint

public String getInsertionPoint()

 If non-empty, indicates that the named file should already exist, and the
 content here is to be inserted into that file at a defined insertion
 point.  This feature allows a code generator to extend the output
 produced by another code generator.  The original generator may provide
 insertion points by placing special annotations in the file that look
 like:
   @@protoc_insertion_point(NAME)
 The annotation can have arbitrary text before and after it on the line,
 which allows it to be placed in a comment.  NAME should be replaced with
 an identifier naming the point -- this is what other generators will use
 as the insertion_point.  Code inserted at this point will be placed
 immediately above the line containing the insertion point (thus multiple
 insertions to the same point will come out in the order they were added).
 The double-@ is intended to make it unlikely that the generated code
 could contain things that look like insertion points by accident.
 For example, the C++ code generator places the following line in the
 .pb.h files that it generates:
   // @@protoc_insertion_point(namespace_scope)
 This line appears within the scope of the file's package namespace, but
 outside of any particular class.  Another plugin can then specify the
 insertion_point "namespace_scope" to generate additional classes or
 other declarations that should be placed in this scope.
 Note that if the line containing the insertion point begins with
 whitespace, the same whitespace will be added to every line of the
 inserted text.  This is useful for languages like Python, where
 indentation matters.  In these languages, the insertion point comment
 should be indented the same amount as any inserted code will need to be
 in order to work correctly in that context.
 The code generator that generates the initial file and the one which
 inserts into it must both run as part of a single invocation of protoc.
 Code generators are executed in the order in which they appear on the
 command line.
 If |insertion_point| is present, |name| must also be present.
 

optional string insertion_point = 2;

Specified by:

getInsertionPoint in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder

getInsertionPointBytes

public ByteString getInsertionPointBytes()

 If non-empty, indicates that the named file should already exist, and the
 content here is to be inserted into that file at a defined insertion
 point.  This feature allows a code generator to extend the output
 produced by another code generator.  The original generator may provide
 insertion points by placing special annotations in the file that look
 like:
   @@protoc_insertion_point(NAME)
 The annotation can have arbitrary text before and after it on the line,
 which allows it to be placed in a comment.  NAME should be replaced with
 an identifier naming the point -- this is what other generators will use
 as the insertion_point.  Code inserted at this point will be placed
 immediately above the line containing the insertion point (thus multiple
 insertions to the same point will come out in the order they were added).
 The double-@ is intended to make it unlikely that the generated code
 could contain things that look like insertion points by accident.
 For example, the C++ code generator places the following line in the
 .pb.h files that it generates:
   // @@protoc_insertion_point(namespace_scope)
 This line appears within the scope of the file's package namespace, but
 outside of any particular class.  Another plugin can then specify the
 insertion_point "namespace_scope" to generate additional classes or
 other declarations that should be placed in this scope.
 Note that if the line containing the insertion point begins with
 whitespace, the same whitespace will be added to every line of the
 inserted text.  This is useful for languages like Python, where
 indentation matters.  In these languages, the insertion point comment
 should be indented the same amount as any inserted code will need to be
 in order to work correctly in that context.
 The code generator that generates the initial file and the one which
 inserts into it must both run as part of a single invocation of protoc.
 Code generators are executed in the order in which they appear on the
 command line.
 If |insertion_point| is present, |name| must also be present.
 

optional string insertion_point = 2;

Specified by:

getInsertionPointBytes in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder

hasContent

public boolean hasContent()

 The file contents.
 

optional string content = 15;

Specified by:

hasContent in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder

getContent

public String getContent()

 The file contents.
 

optional string content = 15;

Specified by:

getContent in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder

getContentBytes

public ByteString getContentBytes()

 The file contents.
 

optional string content = 15;

Specified by:

getContentBytes in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder

writeTo

public void writeTo(CodedOutputStream output)
             throws IOException

Description copied from interface: MessageLite

Serializes the message and writes it to output. This does not flush or close the stream.

Specified by:

writeTo in interface MessageLite

Throws:

IOException

getSerializedSize

public int getSerializedSize()

Description copied from interface: MessageLite

Get the number of bytes required to encode this message. The result is only computed on the first call and memoized after that.

Specified by:

getSerializedSize in interface MessageLite

parseFrom

public static PluginProtos.CodeGeneratorResponse.File parseFrom(ByteString data)
                                                         throws InvalidProtocolBufferException

Throws:

InvalidProtocolBufferException

parseFrom

public static PluginProtos.CodeGeneratorResponse.File parseFrom(ByteString data,
                                                                ExtensionRegistryLite extensionRegistry)
                                                         throws InvalidProtocolBufferException

Throws:

InvalidProtocolBufferException

parseFrom

public static PluginProtos.CodeGeneratorResponse.File parseFrom(byte[] data)
                                                         throws InvalidProtocolBufferException

Throws:

InvalidProtocolBufferException

parseFrom

public static PluginProtos.CodeGeneratorResponse.File parseFrom(byte[] data,
                                                                ExtensionRegistryLite extensionRegistry)
                                                         throws InvalidProtocolBufferException

Throws:

InvalidProtocolBufferException

parseFrom

public static PluginProtos.CodeGeneratorResponse.File parseFrom(InputStream input)
                                                         throws IOException

Throws:

IOException

parseFrom

public static PluginProtos.CodeGeneratorResponse.File parseFrom(InputStream input,
                                                                ExtensionRegistryLite extensionRegistry)
                                                         throws IOException

Throws:

IOException

parseDelimitedFrom

public static PluginProtos.CodeGeneratorResponse.File parseDelimitedFrom(InputStream input)
                                                                  throws IOException

Throws:

IOException

parseDelimitedFrom

public static PluginProtos.CodeGeneratorResponse.File parseDelimitedFrom(InputStream input,
                                                                         ExtensionRegistryLite extensionRegistry)
                                                                  throws IOException

Throws:

IOException

parseFrom

public static PluginProtos.CodeGeneratorResponse.File parseFrom(CodedInputStream input)
                                                         throws IOException

Throws:

IOException

parseFrom

public static PluginProtos.CodeGeneratorResponse.File parseFrom(CodedInputStream input,
                                                                ExtensionRegistryLite extensionRegistry)
                                                         throws IOException

Throws:

IOException

newBuilder

public static PluginProtos.CodeGeneratorResponse.File.Builder newBuilder()

newBuilder

public static PluginProtos.CodeGeneratorResponse.File.Builder newBuilder(PluginProtos.CodeGeneratorResponse.File prototype)

dynamicMethod

protected final Object dynamicMethod(GeneratedMessageLite.MethodToInvoke method,
                                     Object arg0,
                                     Object arg1)

Description copied from class: GeneratedMessageLite

A method that implements different types of operations described in GeneratedMessageLite.MethodToInvoke. Theses different kinds of operations are required to implement message-level operations for builders in the runtime. This method bundles those operations to reduce the generated methods count.

• MERGE_FROM_STREAM is parameterized with an CodedInputStream and ExtensionRegistryLite. It consumes the input stream, parsing the contents into the returned protocol buffer. If parsing throws an InvalidProtocolBufferException, the implementation wraps it in a RuntimeException.
• NEW_INSTANCE returns a new instance of the protocol buffer that has not yet been made immutable. See MAKE_IMMUTABLE.
• IS_INITIALIZED is parameterized with a Boolean detailing whether to memoize. It returns null for false and the default instance for true. We optionally memoize to support the Builder case, where memoization is not desired.
• NEW_BUILDER returns a BuilderType instance.
• VISIT is parameterized with a Visitor and a MessageType and recursively iterates through the fields side by side between this and the instance.
• MAKE_IMMUTABLE sets all internal fields to an immutable state.

This method, plus the implementation of the Builder, enables the Builder class to be proguarded away entirely on Android.

For use by generated code only.

Specified by:

dynamicMethod in class GeneratedMessageLite<PluginProtos.CodeGeneratorResponse.File,PluginProtos.CodeGeneratorResponse.File.Builder>

getDefaultInstance

public static PluginProtos.CodeGeneratorResponse.File getDefaultInstance()

parser

public static Parser<PluginProtos.CodeGeneratorResponse.File> parser()