This release is focusses on a huge clean-up "underneath the hood".
2 User Intervention
Reworked Internal Structure and JRE Upgrade Require User Intervention
In Intershop Studio 4.3.5 comes with some major changes in the internal structure:
Although these changes are largely internal, there are some implications for the user due to this:
3 Localization of
Externalize Texts Wizard
Texts that appear in user interfaces must be localizable.
Versions prior to Intershop 7.4 CI supported multiple approaches for ISML template localization.
Due to technical progress - especially the use of Gradle for continiuos integration environments - it is necessary to unify these approaches.
Thus, Intershop strongly recommends to externalize all texts from ISML templates to properties files.
Please see Guide - 7.4.6 Externalize Texts from ISML Templates for more detailed information on how Intershop Studio supports this tasks.
Hyperlinking for Localization Text
Keys in localization files now provide hyperlinking support.
If the hyperlink is activated, usages of this localization (e.g., in templates of web forms) are provided as link targets.
The image shows the link from test.properties to the using
The key attribute in the ISML file provides a link to the properties file as well.
Activate Hyperlinking for Properties Files
4 Validation Prevents
Validation Warns About Possible Cross-Site-Scripting Vulnerability
ISML templates will now be validated in order to detect possible Cross-Site-Scripting vulnerability.
Fixing such errors is easy since Qucik-Fixes are available:
This validation type can be configured in preferences.
An application is available that generates code from EDL models.
Its ID is
This allows to create code from EDL models via the commandline or during the cartridge build process.
Invoke the application with
Generates code for EDL models. This application accepts following parameters: ---------------------------------------------- -isproperties_location: Required parameter if gradleproperties_location is not used. Specify the location of the intershop.properties file. Typically, this file can be found in the root directory of the Enfinity Suite installation. Allong with other entries it must contain entries specifying the location of the cartridge source directory. -help: Use this parameter to request help. Actually you don't need this explanation, it seems you already found out. -cartridge: Required parameter. Specify the cartridge id of the cartridge to be processed. This parameter accepts multiple values. -enfinity_version: Specify the version of the Enfinity Suite Server. Version identifiers must be integers separated by DOT. If ommited version 7.5 is used as default. -javaTarget: the java target folder (relative to the cartridge folder). Default is 'javasource'. Regardless of this parameter java files get merged with their existing files in the javasource folder. -no_project_import: In order to run this application cartridge source projects are needed. If the workspace does not contain the expected cartridge project it gets generated in the workspace. If this parameter is set, no projects get generated. -gradleproperties_location: Required parameter if isproperties_location is not used. Specify the location of the gradle.properties file. Typically, this file can be found in the gradle directory of the Enfinity Suite installation. -no_progress: Long running operations notify progress. If this parameter is passed to the application no progress is printed to the console. This parameter does not expect any values. Examples: --------- EnfinityStudio -application com.intershop.studio.edl.generator.EDL2Code -data generation_workspace -isproperties_location C:/eserver2/intershop.properties -cartridge test_a test_b: Invokes the EDL2Code generator on all EDL models in cartridges 'test_a' and 'test_b'. EnfinityStudio -application com.intershop.studio.edl.generator.EDL2Code -data generation_workspace -isproperties_location C:/eserver2/intershop.properties -javaTarget src-gen -cartridge test_a: Invokes the EDL2Code generator on all EDL models in cartridges 'test_a'. The generated code will be located in the folder 'src-gen' instead of 'java_source'.
The code generator application
It also provides the ability to validate the models. But this already covered with the much more powerful application
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.