Class TylerEcf4Helper
java.lang.Object
edu.suffolk.litlab.efsp.server.utils.TylerEcf4Helper
Helper class that easily converts Java native types to Cumbersome XML Schema types, particularly
those from Oasis's ECF standard, and the National Information Exchange Model (NIEM).
Some information about NIEM: Many of the types here all include the "SimpleObjectAttributeGroup", which, "provides a collection of attributes which are appropriate for definition of object types", including an ID attribute, a Metadata attribute, and a Link Metadata attribute that directly reference objects via IDs instead of including the object as an element. TBH, I'm not sure what the design decisions that dictate the use of them are, but they exist.
- Author:
- Bryce Willey
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionstatic Optional<ServiceHelpers.EcfError> checkError(ErrorType error) Returns the error type on errors from the ECF side of the API.static List<ServiceHelpers.EcfError> checkErrors(List<ErrorType> errors) static booleangetIsIndividual(TylerFirmFactory firmFactory, UserCreds userCreds) static jakarta.ws.rs.core.ResponsemakeResponse(QueryResponseMessageType resp, Supplier<jakarta.ws.rs.core.Response> defaultRespFunc) static jakarta.ws.rs.core.ResponsemapTylerCodesToHttp(List<ServiceHelpers.EcfError> err, Supplier<jakarta.ws.rs.core.Response> defaultResp) static <T extends QueryMessageType>
Tstatic Optional<TylerFirmClient> setupFirmPort(TylerFirmFactory firmFactory, UserCreds userCreds) static Optional<TylerFirmClient> setupFirmPort(TylerFirmFactory firmFactory, UserCreds creds, boolean needsSoapHeader) static voidsetupReplys(CaseFilingType reply) static voidsetupServicePort(jakarta.xml.ws.BindingProvider bp) Sets up a connection to Tyler's SOAP API WITHOUT any Auth headers, but does handle the X.509 certificate and signing parameters.static voidsetupServicePort(jakarta.xml.ws.BindingProvider bp, UserCreds creds) static voidsetupServicePort(jakarta.xml.ws.BindingProvider bp, List<org.apache.cxf.headers.Header> headerList)
-
Constructor Details
-
TylerEcf4Helper
public TylerEcf4Helper()
-
-
Method Details
-
prep
-
makeResponse
public static jakarta.ws.rs.core.Response makeResponse(QueryResponseMessageType resp, Supplier<jakarta.ws.rs.core.Response> defaultRespFunc) -
mapTylerCodesToHttp
public static jakarta.ws.rs.core.Response mapTylerCodesToHttp(List<ServiceHelpers.EcfError> err, Supplier<jakarta.ws.rs.core.Response> defaultResp) -
setupReplys
-
setupServicePort
public static void setupServicePort(jakarta.xml.ws.BindingProvider bp) Sets up a connection to Tyler's SOAP API WITHOUT any Auth headers, but does handle the X.509 certificate and signing parameters.Can be used to make an Auth request, or can have the header inserted later.
-
setupServicePort
-
setupServicePort
public static void setupServicePort(jakarta.xml.ws.BindingProvider bp, List<org.apache.cxf.headers.Header> headerList) -
getIsIndividual
-
setupFirmPort
public static Optional<TylerFirmClient> setupFirmPort(TylerFirmFactory firmFactory, UserCreds userCreds) -
setupFirmPort
public static Optional<TylerFirmClient> setupFirmPort(TylerFirmFactory firmFactory, UserCreds creds, boolean needsSoapHeader) -
checkError
Returns the error type on errors from the ECF side of the API. They work the same as the Tyler ones. -
checkErrors
-