[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2787:
--------------------------------
Story Points: 8 (was: 5)
> "Data Type" tree-grid table interactions.
> -----------------------------------------
>
> Key: DROOLS-2787
> URL: https://issues.jboss.org/browse/DROOLS-2787
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: treegrid.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.)
> * *Add* a new data type, which might be a nested object as defined by the (ItemDefinition.)
> * *Remove* Data Types from the list of available selections.
> * be prevented from making selections that are not valid or would cause an error.
> * know that when I edit a data type the changes will be updated in the DMN model.
> Functional considerations/ pre conditions:
> * Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2787:
--------------------------------
Attachment: treegrid.png
> "Data Type" tree-grid table interactions.
> -----------------------------------------
>
> Key: DROOLS-2787
> URL: https://issues.jboss.org/browse/DROOLS-2787
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: treegrid.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.)
> * Add a new data type, which might be a nested object as defined by the (ItemDefinition.)
> * Remove Data Types from the list of available selections.
> * be prevented from making selections that are not valid or would cause an error.
> * know that when I edit a data type the changes will be updated in the DMN model.
> Functional considerations/ pre conditions:
> * Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same.
> * Design needs to be consistent with Stunner and PF components.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2787:
--------------------------------
Description:
*Background*
Persona: Business analyst or Rules practitioner
Use Cases:
As a user I want to:
* *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.)
* *Add* a new data type, which might be a nested object as defined by the (ItemDefinition.)
* *Remove* Data Types from the list of available selections.
* be prevented from making selections that are not valid or would cause an error.
* know that when I edit a data type the changes will be updated in the DMN model.
Functional considerations/ pre conditions:
* Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same.
* Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
Verification conditions:
* Scrum team and PO review.
was:
*Background*
Persona: Business analyst or Rules practitioner
Use Cases:
As a user I want to:
* *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.)
* Add a new data type, which might be a nested object as defined by the (ItemDefinition.)
* Remove Data Types from the list of available selections.
* be prevented from making selections that are not valid or would cause an error.
* know that when I edit a data type the changes will be updated in the DMN model.
Functional considerations/ pre conditions:
* Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same.
* Design needs to be consistent with Stunner and PF components.
Verification conditions:
* Scrum team and PO review.
> "Data Type" tree-grid table interactions.
> -----------------------------------------
>
> Key: DROOLS-2787
> URL: https://issues.jboss.org/browse/DROOLS-2787
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: treegrid.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.)
> * *Add* a new data type, which might be a nested object as defined by the (ItemDefinition.)
> * *Remove* Data Types from the list of available selections.
> * be prevented from making selections that are not valid or would cause an error.
> * know that when I edit a data type the changes will be updated in the DMN model.
> Functional considerations/ pre conditions:
> * Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2787:
--------------------------------
Description:
*Background*
Persona: Business analyst or Rules practitioner
Use Cases:
As a user I want to:
* *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.)
* Add a new data type, which might be a nested object as defined by the (ItemDefinition.)
* Remove Data Types from the list of available selections.
* be prevented from making selections that are not valid or would cause an error.
* know that when I edit a data type the changes will be updated in the DMN model.
Functional considerations/ pre conditions:
* Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same.
* Design needs to be consistent with Stunner and PF components.
Verification conditions:
* Scrum team and PO review.
was:
*Background*
Persona: Business analyst or Rules practitioner
Use Cases:
* From the DMN canvas view - as a user I want to *select* a data type, from a list of available data types, so I can associate it with a DMN node.
* From the DMN canvas view - as a user I want a *means to* add a desired data type to the list of available data types.
* From the DMN canvas view - as a user I want a *means to* edit a desired data type from the list of available data types.
Functional considerations/ pre conditions:
* Actions will be offered or spawned from right dock properties panel.
* Design needs to be consistent with Stunner and PF components.
Verification conditions:
* Scrum team and PO review.
> "Data Type" tree-grid table interactions.
> -----------------------------------------
>
> Key: DROOLS-2787
> URL: https://issues.jboss.org/browse/DROOLS-2787
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.)
> * Add a new data type, which might be a nested object as defined by the (ItemDefinition.)
> * Remove Data Types from the list of available selections.
> * be prevented from making selections that are not valid or would cause an error.
> * know that when I edit a data type the changes will be updated in the DMN model.
> Functional considerations/ pre conditions:
> * Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same.
> * Design needs to be consistent with Stunner and PF components.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.
by Liz Clayton (JIRA)
Liz Clayton created DROOLS-2787:
-----------------------------------
Summary: "Data Type" tree-grid table interactions.
Key: DROOLS-2787
URL: https://issues.jboss.org/browse/DROOLS-2787
Project: Drools
Issue Type: Story
Components: DMN Editor
Reporter: Liz Clayton
Assignee: Liz Clayton
*Background*
Persona: Business analyst or Rules practitioner
Use Cases:
* From the DMN canvas view - as a user I want to *select* a data type, from a list of available data types, so I can associate it with a DMN node.
* From the DMN canvas view - as a user I want a *means to* add a desired data type to the list of available data types.
* From the DMN canvas view - as a user I want a *means to* edit a desired data type from the list of available data types.
Functional considerations/ pre conditions:
* Actions will be offered or spawned from right dock properties panel.
* Design needs to be consistent with Stunner and PF components.
Verification conditions:
* Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2787:
--------------------------------
Story Points: 5 (was: 3)
> "Data Type" tree-grid table interactions.
> -----------------------------------------
>
> Key: DROOLS-2787
> URL: https://issues.jboss.org/browse/DROOLS-2787
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to *select* a data type, from a list of available data types, so I can associate it with a DMN node.
> * From the DMN canvas view - as a user I want a *means to* add a desired data type to the list of available data types.
> * From the DMN canvas view - as a user I want a *means to* edit a desired data type from the list of available data types.
> Functional considerations/ pre conditions:
> * Actions will be offered or spawned from right dock properties panel.
> * Design needs to be consistent with Stunner and PF components.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2774) Select a data type from the DMN canvas
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2774?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2774:
--------------------------------
Attachment: Select-b.png
> Select a data type from the DMN canvas
> ---------------------------------------
>
> Key: DROOLS-2774
> URL: https://issues.jboss.org/browse/DROOLS-2774
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: Select-b.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to *select* a data type, from a list of available data types, so I can associate it with a DMN node.
> * From the DMN canvas view - as a user I want a *means to* add a desired data type to the list of available data types.
> * From the DMN canvas view - as a user I want a *means to* edit a desired data type from the list of available data types.
> Functional considerations/ pre conditions:
> * Actions will be offered or spawned from right dock properties panel.
> * Design needs to be consistent with Stunner and PF components.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-3291) Pass Jandex CompositeIndex into Hibernate 5.x
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-3291?page=com.atlassian.jira.plugin.... ]
Scott Marlow resolved WFLY-3291.
--------------------------------
Resolution: Rejected
reopen if this is requested again.
> Pass Jandex CompositeIndex into Hibernate 5.x
> ----------------------------------------------
>
> Key: WFLY-3291
> URL: https://issues.jboss.org/browse/WFLY-3291
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Reporter: Scott Marlow
> Assignee: Scott Marlow
>
> 1. When creating the persistence unit for Hibernate 5.x, pass a Jandex composite index via:
> integrationMap.put( "hibernate.jandex_index", CompositeIndex.create( pu.getAnnotationIndex().values() ).
> 2. Also change from:
> integerationMap.put( "hibernate.ejb.resource_scanner", HibernateArchiveScanner.class )
> To:
> integrationMap.put( "hibernate.jpa.scanner_archive_delegate", VirtualFileSystemArchiveDescriptorFactory.INSTANCE )
> This may turn out to be a Jipajapa only change.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10513) Getting JTA Datasource (Wildfly 13)
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-10513?page=com.atlassian.jira.plugin... ]
Scott Marlow resolved WFLY-10513.
---------------------------------
Resolution: Rejected
Please report Hibernate ORM bugs via their separate jira system at [https://hibernate.atlassian.net/browse/HHH]. It looks like Hibernate ORM still contains support for what your looking for, via [https://github.com/hibernate/hibernate-orm/blob/master/hibernate-core/src...]. Perhaps its a regression caused by an unexpected condition.
> Getting JTA Datasource (Wildfly 13)
> -----------------------------------
>
> Key: WFLY-10513
> URL: https://issues.jboss.org/browse/WFLY-10513
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 13.0.0.Final
> Reporter: David Tierens
> Assignee: Scott Marlow
> Priority: Minor
>
> In Wildfly 12 it ,was possible to get the DataSource via :
>
> {code:java}
> @ApplicationScoped
> public class ExamplePersistenceContextConfiguration {
>
> @PersistenceContext(unitName = "examplePersistenceUnit")
> @Produces
> private EntityManager entityManager;
>
> @Produces
> public DataSource getDataSource() {
> EntityManagerFactory entityManagerFactory = entityManager.getEntityManagerFactory();
> Map<String, Object> properties = entityManagerFactory.getProperties();
> return (DataSource) properties.get("javax.persistence.jtaDataSource");
> }
>
> @Produces
> public SessionFactory getSessionFactory() {
> Session session = entityManager.unwrap(Session.class);
> return session.getSessionFactory();
> }
> }
> {code}
>
> Currently it's returning null in Wildfly 13, however :
> {code:java}
> (DataSource) properties.get("hibernate.connection.datasource");
> {code}
> does work (instead of :
> {code:java}
> (DataSource) properties.get("javax.persistence.jtaDataSource")
> {code}
>
> Persistence.XML :
> {code:xml}
> // Some comments here
> public String getFoo()
> {
> return foo;
> }
> <?xml version="1.0" encoding="UTF-8"?>
> <persistence xmlns="http://xmlns.jcp.org/xml/ns/persistence"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence
> http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd"
> version="2.1">
> <!-- HBM files in this module will be loaded automatically -->
> <persistence-unit name="examplePersistenceUnit" transaction-type="JTA">
> <provider>org.hibernate.jpa.HibernatePersistenceProvider</provider>
> <jta-data-source>jdbc/ExampleXADataSource</jta-data-source>
> <properties>
> <property name="hibernate.dialect" value="org.hibernate.dialect.Oracle10gDialect"/>
> <property name="hibernate.show_sql" value="true"/>
> <property name="hibernate.order_inserts" value="true"/>
> <property name="hibernate.jdbc.wrap_result_sets" value="true"/>
> <property name="hibernate.integration.envers.enabled" value="false"/>
> </properties>
> </persistence-unit>
> </persistence>
> {code}
>
> Is there any way to get it via the properties.get("javax.persistence.jtaDataSource") and not via Hibernate ?
>
> Thanks in advance,
> David
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months