October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7262) Upgrade jackson-core to version that has fix for JBEAP-5870

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-7262: --------------------------------- Summary: Upgrade jackson-core to version that has fix for JBEAP-5870 Key: WFLY-7262 URL: https://issues.jboss.org/browse/WFLY-7262 Project: WildFly Issue Type: Component Upgrade Components: REST Reporter: Tomaz Cerar Assignee: Tomaz Cerar Upgrade to jackson that has fix for memory leak found in WFLY-7037 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7261) Upgrade jackson-core to version that has fix for WFLY-7037

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-7261: --------------------------------- Summary: Upgrade jackson-core to version that has fix for WFLY-7037 Key: WFLY-7261 URL: https://issues.jboss.org/browse/WFLY-7261 Project: WildFly Issue Type: Component Upgrade Components: REST Reporter: Tomaz Cerar Assignee: Tomaz Cerar Upgrade to jackson that has fix for memory leak found in WFLY-7037 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6931) add implicit module dependency to configuration directory

by Juergen Weber (JIRA)

[ https://issues.jboss.org/browse/WFLY-6931?page=com.atlassian.jira.plugin.... ] Juergen Weber resolved WFLY-6931. --------------------------------- Resolution: Won't Fix One can use <subsystem xmlns="urn:jboss:domain:ee:1.2"> <global-modules> > add implicit module dependency to configuration directory > --------------------------------------------------------- > > Key: WFLY-6931 > URL: https://issues.jboss.org/browse/WFLY-6931 > Project: WildFly > Issue Type: Feature Request > Components: Class Loading > Affects Versions: 10.1.0.CR1 > Reporter: Juergen Weber > Assignee: David Lloyd > > Best practice for loading of property files is via classloading. > Many applications try to load a custom properties file via class loading (e.g. Apache JSPWiki tries to load /jspwiki-custom.properties). With Tomcat, you simply drop property files into tomcat/lib. > For Wildfly, you have to create a module and add a jboss-dependency.xml to the application: > https://developer.jboss.org/wiki/HowToPutAnExternalFileInTheClasspath > Wildfly should have resource folder which by default should be added to the classpath of all applications, i.e. should be an implicit dependency. At least one should be able to switch this on in standalone.xml > The folder could be standalone/configuration. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7260) Document in elytron model *-client-auth are mutual exclusive

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7260?page=com.atlassian.jira.plugin.... ] Martin Choma updated WFLY-7260: ------------------------------- Summary: Document in elytron model *-client-auth are mutual exclusive (was: Document in model *-client-auth are mutual exclusive) > Document in elytron model *-client-auth are mutual exclusive > ------------------------------------------------------------ > > Key: WFLY-7260 > URL: https://issues.jboss.org/browse/WFLY-7260 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Priority: Minor > > Add to documentation information that need-client-auth and want-client-auth are mutually exclusive. If one is set other is unset. > Now we just have: > * {{want-client-auth}} - "Set wantClientAuth on the underlying SSLContext - if a security domain is referenced this will automatically be set to true." > * {{need-client-auth}} - "Set needClientAuth on the underlying SSLContext." -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7260) Document in model *-client-auth are mutual exclusive

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7260?page=com.atlassian.jira.plugin.... ] Martin Choma moved JBEAP-6289 to WFLY-7260: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7260 (was: JBEAP-6289) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) Affects Version/s: 11.0.0.Alpha1 (was: 7.1.0.DR6) > Document in model *-client-auth are mutual exclusive > ---------------------------------------------------- > > Key: WFLY-7260 > URL: https://issues.jboss.org/browse/WFLY-7260 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Priority: Minor > > Add to documentation information that need-client-auth and want-client-auth are mutually exclusive. If one is set other is unset. > Now we just have: > * {{want-client-auth}} - "Set wantClientAuth on the underlying SSLContext - if a security domain is referenced this will automatically be set to true." > * {{need-client-auth}} - "Set needClientAuth on the underlying SSLContext." -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1316) Missing MBean for Classpath KieContainer causes RHQ/JON plug-in failure to display the whole hierarchy

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1316?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-1316: ---------------------------------------- This solves the problem of RHQ/JON unable to discover the 1st level parent MXBean for the KieContainer making the MXBean available also when the KieContainer is created from the Classpath, the full 3-level hierarchy is built. Functional test with RHQ: !solved.png|thumbnail! In the screenshot, the Jconsole and JVisualVM is showing the reference nesting of the 3 level, and the actual result on RHQ corresponds correctly. This screenshot has been taken using the demo application(1) using the Classpath KieContainer: {code:java} public static void main(String[] args) { KieServices ks = KieServices.Factory.get(); KieContainer kcontainer = ks.getKieClasspathContainer("abcContainer"); KieSession ksession = kcontainer.newKieSession("rules-session"); ... } {code} (1) https://github.com/jomarko/drools-project > Missing MBean for Classpath KieContainer causes RHQ/JON plug-in failure to display the whole hierarchy > ------------------------------------------------------------------------------------------------------ > > Key: DROOLS-1316 > URL: https://issues.jboss.org/browse/DROOLS-1316 > Project: Drools > Issue Type: Bug > Components: core engine, integration > Affects Versions: 6.5.0.CR2, 7.0.0.Beta1 > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Fix For: 6.5.0.Final, 7.0.0.Beta3, 7.0.0.Final > > Attachments: solved.png > > > As RHQ/JON is able to discover the MBean for the KieBase and KieSession but unable to locate the MXBean for the KieContainer, would fail to display the whole hierarchy. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1316) Missing MBean for Classpath KieContainer causes RHQ/JON plug-in failure to display the whole hierarchy

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1316?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-1316: ----------------------------------- Attachment: solved.png > Missing MBean for Classpath KieContainer causes RHQ/JON plug-in failure to display the whole hierarchy > ------------------------------------------------------------------------------------------------------ > > Key: DROOLS-1316 > URL: https://issues.jboss.org/browse/DROOLS-1316 > Project: Drools > Issue Type: Bug > Components: core engine, integration > Affects Versions: 6.5.0.CR2, 7.0.0.Beta1 > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Attachments: solved.png > > > As RHQ/JON is able to discover the MBean for the KieBase and KieSession but unable to locate the MXBean for the KieContainer, would fail to display the whole hierarchy. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1317) Missing MBean for Classpath KieContainer causes RHQ/JON plug-in failure to display the whole hierarchy

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-1317: -------------------------------------- Summary: Missing MBean for Classpath KieContainer causes RHQ/JON plug-in failure to display the whole hierarchy Key: DROOLS-1317 URL: https://issues.jboss.org/browse/DROOLS-1317 Project: Drools Issue Type: Bug Components: core engine, integration Affects Versions: 6.5.0.CR2, 7.0.0.Beta1 Reporter: Matteo Mortari Assignee: Matteo Mortari As RHQ/JON is able to discover the MBean for the KieBase and KieSession but unable to locate the MXBean for the KieContainer, would fail to display the whole hierarchy. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1850) Failed to process logging directory /. Log files cannot be listed

by Heiko Braun (JIRA)

Heiko Braun created WFCORE-1850: ----------------------------------- Summary: Failed to process logging directory /. Log files cannot be listed Key: WFCORE-1850 URL: https://issues.jboss.org/browse/WFCORE-1850 Project: WildFly Core Issue Type: Bug Reporter: Heiko Braun -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7259) Review elytron kerberos-security-factory resource

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7259?page=com.atlassian.jira.plugin.... ] Martin Choma moved JBEAP-6287 to WFLY-7259: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7259 (was: JBEAP-6287) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) Affects Version/s: 11.0.0.Alpha1 (was: 7.1.0.DR6) > Review elytron kerberos-security-factory resource > ------------------------------------------------- > > Key: WFLY-7259 > URL: https://issues.jboss.org/browse/WFLY-7259 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Darran Lofthouse > > * {{mechanism-oids}} > ** Minimal command for kerberos security factory creation is {code}/subsystem=elytron/kerberos-security-factory=kerberos:add(principal=mchoma, path=/path/to/keytab, mechanism-oids=[1.2.840.113554.1.2.2]){code} > ** I don't think it is user-friendly to require user to specify mechanism-oids. I think some reasonable default value should be used here. > * {{minimum-remaining-lifetime}} > ** please, specify units in documentation, e.g. seconds/minutes > * {{relative-to}} > ** as just path reference can be used here, probably should be just "expressions-allowed" => false > ** In legacy settings it is documented better: "The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute." > * {{server}} > ** I assume based on {{server}} attribute INITIATE_ONLY or ACCEPT_ONLY is configured on GSSCredential [1]. Wouldn't it be useful to have also possibility to set INITIATE_AND_ACCEPT? Couldn't that be useful for example in case of identity propagation. > * {{for-hosts}} > ** comparing to legacy security {{kerberosIdentityType}} I am missing for-hosts. Elytron won't provide such feature? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 October 2016