August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9989) Upgrade messaging-activemq model version to 3.1

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9989?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-9989: -------------------------------- Fix Version/s: 14.0.0.CR1 (was: 14.0.0.Beta2) > Upgrade messaging-activemq model version to 3.1 > ----------------------------------------------- > > Key: WFLY-9989 > URL: https://issues.jboss.org/browse/WFLY-9989 > Project: WildFly > Issue Type: Task > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 14.0.0.CR1 > > > and the XSD to 3.1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9232) mod_cluster decay factor does not support floating-point numerals; decays too quickly

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9232?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-9232: -------------------------------- Fix Version/s: 14.0.0.CR1 (was: 14.0.0.Beta2) > mod_cluster decay factor does not support floating-point numerals; decays too quickly > ------------------------------------------------------------------------------------- > > Key: WFLY-9232 > URL: https://issues.jboss.org/browse/WFLY-9232 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 11.0.0.Beta1, 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 14.0.0.CR1 > > > Downstream counterpart MODCLUSTER-607. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8364) mod_cluster model allows both simple- and dynamic-load-providers to be defined in the model simultaneously

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-8364?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-8364: -------------------------------- Fix Version/s: 14.0.0.CR1 (was: 14.0.0.Beta2) > mod_cluster model allows both simple- and dynamic-load-providers to be defined in the model simultaneously > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-8364 > URL: https://issues.jboss.org/browse/WFLY-8364 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 10.1.0.Final, 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 14.0.0.CR1 > > > {code} > <subsystem xmlns="urn:jboss:domain:modcluster:3.0"> > <mod-cluster-config advertise-socket="modcluster" connector="ajp"> > <simple-load-provider factor="5"/> > <dynamic-load-provider> > <load-metric type="cpu"/> > </dynamic-load-provider> > </mod-cluster-config> > </subsystem> > {code} > However, it would be ideal if this was reworked into correct resources, like the following: > {{/subsystem=modcluster/proxy=default/load-provider=dynamic}} > {{/subsystem=modcluster/proxy=default/load-provider=simple}} > Jira for that is WFLY-10471. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10616) ContextResolver doesn't work

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10616?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10616: --------------------------------- Fix Version/s: 14.0.0.CR1 (was: 14.0.0.Beta2) > ContextResolver doesn't work > ---------------------------- > > Key: WFLY-10616 > URL: https://issues.jboss.org/browse/WFLY-10616 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 13.0.0.Final > Reporter: George Trudeau > Assignee: R Searls > Fix For: 14.0.0.CR1 > > Attachments: test.war > > > I have a simple ContextResolver to set Date serialization format for my JAX-RS service, it works on 12.0.0.Final but it doesn't anymore on 13.0.0.Final : > {code:java} > @Provider > public class DateResolver implements ContextResolver<ObjectMapper> > { > private final ObjectMapper mapper; > public DateResolver() > { > mapper = new ObjectMapper(); > mapper.setDateFormat(new SimpleDateFormat("yyyy-MM-dd")); > mapper.disable(SerializationFeature.WRITE_DATES_AS_TIMESTAMPS); > } > @Override > public ObjectMapper getContext(Class<?> type) { return mapper; } > } > {code} > The {{getContext}} method isn't called on 13.0.0.Final. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10580) WildFly should use Artemis' SQLProvider implementation

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10580?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10580: --------------------------------- Fix Version/s: 14.0.0.CR1 (was: 14.0.0.Beta2) > WildFly should use Artemis' SQLProvider implementation > ------------------------------------------------------ > > Key: WFLY-10580 > URL: https://issues.jboss.org/browse/WFLY-10580 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 13.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 14.0.0.CR1 > > > During development and integration of JDBC persistence store into WildFly, the custom implementation of SQLProvider interface \[1\] was developed for WildFly use case. The reason was that WildFly used Artemis 1.x which was at that time maintenance branch and thus development of new features was focused on 2.x branch. > In the meantime, the code has been donated to Artemis and backported in Artemis 1.5.5.jbossorg-012. > We can now remove the implementation in WildFly code base and use the Artemis one instead. > \[1\] https://github.com/apache/activemq-artemis/blob/f2b5114af8dd505e3c5c3efc1... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10563) Upgrade HAL to 3.0.2.Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10563?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10563: --------------------------------- Fix Version/s: 14.0.0.CR1 (was: 14.0.0.Beta2) > Upgrade HAL to 3.0.2.Final > -------------------------- > > Key: WFLY-10563 > URL: https://issues.jboss.org/browse/WFLY-10563 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Fix For: 14.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10489) Rename mod_cluster Tomcat/JBossWeb-era "connector" attribute to listener

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10489?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10489: --------------------------------- Fix Version/s: 14.0.0.CR1 (was: 14.0.0.Beta2) > Rename mod_cluster Tomcat/JBossWeb-era "connector" attribute to listener > ------------------------------------------------------------------------ > > Key: WFLY-10489 > URL: https://issues.jboss.org/browse/WFLY-10489 > Project: WildFly > Issue Type: Enhancement > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 14.0.0.CR1 > > > mod_cluster listener attribute name is still "connector" (from the Tomcat/JBoss Web days) which is confusing. > The goal is to rename this to listener. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10475) JSF installer module definitions are not synced with JSF modules

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10475?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10475: --------------------------------- Fix Version/s: 14.0.0.CR1 (was: 14.0.0.Beta2) > JSF installer module definitions are not synced with JSF modules > ---------------------------------------------------------------- > > Key: WFLY-10475 > URL: https://issues.jboss.org/browse/WFLY-10475 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 13.0.0.Final > Reporter: Jan Blizňák > Assignee: Dmitrii Tikhomirov > Fix For: 14.0.0.CR1 > > > There is a JSF installer module resources https://github.com/wildfly/wildfly/tree/master/jsf/multi-jsf-installer/sr... which seem to be out of sync with the JSF modules defined in feature-pack: > https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/reso... > https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/reso... > https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/reso... > https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/reso... > I guess these should be synced, ie. changes from feature-pack should be reflected in JSF installer too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10471) mod_cluster load providers should be proper resources

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10471?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10471: --------------------------------- Fix Version/s: 14.0.0.CR1 (was: 14.0.0.Beta2) > mod_cluster load providers should be proper resources > ----------------------------------------------------- > > Key: WFLY-10471 > URL: https://issues.jboss.org/browse/WFLY-10471 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 13.0.0.Beta1, 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 14.0.0.CR1 > > > Follow up on WFLY-8364. It would be ideal if this was reworked into correct resources, like the following: > {{/subsystem=modcluster/proxy=default/load-provider=dynamic}} > {{/subsystem=modcluster/proxy=default/load-provider=simple}} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10777) Add WildFly Elytron / JASPI Integration Tests

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10777?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10777: --------------------------------- Fix Version/s: 14.0.0.CR1 (was: 14.0.0.Beta2) > Add WildFly Elytron / JASPI Integration Tests > --------------------------------------------- > > Key: WFLY-10777 > URL: https://issues.jboss.org/browse/WFLY-10777 > Project: WildFly > Issue Type: Task > Components: Security, Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 14.0.0.CR1 > > > The following key scenarios should be covered within the Elytron testsuite module: - > * Pre-configured JASPIC > In this case the SAMs are configured within the Elytron subsystem and applied at runtime to the web application. > Two predominant modes to consider: - > # Fully integrated, i.e. the Callbacks make use of the SecurityDomain for authentication. > # Ad-Hoc Identity i.e. We still have a security domain but trust the SAM to establish an ad-hoc identity. > * Programatically configured JASPIC > During servlet initilisation the new JaspicConfigurationBuilder API can be used to dynamically register a configuration. > Likely to need the same two modes. > * Retrospective JASPIC > In both the above cases the deployment can be deployed and either use Elytron HTTP authentication mechanisms or be unsecured, JASPIC for the deployment can be activated either via configuration or programatically and should take precedence over the existing authentication. > * Programatic Authentication > A servlet can use the authentication API on the HttpServletRequest and trigger authentication. > * No SecurityDomain > This one may not be as applicable at this stage but we should at some point support JASPIC being applied to a deployment not associated with any security domain, i.e. a new deployment on a clean install could programatically register a JASPIC configuration. > Without any security domain the identity would only have relevance within the servlet container so establishing an ad-hoc identity is actually a better approach. Additionally this relies on no default being present in the default config. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 August 2018