[
https://issues.apache.org/jira/browse/SHINDIG-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Lindner closed SHINDIG-1657.
---------------------------------
part of 2.5.0-beta1 release.
> Wrap some web.xml init parameters in CDATA section
> --------------------------------------------------
>
> Key: SHINDIG-1657
> URL: https://issues.apache.org/jira/browse/SHINDIG-1657
> Project: Shindig
> Issue Type: Improvement
> Affects Versions: 2.5.0-beta1
> Reporter: Auke van Leeuwen
> Priority: Minor
> Labels: patch
> Fix For: 2.5.0-beta1
>
> Attachments: wrap-parameters-in-cdata-section.patch
>
>
> In the web.xml of the shindig-server project there are some init parameters
> that are supposed to be in a kind of 'properties file' format:
> {noformat}
> <param-value>
> # The ShiroFilter configuration is very powerful and
> flexible, while still remaining succinct.
> # Please read the comprehensive example, with full comments
> and explanations, in the JavaDoc:
> #
> #
> http://www.jsecurity.org/api/org/jsecurity/web/servlet/JSecurityFilter.html
> [main]
> shindigSampleRealm =
> org.apache.shindig.sample.shiro.SampleShiroRealm
> securityManager.realm = $shindigSampleRealm
> authc.loginUrl = /login.jsp
> [urls]
> # The /login.jsp is not restricted to authenticated users
> (otherwise no one could log in!), but
> # the 'authc' filter must still be specified for it so it can
> process that url's
> # login submissions. It is 'smart' enough to allow those
> requests through as specified by the
> # shiro.loginUrl above.
> /login.jsp = authc
> /oauth/authorize/** = authc
> /oauth2/authorize/** = authc
> </param-value>
> {noformat}
> I have a (Liferay) server that - upon deployment - processes the web.xml and
> injects other elements in it. Once it reads and writes the elements, they end
> up on a single line since in XML the whitespace is compressed. I think the
> properties just need to be enclosed in a CDATA block.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
