[JBoss JIRA] (DROOLS-4603) Scenario test: CSS support for "add an expression-based value" design implementation.
by Sarah Rambacher (Jira)
[ https://issues.jboss.org/browse/DROOLS-4603?page=com.atlassian.jira.plugi... ]
Sarah Rambacher commented on DROOLS-4603:
-----------------------------------------
Add the Info icon and Clear selection link after the label:
{code:java}
<label for="kie-search" data-i18n-key="Select_Data_Object">
Select Data Object
<a href="">
<span class="pficon pficon-info" style="padding-top: 4px;"></span>
</a>
</label>
<a href="" class="pull-right">Clear selection</a>
{code}
Format the box that is around the search and list:
{code:java}
.kie-test-tools-content__box {
padding: @pf-spacer-xs; // this should be 10px;
border: 1px solid @color-pf-black-400; // this should be #bbb;
}
{code}
You can also remove the `<hr/>` below the box.
[~yamer] The last part should go into the .less so that the @variables are available. If that's not possible then I put the values there.
> Scenario test: CSS support for "add an expression-based value" design implementation.
> --------------------------------------------------------------------------------------
>
> Key: DROOLS-4603
> URL: https://issues.jboss.org/browse/DROOLS-4603
> Project: Drools
> Issue Type: Story
> Components: Scenario Simulation and Testing
> Reporter: Elizabeth Clayton
> Assignee: Sarah Rambacher
> Priority: Major
> Labels: UX, UXTeam
> Attachments: Screen Shot 2019-10-01 at 8.27.30 AM.png, long_value.gif
>
>
> Test scenario implementation needs updates to support this new design/feature. Changes are outlined at: https://docs.google.com/presentation/d/1bHs9ZAbHAnV-cK9LQE6uJ38ZEIHR_QrfV... and in the referenced click-thru.
> User story: As a technical/advanced user (Cameron), I want to be able to input expression-based values in scenario given/expect row cells, so that I can define inputs for complex objects and logic.
> Note: Syntax highlighting etc. and checkbox inputs are out of scope. Refer to: https://issues.jboss.org/browse/DROOLS-3514
> *Verification conditions*
> Team would like CSS for the following:
> - updated CSS for the right panel that reflects the changes in the document. ^^
> - updated List dialog CSS to reflect design additions.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFLY-12798) HealthCheck HTTP endpoint does not support CDI @RequestScoped scope
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFLY-12798?page=com.atlassian.jira.plugin... ]
Jeff Mesnil commented on WFLY-12798:
------------------------------------
The same may apply to the metrics endpoints if one of the metrics from the deployment uses CDI @RequestScoped scope (to be confirmed)
> HealthCheck HTTP endpoint does not support CDI @RequestScoped scope
> -------------------------------------------------------------------
>
> Key: WFLY-12798
> URL: https://issues.jboss.org/browse/WFLY-12798
> Project: WildFly
> Issue Type: Bug
> Components: MP Health
> Affects Versions: 18.0.0.Final
> Reporter: Florian Sailer
> Assignee: Jeff Mesnil
> Priority: Major
>
> 2019-11-15 15:26:11,717 ERROR [org.wildfly.extension.microprofile.health.smallrye] (management I/O-1) Error processing Health Checks: org.jboss.weld.contexts.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.RequestScoped
> at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:647)
> at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:89)
> at org.jboss.weld.bean.ContextualInstanceStrategy$CachingContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:164)
> at org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63)
> at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:87)
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:131)
> at at.arz.bpe.boundary.PingCheck$Proxy$_$$_WeldClientProxy.call(Unknown Source)
> at org.wildfly.extension.microprofile.health.HealthReporter.jsonObject(HealthReporter.java:120)
> at org.wildfly.extension.microprofile.health.HealthReporter.fillCheck(HealthReporter.java:107)
> at org.wildfly.extension.microprofile.health.HealthReporter.processChecks(HealthReporter.java:96)
> at org.wildfly.extension.microprofile.health.HealthReporter.getHealth(HealthReporter.java:79)
> at org.wildfly.extension.microprofile.health.HealthReporter.getHealth(HealthReporter.java:60)
> at org.wildfly.extension.microprofile.health.HealthContextService$HealthCheckHandler.handleRequest(HealthContextService.java:100)
> at org.jboss.as.domain.http.server.security.RealmReadinessHandler.handleRequest(RealmReadinessHandler.java:51)
> at org.jboss.as.domain.http.server.security.ServerErrorReadinessHandler.handleRequest(ServerErrorReadinessHandler.java:35)
> at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:91)
> at io.undertow.server.handlers.ChannelUpgradeHandler.handleRequest(ChannelUpgradeHandler.java:211)
> at io.undertow.server.handlers.cache.CacheHandler.handleRequest(CacheHandler.java:92)
> at io.undertow.server.handlers.error.SimpleErrorPageHandler.handleRequest(SimpleErrorPageHandler.java:78)
> at io.undertow.server.handlers.CanonicalPathHandler.handleRequest(CanonicalPathHandler.java:49)
> at org.jboss.as.domain.http.server.ManagementHttpRequestHandler.handleRequest(ManagementHttpRequestHandler.java:57)
> at org.jboss.as.domain.http.server.cors.CorsHttpHandler.handleRequest(CorsHttpHandler.java:75)
> at org.jboss.as.domain.http.server.ManagementHttpServer$UpgradeFixHandler.handleRequest(ManagementHttpServer.java:666)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:376)
> at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:255)
> at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:136)
> at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:162)
> at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:100)
> at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:57)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:291)
> at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:286)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.nio.QueuedNioTcpServer$1.run(QueuedNioTcpServer.java:132)
> at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:612)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:479)
> MP-Health Spec doesnt enforce a scope and it worked with wildfly 17.0.0.1-Final.
> https://github.com/eclipse/microprofile-health/issues/109
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFLY-12798) HealthCheck HTTP endpoint does not support CDI @RequestScoped scope
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFLY-12798?page=com.atlassian.jira.plugin... ]
Jeff Mesnil updated WFLY-12798:
-------------------------------
Summary: HealthCheck HTTP endpoint does not support CDI @RequestScoped scope (was: HealthCheck HTTP endpoint does not support CDI RequestScoped scope)
> HealthCheck HTTP endpoint does not support CDI @RequestScoped scope
> -------------------------------------------------------------------
>
> Key: WFLY-12798
> URL: https://issues.jboss.org/browse/WFLY-12798
> Project: WildFly
> Issue Type: Bug
> Components: MP Health
> Affects Versions: 18.0.0.Final
> Reporter: Florian Sailer
> Assignee: Jeff Mesnil
> Priority: Major
>
> 2019-11-15 15:26:11,717 ERROR [org.wildfly.extension.microprofile.health.smallrye] (management I/O-1) Error processing Health Checks: org.jboss.weld.contexts.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.RequestScoped
> at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:647)
> at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:89)
> at org.jboss.weld.bean.ContextualInstanceStrategy$CachingContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:164)
> at org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63)
> at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:87)
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:131)
> at at.arz.bpe.boundary.PingCheck$Proxy$_$$_WeldClientProxy.call(Unknown Source)
> at org.wildfly.extension.microprofile.health.HealthReporter.jsonObject(HealthReporter.java:120)
> at org.wildfly.extension.microprofile.health.HealthReporter.fillCheck(HealthReporter.java:107)
> at org.wildfly.extension.microprofile.health.HealthReporter.processChecks(HealthReporter.java:96)
> at org.wildfly.extension.microprofile.health.HealthReporter.getHealth(HealthReporter.java:79)
> at org.wildfly.extension.microprofile.health.HealthReporter.getHealth(HealthReporter.java:60)
> at org.wildfly.extension.microprofile.health.HealthContextService$HealthCheckHandler.handleRequest(HealthContextService.java:100)
> at org.jboss.as.domain.http.server.security.RealmReadinessHandler.handleRequest(RealmReadinessHandler.java:51)
> at org.jboss.as.domain.http.server.security.ServerErrorReadinessHandler.handleRequest(ServerErrorReadinessHandler.java:35)
> at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:91)
> at io.undertow.server.handlers.ChannelUpgradeHandler.handleRequest(ChannelUpgradeHandler.java:211)
> at io.undertow.server.handlers.cache.CacheHandler.handleRequest(CacheHandler.java:92)
> at io.undertow.server.handlers.error.SimpleErrorPageHandler.handleRequest(SimpleErrorPageHandler.java:78)
> at io.undertow.server.handlers.CanonicalPathHandler.handleRequest(CanonicalPathHandler.java:49)
> at org.jboss.as.domain.http.server.ManagementHttpRequestHandler.handleRequest(ManagementHttpRequestHandler.java:57)
> at org.jboss.as.domain.http.server.cors.CorsHttpHandler.handleRequest(CorsHttpHandler.java:75)
> at org.jboss.as.domain.http.server.ManagementHttpServer$UpgradeFixHandler.handleRequest(ManagementHttpServer.java:666)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:376)
> at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:255)
> at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:136)
> at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:162)
> at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:100)
> at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:57)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:291)
> at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:286)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.nio.QueuedNioTcpServer$1.run(QueuedNioTcpServer.java:132)
> at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:612)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:479)
> MP-Health Spec doesnt enforce a scope and it worked with wildfly 17.0.0.1-Final.
> https://github.com/eclipse/microprofile-health/issues/109
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFLY-12798) HealthCheck HTTP endpoint does not support CDI RequestScoped scope
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFLY-12798?page=com.atlassian.jira.plugin... ]
Jeff Mesnil updated WFLY-12798:
-------------------------------
Summary: HealthCheck HTTP endpoint does not support CDI RequestScoped scope (was: Using Smallrye HealthChecks in RequestScoped Beans)
> HealthCheck HTTP endpoint does not support CDI RequestScoped scope
> ------------------------------------------------------------------
>
> Key: WFLY-12798
> URL: https://issues.jboss.org/browse/WFLY-12798
> Project: WildFly
> Issue Type: Bug
> Components: MP Health
> Affects Versions: 18.0.0.Final
> Reporter: Florian Sailer
> Assignee: Jeff Mesnil
> Priority: Major
>
> 2019-11-15 15:26:11,717 ERROR [org.wildfly.extension.microprofile.health.smallrye] (management I/O-1) Error processing Health Checks: org.jboss.weld.contexts.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.RequestScoped
> at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:647)
> at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:89)
> at org.jboss.weld.bean.ContextualInstanceStrategy$CachingContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:164)
> at org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63)
> at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:87)
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:131)
> at at.arz.bpe.boundary.PingCheck$Proxy$_$$_WeldClientProxy.call(Unknown Source)
> at org.wildfly.extension.microprofile.health.HealthReporter.jsonObject(HealthReporter.java:120)
> at org.wildfly.extension.microprofile.health.HealthReporter.fillCheck(HealthReporter.java:107)
> at org.wildfly.extension.microprofile.health.HealthReporter.processChecks(HealthReporter.java:96)
> at org.wildfly.extension.microprofile.health.HealthReporter.getHealth(HealthReporter.java:79)
> at org.wildfly.extension.microprofile.health.HealthReporter.getHealth(HealthReporter.java:60)
> at org.wildfly.extension.microprofile.health.HealthContextService$HealthCheckHandler.handleRequest(HealthContextService.java:100)
> at org.jboss.as.domain.http.server.security.RealmReadinessHandler.handleRequest(RealmReadinessHandler.java:51)
> at org.jboss.as.domain.http.server.security.ServerErrorReadinessHandler.handleRequest(ServerErrorReadinessHandler.java:35)
> at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:91)
> at io.undertow.server.handlers.ChannelUpgradeHandler.handleRequest(ChannelUpgradeHandler.java:211)
> at io.undertow.server.handlers.cache.CacheHandler.handleRequest(CacheHandler.java:92)
> at io.undertow.server.handlers.error.SimpleErrorPageHandler.handleRequest(SimpleErrorPageHandler.java:78)
> at io.undertow.server.handlers.CanonicalPathHandler.handleRequest(CanonicalPathHandler.java:49)
> at org.jboss.as.domain.http.server.ManagementHttpRequestHandler.handleRequest(ManagementHttpRequestHandler.java:57)
> at org.jboss.as.domain.http.server.cors.CorsHttpHandler.handleRequest(CorsHttpHandler.java:75)
> at org.jboss.as.domain.http.server.ManagementHttpServer$UpgradeFixHandler.handleRequest(ManagementHttpServer.java:666)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:376)
> at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:255)
> at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:136)
> at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:162)
> at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:100)
> at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:57)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:291)
> at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:286)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.nio.QueuedNioTcpServer$1.run(QueuedNioTcpServer.java:132)
> at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:612)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:479)
> MP-Health Spec doesnt enforce a scope and it worked with wildfly 17.0.0.1-Final.
> https://github.com/eclipse/microprofile-health/issues/109
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4782) CSS/HTML: Designer - Improve DMN rule task properties UX
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4782?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-4782:
--------------------------------------
Attachment: Screen Shot 2019-11-18 at 11.08.25 AM.png
> CSS/HTML: Designer - Improve DMN rule task properties UX
> --------------------------------------------------------
>
> Key: DROOLS-4782
> URL: https://issues.jboss.org/browse/DROOLS-4782
> Project: Drools
> Issue Type: Story
> Components: Stunner
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: Stunner, UX, UXTeam, drools-tools
> Attachments: Screen Shot 2019-05-03 at 1.53.33 PM.png, Screen Shot 2019-05-03 at 7.31.32 AM.png, Screen Shot 2019-11-18 at 11.06.41 AM.png, Screen Shot 2019-11-18 at 11.08.25 AM.png
>
>
> The properties panel for a DMN Rule task in the Stunner dock needs to be updated, to match designs provided in the Marvel prototype. The focus on the front end development changes are around input fields.
> Background:
> Currently, the user has to know all properties from the head or find them in DMN Modeler which is too long and error-prone task. Define input fields that allow fields/properties to be pre-populated to streamline experience for the user.
> Properties that need be set:
> * DMN file selector: The Namespace is provided in the background.
> * Decision name (optional field): Decision service, Decision, or _blank_.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months