Deprecated API
Contents
-
Terminally Deprecated ElementsElementDescriptionsince 1.6.8, This class has been deprecated in the effort of the library modularization. It is recommended to use the
CommentProcessorclass instead. This class will not be exported in the future releases of the module.since 1.6.8, This class has been deprecated in the effort of the library modularization. It is recommended to use theOfficeStamperExceptionclass instead. This class will not be exported in the future releases of the module.since 1.6.8, This class has been deprecated in the effort of the library modularization. It is recommended to use theEvaluationContextConfigurerclass instead. This class will not be exported in the future releases of the module.since 1.6.8, This class has been deprecated in the effort of the library modularization, because it exposes too many implementation details to library users, and makes it hard to extend the library comfortably. It is recommended to use theOfficeStampersmethods instead. This class will not be exported in the future releases of the module.since 1.6.4, useOfficeStampers.docxStamper()instead.since 1.6.8, This class has been deprecated in the effort of the library modularization, because it exposes too many implementation details to library users, and makes it hard to extend the library comfortably. It is recommended to use theOfficeStamperConfigurations.standard()method andOfficeStamperConfigurationinterface instead. This class will not be exported in the future releases of the module.This method has been deprecated since version 1.6.7, and it is scheduled for removal. It's recommended to use theDocxStamperConfiguration.addResolver(ObjectResolver)method for adding resolvers.use newDocxStamper(OfficeStamperConfiguration)} insteadThis method's been deprecated since version 1.6.7 and is scheduled for removal. You should not have to use it, it was a clutch for previous version of docx-stamper.This method has been deprecated since version 1.6.7 and is scheduled for removal. You shouldn't have to use it, it was a clutch for docx-stamper workings.This method's been deprecated since version 1.6.7This method's been deprecated since version 1.6.7 and will be removed in a future release. You shouldn't have to use it, it was a clutch for docx-stamper workings.This method has been deprecated since version 1.6.7. It is recommended to useDocxStamperConfiguration.addResolver(ObjectResolver)andResolvers.nullToDefault(String)instead.This method has been deprecated since version 1.6.7. It is recommended to useDocxStamperConfiguration.addResolver(ObjectResolver)andResolvers.nullToDefault(String)instead.This method is deprecated and scheduled for removal in version 1.6.7. Please set your "default" resolver throughDocxStamperConfiguration.addResolver(ObjectResolver)by putting your default first in the list, or by usingDocxStamperConfiguration.setResolvers(List)} and putting your fallback resolvers in the last place.since 1.6.8, This class has been deprecated in the effort of the library modularization. It is recommended to use theStampTableclass instead. This class will be removed in the future releases of the module.should be an internal implementation detailsince 1.6.8, This class has been deprecated in the effort of the library modularization. It is recommended to use theCommentUtilclass instead. This class will be removed in the future releases of the module.since 1.6.8, This class has been deprecated in the effort of the library modularization. It is recommended to use theStandardCommentclass andCommentinterface instead. This class will be moved to internals in the future releases of the module.method not used internally so will be removedmethod not used internally so will be removedmethod not used internally so will be removedmethod not used internally so will be removedthe document is passed to the processor through the commitChange method now and will probably pe passed through the constructor in the futurethe document is passed to the processor through the commitChange method now, and will probably pe passed through the constructor in the futureremoved for replacement byComment.getElements()which doesn't imply a specific usageusecreateSubWordDocument(Comment)insteadusecreateSubWordDocument(Comment)insteadthe document is passed to the processor through the commitChange method now, and will probably pe passed through the constructor in the futureas of version 1.6.7, replaced byObjectResolver. The new resolver is more versatile, requires less reflection mechanism, and simplifies the internal workings of the docx-stamper project.as of version 1.6.7, replaced byObjectResolver. The new resolver is more versatile, requires less reflection mechanism, and simplifies the internal workings of the docx-stamper project.This method is marked for removal and should not be used. Consider using a different method instead.This method has been deprecated since version 1.6.7 and will be removed in a future release.This method has been deprecated since version 1.6.7 and will be removed in a future release.This method has been deprecated since version 1.6.7 and will be removed in a future release. Use of this method is discouraged and should be replaced with an alternative implementation.Since version 1.6.7. This method will be removed in a future release.since version 1.6.7since version 1.6.7since version 1.6.7This method's been deprecated since version 1.6.8 and will be removed in the future.usecreateSubWordDocument(Comment)insteadusecreateSubWordDocument(Comment)insteadsince 1.6.8, This class has been deprecated in the effort of the library modularization. It is recommended to use theCommentUtilclass instead. This class will be removed in the future releases of the module.
-
Deprecated InterfacesInterfaceDescriptionsince 1.6.8, This class has been deprecated in the effort of the library modularization. It is recommended to use the
CommentProcessorclass instead. This class will not be exported in the future releases of the module.since 1.6.8, This class has been deprecated in the effort of the library modularization. It is recommended to use theEvaluationContextConfigurerclass instead. This class will not be exported in the future releases of the module.as of version 1.6.7, replaced byObjectResolver. The new resolver is more versatile, requires less reflection mechanism, and simplifies the internal workings of the docx-stamper project.
-
Deprecated ClassesClassDescriptionsince 1.6.8, This class has been deprecated in the effort of the library modularization, because it exposes too many implementation details to library users, and makes it hard to extend the library comfortably. It is recommended to use the
OfficeStampersmethods instead. This class will not be exported in the future releases of the module.since 1.6.8, This class has been deprecated in the effort of the library modularization, because it exposes too many implementation details to library users, and makes it hard to extend the library comfortably. It is recommended to use theOfficeStamperConfigurations.standard()method andOfficeStamperConfigurationinterface instead. This class will not be exported in the future releases of the module.since 1.6.8, This class has been deprecated in the effort of the library modularization. It is recommended to use theStampTableclass instead. This class will be removed in the future releases of the module.since 1.6.8, This class has been deprecated in the effort of the library modularization. It is recommended to use theCommentUtilclass instead. This class will be removed in the future releases of the module.since 1.6.8, This class has been deprecated in the effort of the library modularization. It is recommended to use theStandardCommentclass andCommentinterface instead. This class will be moved to internals in the future releases of the module.will not be removed, but will be made package-privatesince 1.6.8, This class has been deprecated in the effort of the library modularization. It is recommended to use theCommentUtilclass instead. This class will be removed in the future releases of the module.
-
Deprecated Exception ClassesException ClassDescriptionsince 1.6.8, This class has been deprecated in the effort of the library modularization. It is recommended to use the
OfficeStamperExceptionclass instead. This class will not be exported in the future releases of the module.
-
Deprecated MethodsMethodDescriptionThis method has been deprecated since version 1.6.7, and it is scheduled for removal. It's recommended to use the
DocxStamperConfiguration.addResolver(ObjectResolver)method for adding resolvers.use newDocxStamper(OfficeStamperConfiguration)} insteadThis method's been deprecated since version 1.6.7 and is scheduled for removal. You should not have to use it, it was a clutch for previous version of docx-stamper.This method has been deprecated since version 1.6.7 and is scheduled for removal. You shouldn't have to use it, it was a clutch for docx-stamper workings.This method's been deprecated since version 1.6.7This method's been deprecated since version 1.6.7 and will be removed in a future release. You shouldn't have to use it, it was a clutch for docx-stamper workings.This method's been deprecated since version 1.6.7. You shouldn't have to use it, it was a crutch use for inner working of docx-stamperThis method has been deprecated since version 1.6.7. It is recommended to useDocxStamperConfiguration.addResolver(ObjectResolver)andResolvers.nullToDefault(String)instead.This method has been deprecated since version 1.6.7. It is recommended to useDocxStamperConfiguration.addResolver(ObjectResolver)andResolvers.nullToDefault(String)instead.This method is deprecated and scheduled for removal in version 1.6.7. Please set your "default" resolver throughDocxStamperConfiguration.addResolver(ObjectResolver)by putting your default first in the list, or by usingDocxStamperConfiguration.setResolvers(List)} and putting your fallback resolvers in the last place.should be an internal implementation detailmethod not used internally so will be removedmethod not used internally so will be removedmethod not used internally so will be removedmethod not used internally so will be removedthe document is passed to the processor through the commitChange method now and will probably pe passed through the constructor in the futurethe document is passed to the processor through the commitChange method now, and will probably pe passed through the constructor in the futureremoved for replacement byComment.getElements()which doesn't imply a specific usageusecreateSubWordDocument(Comment)insteadusecreateSubWordDocument(Comment)insteadthe document is passed to the processor through the commitChange method now, and will probably pe passed through the constructor in the futureas of version 1.6.7, replaced byObjectResolver. The new resolver is more versatile, requires less reflection mechanism, and simplifies the internal workings of the docx-stamper project.This method is marked for removal and should not be used. Consider using a different method instead.This method has been deprecated since version 1.6.7 and will be removed in a future release.This method has been deprecated since version 1.6.7 and will be removed in a future release.This method has been deprecated since version 1.6.7 and will be removed in a future release. Use of this method is discouraged and should be replaced with an alternative implementation.Since version 1.6.7. This method will be removed in a future release.since version 1.6.7since version 1.6.7since version 1.6.7This method's been deprecated since version 1.6.8 and will be removed in the future.usecreateSubWordDocument(Comment)insteadusecreateSubWordDocument(Comment)instead
-
Deprecated Constructors