[jira] Commented: (BEEHIVE-711) beehive-netui-config.xml elements added need to be documented

["Krista Baker (JIRA)" <be...@incubator.apache.org>]

     [ http://issues.apache.org/jira/browse/BEEHIVE-711?page=comments#action_65151 ]
     
Krista Baker commented on BEEHIVE-711:
--------------------------------------

The following elements have been added as elements to include in beehive-netui-config.xml 

The url-config element and html-amp-entity element was added in: BEEHIVE-500
The url-encode-urls element was added in: BEEHVIE-490
<url-config> 
    <url-encode-urls></url-encode-urls> 
    <html-amp-entity></html-amp-entity> 
</url-config> 

Example:
<url-config> 
    <url-encode-urls>false</url-encode-urls> 
    <html-amp-entity>false</html-amp-entity> 
</url-config> 

Both items default to true

Reason for addition:
 html-amp-entity: the default urls parameters of '&' are now encoded to '&amp;' according to the html 401 specifications by w3c.  This item can be set to false and these items will no longer be encoded to '&amp;' but will stay as '&'.

 url-encode-urls: If a user wants to write their URL for tags with href attributes as already encoded strings, this option allows them to turn off the auto-encoding that beehive does by default.  

Description:
The config elements to turn off url encoding of the href values 
and not use the HTML amp entity are <url-encode-urls> and 
<html-amp-entity>. They are of type boolean and must be within 
the <url-config> element.  

The <url-config> element should go after the <jsp-tag-config> section.

> beehive-netui-config.xml elements added need to be documented
> -------------------------------------------------------------
>
>          Key: BEEHIVE-711
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-711
>      Project: Beehive
>         Type: Bug
>   Components: Documentation
>     Reporter: Krista Baker
>     Assignee: Steve Hanson
>      Fix For: V1

>
> The following elements have been added as possible elements to include in beehive-netui-config.xml
> Added in BEEHIVE-529:
> <default-shared-flow-refs> 
>   <shared-flow-ref> 
>     <name></name> 
>     <type></type> 
>   </shared-flow-ref> 
> </default-shared-flow-refs> 
> Example:
> <default-shared-flow-refs> 
>   <shared-flow-ref> 
>     <name>defaultSharedFlow1</name> 
>     <type>miniTests.jspSeesSharedFlow.sharedFlow1.SharedFlow1</type> 
>   </shared-flow-ref> 
>   <shared-flow-ref> 
>     <name>defaultSharedFlow2</name> 
>     <type>miniTests.jspSeesSharedFlow.sharedFlow2.SharedFlow2</type> 
>   </shared-flow-ref> 
> </default-shared-flow-refs> 
> Reason for addition: there was no way for the JSP to access actions in a shared flow since there was no page flow to declare the shared flow reference.  The <default-shared-flow-refs> declares default shared flow references that are used across the webapp.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira