Thinking about what Henning wrote, I pretty much agree. RunData has way too
much in it, and a replacement would be better..
However, I don't want to go to the Map world where everythign is a
constant.. For instance, if I need the rundata, I don't want to constantly
do:
RunData data = myPipelineDataObject.get(TurbineConstants.RUNDATA)..
I really want:
RunData data = ((TurbinePipelineData)myPipelineDataObject).getRunData();
or alternatively, why can't RunData extend PipelineData?
PipelineData
AbstractPipelineData
RunData
TurbineRunData
Then, PipelineData and AbstractPipelineData can be in the Fulcrum component,
and then Turbine (via RunData) add's all of it's extra crap.. But, in
situations where you don't need/use/want the rundata stuff, you just use
PipelineData objects?
I really want to see the Pipeline be usable outside of a servlet
request/response cycle.. There are lots of places where a pipeline of
actions can be usefull...
Eric
> -----Original Message-----
> From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 17, 2004 6:24 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [Thoughts and proposal] RunData
>
>
> Eric Dobbs <[EMAIL PROTECTED]> writes:
>
> >This example is just a subset of what is offered by Map. If you
> >use Map you don't have to introduce any new concepts to the
> >programmer, you can get() and put(), and also benefit from the
> >rest of the Collections API. You also don't have to write any
> >code for the interface nor for the implementation. Less code is
> >A Good Thing.
>
> I want scope. I want automatic timeouts. I want listeners. :-)
>
> But yes, a Map (or better yet: A subset of a map, you don't want
> everything from the Map interface or you end up with a Context object
> that must be implemented with a map. This is not a map) points in the
> right direction.
>
> Regards
> Henning
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
> [EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
>
> RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
> Linux, Java, perl, Solaris -- Consulting, Training, Development
>
> "Fighting for one's political stand is an honourable action, but re-
> fusing to acknowledge that there might be weaknesses in one's
> position - in order to identify them so that they can be remedied -
> is a large enough problem with the Open Source movement that it
> deserves to be on this list of the top five problems."
> -- Michelle Levesque, "Fundamental Issues with
> Open Source Software Development"
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
