Dedicated has typo as "dedcated". See ValidationContext Point in below Documentation of HapiContext class.

`
/**

• Interface that provides a starting point for
• • Configuring HAPI core services (e.g. parsing)
  • Obtaining correspondingly configured instances of HAPI core services
• HapiContext instances are not supposed to be singletons, i.e. if necessary, it is possible to
• have several HapiContexts within one application.
• HapiContext objects maintains the following configuration information
• • {@link ExecutorService}: thread executors used for the HAPI networking features in
  • ca.uhn.hl7v2.app
  • {@link LowerLayerProtocol}: MLLP protocol used for the HAPI networking features in
  • ca.uhn.hl7v2.app
  • {@link SocketFactory}: Socket factory used for the HAPI networking features in
  • ca.uhn.hl7v2.app
  • {@link ParserConfiguration}: detail configuration for all HL7 parsers
  • {@link ModelClassFactory}: lookup for message model classes during parsing or message
  • creation
  • {@link ValidationContext}: validation rules used during parsing or during a dedcated
  • validation step
  • {@link ValidationRuleBuilder}: alternative way of providing a ValidationContext
  • {@link ValidationExceptionHandlerFactory}: factory for exception handler used during message validation
• HapiContext serves as factory for HAPI objects that refer to this configuration. Changing the
• configuration automatically influence all HAPI objects that were created and will be created
• using the given factory instance:
• • {@link PipeParser}
  • {@link XMLParser}
  • {@link GenericParser}
  • {@link Validator}
  • {@link ConnectionHub}
  • {@link ca.uhn.hl7v2.app.SimpleServer}
  • {@link ca.uhn.hl7v2.app.TwoPortService}

*/`