You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 31, 2022. It is now read-only.
You can use the core:// and web:// prefixes to reference to image resources from the web or core module without having to hard-code webPort and webContextName in the template. For example, the image hosted in the deploy\tomcat\webapps\app\VAADIN\images folder can be inserted like:
In Jmix we should use another prefix for that (web:// and core:// don't make sense any more).
Current prefix names should remain for backward compatibility?
The text was updated successfully, but these errors were encountered:
Replace the "web://" and "core://" prefixes by "resource://" prefix: image resource is searched by path specified after "resource://" prefix in the "conf" directory and classpath resources.
New prefix (resource://) that replaces "web://" and "core://" prefixes is introduced. The resource is searched by a path specified after the "resource://" prefix in the "conf" directory and classpath resources. This logic works only for HTML templates that have PDF as an output type.
Hi @BryanYin,
The "resource://" prefix is processed in the case of the template body is HTML but the output type is PDF. In your case the output type is HTML so this case is not related to changes made in this issue.
From CUBA documentation:
In Jmix we should use another prefix for that (
web://
andcore://
don't make sense any more).Current prefix names should remain for backward compatibility?
The text was updated successfully, but these errors were encountered: