{5} Assigned, Active Tickets by Owner (Full Description) (9 matches)

List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.

MartinLeidig (6 matches)

Ticket Summary Component Milestone Type Created
Description
#4 Restructure Java packages, seperating internal and external classes Core (general) enhancement 01/30/08

In order to expose only external classes and interfaces in an OSGi environment, the Java package structure has to be reordered. Internal interfaces and implementations should be moved to .internal packages.

The new package layout should represent the various subsystems, at least where this change can be performed without breaking backward compatibility.

#19 Make OXM an independent module Core (general) enhancement 03/18/08

The OXM serialization support should be moved outside of the framework core.

#51 Client-side form validation Core (general) enhancement 07/16/08

Pustefix should support the generation of Javascript-Code to do client-side form validation.

#52 Decoupling view and and logic using actions Core (general) enhancement 07/16/08

Defining the IWrappers, which should be called (using SELWRP), and setting direct page jumps within the view has a lot of drawbacks (e.g. maintenance effort/replication for different countries, strong view-logic coupling, implicit view component dependencies). The problem should be solved using actions, which explicitly define dependencies, e.g. as part of the page request configuration.

An action has to be defined in the view-logic layer, replaces SELWRP, and can encapsulate jumps and submits to other pages. View-logic components export it as part of their interface. An action can be in a defined state (available, not available).

Action meta-informations should be displayed in the DOM tree (including their state) and can be used for content assist in the Pustefix editor. Some of these requirements are already implemented (see #12 and #31).

#56 Data scope/lifecycle support Core (general) enhancement 07/16/08

Pustefix should support binding data objects to scopes. At the moment Pustefix only supports the session scope. Storing data for the duration of a page flow, page visit or page request has to be managed/emulated by the application. Pustefix should support these additional scopes.

#18 Move TargetGenerator to own project Core (general) enhancement 03/18/08

The TargetGenerator should be moved to its own package as it might be of use outside of Pustefix.

MichaelHartmeier (1 match)

Ticket Summary Component Milestone Type Created
Description
#86 Update tutorial to the new build system Documentation 0.19.0 task 12/29/08

Update the Pustefix tutorial to the new build system.

SebastianMarsching (1 match)

Ticket Summary Component Milestone Type Created
Description
#6 Replace singleton-style classes by beans using a registry mechanism Core (general) task 01/30/08

At the moment the Pustefix core uses many classes that implement the singleton pattern by using static fields and methods.

This mechanism causes two major problems:

  • Initialization and usage of this classes can hardly be traced throughout the code.
  • The scope of the instances of these classes is always tied to the class loader.

In order to solve these issues all (or at least most of) these classes should be rewritten to use a single registry instead of static fields for life-cycle management. This central registry could be provided by a Spring ApplicationContext.

These issue is related to ticket:5. This ticket depends on ticket:7.

StephanSchmidt (1 match)

Ticket Summary Component Milestone Type Created
Description
#89 Write a new tutorial that explains how to create page flow engines Documentation 0.19.0 task 12/29/08

Write a new tutorial that shows how custom page flow engines can be injected in an application.

Note: See TracReports for help on using and creating reports.