On Tue, 2002-02-19 at 11:53, Edwin Gustafson wrote: > Greetings, > > Is it common to use a custom implementation of RunData? Is it easy?
I don't know how common it is, but it's definitely possible. Jetspeed uses their own variant of RunData and it works but turbine2 as a whole doesn't handle subclasses consistently with respect to pooling and usage. Generally in your modules or actions you have to upcast to get the functionality you need from your subclass. Typically this is what has been done. I'm looking for a better way at the moment for Turbine 3.x. > > The javadoc for DefaultTurbineRunData says it is the default "if another > implementation is not defined in the default or specified RunData > configuration." I've tried changing the default in TR.props... > > services.RunDataService.default.run.data=path.to.my.implementation.of.RunData > > ...but my rundata object is still of class DefaultTurbineRunData. I don't > understand how to specify a different RunData configuration. I set it up > in TR.props... > > services.RunDataService.custom.run.data=path.to.my.implementation.of.RunData > services.RunDataService.custom.parameter.parser=org.apache.turbine.util.parser. > DefaultParameterParser > services.RunDataService.custom.cookie.parser=org.apache.turbine.util.parser. > DefaultCookieParser > > ...but Turbine ignores it. How do I tell Turbine to use this configuration? Here is an example in the Jetspeed TRP file: http://cvs.apache.org/viewcvs/jakarta-jetspeed/webapp/WEB-INF/conf/TurbineResources.properties?rev=1.42&content-type=text/vnd.viewcvs-markup > > -- > Edwin Gustafson > 734 971 3586 x 235 > Cayman Chemical Company > 42�13'44" N 83�43'25" W > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
