March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-614) Review and document usage of UMB

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-614?page=com.atlassian.jira.plugin.... ] Matt Mahoney resolved SWSQE-614. -------------------------------- Resolution: Done > Review and document usage of UMB > -------------------------------- > > Key: SWSQE-614 > URL: https://issues.jboss.org/browse/SWSQE-614 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Matt Mahoney > Priority: Major > > We need to document how we use UMB. > * jenkins master configuration > * jobs which are consuming msgs > * which msgs are consumed > * which msgs are sent to UMS -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3659) DMN: UX for documentation reports

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3659?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3659: ---------------------------------------- [~stetson.robinson] Thanks, your reply seems to have answered my question completely. > DMN: UX for documentation reports > --------------------------------- > > Key: DROOLS-3659 > URL: https://issues.jboss.org/browse/DROOLS-3659 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: DROOLS-3659-documentation.mp4 > > > User stories: > * As a user I want to generate a PDF or HTML report of the DMN model, with documentation, so that I can hand it off to external team and/or business that needs information about the diagrams and the logic of the decisions being automated. The report can be printed out and used by business teams not involved with the modeling itself, to learn about content of the .dmn file. > * As a user I need a means through the UI to input additional documentation, links and attachments to nodes. > Notes: > - Docs to help with docs formatting. > - Might be able to leverage Case View docs widget. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3715) Zipkiemodule nullpointerexception

by Tibor Zimányi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3715?page=com.atlassian.jira.plugi... ] Tibor Zimányi commented on DROOLS-3715: --------------------------------------- Hi [~lukaszkrot], could you please provide a small reproducer project for this? I can fix this, however it would be great to have a regression test for this, simulating your use case, so we are sure this doesn't return again. > Zipkiemodule nullpointerexception > --------------------------------- > > Key: DROOLS-3715 > URL: https://issues.jboss.org/browse/DROOLS-3715 > Project: Drools > Issue Type: Bug > Affects Versions: 7.16.0.Final, 7.17.0.Final > Reporter: Łukasz Szmolke > Assignee: Tibor Zimányi > Priority: Major > > o During ZipKieModule loading in “org.drools.compiler.kie.builder.impl.ZipKieModule:142” nullpointerexception is thrown: > > urlPath = urlPath.substring( urlPath.lastIndexOf( '!' ) + 1 ); > ArrayList<ZipEntry> entries = new ArrayList<>(); > // read jar file from uber-jar > InputStream in = this.getClass().getResourceAsStream(urlPath); // nullpointerexception > > For example full UrlPath on windows to internal .jar is: > C:\Users\xbbnv0c\IdeaProjects\ais-data-exchange\data-exchange-app\target\data-exchange-app-1.0.1-SNAPSHOT.jar!\BOOT-INF\lib\data-exchange-brms-1.0.1-SNAPSHOT.jar > So the result of this first line will be: > \BOOT-INF\lib\data-exchange-brms-1.0.1-SNAPSHOT.jar > It will be perfect, but during accessing internal resource file separator should be “/” not “\”. So InputStream in = null. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3659) DMN: UX for documentation reports

by Stetson Robinson (Jira)

[ https://issues.jboss.org/browse/DROOLS-3659?page=com.atlassian.jira.plugi... ] Stetson Robinson edited comment on DROOLS-3659 at 3/1/19 7:44 AM: ------------------------------------------------------------------ [~manstis], you're correct. My understanding in speaking with [~tirelli] and coordinating with [~uxdlc] is that the Attachments option is to add attachment links of any kind to the node (links to documents, images, forms, whatever), and those attachments get included along with all other DRD information in the DMN report that is generated at the DRD level, in what in BPMN is the Documentation tab. Per Edson's request, I've proposed the following [example DMN model report|https://docs.google.com/document/d/1xZBnRQfaTpFmMjU11Wzc2HhBqJCOVK...] for this purpose, although it sounds like we'll just be tweaking and using the template [~tdolphine] has mentioned. So in short: Attachments are at the node level in the Diagram Properties panel, and Documentation (report) is at the DRD level and is a .docx or .html version of the DMN model, including any attachments per node. This is what my example is of above. If I've misunderstood the feature request or your question, Mike, my apologies. was (Author: stetson.robinson): [~manstis], you're correct. My understanding in speaking with [~tirelli] and coordinating with [~uxdlc] is that the Attachments option is to add attachment links of any kind to the node (links to documents, images, forms, whatever), and those attachments get included along with all other DRD information in the DMN report that is generated at the DRD level, in what in BPMN is the Documentation tab. Per Edson's request, I've proposed this as an [example DMN model report|https://docs.google.com/document/d/1xZBnRQfaTpFmMjU11Wzc2HhBqJCOVK...]. So in short: Attachments are at the node level in the Diagram Properties panel, and Documentation (report) is at the DRD level and is a .docx or .html version of the DMN model, including any attachments per node. This is what my example is of above. If I've misunderstood the feature request or your question, Mike, my apologies. > DMN: UX for documentation reports > --------------------------------- > > Key: DROOLS-3659 > URL: https://issues.jboss.org/browse/DROOLS-3659 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: DROOLS-3659-documentation.mp4 > > > User stories: > * As a user I want to generate a PDF or HTML report of the DMN model, with documentation, so that I can hand it off to external team and/or business that needs information about the diagrams and the logic of the decisions being automated. The report can be printed out and used by business teams not involved with the modeling itself, to learn about content of the .dmn file. > * As a user I need a means through the UI to input additional documentation, links and attachments to nodes. > Notes: > - Docs to help with docs formatting. > - Might be able to leverage Case View docs widget. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3659) DMN: UX for documentation reports

by Stetson Robinson (Jira)

[ https://issues.jboss.org/browse/DROOLS-3659?page=com.atlassian.jira.plugi... ] Stetson Robinson commented on DROOLS-3659: ------------------------------------------ [~manstis], you're correct. My understanding in speaking with [~tirelli] and coordinating with [~uxdlc] is that the Attachments option is to add attachment links of any kind to the node (links to documents, images, forms, whatever), and those attachments get included along with all other DRD information in the DMN report that is generated at the DRD level, in what in BPMN is the Documentation tab. Per Edson's request, I've proposed this as an [example DMN model report|https://docs.google.com/document/d/1xZBnRQfaTpFmMjU11Wzc2HhBqJCOVK...]. So in short: Attachments are at the node level in the Diagram Properties panel, and Documentation (report) is at the DRD level and is a .docx or .html version of the DMN model, including any attachments per node. This is what my example is of above. If I've misunderstood the feature request or your question, Mike, my apologies. > DMN: UX for documentation reports > --------------------------------- > > Key: DROOLS-3659 > URL: https://issues.jboss.org/browse/DROOLS-3659 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: DROOLS-3659-documentation.mp4 > > > User stories: > * As a user I want to generate a PDF or HTML report of the DMN model, with documentation, so that I can hand it off to external team and/or business that needs information about the diagrams and the logic of the decisions being automated. The report can be printed out and used by business teams not involved with the modeling itself, to learn about content of the .dmn file. > * As a user I need a means through the UI to input additional documentation, links and attachments to nodes. > Notes: > - Docs to help with docs formatting. > - Might be able to leverage Case View docs widget. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4125) javax.ejb.NoSuchEJBException should not print a stacktrace on the server console

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFLY-4125?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4125: ----------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1167983|https://bugzilla.redhat.com/show_bug.cgi?id=1167983] from NEW to CLOSED > javax.ejb.NoSuchEJBException should not print a stacktrace on the server console > --------------------------------------------------------------------------------- > > Key: WFLY-4125 > URL: https://issues.jboss.org/browse/WFLY-4125 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Sande Gilda > Assignee: Stuart Douglas > Priority: Major > Fix For: 9.0.0.Beta1 > > > See related bug: https://bugzilla.redhat.com/show_bug.cgi?id=1167293 > The shopping-cart quickstart has a note in the README file that states: > Note: You also see the following EJB Invocation failed and NoSuchEJBException messages in the server log. This is the expected result because method is annotated with @Remove. This means the next invocation after the shopping cart checkout fails because the container has destroyed the instance and it is no longer available. > However, usually people see the stacktrace in the server and assume something is terribly wrong. (see https://bugzilla.redhat.com/show_bug.cgi?id=910868) > I spoke with Brad Maxwell and David M Lloyd to see if there is a way to suppress the stacktrace and only print the exception message, but it is not possible. The stacktrace doesn't really provide any additional information, and since it's thrown, the caller has access to it. > See related bug for JBoss EAP 6.4: https://bugzilla.redhat.com/show_bug.cgi?id=1167983 > David said: Looks like the place to make this change would be in org.jboss.as.ejb3.component.interceptors.LoggingInterceptor. Maybe a specific catch clause for exception types to not log? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-263) Cancelling management op on slave HC tree is broken

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFCORE-263?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-263: ------------------------------------------------ Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1202610|https://bugzilla.redhat.com/show_bug.cgi?id=1202610] from NEW to CLOSED > Cancelling management op on slave HC tree is broken > --------------------------------------------------- > > Key: WFCORE-263 > URL: https://issues.jboss.org/browse/WFCORE-263 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 1.0.0.Alpha9 > Reporter: James Livingston > Assignee: Brian Stansberry > Priority: Major > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > Attachments: unundeployable.zip > > > If you have a DC with a slave HC, and perform a management operation which gets stuck, non-progressing operations will be reported for both the DC and the slave HC via: > /host=master/core-service=management/service=management-operations:find-non-progressing-operation > /host=slave/core-service=management/service=management-operations:find-non-progressing-operation > Cancelling the operation under /host=master works as expected, pushing the cancellation down to the slave and the controllers become responsive again. > If however you attempt to cancel the operation under /host=slave, it goes bad. { "outcome" => "success", "result" => undefined } is reported in the CLI, but the controllers are still unresponsive. > Running :find-non-progressing-operation against the slave will report the {outcome=success,result=undefined} rather than that no non-progressing operations were found, and active-operation=*:read-resource() shows it as not cancelled. > Once you attempt to cancel it on a slave, attempting to cancel it under /host=master will report success, but leave the slave op in a weird state, and things requiring the controller lock (such as the web UI) will still not respond. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-489) The "access-mechanism" field in the active-operation resources is always undefined

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFCORE-489?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-489: ------------------------------------------------ Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1202610|https://bugzilla.redhat.com/show_bug.cgi?id=1202610] from NEW to CLOSED > The "access-mechanism" field in the active-operation resources is always undefined > ---------------------------------------------------------------------------------- > > Key: WFCORE-489 > URL: https://issues.jboss.org/browse/WFCORE-489 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 1.0.0.Alpha15 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 1.0.0.Beta4 > > > The "access-mechanism" field in core-service=management/service=active-operations/active-operation=* is always undefined. The code that sets it is using the wrong var: > {code} > ModelNode accessMechanismNode = model.get(ACCESS_MECHANISM); > if (accessMechanism != null) { > accessMechanismNode.set(accessMechanismNode.toString()); > } > {code} > It should be accessMechanism.toString() -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-67) method-params containing an array not correctly processed for EJB2.1 with CMT

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFLY-67?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-67: --------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1180571|https://bugzilla.redhat.com/show_bug.cgi?id=1180571] from NEW to CLOSED > method-params containing an array not correctly processed for EJB2.1 with CMT > ----------------------------------------------------------------------------- > > Key: WFLY-67 > URL: https://issues.jboss.org/browse/WFLY-67 > Project: WildFly > Issue Type: Bug > Components: EJB > Environment: JBoss 7.2.0-Final Prerelease (Commit 4ed76c) and JBoss 7.1.3.Final on Win7/64 JDK 1.7.0_09 > Reporter: Robert Panzer > Assignee: Ondrej Zizka > Priority: Major > Fix For: 8.0.0.Alpha1 > > Attachments: cmt-never-array-params.zip > > > It seems that the method-params for container transactions are not matched correctly if the contain arrays. > I've got an EJB "First" that calls another EJB "Second". Both have the same interface containing a method void test(String[]); > If I define the transaction attribute NEVER including method-params for "First" and without params for "Second" the test fails with > JBAS014163: Transaction present on server in Never call (EJB3 13.6.2.6) > I define the container transaction like this: > <container-transaction> > <method> > <ejb-name>FirstWithParams</ejb-name> > <method-intf>Local</method-intf> > <method-name>test</method-name> > <method-params> > <method-param>java.lang.String[]</method-param> > </method-params> > </method> > <method> > <ejb-name>FirstWithParams</ejb-name> > <method-intf>Local</method-intf> > <method-name>test</method-name> > <method-params> > <method-param>java.lang.String</method-param> > </method-params> > </method> > <method> > <ejb-name>FirstWithParams</ejb-name> > <method-intf>Local</method-intf> > <method-name>test</method-name> > <method-params> > <method-param>int</method-param> > </method-params> > </method> > <method> > <ejb-name>Second</ejb-name> > <method-intf>Local</method-intf> > <method-name>test</method-name> > </method> > <trans-attribute>Never</trans-attribute> > </container-transaction> > I will attach a test case that fails at the call to test(String[]) but successfully call test(String) and test(int). -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-284) Rewrite CLI FileArgumentTestCase

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFCORE-284?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-284: ------------------------------------------------ Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 900632|https://bugzilla.redhat.com/show_bug.cgi?id=900632] from NEW to CLOSED > Rewrite CLI FileArgumentTestCase > -------------------------------- > > Key: WFCORE-284 > URL: https://issues.jboss.org/browse/WFCORE-284 > Project: WildFly Core > Issue Type: Task > Components: CLI > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Priority: Major > > The test has been failing sporadically for awhile. One of the problems is to figure out the conditions under which the test fails. They haven't been determined so far. Perhaps, attempts to simplify and clean up the logic in the test will help. > The test is org.jboss.as.test.integration.management.cli.FileArgumentTestCase -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2019