> I noticed that PD4ML pastes page breaks when such component is occurred.

No, it is not quite correct. PD4ML forces a page break, when TR { page-break-inside: avoid } is set, and a subsequent TR content does not fit remaining page space.

pd4ml-page-break-border-* properties currently are not useful, as the current table break logic deals correctly with borders in most of the cases.

> How can it be fixed without changing the legacy code?
I hope an HTML sample would help us to correctly understand the problem you faced with. Please publish it here or send it to support pd4ml com