
Package org.hl7.fhir.r5.renderers
Class Renderer
java.lang.Object
org.hl7.fhir.r5.renderers.Renderer
- Direct Known Subclasses:
DataRenderer
Rendering framework:
* boolean render(DomainResource) : produce an HTML representation suitable for runtime / documentation, and insert it into the resource. Return true of any extensions encountered
* boolean render(XhtmlNode, Resource: produce an HTML representation, and fill out the provided node with it. Return true of any extensions encountered
* XhtmlNode build(DomainResource): same as render(DomainResource) but also return the XHtmlNode
* String display(Base) : produce a plan text concise representation that serves to describe the resource
* void display(XhtmlNode, Base) : produce a plan text concise representation that serves to describe the resource
* void describe(XhtmlNode, Resource) : produce a short summary of the resource with key details presented (potentially more verbose than display, but still suitable for a single line)
if not specific code for rendering a resource has been provided, and there's no liquid script to guide it, a generic rendering based onthe profile will be performed
- Author:
- graha
-
Field Summary
FieldsModifier and TypeFieldDescriptionprotected RenderingContext
protected static final String
protected static final String
protected static final String
protected static final String
protected static final String
protected static final String
protected static final String
protected static final String
protected static final String
protected static final String
protected static final String
protected static final String
protected static final String
protected static final String
protected static final String
protected static final String
protected static final String
protected static final String
protected static final String
protected static final String
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionprotected String
formatMessage
(String theMessage, Object... theMessageArguments) the plan here is to make this have it's own implementation of messages, rather than using the validator messages, for better alignment with publisher I18n strategy
-
Field Details
-
context
-
RENDER_BUNDLE_HEADER_ROOT
- See Also:
-
RENDER_BUNDLE_HEADER_ENTRY
- See Also:
-
RENDER_BUNDLE_HEADER_ENTRY_URL
- See Also:
-
RENDER_BUNDLE_RESOURCE
- See Also:
-
RENDER_BUNDLE_SEARCH
- See Also:
-
RENDER_BUNDLE_SEARCH_MODE
- See Also:
-
RENDER_BUNDLE_SEARCH_SCORE
- See Also:
-
RENDER_BUNDLE_RESPONSE
- See Also:
-
RENDER_BUNDLE_LOCATION
- See Also:
-
RENDER_BUNDLE_ETAG
- See Also:
-
RENDER_BUNDLE_LAST_MOD
- See Also:
-
RENDER_BUNDLE_REQUEST
- See Also:
-
RENDER_BUNDLE_IF_NON_MATCH
- See Also:
-
RENDER_BUNDLE_IF_MOD
- See Also:
-
RENDER_BUNDLE_IF_MATCH
- See Also:
-
RENDER_BUNDLE_IF_NONE
- See Also:
-
RENDER_BUNDLE_DOCUMENT_CONTENT
- See Also:
-
RENDER_BUNDLE_HEADER_DOC_ENTRY_URD
- See Also:
-
RENDER_BUNDLE_HEADER_DOC_ENTRY_U
- See Also:
-
RENDER_BUNDLE_HEADER_DOC_ENTRY_RD
- See Also:
-
-
Constructor Details
-
Renderer
-
Renderer
-
-
Method Details
-
formatMessage
the plan here is to make this have it's own implementation of messages, rather than using the validator messages, for better alignment with publisher I18n strategy- Parameters:
theMessage
-theMessageArguments
-- Returns:
-