Starcounter 2.1: Breaking changes for app compositionSeptember 22, 2015 11:42 pm Leave your thoughts
Starting with version 2.1 we introduce the following breaking changes:
- In mapping URIs where “/polyjuice” prefix was used, now we use “/sc/mapping”
For that we recommend
UriMapping.MappingUriPrefix, for example:
UriMapping.Map("/images/menu", UriMapping.MappingUriPrefix + "/menu");
Starcounter.Node.dll is now integrated into Starcounter.Internal.dll, meaning that first reference should be removed from your project.
HTML merger URI “/polyjuice/htmlmerger?…” is changed to “/sc/htmlmerger?…”
Applications are now isolated from each other on SQL level (
Db.SQLcalls). This means that database classes defined in one application are not accessible to another application running in the same code host. However, database classes defined in shared assembly are accessible to all applications that link this shared library. Read more here: SQL isolation
Administrator SQL now forces querying database classes ONLY using their fully-namespaced name. Read more here: SQL isolation
Layouts are moved from Launcher (and deprecated Polyjuice project) to Starcounter. Handlers are renamed from “/launcher/juicytilessetup…” to “/sc/layout/…”.
PolyjuiceNamespacewas removed, as well as
PolyjuiceFlagin database configuration.
The root redirection (for example, “/products” to “/”) should now be done using URI aliasing in gateway: http://starcounter.io/guides/network/aliases-and-redirects/
Polyjuicefolder in StarcounterBin renamed to
URI aliasing API added: URI aliases
The following flags (saved in database config) are added with their default values:
Should edition libraries be loaded in databases:
Should Json responses be wrapped in application name:
Should applications be forced to register handlers starting with application name prefix:
Should Json responses from multiple applications be merged:
Should URI mapping (UriMapping.Map) be enabled:
Should URI ontology mapping (UriMapping.OntologyMap) be enabled:
When codehost is running one can manipulate with these flags at runtime using special REST API. All should be called on system port.
Getter for flags:
GET /sc/[fusion_builder_container hundred_percent="yes" overflow="visible"][fusion_builder_row][fusion_builder_column type="1_1" background_position="left top" background_color="" border_size="" border_color="" border_style="solid" spacing="yes" background_image="" background_repeat="no-repeat" padding="" margin_top="0px" margin_bottom="0px" class="" id="" animation_type="" animation_speed="0.3" animation_direction="left" hide_on_mobile="no" center_content="no" min_height="none"][DatabaseName]/GetFlag/[FlagName]
Setter for flags:
Categorised in: Nightly changes
This post was written by Alexey Moiseenko