You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Krista Baker (JIRA)" <be...@incubator.apache.org> on 2005/05/12 18:57:22 UTC
[jira] Created: (BEEHIVE-711) beehive-netui-config.xml elements added need to be documented
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
Assigned to: 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
[jira] Commented: (BEEHIVE-711) beehive-netui-config.xml elements added need to be documented
Posted by "Krista Baker (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-711?page=comments#action_65454 ]
Krista Baker commented on BEEHIVE-711:
--------------------------------------
Steve, could you please review and submit this patch. Thanks, Krista
> 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
[jira] Updated: (BEEHIVE-711) beehive-netui-config.xml elements added need to be documented
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-711?page=all ]
Rich Feit updated BEEHIVE-711:
------------------------------
Assign To: Rich Feit (was: Steve Hanson)
I can take this one...
> 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: Rich Feit
> 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
[jira] Resolved: (BEEHIVE-711) beehive-netui-config.xml elements added need to be documented
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-711?page=all ]
Rich Feit resolved BEEHIVE-711:
-------------------------------
Assign To: Krista Baker (was: Rich Feit)
Resolution: Fixed
Thanks Krista -- I applied this patch with revision 170304 and added some additional edits. There were some merge conflicts with later edits to the file, but I think I got everything resolved.
> 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: Krista Baker
> 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
[jira] Updated: (BEEHIVE-711) beehive-netui-config.xml elements added need to be documented
Posted by "Krista Baker (JIRA)" <be...@incubator.apache.org>.
[ 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
[jira] Closed: (BEEHIVE-711) beehive-netui-config.xml elements added need to be documented
Posted by "Nathan Jantz (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-711?page=all ]
Nathan Jantz closed BEEHIVE-711:
--------------------------------
I reviewed this in the distribution as of rev 178693 and I saw no obvious issues with the changes applied from the patch. I validated it for well-formedness etc as well and saw no validation errors. Closing issue.
> 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: Nathan Jantz
> 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
[jira] Commented: (BEEHIVE-711) beehive-netui-config.xml elements added need to be documented
Posted by "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 '&' according to the html 401 specifications by w3c. This item can be set to false and these items will no longer be encoded to '&' 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
[jira] Assigned: (BEEHIVE-711) beehive-netui-config.xml elements added need to be documented
Posted by "Alejandro Ramirez (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-711?page=all ]
Alejandro Ramirez reassigned BEEHIVE-711:
-----------------------------------------
Assign To: Nathan Jantz (was: Steve Hanson)
Please verify.
> 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: Nathan Jantz
> 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
[jira] Assigned: (BEEHIVE-711) beehive-netui-config.xml elements added need to be documented
Posted by "Krista Baker (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-711?page=all ]
Krista Baker reassigned BEEHIVE-711:
------------------------------------
Assign To: Steve Hanson (was: Krista Baker)
Steve, I verified that the patch was submitted, would it be possible for you to give the file a once-over to be sure it is correct and close this issue?
Thanks, Krista
> 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