[jbosstools-issues] [JBoss JIRA] (JBIDE-18915) Create Icons for Batch tools

Viacheslav Kabanovich (JIRA) issues at jboss.org
Wed Dec 10 14:21:39 EST 2014


    [ https://issues.jboss.org/browse/JBIDE-18915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026850#comment-13026850 ] 

Viacheslav Kabanovich commented on JBIDE-18915:
-----------------------------------------------

My opinion is that this issue can be committed after the initial commit (PR in JBIDE-18859) to provide parallel work on next tasks for batch, while the icons are being produced. Placeholder icons in the initial PR are provided.

> Create Icons for Batch tools
> ----------------------------
>
>                 Key: JBIDE-18915
>                 URL: https://issues.jboss.org/browse/JBIDE-18915
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: batch
>            Reporter: Viacheslav Kabanovich
>            Assignee: Daniel Azarov
>             Fix For: 4.3.0.Alpha1
>
>         Attachments: batch_icon16.png
>
>
> batch_icon16.png - file batch.xml (initial image is attached, it can be replaced or used)
> analyzer.png - receives intermediary results from each partition sent via partition collector and serves as a collection point for this data; it may be used to implement custom exit status handling for the step
> batchlet.png - 'batchlet' element specifies a task-oriented batch step
> checkpoint-algorithm.png - an optional custom checkpoint algorithm that may be used to provide a checkpoint decision based
> on factors other than only number of items, or amount of time
> chunk.png - kind of step that processes multiple items and is periodically checkpointed by the batch runtime according to a configured checkpoint policy
> collector.png - partition collector is used by step partitions for sharing data that is used to decide the overall outcome of the step
> decision.png - decision provides a customized way of determining sequencing among steps, flows, and splits (batch status is set to FAILED)
> end.png - end element is used to terminate the job at the current step (batch status is set to COMPLETED)
> exclude.png - element 'exclude' specifies a class name of an exception or exception superclass to not be taken into account
> fail.png - fail element is used to terminate the job at the conclusion of the current step or flow
> flow.png - flow defines a sequence of execution elements that execute together as a unit
> include.png - element 'include' specifies the class name of an exception or exception superclass that should be taken into account
> job.png - root node of file batch.xml, it may be the same as batch_icon16.png
> listeners.png - folder for listeners
> listener.png - job listener
> mapper.png - partition mapper provides a programmatic means for calculating the number of partitions and threads for a partitioned step
> next.png - transition element that defines  condition and target for transition to next step.
> partition.png - 'partition' element specifies that a step is a partitioned step
> plan.png - plan defines the number of partitions and the maximum number of threads on which to execute the partitions of the partitioned step
> processor.png - 'processor' element specifies the item processor for a chunk step
> properties.png - folder for properties
> property.png - common 'name'='value' object.
> reader.png - 'reader' element specifies the item reader for a chunk step
> reducer.png - partition reducer provides a kind of unit of work demarcation around the processing of the partitions
> no-rollback-exception-classes.png - list of exceptions that override the default behavior of rollback for retryable exceptions
> retryable-exception-classes.png - set of exceptions that chunk processing will retry
> skippable-exception-classes.png - set of exceptions that chunk processing will skip
> split.png - split defines a set of flows that execute concurrently
> step.png - 'step' element identifies a job step, job may contain any number of steps
> stop.png - stop element is used to terminate the job after the current step or flow (batch status is set to STOPPED), optionally defines step at which job can be restarted
> writer.png - 'writer' element specifies the item writer for a chunk step



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)


More information about the jbosstools-issues mailing list