[ http://issues.apache.org/jira/browse/BEEHIVE-711?page=all ]
Krista Baker updated BEEHIVE-711:
---------------------------------
Attachment: j711.txt
Here is a patch for the beehive-netui-config.xml file. This patch fixes the
following issues (and a couple other minor ones.)
1) removed all references to legacy-tag-support
This element was removed from beehive-netui-config.xml as of svn 165345
2) moved default-language to be a child of expression-languages and not
expression-language
3) login-handler-class is no longer valid:
login-handler with required child of handler-class
and optional child of custom-property [0-*]
4) added handler-class section
type=xsd:string
parents=action-forward-handler, exceptions-handler,
forward-redirect-handler, login-handler, reloadable-class-handler
5) forward-redirect-handler-class is no longer valid:
forward-redirect-handler with required child of handler-class
and optional child of custom-property [0-*]
6) reloadable-class-handler-class, same as above, now reloadable-class-handler
7) exceptions-handler-class, same as above, now exceptions-handler
8) action-forward-handler has been added, same properties as above
9) enable-renesting is now enable-self-nesting
10) multipart-handler - removed the "To disable file To disable file upload,
set the value to "none". [todo: other values include memory, ?, ...]
The values listed in the syntax are consistent with the enumeration on
the element, memory, disk, and disabled.
In pageflow-config, changed set multipart-handler to "disabled" from
"none"
also removed the "There will be more settings here soon."
although prevent-cache could probably use a description
11) module-config-locators
needed child module-config-locator added into General structure item
12) prevent-cache has been added,
parents: pageflow-config
child: none
type: enumerate [default | always | inDevMode ]
13) handlers are now [0-*] not [0-1]
14) spelling of link from iterator-factory to iterator-factorys *ies*
15) factory-class - added parents: expression-language & iterator-factory
16) request-interceptors
Children:global [0-1]
-> request-interceptor [0-*]
->interceptor-class [1]
-> custom-property [0-*]
B) add global as child of request-interceptors
add updated syntax
16A) add request-interceptors as global parents,
add request-interceptor as child of global
add request-interceptor to global example
d) add request-interceptor as parent to custom-property
C) add element request-interceptor
Child: interceptor-class & custom-property
parent: global
e) add request-interceptor as parent to interceptor-class
17) several children have been added into netui-config:
pageflow-config
Added: default-shared-flow-refs
type-converters
jsp-tag-config
Added: url-config
iterator-factories
request-interceptors
Added: prefix-handlers
(and corresponding children)
> 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
> Attachments: j711.txt
>
> 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
