January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2217) [DMN Editor] Allow DMN persistence for an incomplete, still being authored, DMN model

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2217?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-2217: ---------------------------------------- This JIRA can be considered a special case for more generally allowing DMN persistence for an incomplete, still being authored, DMN model. JIRA renamed accordingly. > [DMN Editor] Allow DMN persistence for an incomplete, still being authored, DMN model > ------------------------------------------------------------------------------------- > > Key: DROOLS-2217 > URL: https://issues.jboss.org/browse/DROOLS-2217 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Matteo Mortari > Attachments: Screenshot from 2018-01-22 14-01-38.png, Screenshot from 2018-01-22 14-02-13.png, error.log > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2217) [DMN Editor] Allow DMN persistence for an incomplete, still being authored, DMN model

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2217?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-2217: ----------------------------------- Summary: [DMN Editor] Allow DMN persistence for an incomplete, still being authored, DMN model (was: [DMN Editor] Context Entry Definition is not saved) > [DMN Editor] Allow DMN persistence for an incomplete, still being authored, DMN model > ------------------------------------------------------------------------------------- > > Key: DROOLS-2217 > URL: https://issues.jboss.org/browse/DROOLS-2217 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Matteo Mortari > Attachments: Screenshot from 2018-01-22 14-01-38.png, Screenshot from 2018-01-22 14-02-13.png, error.log > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2951) Add JSON formatter resources to the logging subsystem

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2951?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-2951: ------------------------------------------ I think the analysis of this should make how it's going to be used on OpenShift a first class concern. We're now responsible for our OS images, and our images already have things in place related to this.[1] Features whose use cases are heavily cloud-driven are going to need to start factoring the use on OS into the plan. [1] See https://github.com/jboss-openshift/cct_module/blob/master/os-eap71-opensh... and also https://issues.jboss.org/browse/CLOUD-1517 and the key PR for that, https://github.com/jboss-openshift/cct_module/pull/99/files > Add JSON formatter resources to the logging subsystem > ----------------------------------------------------- > > Key: WFCORE-2951 > URL: https://issues.jboss.org/browse/WFCORE-2951 > Project: WildFly Core > Issue Type: Feature Request > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 4.0.0.Beta1 > > > The logging subsystem should include resources for a {{json-formatter}} -and probably a {{logstash-formatter}}. The {{logstash-formatter}} is likely just an extension of the {{json-formatter}} with some predefined attributes that logstash requires-. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9718) Integrate GOOGLE_PING2 discovery protocol

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-9718: ---------------------------------- Summary: Integrate GOOGLE_PING2 discovery protocol Key: WFLY-9718 URL: https://issues.jboss.org/browse/WFLY-9718 Project: WildFly Issue Type: Feature Request Components: Clustering Affects Versions: 11.0.0.Alpha1 Reporter: Paul Ferraro Assignee: Radoslav Husar The original GOOGLE_PING is being deprecated given how low quality the code is. Going forward, we need to integrate https://github.com/jgroups-extras/jgroups-google to keep supporting Google Cloud Platform-specific discovery mechanism. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9717) Integrate NATIVE_S3_PING discovery protocol

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-9717: ---------------------------------- Summary: Integrate NATIVE_S3_PING discovery protocol Key: WFLY-9717 URL: https://issues.jboss.org/browse/WFLY-9717 Project: WildFly Issue Type: Feature Request Components: Clustering Affects Versions: 11.0.0.Alpha1 Reporter: Paul Ferraro Assignee: Radoslav Husar The original S3_PING is being deprecated given how low quality the code is. Going forward, we need to integrate NATIVE_S3_PING from https://github.com/jgroups-extras/native-s3-ping to keep supporting EC2-specific discovery mechanism. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3534) Add an XML formatter resources to the logging subsystem

by James Perkins (JIRA)

James Perkins created WFCORE-3534: ------------------------------------- Summary: Add an XML formatter resources to the logging subsystem Key: WFCORE-3534 URL: https://issues.jboss.org/browse/WFCORE-3534 Project: WildFly Core Issue Type: Feature Request Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 4.0.0.Beta1 The logging subsystem should include a resource for a {{xml-formatter}}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3533) Add a socket-handler resource to the logging subsystem

by James Perkins (JIRA)

James Perkins created WFCORE-3533: ------------------------------------- Summary: Add a socket-handler resource to the logging subsystem Key: WFCORE-3533 URL: https://issues.jboss.org/browse/WFCORE-3533 Project: WildFly Core Issue Type: Feature Request Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 4.0.0.Beta1 The logging subsystem should include a resource for a {{socket-handler}}. This will be useful for structured formatters, such as the [{{json-formatter}}|WFCORE-2951]. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9716) Integrate KUBE_PING discovery protocol

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-9716: ---------------------------------- Summary: Integrate KUBE_PING discovery protocol Key: WFLY-9716 URL: https://issues.jboss.org/browse/WFLY-9716 Project: WildFly Issue Type: Feature Request Components: Clustering Affects Versions: 11.0.0.Final Reporter: Paul Ferraro Assignee: Radoslav Husar Fix For: 12.0.0.Alpha1 https://github.com/jgroups-extras/jgroups-kubernetes -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3532) Add JSON formatter resources to the logging subsystem

by James Perkins (JIRA)

James Perkins created WFCORE-3532: ------------------------------------- Summary: Add JSON formatter resources to the logging subsystem Key: WFCORE-3532 URL: https://issues.jboss.org/browse/WFCORE-3532 Project: WildFly Core Issue Type: Feature Request Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 4.0.0.Beta1 The logging subsystem should include resources for a {{json-formatter}} -and probably a {{logstash-formatter}}. The {{logstash-formatter}} is likely just an extension of the {{json-formatter}} with some predefined attributes that logstash requires-. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9126) Deployment fails when application domain names referrencing one Elytron domain are different in Undertow and EJB subsystems

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-9126?page=com.atlassian.jira.plugin.... ] Jan Kalina closed WFLY-9126. ---------------------------- Resolution: Rejected > Deployment fails when application domain names referrencing one Elytron domain are different in Undertow and EJB subsystems > --------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9126 > URL: https://issues.jboss.org/browse/WFLY-9126 > Project: WildFly > Issue Type: Bug > Components: EJB, Security, Web (Undertow) > Reporter: Josef Cacek > Assignee: Jan Kalina > Priority: Critical > > The WAR deployment fails when it contains EJBs and Servlets with security domains mapped under different names (application-security-domain). The underlying Elytron domain is the same for both subsystems. > EJB subsystem tries to search also for the domain name which is used in {{jboss-web.xml}} and this lookup fails. > Sample configuration: > {code:xml|title=jboss-ejb3.xml} > <jboss:ejb-jar> > <assembly-descriptor><s:security> > <ejb-name>*</ejb-name> > <s:security-domain>seccontext-whoami</s:security-domain> > </s:security></assembly-descriptor> > </jboss:ejb-jar> > {code} > {code:xml|title=jboss-web.xml} > <jboss-web> > <security-domain>seccontext-web</security-domain> > </jboss-web> > {code} > {code:title=application-security-domain-mapping.cli} > /subsystem=ejb3/application-security-domain=seccontext-whoami:add( \ > security-domain=ApplicationDomain) > /subsystem=undertow/application-security-domain=seccontext-web:add( \ > http-authentication-factory=application-http-authentication) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

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 January 2018