[JBoss JIRA] (DROOLS-2738) View a simple, structured or compound data type
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2738?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2738:
--------------------------------
Summary: View a simple, structured or compound data type (was: Create a simple, structured or compound data type)
> View a simple, structured or compound data type
> -----------------------------------------------
>
> Key: DROOLS-2738
> URL: https://issues.jboss.org/browse/DROOLS-2738
> Project: Drools
> Issue Type: Sub-task
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Attachments: DROOLS-2738.bmpr, DT-nest-People.pdf
>
>
> We're trying to solve two big issues with this dialog:
> I) the definition of a simple (basic) data type; and
> II) the definition of a structured data type.
> * The first one is kind of easy, we just need to provide to the user an input and a select, in order to capture the name and the type of a simple data type.
> * The second problem is a little bit more difficult. Because the user needs to be able to define complex data types, with nested structures. For example, the user can create a data type called Person with 3 nested fields (they are simple data types) Additionally, a structured data type can have other complex nested data types.
> * Requirement to address situations where we're going to have many levels of nesting and many fields. The user should be able to: a) navigate between levels; b) expand/collapse nested types; c) create complex data structures easily.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2728) UX for custom data-types
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2728:
--------------------------------
Issue Type: Epic (was: Story)
> UX for custom data-types
> ------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2700.png, Screen Shot 2018-07-13 at 11.26.43 AM.png, Screen Shot 2018-07-13 at 11.34.15 AM.png, nested.png, prop-panel.png
>
>
> As a practitioner I want to be able to:
> * select an existing data type
> * create a simple or structured data type
> * create a “compound” (or complex) data type, easily.
> *
expand/collapse views of compound data types, so that I can___
> *
navigate between levels in a compound data type, so that I can___
> * edit an existing data type
> * remove an existing data type
>
…so that I can use the data type when creating a decision related asset.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2728) UX for custom data-types
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Liz Clayton reopened DROOLS-2728:
---------------------------------
> UX for custom data-types
> ------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2700.png, Screen Shot 2018-07-13 at 11.26.43 AM.png, Screen Shot 2018-07-13 at 11.34.15 AM.png, nested.png, prop-panel.png
>
>
> As a practitioner I want to be able to:
> * select an existing data type
> * create a simple or structured data type
> * create a “compound” (or complex) data type, easily.
> *
expand/collapse views of compound data types, so that I can___
> *
navigate between levels in a compound data type, so that I can___
> * edit an existing data type
> * remove an existing data type
>
…so that I can use the data type when creating a decision related asset.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2773) NPE when creating a new KieScanner
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2773?page=com.atlassian.jira.plugi... ]
Edson Tirelli reassigned DROOLS-2773:
-------------------------------------
Assignee: Mario Fusco (was: Edson Tirelli)
> NPE when creating a new KieScanner
> ----------------------------------
>
> Key: DROOLS-2773
> URL: https://issues.jboss.org/browse/DROOLS-2773
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Affects Versions: 7.8.0.Final
> Reporter: Raphael Bowen Giudice
> Assignee: Mario Fusco
>
> When creating a new *KieScanner*, a *NullPointerException* is thrown. Here's the code where the *KieScanner* is created:
> {code:java}
> final KieServices kieServices = KieServices.Factory.get();
> final KieContainer kieContainer = kieServices.newKieContainer(
> kieServices.newReleaseId("mygroup", "rules", "1.0-SNAPSHOT"));
> final KieScanner kieScanner = kieServices.newKieScanner(kieContainer);
> {code}
> The method *indexArtifacts* in the *KieRepositoryScannerImpl* class, tries to index all the Maven artefacts.In my case, the artefact *sun.jdk:jconsole:jdk* cannot be resolved, which causes the *NullPointerException* in the line 399:
> {code:java}
> private Map<ReleaseId, DependencyDescriptor> indexArtifacts() {
> Map<ReleaseId, DependencyDescriptor> depsMap = new HashMap<ReleaseId, DependencyDescriptor>();
> for (DependencyDescriptor dep : artifactResolver.getAllDependecies()) {
> if ( !"test".equals(dep.getScope()) && !"provided".equals(dep.getScope()) && !"system".equals(dep.getScope()) ) {
> Artifact artifact = artifactResolver.resolveArtifact(dep.getReleaseId());
> log.debug( artifact + " resolved to " + artifact.getFile() ); // NPE happens here.
> if (isKJar(artifact.getFile())) {
> depsMap.put(adapt( dep.getReleaseIdWithoutVersion() ), new DependencyDescriptor(artifact));
> }
> } else {
> log.debug("{} does not need to be resolved because in scope {}", dep, dep.getScope());
> }
> }
> return depsMap;
> }
> {code}
> The curious part is that the *sun.jdk:jconsole:jdk* artefact is not declared in any of my projects or dependencies, as far as I could investigate.
> Here's the NPE stack trace:
> {code}
> Caused by: java.lang.NullPointerException: null
> at org.kie.scanner.KieRepositoryScannerImpl.indexArtifacts(KieRepositoryScannerImpl.java:399)
> at org.kie.scanner.KieRepositoryScannerImpl.setKieContainer(KieRepositoryScannerImpl.java:116)
> at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieScanner(KieServicesImpl.java:227)
> at com.test.ServiceConfoguration.kieContainer(ServiceConfoguration.java:84)
> at com.test.ServiceConfoguration$$EnhancerBySpringCGLIB$$4fd6caf2.CGLIB$kieContainer$2(<generated>)
> at com.test.ServiceConfoguration$$EnhancerBySpringCGLIB$$4fd6caf2$$FastClassBySpringCGLIB$$f73690dd.invoke(<generated>)
> at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228)
> at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:356)
> at com.test.ServiceConfoguration$$EnhancerBySpringCGLIB$$4fd6caf2.kieContainer(<generated>)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:162)
> ... 19 common frames omitted
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2770) Edit issue in Guided Decision Tree
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2770?page=com.atlassian.jira.plugi... ]
Edson Tirelli updated DROOLS-2770:
----------------------------------
Issue Type: Bug (was: Feature Request)
> Edit issue in Guided Decision Tree
> -----------------------------------
>
> Key: DROOLS-2770
> URL: https://issues.jboss.org/browse/DROOLS-2770
> Project: Drools
> Issue Type: Bug
> Reporter: Chaitanya Patel
> Assignee: Toni Rikkola
> Labels: Decision, Guided, Tree
> Attachments: EditButtonDoesNotWork_DifferentTree.PNG, WorkingDecisionTreeWithEdit.PNG
>
>
> I have a working Decision Tree having a data object whose edit functionality works fine when we try to click on the circles. I want to add another Decision Tree for a different Data Object but when I try to edit the circles(root object/other objects) in this scenario, the edit functionality does not open a pop up. There is no java script error either. Now I try to add a different data object to the new decision tree but still the edit functionality does not work.
> I have moved this decision tree and data object to a different package as well as to a different project. But still the edit button does not open a pop-up. Neither the close(X) button or collapse button work for these circles.
> Attaching the snapshots where edit functionality of one decision tree works and it does not work for other.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2770) Edit issue in Guided Decision Tree
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2770?page=com.atlassian.jira.plugi... ]
Edson Tirelli reassigned DROOLS-2770:
-------------------------------------
Assignee: Toni Rikkola (was: Edson Tirelli)
> Edit issue in Guided Decision Tree
> -----------------------------------
>
> Key: DROOLS-2770
> URL: https://issues.jboss.org/browse/DROOLS-2770
> Project: Drools
> Issue Type: Feature Request
> Reporter: Chaitanya Patel
> Assignee: Toni Rikkola
> Labels: Decision, Guided, Tree
> Attachments: EditButtonDoesNotWork_DifferentTree.PNG, WorkingDecisionTreeWithEdit.PNG
>
>
> I have a working Decision Tree having a data object whose edit functionality works fine when we try to click on the circles. I want to add another Decision Tree for a different Data Object but when I try to edit the circles(root object/other objects) in this scenario, the edit functionality does not open a pop up. There is no java script error either. Now I try to add a different data object to the new decision tree but still the edit functionality does not work.
> I have moved this decision tree and data object to a different package as well as to a different project. But still the edit button does not open a pop-up. Neither the close(X) button or collapse button work for these circles.
> Attaching the snapshots where edit functionality of one decision tree works and it does not work for other.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months