[
https://issues.apache.org/jira/browse/DROIDS-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008417#comment-13008417
]
Thorsten Scherler commented on DROIDS-119:
------------------------------------------
I share your point regarding: "setter injection as a mechanism used for
optional collaborators and constructor injection for required collaborators
without which the object is inconsistent (hence the javadoc - "Before using
make sure you have set the SaveContentHandlerStrategy"). "
Should we apply it first and then change it, this way we make sure we have the
functionality now in our codebase and then review the rest of our components
regarding this strategy.
> Allow SaveHandler to decide the location (directory) where it saves the
> content
> -------------------------------------------------------------------------------
>
> Key: DROIDS-119
> URL: https://issues.apache.org/jira/browse/DROIDS-119
> Project: Droids
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.0.2
> Reporter: Eugen Paraschiv
> Fix For: 0.0.2
>
> Attachments: DROIDS-119-2.patch, droids119.patch
>
>
> At this point, SaveHandler doesn't provide a way to configure where the
> content is saved, other than a single directory path, which clearly lacks
> flexibility.
> A common scenario is to crawl a site and configure where the content gets
> saved based on some particular logic, as opposed to having all content (which
> may be a lot) saved in one single directory.
> For example, I may want to save
> www.domain.com/category1/... into directory a category1 directory and
> www.domain.com/category2/... into directory a category2 directory.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
