<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/stepframework/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/stepframework/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/stepframework/feature-requests/</id><updated>2009-12-18T16:32:12Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>Create code review "learning trails"</title><link href="https://sourceforge.net/p/stepframework/feature-requests/8/" rel="alternate"/><published>2009-12-18T16:32:12Z</published><updated>2009-12-18T16:32:12Z</updated><author><name>Miguel Pardal</name><uri>https://sourceforge.net/u/mflpar/</uri></author><id>https://sourceforge.net7ef7b53db47120d98deae7ac52f39d3f39581351</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Considering the source code as the primary documentation source, then multiple "learning trails" should be created, each with a starting point (a file), and a sequence of other points to visit. E.g. service layer trail, start in Service.java then go to ... &lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Find alternative to embedding all jars into tomcat-step</title><link href="https://sourceforge.net/p/stepframework/feature-requests/7/" rel="alternate"/><published>2009-10-22T11:35:34Z</published><updated>2009-10-22T11:35:34Z</updated><author><name>Miguel Pardal</name><uri>https://sourceforge.net/u/mflpar/</uri></author><id>https://sourceforge.neta4230e1c3daad7a42b8671af2361e0892322c200</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;See if there is any way to start apache tomcat referring to STEP_HOME/lib in an external location, specified by an environment variable.&lt;br /&gt;
This would allow easier upgrading of both servlet container and STEP libraries.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Confirm that tomcat-step package is replicable</title><link href="https://sourceforge.net/p/stepframework/feature-requests/6/" rel="alternate"/><published>2009-10-21T15:10:43Z</published><updated>2009-10-21T15:10:43Z</updated><author><name>Miguel Pardal</name><uri>https://sourceforge.net/u/mflpar/</uri></author><id>https://sourceforge.net3c585d5b40a11b50dddde8a71bf2204ba35bde2a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Confirm that tomcat-step package is replicable, i.e., its configuration files allow for easy configuration replication, using a text find-replace approach to change listening port, etc.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Add test for JAX-R</title><link href="https://sourceforge.net/p/stepframework/feature-requests/5/" rel="alternate"/><published>2009-10-19T17:11:30Z</published><updated>2009-10-19T17:11:30Z</updated><author><name>Miguel Pardal</name><uri>https://sourceforge.net/u/mflpar/</uri></author><id>https://sourceforge.net75828e4288a21088f44c89691459c4588c8a8005</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Add a test for JAX-R registry use.&lt;br /&gt;
Possible location: src_test/test-jax/r&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>STEP Libraries located through environment variable</title><link href="https://sourceforge.net/p/stepframework/feature-requests/4/" rel="alternate"/><published>2009-08-14T14:50:52Z</published><updated>2009-08-14T14:50:52Z</updated><author><name>Miguel Pardal</name><uri>https://sourceforge.net/u/mflpar/</uri></author><id>https://sourceforge.netdee9bed141b5e60715e9faeeeac92c48ea8cbc19</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Instead of locating STEP libraries (lib) through relative paths, the STEP lib location should be specified using an environment variable, akin to CATALINA_HOME.&lt;br /&gt;
This allows several projects to share the same libraries. It also makes it easier to keep libraries out of version control repositories.&lt;br /&gt;
One disadvantage is that it makes it harder to have different versions of STEP running in the same machine.&lt;/p&gt;
&lt;p&gt;The proposed name for the environment variable is STEP_HOME&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Enable mock mode using System property</title><link href="https://sourceforge.net/p/stepframework/feature-requests/3/" rel="alternate"/><published>2009-07-06T13:13:26Z</published><updated>2009-07-06T13:13:26Z</updated><author><name>Miguel Pardal</name><uri>https://sourceforge.net/u/mflpar/</uri></author><id>https://sourceforge.net7cdf97ad633988f07c0e7b3b4d2acdcdf2232f78</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Instead of relying on a configuration file to choose between Hibernate and Mock mode, use a System property instead. It is a more IDE friendly way to run automated tests, and is easily supported by Ant scripts and the Eclipse IDE&lt;/p&gt;
&lt;p&gt;If system property is absent, no mock.&lt;br /&gt;
If system property is present and true, use mock mode.&lt;/p&gt;
&lt;p&gt;The property name should be "scoped" with the complete package name.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Redesign Service class hierarchy</title><link href="https://sourceforge.net/p/stepframework/feature-requests/2/" rel="alternate"/><published>2009-06-08T16:12:58Z</published><updated>2009-06-08T16:12:58Z</updated><author><name>Miguel Pardal</name><uri>https://sourceforge.net/u/mflpar/</uri></author><id>https://sourceforge.net6e3445fd4e35c813990c002c037fc1716d7f4037</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The current Service class hierarchy is broken. The LocalService name has historical reasons based on the first ideas about local and distributed transactions implementation. Being local is not the fundamental feature of a LocalService. The fundamental feature is participating in a work-of-unit (transaction).&lt;/p&gt;
&lt;p&gt;See COM+ transaction types for a possible Service classification.&lt;/p&gt;
&lt;p&gt;Define new Service class for web service client STEP applications?&lt;/p&gt;
&lt;p&gt;Should extensible services implement a marker interface (e.g. implements Extensible)?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Automatic session context</title><link href="https://sourceforge.net/p/stepframework/feature-requests/1/" rel="alternate"/><published>2009-06-08T16:02:14Z</published><updated>2009-06-08T16:02:14Z</updated><author><name>Miguel Pardal</name><uri>https://sourceforge.net/u/mflpar/</uri></author><id>https://sourceforge.netbd3b72c8074e7f4517abf0b6d6db8f4fe8dcfb90</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Implement an automatic and implicit session context for STEP framework extensions, based on an HTTP request scope, using a Java Servlet Filter&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>