Refactoring the jobmanager for adding a chain capability involve to find
a name for the actual jobmanager impl (original class name is
inMemoryJobManager).
So for now we have :
- inmemoryjobmanager
- simple
- default
- static
- weighted
Any other ideas ?
Or consensus on the new baby name ? :)
++
On 11/02/2011 02:23 PM, Fabian Christ (Commented) (JIRA) wrote:
[
https://issues.apache.org/jira/browse/STANBOL-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142127#comment-13142127
]
Fabian Christ commented on STANBOL-370:
---------------------------------------
+1 for not using camel case.
About the naming we should think about what distinguishes the different job manager implementations. I'm -1
for "default" because the default might change in the future. "simple" is not good either
because there may be a simpler one ;) What about "static" because it does not allow dynamic
reordering?
And perhaps the old eu.iksproject.fise packages could be renamed.
Change StanbolJobManager Structure
----------------------------------
Key: STANBOL-370
URL: https://issues.apache.org/jira/browse/STANBOL-370
Project: Stanbol
Issue Type: Improvement
Reporter: Florent ANDRE
The idea is to get a folder structure like Engines stuff for hold Jobmanager
implementations
This actually mean :
* move the Jobmanager folder from enhancer/generic/jobmanager to
enhancer/jobmanager
* create inside the jobmanager a pom and folders to hold differents
implementations.
* Create an inMemory folder for this implementation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
