Recent changes to feature-requests

Generalize URL where requests are posted from the JSP pages

2007-03-08T00:22:43Z

In the current version of Chronicle each JSP page has hardcoded the URL where the request from the page is submitted to. This is not very flexible since it cannot be changed in any way. All other URls are determined by the navigator instance. We should make this behaviour consistent and let the post URL be determined by the navigator instance.

Simplify BlogNavigator code by eliminating duplicate code

2007-03-08T00:11:11Z

The BlogNavigator class is responsible for determining what blog or entry is the request aimed at and for generation of URLS to dusplay on the web pages. Many methods in this class use very similar or the same code. Review the code in this class and make the code reusable to make the class more efficient and readable.

Generalize handling of login and logout requests

2007-03-07T23:47:39Z

Current version of Chronicle let the BlogEditServlet determine if the request is for login or logout page and then handle it. This is different from other requests where the navigator class handles such logic. Move the logic to determine if the request is for login or logout page to the BlogNavigator class.

Generalize blog navigation to allow per request behavior

2007-03-07T23:31:46Z

Current version of Chronicle constructs single BlogNavigator object which is then shared between all requests to parse the URLs and generate new URLs to display in pages. The application that use this servet may want to modify this behavior and generate different navigator based on the information from the request. Generalize the construction of navigator to allow different behavior for individual requests.

Generalize blog identification accessed using static URL

2007-03-07T23:21:41Z

The existing version of Chronicle identifies blog and their entries using combination of blog folder and the entry id. In some situation we may want to identify the blog and entry using combination of blog id and entry id. We need to generalize the BlogEntryIdentification class to allow both variations.

Upgrade to Core release 1.0rc3

2007-03-07T22:51:04Z

New upcoming release 1.0rc3 of Open Core features several changes especially in the persistence tier
and in web user interface. Upgrade OpenChronicle to this release.

Simplify coding of persistence tier of list data pattern

2007-03-07T19:58:22Z

ListDatabaseSchema and ListDatabaseFactory interfaces should be implemented by all subsystems that implement the list data pattern. Many of the methods prescribed by this interface and repetitive or similar between subsystems. Simplify coding of factories and schemas of subsystems that implement the list data pattern so that we eliminate as much repetitive tasks as possible.

Allow to customize page displayed by ListBrowserServlet

2007-03-07T18:31:16Z

The ListBrowserServlet was using the single page configured using single constant to display results of its operation. The only option to change this page was to change the value of the configuration setting. Some applications may need to display different page for each request. Allow such customization by allowing the code that overrides or uses the completeAction method to specify what rendering page to use.

Simplify coding of ListTag derived custom JSP tags

2007-03-07T00:02:24Z

List data pattern provides ListTag class, which is base class of data object specific custom JSP tags that display data loaded using list data pattern in a table. Currently the derived class must implement several methods to expose various details about the data being loaded. This is cumbersome and difficult. Simplify coding of classes derived from ListTag so that the data object specific modules can implement these as easy as possible.

Simplify creation of custom list data pattern result pages

2007-03-06T23:02:59Z

When ListBrowser servlet loads list of data from the data store, it redirects the request to the configured JSP page. The page then displays the results and offers user navigation controls to navigate to other portions of the data list. It can also offers gui to customize the the way the list is loaded, sorted and displayed. Then when the page is submitted again to server, the ListBrowser servlet can handle the request automatically. In order to do so it requires set of HTML variables storing information that influence how the list is loaded. Currently these variables are only available in datalist.jsp and they cannot be easily reused in a different page.

Create a way how to easily include all required variable to a custom JSP page so that it is easily possible to create custom JSP pages displaying result of ListBrowserServlet.