Oh, you want humane apis.. For an example have a look at paxexam: We have "CoreOptions" that are defined my paxexam api. But we also have additional options that are located in a paxrunner module (with dependencies to paxrunner).
So, if you want paxrunner api options, then you have to add the paxrunner-support component. In the end, you still provide the api in _your_ "support" components. but don't boat the standard installation (when people want to use it). On Thu, Mar 26, 2009 at 3:31 PM, Filippo Diotalevi < filippo.diotal...@gmail.com> wrote: > On Thu, Mar 26, 2009 at 3:14 PM, Alin Dreghiciu <adreghi...@gmail.com> > wrote: > > I get now what you want to do but what I do not understand is why? Why > > would you get new Source and SourceParser for each url handler? To me > > is just unnecessary complexity. > > > > The reason is I want to have a clean api to integrate proveasyo (pyo?) > with other applications (in particular, with a user interface). > > Separating sources i can write > > Push push = new Push() //was Send() before > Source source = new WrapSource(...) > Destination destination = new LocalFileDestination(..) > push.execute(source, destination, parameters) > > On the contrary, with generic sources > > Push push = new Push() //was Send() before > Source source = new PaxUrlAdaptorSource(...) > Destination destination = new LocalFileDestination(..) > push.execute(source, destination, parameters) > > In the latter, it's not clear from the API what kind of sources > PaxUrlAdaptorSource handles > > > -- > Filippo Diotalevi > -- Toni Menzel Software Developer Professional Profile: http://www.osgify.com t...@okidokiteam.com http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software.
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
