Hi all,
There's one other idea, which may work in each and all of the cases here described.
Inspired by Swing Architecture, my sugestion would be to make some architectural enhancements so as to allow this (Name Lenght) and other parameters to be configurable by the developer.
In this case, there could be some static method such as:
public static void setDefaultNameLengthPolicy(int policy)
with constants (or enumerations) like STRICT_NAME_LIMIT_CHECK and DISABLE_NAME_LIMIT_CHECK and so on. This idea could be extended to other "would-be" configurable properties. Therefore we could have some static setDefault* methods (like setDefaultCloseOperation(), setDefaultLookAndFeelDecorated() in JFrame class).
This way iText API could adhere to both (or more) policies, according to designer's choice.
Of course this is a humble opinion. I'm not considering that iText may deliberately not have been designed to meet such architectural glitches. If this is the case, please forgive me.
Best regards,
Filipe Fedalto
Cansado dos disparates e despautérios da República?
Quer um basta nas desventuras de nossos governantes?
Acesse http://www.monarquia.org.br e http://www.brasilimperial.org.br
e saiba mais a respeito.
