March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1490) Unable to see LocalDateTime specific operations for comparison

by chandra vudumula (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1490?page=com.atlassian.jira.plugi... ] chandra vudumula updated DROOLS-1490: ------------------------------------- Labels: (was: new_and_noteworthy) > Unable to see LocalDateTime specific operations for comparison > -------------------------------------------------------------- > > Key: DROOLS-1490 > URL: https://issues.jboss.org/browse/DROOLS-1490 > Project: Drools > Issue Type: Feature Request > Reporter: chandra vudumula > Assignee: Edson Tirelli > Attachments: image-2017-03-20-11-45-20-413.png > > > Hi, > I am trying to create a rule using UI,i have a filed LocalDateTime have to compare using after or before. > but in UI i am unable to see those options, its just showing default options like :equal to", "not equal to"... > Added dependencies in sourceObject and didnt helped -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-63) Hawkular Agent - Changes (Non JMANs)

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-63?page=com.atlassian.jira.plu... ] Matt Mahoney commented on HAWKULARQE-63: ---------------------------------------- There is no developer doc on Agent changes, thus rolled up emails on the subject. JMazz is the go-to developer for questions on the changes. https://mojo.redhat.com/docs/DOC-1131931 > Hawkular Agent - Changes (Non JMANs) > ------------------------------------ > > Key: HAWKULARQE-63 > URL: https://issues.jboss.org/browse/HAWKULARQE-63 > Project: Hawkular QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Michael Foley > > Place Holder task for now: > Changes expected to Hawkular Agent which will require full regression testing: > * Agent running on Bare Metal: Start/Stop will change - full regress needed. > * OpenShift: No expected changes, but should regression test. > *+*Development will write a blog post on the changes, once they are ready to be merged.*+* -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-63) Hawkular Agent - Changes (Non JMANs)

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-63?page=com.atlassian.jira.plu... ] Matt Mahoney updated HAWKULARQE-63: ----------------------------------- Comment: was deleted (was: From JMazz: The only thing added post-0.28.0.Final was this Java Agent stuff. The Wildfly Agent (the thing you've been testing with) hasn't changed - it should work the same as before. The Java Agent that was introduced should work the same as that WildFly agent except: 1) it is installed via the -javaagent option when launching a JVM, not injected in standalone.xml within WildFly itself 2) it uses its own YAML configuration file rather than XML in the standalone.xml (thought the yaml setting names mimic the XML element/attribute names - e.g. metric-set-dmr, local-dmr, etc). Example yaml files are found here (see the real-config*.yaml ones): https://github.com/hawkular/hawkular-agent/tree/master/hawkular-javaagent... 3) You cannot run Java Agent directly in a Host Controller - but since domain mode isn't supported in this Middleware Manager stuff, I doubt you care about that. Really, other than that, this Java Agent should behave just like the WildFly Agent. That is in theory - in actuality, we'll need testing to find the places that are broken But the pieces that are going to be broke are probably not in the agent directly, but in the Middleware Manager UI that hardcoded some things it expects when the agent is deployed as a WildFly subsystem. We would need to fix those kinds of things.) > Hawkular Agent - Changes (Non JMANs) > ------------------------------------ > > Key: HAWKULARQE-63 > URL: https://issues.jboss.org/browse/HAWKULARQE-63 > Project: Hawkular QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Michael Foley > > Place Holder task for now: > Changes expected to Hawkular Agent which will require full regression testing: > * Agent running on Bare Metal: Start/Stop will change - full regress needed. > * OpenShift: No expected changes, but should regression test. > *+*Development will write a blog post on the changes, once they are ready to be merged.*+* -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-63) Hawkular Agent - Changes (Non JMANs)

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-63?page=com.atlassian.jira.plu... ] Matt Mahoney updated HAWKULARQE-63: ----------------------------------- Comment: was deleted (was: On Sat, Mar 18, 2017 at 3:22 PM, John Mazzitelli <mazz(a)redhat.com> wrote: Just released Hawkular Java Agent 0.29.1.Final that contains a new feature. To support deploying Java Agent within containers (though this feature isn't restricted to that use-case), you can configure many settings in the Java Agent YAML config with ${x} expressions (similar to how HWFA can be configured in standalone.xml). It supports getting values from system properties, environment variables, with default values optionally defined. The following expressions are supported - hopefully this is self-explanatory: ${some.system.property} ${some.system.property:a-default-value} ${ENV~SOME_ENV_VAR} ${ENV~SOME_ENV_VAR:a-default-value} Not all properties support expressions (most don't need them) but properties that define things like hosts, ports, urls, passwords, filepaths, do support expressions. If I missed any, or if you'd like a property to support expressions that does not currently, write a HWKAGENT JIRA: https://issues.jboss.org/projects/HWKAGENT) > Hawkular Agent - Changes (Non JMANs) > ------------------------------------ > > Key: HAWKULARQE-63 > URL: https://issues.jboss.org/browse/HAWKULARQE-63 > Project: Hawkular QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Michael Foley > > Place Holder task for now: > Changes expected to Hawkular Agent which will require full regression testing: > * Agent running on Bare Metal: Start/Stop will change - full regress needed. > * OpenShift: No expected changes, but should regression test. > *+*Development will write a blog post on the changes, once they are ready to be merged.*+* -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-46) Agent starts the agentservice when an agent config is changed.

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-46?page=com.atlassian.jira.plu... ] Matt Mahoney commented on HAWKULARQE-46: ---------------------------------------- There is no developer doc on Agent changes, thus rolled up emails on the subject. JMazz is the go-to developer for questions on the changes. https://mojo.redhat.com/docs/DOC-1131931 > Agent starts the agentservice when an agent config is changed. > -------------------------------------------------------------- > > Key: HAWKULARQE-46 > URL: https://issues.jboss.org/browse/HAWKULARQE-46 > Project: Hawkular QE > Issue Type: Task > Environment: From hrupp Status 2/23/2017 - Agent Release 0.28 > Major change to wildfly agent internals - it now restarts the agent > service when an agent config is changed. > Reporter: Matt Mahoney > Assignee: Hayk Hovsepyan > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1507) Expose features currently provided by ModelController via capabilities usable by extensions

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1507?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1507: ------------------------------------- Description: -A server installs ServerService while an HC installs DomainModelControllerService, under different service names but both of which implement Service<ModelController>. To make it easier for subsystems that want ModelController access to work on both a server and an HC, we should create a capability with service type ModelController and have both processes use it.- Extensions may have a need to create an internal ModelControllerClient or to register notification handlers. Currently this is done by looking up the ModelController via its internal service name but: 1) ModelController exposes methods that should not be available to extensions 2) Accessing services should be via a capability. So, we need to expose capabilities for these functions. was:A server installs ServerService while an HC installs DomainModelControllerService, under different service names but both of which implement Service<ModelController>. To make it easier for subsystems that want ModelController access to work on both a server and an HC, we should create a capability with service type ModelController and have both processes use it. > Expose features currently provided by ModelController via capabilities usable by extensions > ------------------------------------------------------------------------------------------- > > Key: WFCORE-1507 > URL: https://issues.jboss.org/browse/WFCORE-1507 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > -A server installs ServerService while an HC installs DomainModelControllerService, under different service names but both of which implement Service<ModelController>. To make it easier for subsystems that want ModelController access to work on both a server and an HC, we should create a capability with service type ModelController and have both processes use it.- > Extensions may have a need to create an internal ModelControllerClient or to register notification handlers. Currently this is done by looking up the ModelController via its internal service name but: > 1) ModelController exposes methods that should not be available to extensions > 2) Accessing services should be via a capability. > So, we need to expose capabilities for these functions. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1489) Repeated fireAllRules() causes firing rules multiple times when using OOPath + JPA

by Martin Cimbalek (JIRA)

Martin Cimbalek created DROOLS-1489: --------------------------------------- Summary: Repeated fireAllRules() causes firing rules multiple times when using OOPath + JPA Key: DROOLS-1489 URL: https://issues.jboss.org/browse/DROOLS-1489 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.0.0.Beta8 Reporter: Martin Cimbalek Assignee: Mario Fusco Repeated calling fireAllRules causes firing rules repeatedely when using OOPath in combination with JPA persistence even when facts were not modified. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2560) User names in Elytron FileSystemRealm are not case sensitive on Windows

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2560?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet moved JBEAP-9698 to WFCORE-2560: -------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2560 (was: JBEAP-9698) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) Affects Version/s: 3.0.0.Beta9 (was: 7.1.0.DR12) > User names in Elytron FileSystemRealm are not case sensitive on Windows > ----------------------------------------------------------------------- > > Key: WFCORE-2560 > URL: https://issues.jboss.org/browse/WFCORE-2560 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta9 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Priority: Blocker > Labels: filesystem-realm, security-realm, windows > > User names are case sensitive on Linux but not on Windows when using the Elytron {{FileSystemSecurityRealm}} > This is IMO a security issue. And it also affects platform certifications. > If this is by any chance an expected behavior, then it has to be emphasized in documentation and in the domain model too (description of file-system-realm) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8408) Upgrade HAL to 2.9.5.Final

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/WFLY-8408?page=com.atlassian.jira.plugin.... ] Harald Pehl updated WFLY-8408: ------------------------------ Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/9799) > Upgrade HAL to 2.9.5.Final > -------------------------- > > Key: WFLY-8408 > URL: https://issues.jboss.org/browse/WFLY-8408 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8408) Upgrade HAL to 2.9.5.Final

by Harald Pehl (JIRA)

Harald Pehl created WFLY-8408: --------------------------------- Summary: Upgrade HAL to 2.9.5.Final Key: WFLY-8408 URL: https://issues.jboss.org/browse/WFLY-8408 Project: WildFly Issue Type: Component Upgrade Components: Web Console Reporter: Harald Pehl Assignee: Harald Pehl Fix For: 11.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2017