New parser interfaces and RunData service

[Ilkka Priha <il...@codeonline.com>]

The ValueParser, ParameterParser and CookieParser classes have been changed
into interfaces and their default implementations have been moved from the
util package to a subpackage named parser. The idea is to support customized
parser and RunData implementations in addition to the default ones.

The RunDataFactory of Turbine has been changed to use a new RunData service
instead of instantiating RunData and parser objects by itself. The RunData
service can be configured to produce different implementations in addition
to the default ones. The configurations are defined in TR with three
properties

- services.TurbineRunDataService.<key>.run.data=<class name>
- services.TurbineRunDataService.<key>.parameter.parser=<class name>
- services.TurbineRunDataService.<key>.cookie.parser=<class name>

where <key> specifies the name of the configuration. Currently, the
RunDataFactory supports only the default key named 'default'.

The RunDataService supports three methods

- getRunData(req,res,cfg) returns a default RunData implementation
- getRunData(key,req,res,cfg) returns a config specific RunData
implementation
- putRunData(data) pools the RunData implementation

Some discussion is going on, how to integrate DynamicURI to this service.
All ideas are welcome.

-- Ilkka

[mailto:ext-ilkka.priha@nokia.com]


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org

Re: New parser interfaces and RunData service

[Shamil Yahin <sh...@newst.net>]

Hello Ilkka,

Friday, March 16, 2001, 6:55:39 AM, you wrote:


IP> Some discussion is going on, how to integrate DynamicURI to this service.
IP> All ideas are welcome.

Just a general idea.

DynamicURI is used when we want to create URLs.
But in more abstract level it means we want to create some object
that will represent ability to make server-side call.

If application generate HTML, then this object will be URL.

If application generate some custom XML, then this object will be some
XML element.

If application generate another output, then this object will have
some special representation.

But what is common for all this cases is that this object should
contain param/value pairs, and this is the main.

It would be nice if in general level instead of DynamicURI we will
have some abstract object that represents param/value pairs
(ParameterParser?). Then there should be ability to establish
application-dependent wrappers, that will transform this object to
some custom representation (URLs, etc).


/ Shamil



---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org