...
More robust HTML escaping JSP functions are introduced as a replacement for fn:escapeXml. These are wmfn:escapeToHTML for generic use in HTML and wmfn:escapeToHTMLAttribute for escaping HTML attributes. Unlike fn:escapeXml, these functions do not escape L CODE tags that are used for links and personalization tags. It is recommended that you replace all instances of fn:escapeXml in frontend presentations with these functions. In specific cases this is required for L CODE tags and personalization to work correctly.
...
XperienCentral 10.9.0
...
- The GetText servlet has been deleted. If you are using a modified web.xml file then be sure to
...
- remove any references to the GetText servlet.
...
- From now on the 3.0 servlet API is supported only. To enable this the dependencies to the related
...
- artifacts need to be changed in custom poms that refer to these artifacts:
...
javax.servlet:servlet-api
...
- and
javax.servlet:
...
jsp-api
...
- .
...
The
web.xmldeployment descriptor header should be changed to the 3.0 format:Code Block theme
...
Eclipse
...
<web-app xmlns="http://java.sun.com/xml/ns/javaee"
...
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
...
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
...
http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"
...
version="3.0"
...
> </web-app>
...
...
Maven 3.X does not support file URLs like "file:./maven-repository" in the settings.xml anymore,
...
therefore the "localRepository" setting must be a real file path from now on and this should be
...
updated in your custom Maven settings if needed. An absolute path is preferred for referring to
...
the same repository (for example in subprojects) because the settings are relative to the current
...
project directory (see
...
...
Maven 3.X discourages using expressions for the groupId, artifactId and version settings in
...
POMs and other descriptors. These have been replaced by constant values and, as a result, the
...
webmanager.project.groupId, webmanager.project.artifactId and webmanager.project.version
...
settings from the settings.xml no longer serve a purpose and thus have been removed from the settings.xml.
...
As a result of this it may be necessary to update the values of your project specific
...
webmanager.staticbasedir, webmanager.backendbasedir and webmanager.cleansitelocation settings.
...
Because the Maven plugin for OSGI bundles has been replaced in Maven 3.X, the following adjustments
...
are needed in the
pom.xmlof custom plugins.
PACKAGING:Maven 2:<project ...><packaging>osgi-bundle</packaging>...Replacement in Maven 3:<project ...><packaging>bundle</packaging>
...
MAVEN OSGI PLUGIN: Note especially that the <explicitImportPackage> tag is not needed any more.
Previously this tag was used to make exported local packages available within the plugin code.
Maven 2:<plugin><groupId>org.apache.felix.plugins</groupId><artifactId>maven-osgi-plugin</artifactId><configuration><osgiManifest><bundleActivator>...</bundleActivator><exportPackage>...</exportPackage>
...
<explicitImportPackage>...</explicitImportPackage></osgiManifest><configuration>...
...
Replacement in Maven 3:<plugin><groupId>org.apache.felix</groupId><artifactId>maven-bundle-plugin</artifactId><configuration><instructions><Bundle-Activator>...</Bundle-Activator><Export-Package>...</Export-Package>
...
<!-- REMOVED! explicitImportPackage --></instructions><configuration>...
...
If a custom parent pom.xml is used in place of the one delivered in the XperienCentral SDK ZIP
...
(
nl.gx.webmanager.wcbs:webmanager-wcbs), then you need to make the following changes in the
...
parent
pom.xml. Some of these tags can also be used directly in the pom.xml of a plugin. In that
...
case, the same "translation" should be used there.
Maven 2:<plugin><groupId>org.apache.felix.plugins</groupId><artifactId>maven-osgi-plugin</artifactId><version>...</version><configuration><manifestFile>...</manifestFile><osgiManifest><bundleVendor>...</bundleVendor><bundleSymbolicName>...</bundleSymbolicName><bundleName>...</bundleName><bundleDescription>...</bundleDescription><bundleSource>...</bundleSource><bundleDate>...</bundleDate>
...
<bundleManifestVersion>${webmanager.manifestversion}</bundleManifestVersion></osgiManifest><configuration>...
...
...
Replacement in Maven 3:<plugin><groupId>org.apache.felix</groupId><artifactId>maven-bundle-plugin</artifactId><version>2.5.3</version><configuration><archive><manifestFile>...</manifestFile></archive><instructions><Embed-Dependency>*;scope=compile</Embed-Dependency> <!-- NEW! --><Embed-Transitive>true</Embed-Transitive> <!-- NEW! --><Export-Package/> <!-- NEW! -->
...
<Bundle-Vendor>...</Bundle-Vendor><Bundle-SymbolicName>...</Bundle-SymbolicName><Bundle-Name>...</Bundle-Name><Bundle-Description>...</Bundle-Description><Bundle-Source>...</Bundle-Source><Bundle-Date>...</Bundle-Date>
...
<!-- REMOVED: bundleManifestVersion --></instructions><configuration>...
...
The maven-bundle-plugin adds version information to the Manifest file for its dependencies. This
...
information is checked at runtime in order to ensure that an accepted version of the referred
...
plugin is installed on the system, otherwise the plugin will fail to start. The default runtime
...
version requirements are sensible, but when dealing with 3rd party components you might need to
...
overrule these default requirements. This can be done as follows to allow v1.x.x - v5.x.x:
...
<Import-Package>com.gxwebmanager.tests.testservice.*;version="[1,6)",*</Import-Package>.
...
XperienCentral 10.7.1
- GX WebManager 10.7.1 provides an oEmbed service to embed XC content in external oEmbed consumers.
...