i.1.9.2.source-code.model.xsd Maven / Gradle / Ivy
The newest version!
By default this is the object name suffixed with s.
If there is a different plural, like Children, set this element.
When trashcan is set to true, redora.rdo.configuration.model.RedoraTrash
will be implemented. This mean that when
a record is deleted, it will not be
really deleted, but the roDeleted
attribute will be set to true.
Custom order by clause without 'order by'. You can use ${ALIAS}.
When sorted is set to true, a field called
sortOrder is added to this pojo. With this
field a sorting order can be maintained.
Comma separated list of interfaces that
the generated object should implement.
Optional, if you use multiple schemas, set the schema name here.
You can set a database to schema mapping in the configuration.properties file if needed.
Override the default finders: findById and findAll. This finder should
have a name attribute (in order to be overridable).
Generates Boolean type attribute. In the database this
will become also boolean.
Mandatory sequence number
Mandatory description of the business rule, this is
used for the Java API documentation in your model
Comma separated list of attributes in this models
that are touched by this rule.
Translate to java.util.Date, but it is a date field in
the database, so with the accuracy on day level. If you
want accuracy on seconds level, choose datatime.
Datetime however requires 8 bytes storages while date
just needs 3.
evaluates the 'yyyy-MM-dd' string representation of the date
Translates to java.util.Date in seconds accuracy. If
only per day accuracy is needed use date instead.
evaluates the 'yyyy-MM-dd hh:mm:ss' string
representation of the date
The content of this element is used to generate the
Javadoc. So, provide API style documentation here.
Optional, by default the class name is used (uncapitalized), but if you want
a different field name, use this to override.
Default local. When true an external enum class will
be generated in the xxx.enums. package and thereby
get a global scope.
Relationships and enums get default finder, for other element, if you want
a finder to be generated, you must specify this explicitly.
Finders are by default turned of for http request. If you want to allow
access from http, turn it on by setting http to true.
A descriptive help text that will be available to the
user when he, for example, clicks on a help button, or
hovers over a caption.
Generates String type attribute specialized for HTML
content. In the database this will become text. The
content will be cleaned up using AntiSamy
(http://www.owasp.org/index.php/Category:OWASP_AntiSamy_Project),
meaning the HTML tags will be balanced and evaluated for
being valid and javascript code and any other posible
malicious content will be removed silently (INFO
loglevel trace).
The AntiSamy policy file that should be used. You
can use one of the standard policy files: -
antisamy.xml; - antisamy-slashdot.xml; -
antisamy-myspace.xml; - antisamy-ebay.xml; -
antisamy-anythinggoes.xml; - antisamy-tinymce.xml;
Or you can add a custom policy file in the classpath. See also
http://www.owasp.org/index.php/Category:OWASP_AntiSamy_Project
Includes a re-usable model snippet into this
model. You can create a reusable building
blocks in the model, for example the
attributes needed for an address. Or to
define globally scoped enum's in one place.
The include file must implement the
include.xsd schema and located in the
model/includes directory. The name of the
file must be given with the name attribute
without path and without file extension
(.xml). For example name="address", for the
address example.
Message name
Constant name
Name of the referenced objects. This class should exist in this model.
For n-to-m relations, you can define the name used in the relation table (the join table) to
define this object. By default this name is defined by [object].[name]. For 1-to-n relations
myName defines how this object is named at the related object.
For n-to-m relations, you can define the name used in the relation table (the join table) to define the related object.
Normally this name is defined by [relatedObject].[name].
Normally as plural the class name is use adding 's'.
For example if the class name is Detail, in the
model the Details is used. If the plural is
different, for example Child / Children, provide the
plural here.
When true the child records are deleted when the
parent is deleted. Default on for multiplicity='1-to-n').
Not applicable for n-to-m relations.
By default the simple 1-to-n multiplicity is
assumed. When set n-to-m a helper table is created
called <this Object><reference Object>
an n to m relationships will be possible.
Generates String type attribute. In the database this
will become varchar, mediumtext or longtext.
References a n-to-1 relationship with another class in
the model.
Optional alternative name for the related object. For example when you use several relations to the same class.
Remember that you also have to set theirName in the opposing set on the related object.
When provided, by default the queries will sort on this field.
Mind you Redora does by default sort on fields that have list=true.
If you did not set list, it will sort on the notnull fields.
If you also donot have these fields it will sort on the first
attribute you defined.
And, the order of the definition of attrributes defines the
pecking order for sorting.
Sort can be set to asc (ascending) and desc (descending).
Custom queries that are generated in PojoSQLBase. Define here your custom query, you can then use it in the code.
© 2015 - 2024 Weber Informatics LLC | Privacy Policy