[JBoss JIRA] (JBIDE-18997) Editor for batch.xml
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18997?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18997:
-----------------------------------
Parent: (was: JBIDE-18857)
Issue Type: Feature Request (was: Sub-task)
> Editor for batch.xml
> --------------------
>
> Key: JBIDE-18997
> URL: https://issues.jboss.org/browse/JBIDE-18997
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Labels: new_and_noteworthy
> Fix For: 4.3.x
>
>
> It is a very simple xml:
> {code}
> <batch-artifacts xmlns="http://xmlns.jcp.org/xml/ns/javaee">
> <ref id="<reference-name>" class="<impl-class-name>" />
> </batch-artifacts>
> {code}
> that can be easily managed in a text editor, but for our tool completeness we may provide a Tree+Source editor for it.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18996) Support batch.xml in Batch project model
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18996?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18996:
-----------------------------------
Parent: (was: JBIDE-18857)
Issue Type: Feature Request (was: Sub-task)
> Support batch.xml in Batch project model
> ----------------------------------------
>
> Key: JBIDE-18996
> URL: https://issues.jboss.org/browse/JBIDE-18996
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.3.x
>
>
> Default loading of batch artifacts described by JSR-352 is provided by batch.xml:
> {code}
> <batch-artifacts xmlns="http://xmlns.jcp.org/xml/ns/javaee">
> <ref id="<reference-name>" class="<impl-class-name>" />
> </batch-artifacts>
> {code}
> Batch implementations may define specific loaders and probably most popular is going to be the use of javax.inject.Named annotation.
> For the completeness, we have better to support the default way as well.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18950) New Batch Artifact wizard
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18950?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18950:
-----------------------------------
Sprint: Sprint #2 April 2015
> New Batch Artifact wizard
> -------------------------
>
> Key: JBIDE-18950
> URL: https://issues.jboss.org/browse/JBIDE-18950
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
>
> There are about 20 artifacts in Java EE Batch:
> Batchlet; Checkpoint Algorithm; Decider; Item Reader; Item Writer; Item Processor; Partition Analyzer; Partition Reducer; Partition Collector; Partition Mapper; Partition Plan; Chunk Listener; Item Process Listener; Item Reader Listener; Item Writer Listener; Job Listener; Step Listener; Retry Process Listener; Retry Read Listener; Retry Write Listener; Skip Process Listener; Skip Listener; Skip Write Listener.
> We may have one wizard for each, or some of this artifacts. However, there is so much common in them that it makes sense also (or instead) to have one wizard with list choice of artifact. When a specific artifact should be created from the context of Batch XML editor, this wizard can be invoked with selection of that artifact (list of artifacts may be disabled or hidden).
> 1. Artifact implements a specific Java interface (for interfaces that have more than 1 method, there is optional abstract class to extend that implements rarely overridden methods);
> 2. Reference name should be provided for each artifact. There are 3 options:
> - An implementation of Batch runtime may define its own way of matching class to name. For example, CDI uses javax.inject.Named;
> - META-INF/batch.xml
> - by default, when first 2 options failed reference name is tried as the qualified class name.
> 3. Artifact class may declare fields, with values to be injected from properties set in job xml element referencing that artifact:
> {code}
> @Inject @BatchProperty(name="property1") String property;
> @Inject @BatchProperty String property2;
> {code}
> Thus, the wizard will have inputs as follows:
> - Artifact: [combo]
> - Source folder: [as in New Java Class wizard]
> - Package: [as in New Java Class wizard]
> - Class name: [text]
> - [radio] implement interface [radio] extend abstract class (if class is not available, the option is disabled)
> - Reference name: (block of inputs)
> | - [radio] Annotation Named [radio] batch.xml [radio] Qualified name
> | - Name: [text] (for first 2 options filled with default value; for the last option disabled)
> - Properties: [table editor with 'Property name' and 'Field name' columns]
> Some more inputs may be inherited from New Java Class wizard, if default values are not enough.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18950) New Batch Artifact wizard
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18950?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18950:
-----------------------------------
Parent: (was: JBIDE-18857)
Issue Type: Feature Request (was: Sub-task)
> New Batch Artifact wizard
> -------------------------
>
> Key: JBIDE-18950
> URL: https://issues.jboss.org/browse/JBIDE-18950
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
>
> There are about 20 artifacts in Java EE Batch:
> Batchlet; Checkpoint Algorithm; Decider; Item Reader; Item Writer; Item Processor; Partition Analyzer; Partition Reducer; Partition Collector; Partition Mapper; Partition Plan; Chunk Listener; Item Process Listener; Item Reader Listener; Item Writer Listener; Job Listener; Step Listener; Retry Process Listener; Retry Read Listener; Retry Write Listener; Skip Process Listener; Skip Listener; Skip Write Listener.
> We may have one wizard for each, or some of this artifacts. However, there is so much common in them that it makes sense also (or instead) to have one wizard with list choice of artifact. When a specific artifact should be created from the context of Batch XML editor, this wizard can be invoked with selection of that artifact (list of artifacts may be disabled or hidden).
> 1. Artifact implements a specific Java interface (for interfaces that have more than 1 method, there is optional abstract class to extend that implements rarely overridden methods);
> 2. Reference name should be provided for each artifact. There are 3 options:
> - An implementation of Batch runtime may define its own way of matching class to name. For example, CDI uses javax.inject.Named;
> - META-INF/batch.xml
> - by default, when first 2 options failed reference name is tried as the qualified class name.
> 3. Artifact class may declare fields, with values to be injected from properties set in job xml element referencing that artifact:
> {code}
> @Inject @BatchProperty(name="property1") String property;
> @Inject @BatchProperty String property2;
> {code}
> Thus, the wizard will have inputs as follows:
> - Artifact: [combo]
> - Source folder: [as in New Java Class wizard]
> - Package: [as in New Java Class wizard]
> - Class name: [text]
> - [radio] implement interface [radio] extend abstract class (if class is not available, the option is disabled)
> - Reference name: (block of inputs)
> | - [radio] Annotation Named [radio] batch.xml [radio] Qualified name
> | - Name: [text] (for first 2 options filled with default value; for the last option disabled)
> - Properties: [table editor with 'Property name' and 'Field name' columns]
> Some more inputs may be inherited from New Java Class wizard, if default values are not enough.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-13904) Minor UI issues in "Configure Repositories" wizard
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13904?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-13904 at 4/14/15 6:42 PM:
--------------------------------------------------------------
So I finally applied the fix to master, even though OSX still has the issue (JBIDE-19593). But I guess having Windows and Linux working is better than nothing.
was (Author: fbricon):
So I finally applied the fix to master, even though OSX still has the issue. But I guess having Windows and Linux working is better than nothing.
> Minor UI issues in "Configure Repositories" wizard
> --------------------------------------------------
>
> Key: JBIDE-13904
> URL: https://issues.jboss.org/browse/JBIDE-13904
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.1.0.Alpha2
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Minor
> Labels: uxp
> Fix For: 4.3.0.Alpha2
>
>
> In the Window > Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories...
> * The repo viewer should have a horizontal scroller, since adding the (inactive) suffix can make a pretty long label and you have to resize the whole dialog to be able to read the labels
> * Edit a repo, switching the profile activation status : it reorders the repositories/profiles in settings.xml.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months