Interface RequestHeaderAnnotationOrBuilder

All Superinterfaces:
com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder
All Known Implementing Classes:
RequestHeaderAnnotation, RequestHeaderAnnotation.Builder

@Generated(value="protoc", comments="annotations:RequestHeaderAnnotationOrBuilder.java.pb.meta") public interface RequestHeaderAnnotationOrBuilder extends com.google.protobuf.MessageOrBuilder
  • Method Summary

    Modifier and Type
    Method
    Description
    The name of the header to set (e.g., "temporal-resource-id")
    com.google.protobuf.ByteString
    The name of the header to set (e.g., "temporal-resource-id")
    A template string that may contain field paths in braces.
    com.google.protobuf.ByteString
    A template string that may contain field paths in braces.

    Methods inherited from interface com.google.protobuf.MessageLiteOrBuilder

    isInitialized

    Methods inherited from interface com.google.protobuf.MessageOrBuilder

    findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
  • Method Details

    • getHeader

      String getHeader()
       The name of the header to set (e.g., "temporal-resource-id")
       
      string header = 1;
      Returns:
      The header.
    • getHeaderBytes

      com.google.protobuf.ByteString getHeaderBytes()
       The name of the header to set (e.g., "temporal-resource-id")
       
      string header = 1;
      Returns:
      The bytes for header.
    • getValue

      String getValue()
       A template string that may contain field paths in braces.
       Field paths use dot notation to traverse nested messages.
       Example: "{workflow_execution.workflow_id}"
       
      string value = 2;
      Returns:
      The value.
    • getValueBytes

      com.google.protobuf.ByteString getValueBytes()
       A template string that may contain field paths in braces.
       Field paths use dot notation to traverse nested messages.
       Example: "{workflow_execution.workflow_id}"
       
      string value = 2;
      Returns:
      The bytes for value.