Class OnlyofficeApplication
- All Implemented Interfaces:
org.springframework.web.WebApplicationInitializer
ApplicationContext, so its Spring-annotated beans (notably the
OnlyofficeMcpTool @Service, active under the
mcp-server profile) are discovered and can be collected by the
mcp-server tool registry.
The add-on has NO JPA / Elasticsearch repositories and no Liquibase Spring
configuration, so only the kernel and web integration modules are scanned in
addition to the add-on package. The existing kernel wiring (declared in the
add-on configuration.xml) is untouched: this Spring context lives
alongside it, exactly like the Documents add-on does.
Because there is no DB layer at all, the Spring Boot DataSource / JPA /
Liquibase auto-configurations (which are on the classpath transitively) are
fully excluded. Otherwise Spring Boot would try to build an
entityManagerFactory that depends on a liquibase bean whose
default classpath:/db/changelog/db.changelog-master.yaml does not
exist in this add-on, failing the context startup with a
BeanCreationException at boot.
-
Field Summary
FieldsFields inherited from class org.springframework.boot.web.servlet.support.SpringBootServletInitializer
logger -
Constructor Summary
Constructors -
Method Summary
Methods inherited from class io.meeds.spring.kernel.PortalApplicationContextInitializer
createSpringApplicationBuilder, isAsync, onStartupMethods inherited from class org.springframework.boot.web.servlet.support.SpringBootServletInitializer
configure, createRootApplicationContext, deregisterJdbcDrivers, run, setRegisterErrorPageFilter, shutDownSharedReactorSchedulers
-
Field Details
-
MODULE_NAME
- See Also:
-
-
Constructor Details
-
OnlyofficeApplication
public OnlyofficeApplication()
-