[JBoss JIRA] (DROOLS-2829) [DMN Designer] Expression header cell is not updated from properties panel
by Jozef Marko (JIRA)
Jozef Marko created DROOLS-2829:
-----------------------------------
Summary: [DMN Designer] Expression header cell is not updated from properties panel
Key: DROOLS-2829
URL: https://issues.jboss.org/browse/DROOLS-2829
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.10.0.Final
Reporter: Jozef Marko
Assignee: Michael Anstis
Priority: Optional
Decision and BKM elements holds some expression inside. This expression can be edited via expression grid editor. The expression grid editor shows the name of the parent element in its header cell. The problem is that this header cell is not updated if the element name is updated form the properties panel while expression grid editor is opened.
Spotted during DROOLS-2755 review. Not sure if it is related.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10791) Add a CLI Command to display the IIOP Naming Registry
by Brad Maxwell (JIRA)
[ https://issues.jboss.org/browse/WFLY-10791?page=com.atlassian.jira.plugin... ]
Brad Maxwell updated WFLY-10791:
--------------------------------
Priority: Minor (was: Major)
> Add a CLI Command to display the IIOP Naming Registry
> -----------------------------------------------------
>
> Key: WFLY-10791
> URL: https://issues.jboss.org/browse/WFLY-10791
> Project: WildFly
> Issue Type: Feature Request
> Components: IIOP
> Affects Versions: 13.0.0.Final
> Reporter: Brad Maxwell
> Assignee: Tomasz Adamski
> Priority: Minor
>
> Add a CLI Command to display the IIOP Naming Registry
> the Naming subsystem has a jndi-view operation to list out the contents of JNDI, something similar for the IIOP subsystem to see what is registered in the IIOP Naming Registry would be useful.
> {code}
> /subsystem=naming:jndi-view()
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10791) Add a CLI Command to display the IIOP Naming Registry
by Brad Maxwell (JIRA)
Brad Maxwell created WFLY-10791:
-----------------------------------
Summary: Add a CLI Command to display the IIOP Naming Registry
Key: WFLY-10791
URL: https://issues.jboss.org/browse/WFLY-10791
Project: WildFly
Issue Type: Feature Request
Components: IIOP
Affects Versions: 13.0.0.Final
Reporter: Brad Maxwell
Assignee: Tomasz Adamski
Add a CLI Command to display the IIOP Naming Registry
the Naming subsystem has a jndi-view operation to list out the contents of JNDI, something similar for the IIOP subsystem to see what is registered in the IIOP Naming Registry would be useful.
{code}
/subsystem=naming:jndi-view()
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10783) ChannelServiceConfigurator failed to open a port while deploying kitchenskink qs on migrated server
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-10783?page=com.atlassian.jira.plugin... ]
Paul Ferraro commented on WFLY-10783:
-------------------------------------
OK - I see the problem. When we fabricate channel after reading the 6.4 config, we need to ensure that the port_range is set to a non-zero value. EAP 6.4 relied on a shared transport to avoid port conflicts when sharing a protocol stack between multiple channels, but shared transport feature no longer exists.
> ChannelServiceConfigurator failed to open a port while deploying kitchenskink qs on migrated server
> ---------------------------------------------------------------------------------------------------
>
> Key: WFLY-10783
> URL: https://issues.jboss.org/browse/WFLY-10783
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Migration
> Environment: {noformat}
> ../wildfly] $ git rev-parse --short HEAD
> 0236eda5a2
> {noformat}
> Reporter: Petr Kremensky
> Assignee: Paul Ferraro
> Priority: Blocker
> Attachments: jboss-kitchensink.war
>
>
> Trying to deploy kitchensink quickstart on the server with configuration migrated from EAP 6.4.x fails with {{java.lang.IllegalStateException: java.lang.Exception: failed to open a port in range 55200-55200}}.
> *Reproduce*
> {noformat}
> WORKSPACE=`pwd`
> CONFIG=standalone-ha.xml
> unzip -q jboss-eap-6.4.20.zip
> cp -r ${WILDFLY}/dist/target/wildfly-14.0.0.Beta2-SNAPSHOT wildfly
> SOURCE_HOME=${WORKSPACE}/jboss-eap-6.4
> TARGET_HOME=${WORKSPACE}/wildfly
> cp ${SOURCE_HOME}/standalone/configuration/${CONFIG} ${TARGET_HOME}/standalone/configuration
> ${TARGET_HOME}/bin/standalone.sh -c ${CONFIG} --start-mode=admin-only &
> ${TARGET_HOME}/bin/jboss-cli.sh --connect --controller=remote://localhost:9999
> # Migrate
> /subsystem=web:migrate
> /subsystem=threads:remove
> /extension=org.jboss.as.threads:remove
> reload
> deploy jboss-kitchensink.war
> {noformat}
>
> *Outcome*
> {noformat}
> 14:44:13,799 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 56) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee-ejb: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.ee-ejb: java.lang.IllegalStateException: java.lang.Exception: failed to open a port in range 55200-55200
> at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:70) [wildfly-clustering-service-14.0.0.Beta2-SNAPSHOT.jar:14.0.0.Beta2-SNAPSHOT]
> at org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117) [wildfly-clustering-service-14.0.0.Beta2-SNAPSHOT.jar:14.0.0.Beta2-SNAPSHOT]
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171]
> at org.jboss.threads.JBossThread.run(JBossThread.java:485) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
> Caused by: java.lang.IllegalStateException: java.lang.Exception: failed to open a port in range 55200-55200
> at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:116)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:58)
> at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:67) [wildfly-clustering-service-14.0.0.Beta2-SNAPSHOT.jar:14.0.0.Beta2-SNAPSHOT]
> ... 7 more
> Caused by: java.lang.Exception: failed to open a port in range 55200-55200
> at org.jgroups.protocols.UDP.createMulticastSocketWithBindPort(UDP.java:519)
> at org.jgroups.protocols.UDP.createSockets(UDP.java:357)
> at org.jgroups.protocols.UDP.start(UDP.java:300)
> at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:861)
> at org.jgroups.JChannel.startStack(JChannel.java:1023)
> at org.jgroups.JChannel._preConnect(JChannel.java:886)
> at org.jgroups.JChannel.connect(JChannel.java:390)
> at org.jgroups.JChannel.connect(JChannel.java:384)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:112)
> ... 9 more
> {noformat}
> This works fine with EAP 7.1.3 as a TARGET_SERVER, thus marking as a blocker due to a regression.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10790) (7.1.z) HttpSessionListener.sessionDestroyed() not called if session invalidated in another WAR
by Brad Maxwell (JIRA)
Brad Maxwell created WFLY-10790:
-----------------------------------
Summary: (7.1.z) HttpSessionListener.sessionDestroyed() not called if session invalidated in another WAR
Key: WFLY-10790
URL: https://issues.jboss.org/browse/WFLY-10790
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 10.0.0.Final, 13.0.0.Final
Environment: Windows 10, Java 1.8.0_131
Reproducible with both WildFly-10.0.0.Final and Wildfly-13.0.0.Final
Reporter: Brad Maxwell
Assignee: Bartosz Baranowski
Attachments: LoginForm.png, roles.properties, sessionlistener-test.ear, standalone.xml, users.properties
For sessions shared across different WARs in a single EAR, the notification of HttpSessionListener works differently in WildFly 10.0.0.Final (and Wildfly 13.0.0.Final) than it it used to work in WildFly 8.2.0.Final:
I have an EAR containing two WARs with enabled session sharing across the WARs. Basically, one WAR contains the web UI, and the other WAR contains the REST interfaces for AJAX calls made by the UI. The user authenticates against the UI-WAR. On logout, a REST method in the AJAX-WAR is triggered which calls HttpSession.invalidate() on the user session.
In WildFly 8.2.0.Final, a HttpSessionListener in the UI-WAR gets notified immediately about session creation and destruction.
In WildFly 13.0.0.Final, however, a HttpSessionListener in either WAR only gets one of the two notifications:
* In the UI-WAR, I get a notification about the created session immediately when the login form is loaded. However, I do not receive any notification about the session destruction (unless it times out).
* In the AJAX-WAR, I do not get any notification about the session creation at all, but I immediately receive a notification about the session destruction.
--
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 commented on DROOLS-2787:
-------------------------------------
[~manstis] Okay that makes sense, but I'll wait to hear what the others say before updating the wireframes. There is a proposed button (link) on the property panel view: https://issues.jboss.org/browse/DROOLS-2774. I named it "Manage" but in light of this discussion maybe it should be "Customize"?
> "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: DROOLS-2738.bmpr, Manage1.png, Manage2.png, Screen Shot 2018-07-24 at 3.51.03 PM.png, Screen Shot 2018-07-27 at 11.48.34 AM.png, Screen Shot 2018-07-27 at 12.24.49 PM.png, Screen Shot 2018-07-27 at 12.27.13 PM.png, add_basic.png, treegrid.png, type_definitions.pdf
>
>
> *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 or otherwise complex 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 Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2787:
----------------------------------------
[~uxdlc] personally I find no value in adding a list of the built-in/default data-types (they'd be listed in the "Type selector" ("Text" [here|https://redhat.invisionapp.com/share/YXNBM5PGE52#/screens/312337253]). Others, [~tirelli] [~karreiro] may have an opinion.
The dialog is absolutely all about managing (create, edit, delete --> no button to do this ATM) "Custom Data-types".
> "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: DROOLS-2738.bmpr, Manage1.png, Manage2.png, Screen Shot 2018-07-24 at 3.51.03 PM.png, Screen Shot 2018-07-27 at 11.48.34 AM.png, Screen Shot 2018-07-27 at 12.24.49 PM.png, Screen Shot 2018-07-27 at 12.27.13 PM.png, add_basic.png, treegrid.png, type_definitions.pdf
>
>
> *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 or otherwise complex 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] (ELY-1622) BC FIPS with CLI: SunX509 KeyManagerFactory not available
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/ELY-1622?page=com.atlassian.jira.plugin.s... ]
Farah Juma commented on ELY-1622:
---------------------------------
This issue only occurs when there is no {{key-store-ssl-certificate}} configured in the wildfly-config.xml file. When there is a {{key-store-ssl-certificate}} configured, I'm able to successfully connect to EAP from the CLI. One thing to note is that ELY-1385 added an option to override the algorithm for {{TrustManager}}. However, a similar option was [not added|https://issues.jboss.org/browse/ELY-1385?focusedCommentId=13478645&...] for {{KeyManager}} because we're actually using our own custom {{KeyManager}} impl so there was no need to override that one.
To fix this, I wonder if our custom {{ConfigurationKeyManager.Builder}} should also be used for the case where no {{key-store-ssl-certificate}} is specified, i.e., something like:
{code}
diff --git a/src/main/java/org/wildfly/security/auth/client/ElytronXmlParser.java b/src/main/java/org/wildfly/security/auth/client/ElytronXmlParser.java
index c999217a4..4cb517e07 100644
--- a/src/main/java/org/wildfly/security/auth/client/ElytronXmlParser.java
+++ b/src/main/java/org/wildfly/security/auth/client/ElytronXmlParser.java
@@ -508,13 +508,13 @@ public final class ElytronXmlParser {
if (finalProtocolSelector != null) {
sslContextBuilder.setProtocolSelector(finalProtocolSelector);
}
+ final ConfigurationKeyManager.Builder builder = new ConfigurationKeyManager.Builder();
if (finalCredentialFactory != null) {
- final ConfigurationKeyManager.Builder builder = new ConfigurationKeyManager.Builder();
final X509CertificateChainPrivateCredential privateCredential;
privateCredential = finalCredentialFactory.get();
builder.addCredential(privateCredential);
- sslContextBuilder.setKeyManager(builder.build());
}
+ sslContextBuilder.setKeyManager(builder.build());
if (initTrustManager) {
{code}
[~dlofthouse] [~mchoma] WDYT?
> BC FIPS with CLI: SunX509 KeyManagerFactory not available
> ---------------------------------------------------------
>
> Key: ELY-1622
> URL: https://issues.jboss.org/browse/ELY-1622
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.5.1.Final
> Reporter: Martin Choma
> Assignee: Farah Juma
> Priority: Blocker
> Attachments: cli-test-wildfly-config.xml, jboss-cli.log, truststore.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}
> 11:50:25,147 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:330)
> 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.jboss.as.cli.CommandLineException: Failed to resolve host 'localhost'
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1256)
> 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)
> ... 5 more
> Caused by: java.io.IOException: Failed to obtain SSLContext
> at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:156)
> at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222)
> ... 8 more
> Caused by: java.security.KeyManagementException: java.security.NoSuchAlgorithmException: SunX509 KeyManagerFactory not available
> at org.bouncycastle.jsse.provider.ProvSSLContextSpi.selectKeyManager(ProvSSLContextSpi.java:589)
> at org.bouncycastle.jsse.provider.ProvSSLContextSpi.engineInit(ProvSSLContextSpi.java:531)
> at javax.net.ssl.SSLContext.init(SSLContext.java:282)
> at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:372)
> at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:53)
> at org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getSSLContext(AuthenticationContextConfigurationClient.java:221)
> at org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getSSLContext(AuthenticationContextConfigurationClient.java:208)
> at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:153)
> ... 10 more
> Caused by: java.security.NoSuchAlgorithmException: SunX509 KeyManagerFactory not available
> at sun.security.jca.GetInstance.getInstance(GetInstance.java:159)
> at javax.net.ssl.KeyManagerFactory.getInstance(KeyManagerFactory.java:137)
> at org.bouncycastle.jsse.provider.ProvSSLContextSpi.selectKeyManager(ProvSSLContextSpi.java:583)
> ... 17 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.
> When I use BCFKS truststore on server side, e.g. in 2-way http communication it works.
> I believe problem is I cant configure algorithm for keymanager on client side in wildfly-config.xml. (At least I don't see how could I do so).
> BC provider does not know SunX509 arlgorithm, rather X509, X.509 or PKIX could be used.
--
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 commented on DROOLS-2787:
-------------------------------------
[~manstis] Okay, thanks. Do you think there's any benefit to listing them there, as a kind of a master list reference? If not, then this is more of a Customize data types dialog or Manage Custom...
> "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: DROOLS-2738.bmpr, Manage1.png, Manage2.png, Screen Shot 2018-07-24 at 3.51.03 PM.png, Screen Shot 2018-07-27 at 11.48.34 AM.png, Screen Shot 2018-07-27 at 12.24.49 PM.png, Screen Shot 2018-07-27 at 12.27.13 PM.png, add_basic.png, treegrid.png, type_definitions.pdf
>
>
> *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 or otherwise complex 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