cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aadamc...@apache.org
Subject svn commit: r1618337 - /cayenne/site/cms/trunk/content/docs/1.2/
Date Sat, 16 Aug 2014 11:37:03 GMT
Author: aadamchik
Date: Sat Aug 16 11:37:02 2014
New Revision: 1618337

URL: http://svn.apache.org/r1618337
Log:
fixing broken image

Modified:
    cayenne/site/cms/trunk/content/docs/1.2/accessing-pk-and-fk-values.html
    cayenne/site/cms/trunk/content/docs/1.2/configuring-logging.html
    cayenne/site/cms/trunk/content/docs/1.2/dataviews.html
    cayenne/site/cms/trunk/content/docs/1.2/flattened-relationships.html
    cayenne/site/cms/trunk/content/docs/1.2/handling-inheritance.html
    cayenne/site/cms/trunk/content/docs/1.2/parameterized-queries.html
    cayenne/site/cms/trunk/content/docs/1.2/path-expressions.html
    cayenne/site/cms/trunk/content/docs/1.2/primary-key-generation.html
    cayenne/site/cms/trunk/content/docs/1.2/relationships.html
    cayenne/site/cms/trunk/content/docs/1.2/selecting-objects.html
    cayenne/site/cms/trunk/content/docs/1.2/swing-applications.html

Modified: cayenne/site/cms/trunk/content/docs/1.2/accessing-pk-and-fk-values.html
URL: http://svn.apache.org/viewvc/cayenne/site/cms/trunk/content/docs/1.2/accessing-pk-and-fk-values.html?rev=1618337&r1=1618336&r2=1618337&view=diff
==============================================================================
--- cayenne/site/cms/trunk/content/docs/1.2/accessing-pk-and-fk-values.html (original)
+++ cayenne/site/cms/trunk/content/docs/1.2/accessing-pk-and-fk-values.html Sat Aug 16 11:37:02
2014
@@ -4,7 +4,7 @@ Title: Accessing PK and FK values
 
 <P>Normally it is not advisable to map primary and foreign key columns (PK and FK)
as Java class properties (ObjAttributes). When reverse engineering of the database is done
using CayenneModeler, produced mapping will reflect that - PKs and FKs will not be included
in the Java class. However sometimes an application requires access to these values.</P>
 
-<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD>For generic
and easy API to obtain an object primary key or to find an object from a known PK, skip to
the next chapter on DataObjectUtils class.</TD></TR></TABLE></DIV>
+<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="http://cayenne.apache.org/docs/1.2/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD>For generic
and easy API to obtain an object primary key or to find an object from a known PK, skip to
the next chapter on DataObjectUtils class.</TD></TR></TABLE></DIV>
 
 <P>Cayenne provides a generic way to do access primary and foreign keys by creating
custom get* methods in the DataObject subclass. Lets take a Painting class as an example.
The following code is generated by CayenneModeler:</P>
 
@@ -56,7 +56,7 @@ Title: Accessing PK and FK values
 
 <P>The following custom methods should be added to the Painting class to access the
values of ARTIST_ID and PAINTING_ID:</P>
 
-<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD>If you
perform class generation using Ant, you can customize class generation templates to generte
these methods for you. Eventually CayenneModeler will support this too as optional functionality.</TD></TR></TABLE></DIV>
+<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="http://cayenne.apache.org/docs/1.2/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD>If you
perform class generation using Ant, you can customize class generation templates to generte
these methods for you. Eventually CayenneModeler will support this too as optional functionality.</TD></TR></TABLE></DIV>
 
 <DIV class="code panel" style="border-width: 1px;"><DIV class="codeContent panelContent">
 <PRE class="code-java"><SPAN class="code-keyword">package</SPAN> org.objectstyle.art;

Modified: cayenne/site/cms/trunk/content/docs/1.2/configuring-logging.html
URL: http://svn.apache.org/viewvc/cayenne/site/cms/trunk/content/docs/1.2/configuring-logging.html?rev=1618337&r1=1618336&r2=1618337&view=diff
==============================================================================
--- cayenne/site/cms/trunk/content/docs/1.2/configuring-logging.html (original)
+++ cayenne/site/cms/trunk/content/docs/1.2/configuring-logging.html Sat Aug 16 11:37:02 2014
@@ -19,7 +19,7 @@ log4j.logger.org.objectstyle.cayenne.acc
 </PRE>
 </DIV></DIV>
 
-<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD><B>Users
of Other Logging Frameworks</B><BR>If your application uses another package for
its own logging purposes (like JDK 1.4 java.util.logging, or commons-logging from Jakarta),
Cayenne Log4J-based logging will not interfere with your other logging configurations.</TD></TR></TABLE></DIV>
+<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="http://cayenne.apache.org/docs/1.2/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD><B>Users
of Other Logging Frameworks</B><BR>If your application uses another package for
its own logging purposes (like JDK 1.4 java.util.logging, or commons-logging from Jakarta),
Cayenne Log4J-based logging will not interfere with your other logging configurations.</TD></TR></TABLE></DIV>
 
 <DIV class="panelMacro"><TABLE class="tipMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD><B>Log4J
Users</B><BR>If your application already uses Log4J, Cayenne will simply use your
existing configuration.</TD></TR></TABLE></DIV>
 

Modified: cayenne/site/cms/trunk/content/docs/1.2/dataviews.html
URL: http://svn.apache.org/viewvc/cayenne/site/cms/trunk/content/docs/1.2/dataviews.html?rev=1618337&r1=1618336&r2=1618337&view=diff
==============================================================================
--- cayenne/site/cms/trunk/content/docs/1.2/dataviews.html (original)
+++ cayenne/site/cms/trunk/content/docs/1.2/dataviews.html Sat Aug 16 11:37:02 2014
@@ -10,5 +10,5 @@ Title: DataViews
 
 <P>For manual editing of the DataViews, DataView DTD is included in the distribution.
It is pretty small and the names are self-explanatory once you become familiar with the Data
View structure described in this chapter.</P>
 
-<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD><B>JDOM
Note</B><BR>DataViews use JDOM, so in addition to the jar files required by a
regular Cayenne application, DataViews-based application must have access to JDOM jars. JDOM
can be downloaded from <A href="http://www.jdom.org/" class="external-link" rel="nofollow">http://www.jdom.org/</A>.</TD></TR></TABLE></DIV>
+<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="http://cayenne.apache.org/docs/1.2/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD><B>JDOM
Note</B><BR>DataViews use JDOM, so in addition to the jar files required by a
regular Cayenne application, DataViews-based application must have access to JDOM jars. JDOM
can be downloaded from <A href="http://www.jdom.org/" class="external-link" rel="nofollow">http://www.jdom.org/</A>.</TD></TR></TABLE></DIV>
 

Modified: cayenne/site/cms/trunk/content/docs/1.2/flattened-relationships.html
URL: http://svn.apache.org/viewvc/cayenne/site/cms/trunk/content/docs/1.2/flattened-relationships.html?rev=1618337&r1=1618336&r2=1618337&view=diff
==============================================================================
--- cayenne/site/cms/trunk/content/docs/1.2/flattened-relationships.html (original)
+++ cayenne/site/cms/trunk/content/docs/1.2/flattened-relationships.html Sat Aug 16 11:37:02
2014
@@ -3,4 +3,4 @@ Title: Flattened Relationships
 	
 
 <P>Flattened relationships represent relationship between two types of DataObjects
that is not direct in the underlying relational storage. Instead it is mapped across one or
more &quot;join&quot; tables. Still from the application point of view there is no
diffrence in working with flattened relationships compared to the &quot;normal&quot;
ones. Cayenne internally figures out how to build the needed query joins to retrieve related
objects. On adding or removing an object to/from a flattened relationship via a corresponding
&quot;addTo...&quot; / &quot;removeFrom...&quot; method an appropriate join
record is created or removed.</P>
-<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD><B>Flattened
Relationships Limitations</B><BR>Currently only many-to-many flattened relatationships
with a single join table can be modified. All other types of flattened relationships can be
used as &quot;read-only&quot;. This is reflected in the DataObject code generated
for such relationships - no set/addTo/RemoveFrom methods are created for read-only relationships.</TD></TR></TABLE></DIV>
+<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="http://cayenne.apache.org/docs/1.2/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD><B>Flattened
Relationships Limitations</B><BR>Currently only many-to-many flattened relatationships
with a single join table can be modified. All other types of flattened relationships can be
used as &quot;read-only&quot;. This is reflected in the DataObject code generated
for such relationships - no set/addTo/RemoveFrom methods are created for read-only relationships.</TD></TR></TABLE></DIV>

Modified: cayenne/site/cms/trunk/content/docs/1.2/handling-inheritance.html
URL: http://svn.apache.org/viewvc/cayenne/site/cms/trunk/content/docs/1.2/handling-inheritance.html?rev=1618337&r1=1618336&r2=1618337&view=diff
==============================================================================
--- cayenne/site/cms/trunk/content/docs/1.2/handling-inheritance.html (original)
+++ cayenne/site/cms/trunk/content/docs/1.2/handling-inheritance.html Sat Aug 16 11:37:02
2014
@@ -4,7 +4,7 @@ Title: Handling Inheritance
 
 <P>&quot;Inheritance&quot; is an Object Oriented concept absent in traditional
RDBMS. Cayenne however allows to map a hierarchical class tree to a single base table (so
called &quot;single table inheritance&quot;). Such mapping is described in detail
in the <A href="modeling-inheritance.html" title="Modeling Inheritance">Modeler Guide</A>.
The idea of single table inheritance is that a &quot;class&quot; of a database row
is determined from the values in one or more columns of the base table. These columns are
called &quot;class designator columns&quot;.</P>
 
-<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD><B>Initial
Values of the Classs Designator Columns</B><BR>Assigning correct values to the
&quot;class designator columns&quot; mentioned above is one task that is not yet automated
in Cayenne and requires user code in the DataObject, as discussed in the next subsection.
In the future versions this will likely be handled in the mapping and completely outside of
the Java classes, so the advise below will become obsolete.</TD></TR></TABLE></DIV>
+<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="http://cayenne.apache.org/docs/1.2/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD><B>Initial
Values of the Classs Designator Columns</B><BR>Assigning correct values to the
&quot;class designator columns&quot; mentioned above is one task that is not yet automated
in Cayenne and requires user code in the DataObject, as discussed in the next subsection.
In the future versions this will likely be handled in the mapping and completely outside of
the Java classes, so the advise below will become obsolete.</TD></TR></TABLE></DIV>
 
 <H3><A name="HandlingInheritance-InheritanceandnewDataObjects"></A>Inheritance
and new DataObjects</H3>
 <P>Consider the following class hierarchy (also used in the Modeler Guide example):<BR>
@@ -87,6 +87,6 @@ List employees = context.performQuery(qu
 </PRE>
 </DIV></DIV>
 
-<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD>Whenever
an object is obtained via a relationship, it is always fully resolved to the lowest possible
subclass in an entity inheritance tree.</TD></TR></TABLE></DIV>
+<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="http://cayenne.apache.org/docs/1.2/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD>Whenever
an object is obtained via a relationship, it is always fully resolved to the lowest possible
subclass in an entity inheritance tree.</TD></TR></TABLE></DIV>
 
 <DIV class="panelMacro"><TABLE class="warningMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="https://cwiki.apache.org/confluence/images/icons/emoticons/forbidden.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD>Use <TT>setResolvingInherited(false)</TT>
with caution, and only if you never plan to work with subclasses. The downside of it is that
the DataContext may end up with two objects pointing to the same database row, thus violating
uniquing principle. With the above example, this may happen if at a later time user decides
to fetch Managers directly, or if a Manager object is obtained via a relationship.</TD></TR></TABLE></DIV>

Modified: cayenne/site/cms/trunk/content/docs/1.2/parameterized-queries.html
URL: http://svn.apache.org/viewvc/cayenne/site/cms/trunk/content/docs/1.2/parameterized-queries.html?rev=1618337&r1=1618336&r2=1618337&view=diff
==============================================================================
--- cayenne/site/cms/trunk/content/docs/1.2/parameterized-queries.html (original)
+++ cayenne/site/cms/trunk/content/docs/1.2/parameterized-queries.html Sat Aug 16 11:37:02
2014
@@ -3,7 +3,7 @@ Title: Parameterized Queries
 	
 
 <P>SelectQuery objects can be rather complex. They may contain long qualifiers and
lots of tuning parameters. Parameterized Queries feature addresses reusability of complex
queries. With this feature, for each group of queries that differ only in the values used
in the qualifier, a developer may create a single shared &quot;prototype&quot; or
&quot;template&quot; query, and use it later as a factory for other queries. All settings
configured in the prototype object will be passed to the final queries. Qualifier of the prototype
query may use named parameters that are substituted for real values when a final query is
created from the prototype.</P>
-<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD>&quot;Prototype&quot;
queries are normally created in CayenneModeler and stored in the DataMap XML file. &quot;Queries
Stored in DataMap&quot; chapter describes how to use such templates. This chapter shows
how to create them on the spot using the API calls.</TD></TR></TABLE></DIV>
+<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="http://cayenne.apache.org/docs/1.2/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD>&quot;Prototype&quot;
queries are normally created in CayenneModeler and stored in the DataMap XML file. &quot;Queries
Stored in DataMap&quot; chapter describes how to use such templates. This chapter shows
how to create them on the spot using the API calls.</TD></TR></TABLE></DIV>
 
 <P>Building a prototype query using <TT>Expression.fromString(..)</TT>:</P>
 

Modified: cayenne/site/cms/trunk/content/docs/1.2/path-expressions.html
URL: http://svn.apache.org/viewvc/cayenne/site/cms/trunk/content/docs/1.2/path-expressions.html?rev=1618337&r1=1618336&r2=1618337&view=diff
==============================================================================
--- cayenne/site/cms/trunk/content/docs/1.2/path-expressions.html (original)
+++ cayenne/site/cms/trunk/content/docs/1.2/path-expressions.html Sat Aug 16 11:37:02 2014
@@ -15,7 +15,7 @@ Title: Path Expressions
 </UL>
 
 
-<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD><B>What
Does 'navigation' Means</B><BR>The term &quot;navigation&quot; in the
description above could mean different things depending on the context. For instance, when
evaluating an expression in memory, &quot;navigating&quot; an object path would simply
return the value of a corresponding object property. When the same expression is used in a
select query qualifier, it resolves to the name of a table column used in a WHERE clause of
a generated SQL statement.</TD></TR></TABLE></DIV>
+<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="http://cayenne.apache.org/docs/1.2/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD><B>What
Does 'navigation' Means</B><BR>The term &quot;navigation&quot; in the
description above could mean different things depending on the context. For instance, when
evaluating an expression in memory, &quot;navigating&quot; an object path would simply
return the value of a corresponding object property. When the same expression is used in a
select query qualifier, it resolves to the name of a table column used in a WHERE clause of
a generated SQL statement.</TD></TR></TABLE></DIV>
 
 <H3><A name="PathExpressions-DatabasePathExpressions"></A>Database Path
Expressions</H3>
 <P>Database Path Expressions provide an easy way to navigate through DB table joins.
Instead of complex join semantics such expressions utilize the names of DbRelationships defined
in Cayenne DataMap. Translating the above object path examples into the DB realm, database
path expressions might look like this:</P>

Modified: cayenne/site/cms/trunk/content/docs/1.2/primary-key-generation.html
URL: http://svn.apache.org/viewvc/cayenne/site/cms/trunk/content/docs/1.2/primary-key-generation.html?rev=1618337&r1=1618336&r2=1618337&view=diff
==============================================================================
--- cayenne/site/cms/trunk/content/docs/1.2/primary-key-generation.html (original)
+++ cayenne/site/cms/trunk/content/docs/1.2/primary-key-generation.html Sat Aug 16 11:37:02
2014
@@ -68,5 +68,5 @@ Title: Primary Key Generation
 
 <P>To generate the necessary database objects for the primary key autogeneration, use
CayenneModeler and follow the instructions given <A href="generate-primary-key-support.html"
title="Generate Primary Key Support">here</A>.</P>
 
-<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD>Cayenne
only supports automatic PK generation for a single column per table.</TD></TR></TABLE></DIV>
+<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="http://cayenne.apache.org/docs/1.2/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD>Cayenne
only supports automatic PK generation for a single column per table.</TD></TR></TABLE></DIV>
 

Modified: cayenne/site/cms/trunk/content/docs/1.2/relationships.html
URL: http://svn.apache.org/viewvc/cayenne/site/cms/trunk/content/docs/1.2/relationships.html?rev=1618337&r1=1618336&r2=1618337&view=diff
==============================================================================
--- cayenne/site/cms/trunk/content/docs/1.2/relationships.html (original)
+++ cayenne/site/cms/trunk/content/docs/1.2/relationships.html Sat Aug 16 11:37:02 2014
@@ -21,7 +21,7 @@ painting.setToArtist(newArtist);
 </SPAN><SPAN class="code-comment">// painting.setToArtist(<SPAN class="code-keyword">null</SPAN>);</SPAN>
 </PRE>
 </DIV></DIV>
-<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD>When adding
or removing an object from any kind of relationship, Cayenne will locate and modify an existing
reverse relationship as appropriate.</TD></TR></TABLE></DIV>
+<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="http://cayenne.apache.org/docs/1.2/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD>When adding
or removing an object from any kind of relationship, Cayenne will locate and modify an existing
reverse relationship as appropriate.</TD></TR></TABLE></DIV>
 
 <H3><A name="Relationships-ToManyRelationships"></A>To-Many Relationships</H3>
 
@@ -43,4 +43,4 @@ painting.setToArtist(newArtist);
 artist.addToPaintingArray(newPainting);
 </PRE>
 </DIV></DIV>
-<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD>While to-many
relationships in Cayenne are represented by Lists, they are really ordered Sets, as they are
not allowed to contain the same object more than once.</TD></TR></TABLE></DIV>
+<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="http://cayenne.apache.org/docs/1.2/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD>While to-many
relationships in Cayenne are represented by Lists, they are really ordered Sets, as they are
not allowed to contain the same object more than once.</TD></TR></TABLE></DIV>

Modified: cayenne/site/cms/trunk/content/docs/1.2/selecting-objects.html
URL: http://svn.apache.org/viewvc/cayenne/site/cms/trunk/content/docs/1.2/selecting-objects.html?rev=1618337&r1=1618336&r2=1618337&view=diff
==============================================================================
--- cayenne/site/cms/trunk/content/docs/1.2/selecting-objects.html (original)
+++ cayenne/site/cms/trunk/content/docs/1.2/selecting-objects.html Sat Aug 16 11:37:02 2014
@@ -4,7 +4,7 @@ Title: Selecting Objects
 
 <P>If a stored procedure is known to return at least one result set, procedure queries
can be executed just like normal select queries. Of course in addtion to returning data, such
procedures can perform any other database operations.</P>
 
-<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD>Currently
all procedure queries will return data rows, not DataObjects. If the returned row (Map) contains
all the attributes needed to recreate a DataObject, this can be done by calling <TT>DataContext.objectFromDataRow()</TT>.</TD></TR></TABLE></DIV>
+<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="http://cayenne.apache.org/docs/1.2/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD>Currently
all procedure queries will return data rows, not DataObjects. If the returned row (Map) contains
all the attributes needed to recreate a DataObject, this can be done by calling <TT>DataContext.objectFromDataRow()</TT>.</TD></TR></TABLE></DIV>
 
 <P>Below is an example of creating a ProcedureQuery, initializing its parameters, and
processing execution results.</P>
 

Modified: cayenne/site/cms/trunk/content/docs/1.2/swing-applications.html
URL: http://svn.apache.org/viewvc/cayenne/site/cms/trunk/content/docs/1.2/swing-applications.html?rev=1618337&r1=1618336&r2=1618337&view=diff
==============================================================================
--- cayenne/site/cms/trunk/content/docs/1.2/swing-applications.html (original)
+++ cayenne/site/cms/trunk/content/docs/1.2/swing-applications.html Sat Aug 16 11:37:02 2014
@@ -9,4 +9,4 @@ Title: Swing Applications
 <P>Cayenne DataViews solve these problems. Data Views act as a bridge between the domain
defined in terms of Cayenne DataObjects and a presentation layer built with Swing. Potentially
they can be used in the Web environment as well, but Swing integration is the main direction.
Conceptually, Data Views are close to the application facades described, for instance, by
<A href="http://www.martinfowler.com/apsupp/appfacades.pdf" class="external-link" rel="nofollow">Martin
Fowler</A>. The following figure shows the area where Data Views can be applied.<BR>
 <SPAN class="image-wrap" style=""><IMG src="swing-applications.data/dataview-usecases.gif"
style="border: 0px solid black"></SPAN></P>
 
-<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD><B>Validation</B><BR>The
validation rules mentioned in the Use Cases are meant to be &quot;lightweght&quot;,
i.e. it is generally agreed the validation related code to enforce the business rules should
be located in the domain area but, still, there are various checks one could prefer to perform
right in the presentation layer like inclusion in a predefined range of values, correct input
format, sometimes, even preliminary credit card number validity check with the well known
Luhn algorithm, the other kinds of sanity checks. Presently the validation is on the list
of the features to be added.</TD></TR></TABLE></DIV>
+<DIV class="panelMacro"><TABLE class="infoMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD
valign="top"><IMG src="http://cayenne.apache.org/docs/1.2/images/icons/emoticons/information.gif"
width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD><B>Validation</B><BR>The
validation rules mentioned in the Use Cases are meant to be &quot;lightweght&quot;,
i.e. it is generally agreed the validation related code to enforce the business rules should
be located in the domain area but, still, there are various checks one could prefer to perform
right in the presentation layer like inclusion in a predefined range of values, correct input
format, sometimes, even preliminary credit card number validity check with the well known
Luhn algorithm, the other kinds of sanity checks. Presently the validation is on the list
of the features to be added.</TD></TR></TABLE></DIV>



Mime
View raw message