cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache Cayenne > 3.0 Wish List
Date Wed, 18 Nov 2009 19:19:00 GMT
<html>
<head>
    <base href="http://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/1519/1/25/_/styles/combined.css?spaceKey=CAY&amp;forWysiwyg=true"
type="text/css">
    </head>
<body style="background-color: white" bgcolor="white">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
     <h2><s>3.0 Wish List</s></h2>
     <h4>Page <b>removed</b> by             <a href="http://cwiki.apache.org/confluence/display/~andrus">Andrus
Adamchik</a>
    </h4>
     <br/>
     <div class="notificationGreySide">
         <h3><a name="3.0WishList-CoreFramework"></a>Core Framework</h3>


<h5><a name="3.0WishList-ExpressionEnhancements"></a>Expression Enhancements</h5>

<ul>
	<li>Implement split expressions and other expression enhancement ideas per <a href="http://issues.apache.org/cayenne/browse/CAY-514"
rel="nofollow">CAY-514</a>.</li>
	<li><a href="/confluence/display/CAY/Expression+Functions" title="Expression Functions">Expression
Functions</a></li>
</ul>


<h5><a name="3.0WishList-CachingEnhancements"></a>Caching Enhancements</h5>
<div class='panelMacro'><table class='tipMacro'><colgroup><col width='24'><col></colgroup><tr><td
valign='top'><img src="/confluence/images/icons/emoticons/check.gif" width="16" height="16"
align="absmiddle" alt="" border="0"></td><td><b>"DONE"</b><br
/><p><a href="/confluence/pages/createpage.action?spaceKey=CAYDOC&amp;title=RefreshQuery"
class="createlink">CAYDOC:RefreshQuery</a></p></td></tr></table></div>

<h3><a name="3.0WishList-CayenneModelerImprovements"></a>Cayenne Modeler
Improvements</h3>


<h5><a name="3.0WishList-ConsolidateDbEntity%2FObjEntityViews"></a>Consolidate
DbEntity/ObjEntity Views</h5>

<p>Consolidate the DbEntity/ObjEntity views in Cayenne Modeler so the information is
easier to see (more like EOModeler). This will make editing and viewing models much easier,
especially with large models, since the current approach requires a lot of scrolling to see
everything.</p>

<h5><a name="3.0WishList-AutoSync"></a>AutoSync</h5>
<div class='panelMacro'><table class='tipMacro'><colgroup><col width='24'><col></colgroup><tr><td
valign='top'><img src="/confluence/images/icons/emoticons/check.gif" width="16" height="16"
align="absmiddle" alt="" border="0"></td><td><b>"DONE"</b><br
/><p>Add a preference to allow auto-synchronization of DbEntity changes into the
ObjEntity.</p></td></tr></table></div>

<h5><a name="3.0WishList-ModificationTracking"></a>Modification Tracking</h5>

<p>Have the modeler better understand which ObjEntities have been updated since the
last code generation cycle and auto-select the "dirty" classes by default.</p>

<h5><a name="3.0WishList-JavaDoc"></a>JavaDoc</h5>

<p>Allow JavaDoc to be entered into the model to be output in the generated Java classes.
<em>(Andrus) see <a href="http://objectstyle.org/jira/browse/CAY-400" rel="nofollow">CAY-400
Jira Issue</a></em></p>

<h5><a name="3.0WishList-PasswordEncoding"></a>Password Encoding</h5>
<div class='panelMacro'><table class='tipMacro'><colgroup><col width='24'><col></colgroup><tr><td
valign='top'><img src="/confluence/images/icons/emoticons/check.gif" width="16" height="16"
align="absmiddle" alt="" border="0"></td><td><b>"DONE"</b><br
/><p>Add extra password encoding options to the modeler per <a href="http://objectstyle.org/jira/browse/CAY-642"
rel="nofollow">Jira Issue 642</a>.  See <a href="/confluence/display/CAY/Password+Encoding"
title="Password Encoding">Password Encoding</a> for more information.</p></td></tr></table></div>

<h3><a name="3.0WishList-CayenneModelImprovements"></a>Cayenne Model Improvements</h3>


<h5><a name="3.0WishList-ChangeModelFilename"></a>Change Model Filename</h5>

<p>Allow for models that are not named "cayenne.xml". This would accomplish two things:</p>
<ol>
	<li>More complex/layered applications could be constructed. One team could be creating
and maintaining an Authorization framework and administration application while other teams
could be creating web applications that use the Authorization framework while connecting to
their own separate databases/models. The current version of Cayenne will only load one "cayenne.xml"
by default - the first one it finds in the Java CLASSPATH.</li>
	<li>XML is too generic of a file extension. It doesn't associate well with Cayenne
Modeler. If you had models named Authorization.cayenne, then the ".cayenne" extension could
be associated with Cayenne Modeler via an OS's extension mapping features and allow for double-clicking
on the model name to open it up in Cayenne Modeler.[mlk:&nbsp;&nbsp; Actually, I'd
rather see .cayenne.xml so it opens as an xml file in non-cayenne-aware editors, but maybe
that won't help on some operating systems.]</li>
</ol>


<p>This change would also require changes to Cayenne Modeler to support saving with
different names.</p>

<h5><a name="3.0WishList-LinkUnregisteredDOs"></a>Link Unregistered DOs</h5>

<p>Cayenne 1.2 has made things a lot easier by allowing an unregistered DO to be linked
with a registered one. In this case, the unregistered one is registered with the DC of the
DO it is linked with. It would be very useful if two unregistered DOs could be linked and
then when one is registered with a DC, it cascades down the whole object graph. The DOs could
then truly be treated as POJOs and all the persistence stuff centralized to one part of the
program, rather than being interspersed throughout.</p>

<h5><a name="3.0WishList-Memorymanagement"></a>Memory management</h5>

<p>It would be nice to be able to have more control of the memory usage.</p>
<ol>
	<li>Streaming blob/clob. It should be possible to not cache blobs. <a href="http://objectstyle.org/jira/secure/ViewIssue.jspa?key=CAY-316"
rel="nofollow">CAY-316</a></li>
	<li>Be able to have different level of caching for different tables.</li>
</ol>


<h5><a name="3.0WishList-DbEntity%2FObjEntitymappingenhancements"></a>DbEntity
/ ObjEntity mapping enhancements</h5>

<p>Add the ability for users to define regexes to manipulate field names, table names,
etc when syncing or importing a database. This was discussed in the mailing list:</p>

<p><a href="http://www.objectstyle.org/cayenne/lists/cayenne-user/2005/11/0090.html"
rel="nofollow">http://www.objectstyle.org/cayenne/lists/cayenne-user/2005/11/0090.html</a></p>

<p>May be nice to abstract this even further with a mapping class, which would be a
RegexMapper by default. This way, users could get total control if they happen to need it.</p>

<h3><a name="3.0WishList-JPAcompliance"></a>JPA compliance</h3>
     </div>
</div>
</div>
</div>
</div>
</body>
</html>

Mime
View raw message