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
Embedded-DB Seed Data Corruption (Windows): Korean seed data in embedded-database WAR templates (e.g. simple-homepage's HSQLDB shtdb.sql) rendered as mojibake when Tomcat ran under the RSP backend, because Spring's <jdbc:script> reads seed SQL with the JVM default charset (MS949 on Korean Windows). The launcher now injects encoding="UTF-8" into <jdbc:script> elements across cloned WAR projects before build/deploy. MySQL-backed templates (portal, enterprise) were unaffected since their schemas are imported via the container's utf8mb4 client.