acbr-patterns

ACBr Project — Rules

Use these rules when working with components from the ACBr Project suite (Commercial Automation Brazil) in Delphi applications.

Isolation and Standards (SOLID)

• ❌ Do not instantiate or attach ACBr components directly to UI forms (e.g. placing a TACBrNFe inside TfrmEmissao).
• ✅ Create abstractions or Service classes (ex: TNFeService) in Domain/Infra Modules that encapsulate TACBrNFe.
• The form should only trigger one interface, for example: INFeService.Emitir(Nota).

Memory Management

• ACBr components created dynamically in Services always must be released appropriately (Try/Finally or created as Child of DataModules maintained by injection).

//Encapsulated dynamic creation example
var
  LAcbrNFe: TACBrNFe;
begin
  LAcbrNFe := TACBrNFe.Create(nil);
  try
    //Settings and usage
    LAcbrNFe.Configuracoes.Certificados.NumeroSerie := 'XYZ';
  finally
    LAcbrNFe.Free;
  end;
end;

Dynamic Settings

• Avoid reading from .ini files via UI. Load the configurations via a system configuration layer (IConfiguration) and inject it into the service that encapsulates the ACBr.

Error and Return Handling

• Catch ACBr specific exceptions when possible.
• Convert long component returns (e.g. status, rejection reasons) into application Object Results/Records instead of tying the application to the component's natural formatting string.

Signing/Crypto Library Abstraction (OpenSSL vs WinCrypt)

Isolate the SSL/crypto library choice per target OS (e.g. Linux Docker vs Windows) inside the wrapper service — configure it always via code, dynamically, never fixed at design time:

LAcbrNFe.Configuracoes.Geral.SSLLib := libWinCrypt; // or libOpenSSL per platform

TEF Callbacks and Events

TACBrTEFD works heavily through VCL events (OnExibeMensagem, OnAguardaDigitacao). Keep the component in the Business/Gateway layer by injecting a generic presentation handler, so headless/REST scenarios can override the "draw to screen" part: