This is an automated email from the ASF dual-hosted git repository.
jleroux pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ofbiz-site.git
The following commit(s) were added to refs/heads/master by this push:
new 231a09a Improved: updates test-suite.xsd and site-conf.xsd
documentation
231a09a is described below
commit 231a09ad0f8a020443ebb1294e5bbb5a31f65c28
Author: Jacques Le Roux <jacques.le.r...@les7arts.com>
AuthorDate: Tue Dec 3 11:04:04 2024 +0100
Improved: updates test-suite.xsd and site-conf.xsd documentation
---
dtds/site-conf.xsd | 10 ++++++++++
dtds/test-suite.xsd | 29 -----------------------------
2 files changed, 10 insertions(+), 29 deletions(-)
diff --git a/dtds/site-conf.xsd b/dtds/site-conf.xsd
index cbf2cfd..79a02b7 100644
--- a/dtds/site-conf.xsd
+++ b/dtds/site-conf.xsd
@@ -792,6 +792,16 @@ under the License.
</xs:documentation>
</xs:annotation>
</xs:attribute>
+ <xs:attribute type="xs:boolean" name="secure-context" default="true">
+ <xs:annotation>
+ <xs:documentation>
+ If secure-context=false, we authorize to forward to the
renderer some parameters with interpretable code.
+ This raise a potential risk of code injection. This can be
usefully for some administration page to
+ configure templating (like ftl for email or dynamic screen
template).
+ For this reason if secure-context=false, auth is set as
true.
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
<xs:attribute name="x-frame-options" default="sameorigin">
<xs:annotation>
<xs:documentation>
diff --git a/dtds/test-suite.xsd b/dtds/test-suite.xsd
index 6092aff..74d6b71 100644
--- a/dtds/test-suite.xsd
+++ b/dtds/test-suite.xsd
@@ -89,35 +89,6 @@ under the License.
</xs:attribute>
</xs:attributeGroup>
- <xs:element name="groovy-test-suite" substitutionGroup="TestCaseTypes">
- <xs:annotation>
- <xs:documentation>
- Used for JUnit test suites written as a Groovy class. See
http://groovy-lang.org/testing.html. This is rather to be used during
development and testing.
- When going to production; for performance reason
(compilation), you should use rather use junit-test-suite and move the test
file under main and use.
- See existing examples.
- </xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:attributeGroup ref="attlist.groovy-test-suite"/>
- </xs:complexType>
- </xs:element>
- <xs:attributeGroup name="attlist.groovy-test-suite">
- <xs:attribute type="xs:string" name="name"/>
- <xs:attribute type="xs:string" name="location" use="required">
- <xs:annotation>
- <xs:documentation>
- Give the location where is groovy file that contains the
test suite.
- You can use a flexible URL location like
-
component://service/src/test/groovy/org/apache/ofbizservice/test/TestServices.groovy
- This is rather to be used during development and testing
- When going to production you need to move the test file
under main. See existing examples.
- When going to production; for performance reason
(compilation), you should use rather use junit-test-suite and move the test
file under main and use.
- See existing examples.
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:attributeGroup>
-
<xs:element name="service-test" substitutionGroup="TestCaseTypes">
<xs:complexType>
<xs:attributeGroup ref="attlist.service-test"/>
