You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by jv...@apache.org on 2001/07/04 22:29:41 UTC
cvs commit: jakarta-turbine/xdocs/proposals security-service.xml bo-managers.xml
jvanzyl 01/07/04 13:29:41
Modified: xdocs proposals.xml
xdocs/proposals bo-managers.xml
Added: xdocs/proposals security-service.xml
Log:
- adding link to leandro's prop
Revision Changes Path
1.6 +1 -0 jakarta-turbine/xdocs/proposals.xml
Index: proposals.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/proposals.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- proposals.xml 2001/06/06 22:37:19 1.5
+++ proposals.xml 2001/07/04 20:29:40 1.6
@@ -34,6 +34,7 @@
<li><a href="proposals/services-repository.html">Services Repository</a></li>
<li><a href="proposals/xslt-service.html">XSLT Service</a></li>
<li><a href="proposals/unified-templating.html">Unified Templating Service</a></li>
+<li><a href="proposals/bo-managers.html">Torque BO Managers</a></li>
</ul>
</section>
1.2 +14 -13 jakarta-turbine/xdocs/proposals/bo-managers.xml
Index: bo-managers.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/proposals/bo-managers.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- bo-managers.xml 2001/07/04 19:40:53 1.1
+++ bo-managers.xml 2001/07/04 20:29:40 1.2
@@ -22,33 +22,34 @@
<p>
<li>
BO's should shrink to be application independent and improve code reuse instead
- of agregate other functions like it does today.<br> To aliviate the BO's of
+ of agregate other functions like it does today.<br/> To aliviate the BO's of
the its actual functions , a service dedicated to all BO's of the same type
- would have to be created and deal with inclusions, exclusions, associations, etc.<br>
+ would have to be created and deal with inclusions, exclusions, associations, etc.
</li>
<li>
Aditional advantages of having a Manager per BO would be : transaction
- control, thread isolation and cache managment.<br>
- - transations would occur in Manager level and update all related caches.<br>
+ control, thread isolation and cache managment.<br/>
+ - transations would occur in Manager level and update all related caches.<br/>
- the manager should be responsible to limit access to it's internal data
- structures and BO's
+ structures and BO's <br/>
- the manager should have a pluggable cache (LRU for example). Compare this to all
- small caches that torque uses.
+ small caches that torque uses. <br/>
</li>
</p>
</section>
<section name="Requirements">
<p>
- Torque has to be modified to generate code using other templates. For example : om/Control.vm has to be patched to add the following lines :<br>
+ Torque has to be modified to generate code using other templates. For example :
+ om/Control.vm has to be patched to add the following lines :<br/>
<blockquote>
- + #set ( $fname = "${basePrefix}${firstcap}Manager.java" )<br>
- + #set ( $path = "${strings.getPackageAsPath($pkbase)}$fname" )<br>
- + $generator.parse("manager/BaseManager.vm",$path,"table",$tbl)<br>
+ + #set ( $fname = "${basePrefix}${firstcap}Manager.java" )<br/>
+ + #set ( $path = "${strings.getPackageAsPath($pkbase)}$fname" )<br/>
+ + $generator.parse("manager/BaseManager.vm",$path,"table",$tbl)<br/>
</blockquote>
- <br>
- # This should follow the same code generation policy and create : Base___Manager.java and ___Manager.java ( empty )<br>
- # All BO's will be modified, but all functionality will be preserved to avoid breaking existing code.<br>
+ <br/>
+ # This should follow the same code generation policy and create : Base___Manager.java and ___Manager.java ( empty )<br/>
+ # All BO's will be modified, but all functionality will be preserved to avoid breaking existing code.<br/>
# aditional code could be generated ( Facades, Tools ,Screens and Actions )
</p>
1.4 +0 -0 jakarta-turbine/xdocs/proposals/security-service.xml
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org