KEYCLOAK-8818 Support message bundle in theme resources
This commit is contained in:
parent
43f5da83e7
commit
4ef7f7e17b
1 changed files with 2 additions and 2 deletions
|
@ -1,14 +1,14 @@
|
||||||
[[_theme_resource]]
|
[[_theme_resource]]
|
||||||
=== Theme Resources
|
=== Theme Resources
|
||||||
|
|
||||||
When implementing custom providers in {project_name} there may often be a need to add additional templates and resources.
|
When implementing custom providers in {project_name} there may often be a need to add additional templates, resources and messages bundles.
|
||||||
|
|
||||||
ifeval::[{project_community}==true]
|
ifeval::[{project_community}==true]
|
||||||
An example use-case would be a <<_auth_spi,custom authenticator>> that requires additional templates and resources.
|
An example use-case would be a <<_auth_spi,custom authenticator>> that requires additional templates and resources.
|
||||||
endif::[]
|
endif::[]
|
||||||
|
|
||||||
The easiest way to load additional theme resources is to create a JAR with templates in `theme-resources/templates`
|
The easiest way to load additional theme resources is to create a JAR with templates in `theme-resources/templates`
|
||||||
and resources in `theme-resources/resources` and drop it into the `standalone/deployments/` directory of {project_name}.
|
resources in `theme-resources/resources` and messages bundles in `theme-resources/messages` and drop it into the `standalone/deployments/` directory of {project_name}.
|
||||||
|
|
||||||
If you want a more flexible way to load templates and resources that can be achieved through the ThemeResourceSPI.
|
If you want a more flexible way to load templates and resources that can be achieved through the ThemeResourceSPI.
|
||||||
By implementing `ThemeResourceProviderFactory` and `ThemeResourceProvider` you can decide exactly how to load templates
|
By implementing `ThemeResourceProviderFactory` and `ThemeResourceProvider` you can decide exactly how to load templates
|
||||||
|
|
Loading…
Reference in a new issue