[JBoss JIRA] (ELY-1621) BC FIPS with CLI: the trustAnchors parameter must be non-empty
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/ELY-1621?page=com.atlassian.jira.plugin.s... ]
Martin Choma closed ELY-1621.
-----------------------------
Resolution: Explained
> BC FIPS with CLI: the trustAnchors parameter must be non-empty
> --------------------------------------------------------------
>
> Key: ELY-1621
> URL: https://issues.jboss.org/browse/ELY-1621
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.5.1.Final
> Reporter: Martin Choma
> Priority: Blocker
> Attachments: cli-test-wildfly-config.xml, jboss-cli.log, keystore.bcfks
>
>
> I am trying to connect from jboss-cli.sh to EAP server. To reproduce the problem it is enough BC FIPS is used only on client side.
> {code:java|titlejboss-cli.log}
> 08:13:18,469 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: java.lang.ExceptionInInitializerError
> at org.wildfly.security.auth.client.AuthenticationContext.lambda$static$0(AuthenticationContext.java:54)
> at org.wildfly.common.context.ContextManager.getPrivileged(ContextManager.java:286)
> at org.wildfly.security.auth.client.AuthenticationContext.captureCurrent(AuthenticationContext.java:86)
> at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:146)
> at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198)
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:291)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Caused by: org.wildfly.security.auth.client.InvalidAuthenticationConfigurationException: org.wildfly.client.config.ConfigXMLParseException: java.security.KeyStoreException: initialization failed
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:40)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.<clinit>(DefaultAuthenticationContextProvider.java:36)
> ... 14 more
> Caused by: org.wildfly.client.config.ConfigXMLParseException: java.security.KeyStoreException: initialization failed
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$10(ElytronXmlParser.java:525)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextRuleType$11(ElytronXmlParser.java:711)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseRulesType$13(ElytronXmlParser.java:749)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:356)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:231)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:192)
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:38)
> ... 16 more
> Caused by: java.security.KeyStoreException: initialization failed
> at org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi.engineInit(ProvTrustManagerFactorySpi.java:150)
> at javax.net.ssl.TrustManagerFactory.init(TrustManagerFactory.java:250)
> at org.wildfly.security.auth.client.ElytronXmlParser$TrustManagerBuilder.build(ElytronXmlParser.java:590)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$10(ElytronXmlParser.java:523)
> ... 22 more
> Caused by: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
> at java.security.cert.PKIXParameters.setTrustAnchors(PKIXParameters.java:200)
> at java.security.cert.PKIXParameters.<init>(PKIXParameters.java:120)
> at java.security.cert.PKIXBuilderParameters.<init>(PKIXBuilderParameters.java:104)
> at org.bouncycastle.jsse.provider.ProvX509TrustManagerImpl.<init>(ProvX509TrustManagerImpl.java:53)
> at org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi.engineInit(ProvTrustManagerFactorySpi.java:146)
> ... 25 more
> {code}
> When I use non-FIPS java with CLI I can make it work. It does occure also when connecting to default unsecured port 9990.
> I have double check truststore is there. Correct password is used. Server has permission to open the truststure. And truststore contains certificate
> When I use BCFKS truststore on server side, e.g. in 2-way http communication it works.
> So it looks to me something on client side is missing? Any hint?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (ELY-1621) BC FIPS with CLI: the trustAnchors parameter must be non-empty
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/ELY-1621?page=com.atlassian.jira.plugin.s... ]
Martin Choma edited comment on ELY-1621 at 8/2/18 6:02 AM:
-----------------------------------------------------------
It turn out BC provider behave differently compared to another providers. For testing pusrposes I have under one alias private key and certificate.
Seems BC does not handle this situation properly. After I have created truststore with only certificate entry it works now.
{code}
@Override
public boolean engineIsCertificateEntry(String alias)
{
ObjectData ent = entries.get(alias);
if (ent != null)
{
return ent.getType().equals(CERTIFICATE);
}
return false;
}
{code}
But there seems to be another problem with this scenario. I will report once I will investigate.
[~rlucente-se-jboss] FYI
was (Author: mchoma):
It turn out BC provider behave differently compared to another providers. For testing pusrposes I had only under one alias private key and certificate.
Seems BC does not handle this situation properly. After I have created truststore with only certificate entry it works now.
{code}
@Override
public boolean engineIsCertificateEntry(String alias)
{
ObjectData ent = entries.get(alias);
if (ent != null)
{
return ent.getType().equals(CERTIFICATE);
}
return false;
}
{code}
[~rlucente-se-jboss] FYI
> BC FIPS with CLI: the trustAnchors parameter must be non-empty
> --------------------------------------------------------------
>
> Key: ELY-1621
> URL: https://issues.jboss.org/browse/ELY-1621
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.5.1.Final
> Reporter: Martin Choma
> Priority: Blocker
> Attachments: cli-test-wildfly-config.xml, jboss-cli.log, keystore.bcfks
>
>
> I am trying to connect from jboss-cli.sh to EAP server. To reproduce the problem it is enough BC FIPS is used only on client side.
> {code:java|titlejboss-cli.log}
> 08:13:18,469 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: java.lang.ExceptionInInitializerError
> at org.wildfly.security.auth.client.AuthenticationContext.lambda$static$0(AuthenticationContext.java:54)
> at org.wildfly.common.context.ContextManager.getPrivileged(ContextManager.java:286)
> at org.wildfly.security.auth.client.AuthenticationContext.captureCurrent(AuthenticationContext.java:86)
> at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:146)
> at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198)
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:291)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Caused by: org.wildfly.security.auth.client.InvalidAuthenticationConfigurationException: org.wildfly.client.config.ConfigXMLParseException: java.security.KeyStoreException: initialization failed
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:40)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.<clinit>(DefaultAuthenticationContextProvider.java:36)
> ... 14 more
> Caused by: org.wildfly.client.config.ConfigXMLParseException: java.security.KeyStoreException: initialization failed
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$10(ElytronXmlParser.java:525)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextRuleType$11(ElytronXmlParser.java:711)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseRulesType$13(ElytronXmlParser.java:749)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:356)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:231)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:192)
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:38)
> ... 16 more
> Caused by: java.security.KeyStoreException: initialization failed
> at org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi.engineInit(ProvTrustManagerFactorySpi.java:150)
> at javax.net.ssl.TrustManagerFactory.init(TrustManagerFactory.java:250)
> at org.wildfly.security.auth.client.ElytronXmlParser$TrustManagerBuilder.build(ElytronXmlParser.java:590)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$10(ElytronXmlParser.java:523)
> ... 22 more
> Caused by: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
> at java.security.cert.PKIXParameters.setTrustAnchors(PKIXParameters.java:200)
> at java.security.cert.PKIXParameters.<init>(PKIXParameters.java:120)
> at java.security.cert.PKIXBuilderParameters.<init>(PKIXBuilderParameters.java:104)
> at org.bouncycastle.jsse.provider.ProvX509TrustManagerImpl.<init>(ProvX509TrustManagerImpl.java:53)
> at org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi.engineInit(ProvTrustManagerFactorySpi.java:146)
> ... 25 more
> {code}
> When I use non-FIPS java with CLI I can make it work. It does occure also when connecting to default unsecured port 9990.
> I have double check truststore is there. Correct password is used. Server has permission to open the truststure. And truststore contains certificate
> When I use BCFKS truststore on server side, e.g. in 2-way http communication it works.
> So it looks to me something on client side is missing? Any hint?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (ELY-1621) BC FIPS with CLI: the trustAnchors parameter must be non-empty
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/ELY-1621?page=com.atlassian.jira.plugin.s... ]
Martin Choma commented on ELY-1621:
-----------------------------------
It turn out BC provider behave differently compared to another providers. For testing pusrposes I had only under one alias private key and certificate.
Seems BC does not handle this situation properly. After I have created truststore with only certificate entry it works now.
{code}
@Override
public boolean engineIsCertificateEntry(String alias)
{
ObjectData ent = entries.get(alias);
if (ent != null)
{
return ent.getType().equals(CERTIFICATE);
}
return false;
}
{code}
[~rlucente-se-jboss] FYI
> BC FIPS with CLI: the trustAnchors parameter must be non-empty
> --------------------------------------------------------------
>
> Key: ELY-1621
> URL: https://issues.jboss.org/browse/ELY-1621
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.5.1.Final
> Reporter: Martin Choma
> Priority: Blocker
> Attachments: cli-test-wildfly-config.xml, jboss-cli.log, keystore.bcfks
>
>
> I am trying to connect from jboss-cli.sh to EAP server. To reproduce the problem it is enough BC FIPS is used only on client side.
> {code:java|titlejboss-cli.log}
> 08:13:18,469 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: java.lang.ExceptionInInitializerError
> at org.wildfly.security.auth.client.AuthenticationContext.lambda$static$0(AuthenticationContext.java:54)
> at org.wildfly.common.context.ContextManager.getPrivileged(ContextManager.java:286)
> at org.wildfly.security.auth.client.AuthenticationContext.captureCurrent(AuthenticationContext.java:86)
> at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:146)
> at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198)
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:291)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Caused by: org.wildfly.security.auth.client.InvalidAuthenticationConfigurationException: org.wildfly.client.config.ConfigXMLParseException: java.security.KeyStoreException: initialization failed
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:40)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.<clinit>(DefaultAuthenticationContextProvider.java:36)
> ... 14 more
> Caused by: org.wildfly.client.config.ConfigXMLParseException: java.security.KeyStoreException: initialization failed
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$10(ElytronXmlParser.java:525)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextRuleType$11(ElytronXmlParser.java:711)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseRulesType$13(ElytronXmlParser.java:749)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:356)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:231)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:192)
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:38)
> ... 16 more
> Caused by: java.security.KeyStoreException: initialization failed
> at org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi.engineInit(ProvTrustManagerFactorySpi.java:150)
> at javax.net.ssl.TrustManagerFactory.init(TrustManagerFactory.java:250)
> at org.wildfly.security.auth.client.ElytronXmlParser$TrustManagerBuilder.build(ElytronXmlParser.java:590)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$10(ElytronXmlParser.java:523)
> ... 22 more
> Caused by: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
> at java.security.cert.PKIXParameters.setTrustAnchors(PKIXParameters.java:200)
> at java.security.cert.PKIXParameters.<init>(PKIXParameters.java:120)
> at java.security.cert.PKIXBuilderParameters.<init>(PKIXBuilderParameters.java:104)
> at org.bouncycastle.jsse.provider.ProvX509TrustManagerImpl.<init>(ProvX509TrustManagerImpl.java:53)
> at org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi.engineInit(ProvTrustManagerFactorySpi.java:146)
> ... 25 more
> {code}
> When I use non-FIPS java with CLI I can make it work. It does occure also when connecting to default unsecured port 9990.
> I have double check truststore is there. Correct password is used. Server has permission to open the truststure. And truststore contains certificate
> When I use BCFKS truststore on server side, e.g. in 2-way http communication it works.
> So it looks to me something on client side is missing? Any hint?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10781) Jackson Annotations are broken
by Mario-Luca Hoffmann (JIRA)
Mario-Luca Hoffmann created WFLY-10781:
------------------------------------------
Summary: Jackson Annotations are broken
Key: WFLY-10781
URL: https://issues.jboss.org/browse/WFLY-10781
Project: WildFly
Issue Type: Bug
Components: REST
Affects Versions: 13.0.0.Final
Environment: Windows 10 x64, WildFly 12 & 13
Reporter: Mario-Luca Hoffmann
Assignee: Alessio Soldano
With the switch from WildFly 12 to 13 our Jackson Annotations stopped working properly. While some of these are working (@JsonProperty) sometimes, others (@JsonIgnore) aren't working anymore. With WildFly 12 everything is fine, this issue only arises using WildFly 13 using a EE8 profile.
However, I tried it with a pristine WildFly 13: not working, WildFly 12: works like a charme. I tried to fix it with replacing the jackson-databind library with the newest version (2.9.6) but this didn't work as well.
Example for the attached Github Project:
The expected output is: {"name":"Mario","attribute":"notWorking"}
The acutal output is: {"attribute":"notWorking","name":"Mario","number":-1337}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2708) Icon for test results dock
by Toni Rikkola (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2708?page=com.atlassian.jira.plugi... ]
Toni Rikkola commented on DROOLS-2708:
--------------------------------------
[~uxdlc] I don't think there are any icons used at the moment.
We can use this in the Test Results Dock one it gets moved there.
> Icon for test results dock
> --------------------------
>
> Key: DROOLS-2708
> URL: https://issues.jboss.org/browse/DROOLS-2708
> Project: Drools
> Issue Type: Sub-task
> Components: Scenario Simulation and Testing, Test Scenarios Editor
> Reporter: Liz Clayton
> Assignee: Brian Dellascio
> Labels: UX, UXTeam, VisualDesign
>
> As a practitioner I need to know which docked tab indicates the Scenario Test results panel within the test editor.
> Notes:
> Icon needed for the right panel dock (functions as a tab) - same behavior as all Process Designer docks. Additional details outlined in icon spreadsheet and parent jira.
> Reasonable icon concept could be something like the font awesome "play-circle" icon: https://fontawesome.com/cheatsheet?from=io
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2730) CSS for test "syntax cheatsheet" dock tab design
by Gabriele Cardosi (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2730?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi commented on DROOLS-2730:
------------------------------------------
[~ederign] Hi Eder. I am talking with [~Rikkola] and I am reading the Uberfire documentation
http://www.uberfireframework.org/docs/overview/workbench.html
http://www.uberfireframework.org/docs/overview/docks.html
But I am not sure about our use case. From the documentation - and also looking at the
graphical behaviour - I have the impression that docks are meant to show something that it is not strictly related to the editor itself (for example general application errors/messages, navigation between different components, stuff like that) - so that makes sense to hide or move them around. On the other hand, the "editor" itself could be made of different parts, and in our case the right panel is a necessary part of the editor because you use it to edit the values - it should not be "hided" nor moved around: in my understanding it should be a fixed panel.
Am I misunderstanding something? Is it that the documentation should be updated?
> CSS for test "syntax cheatsheet" dock tab design
> ------------------------------------------------
>
> Key: DROOLS-2730
> URL: https://issues.jboss.org/browse/DROOLS-2730
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Sarah Rambacher
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Dock-deets.png, nospace.png, space.png
>
>
> As a practitioner I want to reference valid expression syntax, so that I can create expression formatted Given/Expect input values when creating a scenario test outline.
> *Verification conditions:*
> - CSS styles that employ relevant PatternFly styles.
> - CSS that articulates the design wireframe attached, and:
> https://redhat.invisionapp.com/share/BVKORFBUJ24#/screens/302476080, and:
> https://docs.google.com/document/d/1I_ghU9An--uQRzuVV9zXB387HLYjZcc01LXFX...
> - Reviewed by scrum team prior to PR/dev delivery.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2827) [DMN Designer] Diagram save produces svg
by Kirill Gaevskii (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2827?page=com.atlassian.jira.plugi... ]
Kirill Gaevskii commented on DROOLS-2827:
-----------------------------------------
Hi [~manstis], [~jomarko],
jBPM engine needs SVG to display current active node in a running process. It wasn't mandatory for 6.x, but since 7.0.GA we need to generate SVG for every process before execution, so Designer generating SVG files on save.
But I am not sure is this use case valid for the DMN editor.
> [DMN Designer] Diagram save produces svg
> ----------------------------------------
>
> Key: DROOLS-2827
> URL: https://issues.jboss.org/browse/DROOLS-2827
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Labels: drools-tools
> Attachments: Screenshot from 2018-08-02 10-56-15.png
>
>
> When user saves the diagram, the svg file appears in the workbench.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2755) [DMN Designer] Error when the user switches between DMN files
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2755?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2755:
--------------------------------
Description:
When the user switches between DMN files, the following error happens:
!demo.gif|thumbnail!
It's an intermittent problem, therefore the steps to reproduce the bug (showed in the GIF) don't propagate the error every time.
h3. Manual Acceptance Test
Switch between multiple files
- using library (/)
- using project explorer (/)
was:
When the user switches between DMN files, the following error happens:
!demo.gif|thumbnail!
It's an intermittent problem, therefore the steps to reproduce the bug (showed in the GIF) don't propagate the error every time.
h3. Manual Acceptance Test
Switch between multiple files
- using library
- using project explorer
> [DMN Designer] Error when the user switches between DMN files
> -------------------------------------------------------------
>
> Key: DROOLS-2755
> URL: https://issues.jboss.org/browse/DROOLS-2755
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.9.0.Final
> Reporter: Guilherme Carreiro
> Assignee: Michael Anstis
> Labels: drools-tools
> Attachments: demo.gif
>
>
> When the user switches between DMN files, the following error happens:
> !demo.gif|thumbnail!
> It's an intermittent problem, therefore the steps to reproduce the bug (showed in the GIF) don't propagate the error every time.
> h3. Manual Acceptance Test
> Switch between multiple files
> - using library (/)
> - using project explorer (/)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2827) [DMN Designer] Diagram save produces svg
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2827?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2827:
----------------------------------------
[~roger600] Hi, this is _core_ Stunner behaviour.
Can you provide a link to the use-case requesting this operation?
[~tirelli] FYI.... what do you want DMN to do? (Stunner - so BPMN, DMN and Case Management - is automatically generating a SVG "on save").
> [DMN Designer] Diagram save produces svg
> ----------------------------------------
>
> Key: DROOLS-2827
> URL: https://issues.jboss.org/browse/DROOLS-2827
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Labels: drools-tools
> Attachments: Screenshot from 2018-08-02 10-56-15.png
>
>
> When user saves the diagram, the svg file appears in the workbench.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months