[JBoss JIRA] (DROOLS-1748) Drools workbench datasource on Wildfly domain.
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1748?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-1748:
---------------------------------------
[~wmedvede] , can you check if this needs to be added to the docs and then close this ticket?
> Drools workbench datasource on Wildfly domain.
> ----------------------------------------------
>
> Key: DROOLS-1748
> URL: https://issues.jboss.org/browse/DROOLS-1748
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.0.0.Final, 7.3.0.Final
> Environment: Drools workbench on Wildfly domain cluster
> Reporter: M C
> Assignee: Walter Medvedeo
> Priority: Critical
>
> After starting workbench war (version 7.3 and 7.0, both Final) on Wildfly 10.1 domain cluster, got the issues with data source.
> [Server:server-one] 13:09:07,908 WARN [org.kie.workbench.common.screens.datasource.management.backend.DataSourceManagementBootstrap] (pool-14-thread-1) Initialize deployments task finished with errors: operation execution failed. :WFLYCTL0030: No resource definition is registered for address [("subsystem" => "datasources")]
> Problem does not affect Wildfly standalone configuration, only domain configuration using profiles.
> WFLYCTL0030 warning says the syntax problem using jboss-cli.sh. In domain cluster it's used /profile=full-ha/subsystem=datasource/...
> In standalone syntax is: /subsystem=datasource/.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month
[JBoss JIRA] (DROOLS-1748) Drools workbench datasource on Wildfly domain.
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1748?page=com.atlassian.jira.plugi... ]
Edson Tirelli reassigned DROOLS-1748:
-------------------------------------
Assignee: Walter Medvedeo (was: Petr Široký)
> Drools workbench datasource on Wildfly domain.
> ----------------------------------------------
>
> Key: DROOLS-1748
> URL: https://issues.jboss.org/browse/DROOLS-1748
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.0.0.Final, 7.3.0.Final
> Environment: Drools workbench on Wildfly domain cluster
> Reporter: M C
> Assignee: Walter Medvedeo
> Priority: Critical
>
> After starting workbench war (version 7.3 and 7.0, both Final) on Wildfly 10.1 domain cluster, got the issues with data source.
> [Server:server-one] 13:09:07,908 WARN [org.kie.workbench.common.screens.datasource.management.backend.DataSourceManagementBootstrap] (pool-14-thread-1) Initialize deployments task finished with errors: operation execution failed. :WFLYCTL0030: No resource definition is registered for address [("subsystem" => "datasources")]
> Problem does not affect Wildfly standalone configuration, only domain configuration using profiles.
> WFLYCTL0030 warning says the syntax problem using jboss-cli.sh. In domain cluster it's used /profile=full-ha/subsystem=datasource/...
> In standalone syntax is: /subsystem=datasource/.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month
[JBoss JIRA] (DROOLS-1749) Allow Build & Deploy to execute regardless of KieContainer currently executing
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1749?page=com.atlassian.jira.plugi... ]
Edson Tirelli reassigned DROOLS-1749:
-------------------------------------
Assignee: Alexandre Porcelli (was: Edson Tirelli)
> Allow Build & Deploy to execute regardless of KieContainer currently executing
> ------------------------------------------------------------------------------
>
> Key: DROOLS-1749
> URL: https://issues.jboss.org/browse/DROOLS-1749
> Project: Drools
> Issue Type: Enhancement
> Reporter: Chad Poe
> Assignee: Alexandre Porcelli
>
> Currently, when clicking Build & Deploy the first time, an artifact is created and put in the maven repository, and a KieContainer (with the artifact GAV) is created and started on Kie Server. When doing active development on a SNAPSHOT of that GAV it would be nice if Build & Deploy could be used to create a new SNAPSHOT version in the repository which would allow for the KieScanner to pick up those changes if the container was configured to do so.
> Currently, when clicking Build & Deploy a second time, an error is returned indicating that a Container already exists with container id matching the GAV of the artifact.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month
[JBoss JIRA] (ELY-1380) Calling getNegotiatedProperty for Elytron SASL mechanisms doesn't throw IllegalStateException when negotiatition is not completed
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-1380?page=com.atlassian.jira.plugin.s... ]
Jan Kalina moved JBEAP-13360 to ELY-1380:
-----------------------------------------
Project: WildFly Elytron (was: JBoss Enterprise Application Platform)
Key: ELY-1380 (was: JBEAP-13360)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: SASL
(was: Security)
Affects Version/s: 1.2.0.Beta4
(was: 7.1.0.CR2)
> Calling getNegotiatedProperty for Elytron SASL mechanisms doesn't throw IllegalStateException when negotiatition is not completed
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: ELY-1380
> URL: https://issues.jboss.org/browse/ELY-1380
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SASL
> Affects Versions: 1.2.0.Beta4
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Critical
>
> The Elytron SASL mechanism implementations don't throw {{IllegalStateException}} when calling the {{getNegotiatedProperty()}} method before the negotiation is finished.
> The contract of the {{Object javax.security.sasl.SaslClient.getNegotiatedProperty(String propName)}} says:
> bq. Retrieves the negotiated property. This method can be called only after the authentication exchange has completed (i.e., when isComplete() returns true); otherwise, an IllegalStateException is thrown.
> The same is valid for the {{SaslServer}} interface.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month
[JBoss JIRA] (ELY-1379) KeyStore element does not support overriding Provider discovery
by Darran Lofthouse (JIRA)
Darran Lofthouse created ELY-1379:
-------------------------------------
Summary: KeyStore element does not support overriding Provider discovery
Key: ELY-1379
URL: https://issues.jboss.org/browse/ELY-1379
Project: WildFly Elytron
Issue Type: Enhancement
Components: Authentication Client
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 1.2.0.Beta5
Additionally it doesn't take into account the default Provider discovery or the Provider definition at the root of the <authentication-configuration /> definition.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month