You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by jo...@apache.org on 2001/04/13 19:24:44 UTC
cvs commit: jakarta-turbine/docs/proposals application-service-proposal.html services-repository-proposal.html turbine-2.2-proposals.html
jon 01/04/13 10:24:44
Modified: docs index.html
docs/proposals application-service-proposal.html
services-repository-proposal.html
turbine-2.2-proposals.html
Log:
html cleanup
applied geir's patch to index.html
Revision Changes Path
1.35 +3 -1 jakarta-turbine/docs/index.html
Index: index.html
===================================================================
RCS file: /home/cvs/jakarta-turbine/docs/index.html,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- index.html 2001/04/12 12:30:20 1.34
+++ index.html 2001/04/13 17:24:44 1.35
@@ -291,7 +291,9 @@
</td></tr>
<tr><td>
<blockquote>
- <a href="http://jakarta.apache.org/turbine/tdk/">Here</a>
+ <p>
+JDK 1.2 versions are available <a href="http://jakarta.apache.org/turbine/tdk/">Here</a>.
+</p>
</blockquote>
</td></tr>
</table>
1.7 +73 -1 jakarta-turbine/docs/proposals/application-service-proposal.html
Index: application-service-proposal.html
===================================================================
RCS file: /home/cvs/jakarta-turbine/docs/proposals/application-service-proposal.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- application-service-proposal.html 2001/04/12 12:30:25 1.6
+++ application-service-proposal.html 2001/04/13 17:24:44 1.7
@@ -141,7 +141,10 @@
<tr><td>
<blockquote>
<p>
-</p>
+ The application services would allow fully functional Turbine applications
+ to be packaged up in the form of JAR files and deployed during Turbine
+ startup.
+ </p>
</blockquote>
</td></tr>
</table>
@@ -155,6 +158,75 @@
<blockquote>
<p>
</p>
+ </blockquote>
+ </td></tr>
+ </table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="Requirements"><strong>Requirements</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <p>
+<ul>
+ <li>
+ Turbine would probably process a directory of JAR files
+ that contain sub-applications. The manifest would contain
+ a set of instructions to be used by the application service
+ so that the sub-application would be processed correctly
+ and usable by Turbine. This may be the module.packages
+ to add, or template paths to add, or whatever else is
+ needed to bootstrap the sub-application.
+ </li>
+
+ <li>
+ Module packages have to be dynamically configurable.
+ The assembler broker must accept additional packages
+ to look in for modules after the system has started.
+ </li>
+
+ <li>
+ Must be able to load templates from JAR files. Velocity
+ can do this, and it can probably be done for the other
+ template services as well.
+ </li>
+
+ <li>
+ Configuration information must be able to enter a
+ running Turbine application. A sub application might
+ have many forms of configuration info. It might be properties
+ that have to be accessible via TurbineResources. Or
+ it might configuration information to be used by one
+ of the services, say for example an intake XML descriptor
+ for the input forms used in the sub-application.
+ <p />
+ The services in general might need some work to allow
+ dynamic configuration so that sub-applications can
+ really work properly.
+ </li>
+
+ <li>
+ Sub-applications may require certain operations to be
+ executed in order to run. This might be a forum application
+ that has an SQL schema that needs to be inserted in order
+ to function. These stops could either be performed by Ant,
+ or scripts that could be executed by the proposed BSF
+ (Bean Scripting Framework) service.
+ </li>
+
+ <li>
+ Sub-applications will require a unique id to to keep things
+ like templates in their own namespace. Eventually there
+ may also be other entities that need to be kept separate.
+ We could probably start a catalog of sub-applications to
+ make sure that people don't use a unique id already being
+ used by another sub-application in existence.
+ </li>
+
+ </ul>
+ </p>
</blockquote>
</td></tr>
</table>
1.5 +90 -3 jakarta-turbine/docs/proposals/services-repository-proposal.html
Index: services-repository-proposal.html
===================================================================
RCS file: /home/cvs/jakarta-turbine/docs/proposals/services-repository-proposal.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- services-repository-proposal.html 2001/04/08 18:38:20 1.4
+++ services-repository-proposal.html 2001/04/13 17:24:44 1.5
@@ -96,6 +96,8 @@
</li>
<li> <a href="../services.html">Services</a>
</li>
+ <li> <a href="../security.html">Turbine and Security</a>
+</li>
<li> <a href="../python.html">Turbine and Python</a>
</li>
<li> <a href="../jsp-configuration.html">Turbine and JSP</a>
@@ -138,7 +140,28 @@
</td></tr>
<tr><td>
<blockquote>
- </blockquote>
+ <p>
+ The services repository would be a place to store non-core/third party
+ Turbine services that could be utilized by anyone developing with the
+ Turbine services framework. There are services that are stored in
+ the main Turbine CVS that would be good candidates for the services
+ repository: castor, xmlrpc, xslt, webmacro, freemarker, naming.
+ These are services that Turbine can function without. Many Turbine
+ developers have probably created services but have never offered them
+ to the group because they are somewhat specialized: these services would
+ be ideal in the repository because they would have a description and
+ might be a great starting place for another developer. Or even better,
+ a contributed service might be exactly what another developer needs.
+ </p>
+ <p>
+ There are also services in other OSS Turbine-based applications that
+ would be good candidates for the services repository. Tambora has
+ a rule service and processing service that could be useful for other
+ Turbine-based B2B solutions, and the URL management and disk caching
+ services in Jetspeed are also general purpose services that would be
+ very useful to a wide audience of developers.
+ </p>
+ </blockquote>
</td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
@@ -148,8 +171,65 @@
</font>
</td></tr>
<tr><td>
+ <blockquote>
+ <p>
+ It would be nice to try and slim down the primary Turbine CVS.
+ There are many services currently in that are not core services. These
+ non-core services could easily be stored somewhere else and make the
+ primary Turbine CVS easier to navigate and become familiar with.
+ </p>
+ <p>
+ It would be highly desirable to build up an extensive library
+ of services. All of these services can't be kept in the primary
+ Turbine CVS and so I imagine there are quite a few services out there
+ that have not been contributed due to there specialized nature.
+ Specialized services are ideal for the repository, if the services
+ are kept in a central location and cataloged all parties involved
+ will benefit.
+ </p>
+ </blockquote>
+ </td></tr>
+ </table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="Requirements"><strong>Requirements</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
<blockquote>
- </blockquote>
+ <ul>
+ <li>
+ Services would have to be functional from JAR files. For this to work
+ the following changes would have to be made:
+ <p />
+ <ul>
+ <li>
+ The Services framework would have to be altered to load services
+ packaged in the form of JAR files.
+ </li>
+
+ <li>
+ Dependent services would have to be listed in the manifest so that the
+ the initialization of a service could be deferred until all
+ prerequisites of the service have been initialized.
+ </li>
+
+ <li>
+ The service package in a JAR should state all of its configuration
+ options as it may be necessary to have this configuration information
+ extracted from the JAR and added to TR.props or whatever future
+ configuration mechanisms we devise. It might be nice to have an
+ option in Turbine where there is no TR.props to begin with but
+ starting Turbine with a certain option would produce a configuration
+ that reflected the use of a set of services. Or Turbine would start,
+ but would require some configuration from via a little web application
+ before Turbine would accept connections from the outside world.
+ </li>
+ </ul>
+ </li>
+ </ul>
+ </blockquote>
</td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
@@ -160,7 +240,14 @@
</td></tr>
<tr><td>
<blockquote>
- </blockquote>
+ <p>
+ This would primarily affect the services framework, but the tools
+ required to pull information from JARS and load the JARS could probably
+ be used for loading/configuration sub-applications. We can probably
+ borrow a lot of this code from Avalon as I think this is pretty
+ much worked out in its service framework.
+ </p>
+ </blockquote>
</td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
1.2 +123 -40 jakarta-turbine/docs/proposals/turbine-2.2-proposals.html
Index: turbine-2.2-proposals.html
===================================================================
RCS file: /home/cvs/jakarta-turbine/docs/proposals/turbine-2.2-proposals.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- turbine-2.2-proposals.html 2001/04/12 03:41:39 1.1
+++ turbine-2.2-proposals.html 2001/04/13 17:24:44 1.2
@@ -98,6 +98,8 @@
</li>
<li> <a href="../services.html">Services</a>
</li>
+ <li> <a href="../security.html">Turbine and Security</a>
+</li>
<li> <a href="../python.html">Turbine and Python</a>
</li>
<li> <a href="../jsp-configuration.html">Turbine and JSP</a>
@@ -140,13 +142,18 @@
</td></tr>
<tr><td>
<blockquote>
- <li>
+ <p>
+ <ul>
+ <li>
Messages that turbine outputs should live in a resource bundles, not
in in TR.props
</li>
- <li>
+
+ <li>
Template lookups depending on locale (Is Ilkka working on that?)
</li>
+ </ul>
+</p>
</blockquote>
</td></tr>
</table>
@@ -158,22 +165,30 @@
</td></tr>
<tr><td>
<blockquote>
- <li>
+ <p>
+ <ul>
+ <li>
Separate template/module namespaces for diffent sub-applications.
</li>
- <li>
+
+ <li>
Extension do DynamicURI and derivates to support new parameter
(sub-application selector)
</li>
- <li>
+
+ <li>
Sub Application configuration issues.
</li>
- <li>
+
+ <li>
Loading sub-application from jar files.
</li>
- <li>
+
+ <li>
Deployment/undeployment of sub-applications - runtime or not?
</li>
+ </ul>
+</p>
</blockquote>
</td></tr>
</table>
@@ -185,22 +200,29 @@
</td></tr>
<tr><td>
<blockquote>
- <li>
+ <p>
+ <ul>
+ <li>
Simplify initialization sequence - no more init(Object), just start(),
init(), shutdown()
</li>
- <li>
+
+ <li>
system property repository in the broker, for the services that
*really* need to use ServletConfig or RunData
</li>
- <li>
+
+ <li>
getRealPath/getResourceAsStream for the use in the services in the
broker
</li>
- <li>
+
+ <li>
initialization of the broker needs to be refactored - logic for that
should moved from TurbineServices into BaseServiceBroker
</li>
+ </ul>
+</p>
</blockquote>
</td></tr>
</table>
@@ -212,7 +234,9 @@
</td></tr>
<tr><td>
<blockquote>
- <li>
+ <p>
+ <ul>
+ <li>
clean up property names so that dot is used as namespace separator,
not as a space character replacement examples:
<br />
@@ -229,6 +253,8 @@
names onto a DOM tree or a JNDI namespace. These two alternative
ResourceService implementation would be a nice addition to Turbine.
</li>
+ </ul>
+</p>
</blockquote>
</td></tr>
</table>
@@ -240,10 +266,13 @@
</td></tr>
<tr><td>
<blockquote>
- <li>
+ <p>
+ <ul>
+ <li>
UserManager should become a service in it's own right
</li>
- <li>
+
+ <li>
ACL mechanism should become pluggable. A new interface ACLBuilder must
be defined, the interface would have single method of 'Object
buildACL(User)' signature. UserManagerService would have a property that
@@ -251,42 +280,51 @@
instance not class method, so a concrete instance of the service must be
consulted.
</li>
- <li>
+
+ <li>
User object will have method of 'Object getACL()' signature that will
delegate to UserManagerService, which in turn delegates to the
configured ACLBuilder. It's OK to cache the returned object, since
the ACLBuilder will keep references ACL objects internally, to reflect
the changes of sercurity information at runtime.
</li>
- <li>
+
+ <li>
TurbineSecurityService will be the default ACLBuilder shipped with the
system.
</li>
- <li>
+
+ <li>
TurbineSecurityService should have it's OM/Peer classes Torque
generated
</li>
- <li>
+
+ <li>
Group should be could be renamed to 'Realm' or 'Domain'. This should
decrease the confusion about it's meaning
</li>
- <li>
+
+ <li>
Attributes of Roles/Groups/Permissions will be dropped. I don't think
the idea catched on.
</li>
- <li>
+
+ <li>
User attributes should be moved into a seaprate table, or even two
tables if we want to store meta information for user attributes.
This will require a customized Peer class for User objects, but
this will be easy with recent Torque's two-level class generation
</li>
- <li>
+
+ <li>
On session unbind event, only acces counters/timestamps should be
updated not the whole data. This should fix the overriding of
admin's changes by the unbound session problems. The information
which attributes should be updated could be placed in user attribute
meta-information table.
</li>
+ </ul>
+</p>
</blockquote>
</td></tr>
</table>
@@ -298,11 +336,15 @@
</td></tr>
<tr><td>
<blockquote>
- <li>
+ <p>
+ <ul>
+ <li>
this service is rater outdated, it needs some cleanup, and adding
suppport for DirContexts (low priority, might be useful in
creating LDAP User Manager / Security Service implementations)
</li>
+ </ul>
+</p>
</blockquote>
</td></tr>
</table>
@@ -314,11 +356,15 @@
</td></tr>
<tr><td>
<blockquote>
- <li>
+ <p>
+ <ul>
+ <li>
support for processing of DOM trees present in memory could be
useful (right now both data and stylesheet are read from disk
files)
</li>
+ </ul>
+</p>
</blockquote>
</td></tr>
</table>
@@ -330,10 +376,14 @@
</td></tr>
<tr><td>
<blockquote>
- <li>
+ <p>
+ <ul>
+ <li>
implementaions independent of DB/Peers should be added. An xml
based implementation seems easy and useable.
</li>
+ </ul>
+</p>
</blockquote>
</td></tr>
</table>
@@ -345,14 +395,19 @@
</td></tr>
<tr><td>
<blockquote>
- <li>
+ <p>
+ <ul>
+ <li>
facilities for presenation of tabular data, with the ability
to do paging, filtering and sorting
</li>
- <li>
+
+ <li>
date selection component (skinnable calendar with year/month/week
views in a popup window, includes some JS)
</li>
+ </ul>
+</p>
</blockquote>
</td></tr>
</table>
@@ -364,21 +419,28 @@
</td></tr>
<tr><td>
<blockquote>
- <li>
+ <p>
+ <ul>
+ <li>
SessionContext interface similar to that of ServletSession
</li>
- <li>
+
+ <li>
getGlobalContext() and getLocalContext() methods in RunData
</li>
- <li>
+
+ <li>
objects stored in local context must be Cloneable (they
will be cloned per every hit. A configurable number of local
contexts will be kept, so that user may continue a sub-session
from an alternate window)
- </li>
- <li>
+ </li>
+
+ <li>
those will not interfere with normal usage of Servlet session
</li>
+ </ul>
+</p>
</blockquote>
</td></tr>
</table>
@@ -390,11 +452,15 @@
</td></tr>
<tr><td>
<blockquote>
- <li>
+ <p>
+ <ul>
+ <li>
Criteria should not extend Hashtable. This is widely considered to be
a bad practice. Even if criteria is to maintain hashtable-like
semantics, it should do so by delegation not derivation.
</li>
+ </ul>
+</p>
</blockquote>
</td></tr>
</table>
@@ -406,14 +472,18 @@
</td></tr>
<tr><td>
<blockquote>
- <li>
+ <p>
+ <ul>
+ <li>
clean up and orthogonalize APIs (add vs append vs set)
</li>
- <li>
+
+ <li>
what the heck is uploadData? I think UploadService/FileItems do the
trick just fine
</li>
- <li>
+
+ <li>
BaseValueParser should not extend RecyclableSupport. If I understand
the pattern correctly, it should include an instance of
RecyclableSupport and delegate Recyclable interface method to it.
@@ -422,6 +492,8 @@
kind of apprach is used to emulate multiple inheritance in Java.
I'd appreciate a comment on this issue from Ilkka.
</li>
+ </ul>
+</p>
</blockquote>
</td></tr>
</table>
@@ -433,14 +505,19 @@
</td></tr>
<tr><td>
<blockquote>
- <li>
+ <p>
+ <ul>
+ <li>
Begone, ECS! We want ECS to dissappear completly from Turbine. Instead
of Elements, modules should pass Strings around.
</li>
- <li>
+
+ <li>
the inheritance hierarchy of modules - if you look at the class
diagram, you'll notice that it looks rather ugly.
</li>
+ </ul>
+</p>
</blockquote>
</td></tr>
</table>
@@ -452,17 +529,23 @@
</td></tr>
<tr><td>
<blockquote>
- <li>
+ <p>
+ <ul>
+ <li>
2.2 will be a good moment to rename, and move classes around.
</li>
- <li>
+
+ <li>
WebMacroSite classes could be renamed to just WebMacro
</li>
- <li>
+
+ <li>
some utility classes could be moved into service packages, to
decerease the crazy number of packages we have, and help better
hermetisation of code with package accesible fields/methods.
</li>
+ </ul>
+</p>
</blockquote>
</td></tr>
</table>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org