September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-186) PVC access mode is hardcoded to ReadWriteOnce

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-186?page=com.atlassian.jira.plugin.... ] Martin Choma commented on WFWIP-186: ------------------------------------ [~jmesnil] could you also document in [1] User does not have to declare access mode in {{PersistentVolumeClaim}} as it is hardcoded to {{ReadWriteOnce}} [1] https://github.com/wildfly/wildfly-operator/blob/master/doc/apis.adoc#sto... > PVC access mode is hardcoded to ReadWriteOnce > --------------------------------------------- > > Key: WFWIP-186 > URL: https://issues.jboss.org/browse/WFWIP-186 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > > Setting different access mode (ReadWriteMany, ReadOnlyMany) is ignored > [1] https://github.com/wildfly/wildfly-operator/blob/master/pkg/controller/wi... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12592) Usage of Elytron's SSL-Context in establishing SSL communication with DataBase

by Saurabh Shriramwar (Jira)

[ https://issues.jboss.org/browse/WFLY-12592?page=com.atlassian.jira.plugin... ] Saurabh Shriramwar updated WFLY-12592: -------------------------------------- Affects Version/s: 14.0.0.Final > Usage of Elytron's SSL-Context in establishing SSL communication with DataBase > ------------------------------------------------------------------------------ > > Key: WFLY-12592 > URL: https://issues.jboss.org/browse/WFLY-12592 > Project: WildFly > Issue Type: Feature Request > Affects Versions: 14.0.0.Final > Reporter: Saurabh Shriramwar > Assignee: Brian Stansberry > Priority: Minor > > To secure the connection between Wildfly and datasource using TCP/IP over SSL datasource should be able to utilize the ssl-context for trust-managers (pointing to java keystore or truststore containing the datasource CA certificates) configured in Elytron so that Wildfly can trust the datasource connection instead of setting java truststore in the system properties or providing as JAVA_OPTS (-Djavax.net.ssl.trustStore=/path/to/truststore.jks) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12592) Usage of Elytron's SSL-Context in establishing SSL communication with DataBase

by Saurabh Shriramwar (Jira)

[ https://issues.jboss.org/browse/WFLY-12592?page=com.atlassian.jira.plugin... ] Saurabh Shriramwar updated WFLY-12592: -------------------------------------- Description: To secure the connection between Wildfly and datasource using TCP/IP over SSL datasource should be able to utilize the ssl-context for trust-managers (pointing to java keystore or truststore containing the datasource CA certificates) configured in Elytron so that Wildfly can trust the datasource connection instead of setting java truststore in the system properties or providing as JAVA_OPTS (-Djavax.net.ssl.trustStore=/path/to/truststore.jks) (was: DataSource should be able to establish the SSL/TLS handshake with the usage of SSL-context configured within Elytron.) > Usage of Elytron's SSL-Context in establishing SSL communication with DataBase > ------------------------------------------------------------------------------ > > Key: WFLY-12592 > URL: https://issues.jboss.org/browse/WFLY-12592 > Project: WildFly > Issue Type: Feature Request > Reporter: Saurabh Shriramwar > Assignee: Brian Stansberry > Priority: Minor > > To secure the connection between Wildfly and datasource using TCP/IP over SSL datasource should be able to utilize the ssl-context for trust-managers (pointing to java keystore or truststore containing the datasource CA certificates) configured in Elytron so that Wildfly can trust the datasource connection instead of setting java truststore in the system properties or providing as JAVA_OPTS (-Djavax.net.ssl.trustStore=/path/to/truststore.jks) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12592) Usage of Elytron's SSL-Context in establishing SSL communication with DataBase

by Saurabh Shriramwar (Jira)

Saurabh Shriramwar created WFLY-12592: ----------------------------------------- Summary: Usage of Elytron's SSL-Context in establishing SSL communication with DataBase Key: WFLY-12592 URL: https://issues.jboss.org/browse/WFLY-12592 Project: WildFly Issue Type: Feature Request Reporter: Saurabh Shriramwar Assignee: Brian Stansberry DataSource should be able to establish the SSL/TLS handshake with the usage of SSL-context configured within Elytron. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12591) Upgrade mustache to 0.9.6

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12591: --------------------------------------- Summary: Upgrade mustache to 0.9.6 Key: WFLY-12591 URL: https://issues.jboss.org/browse/WFLY-12591 Project: WildFly Issue Type: Component Upgrade Components: Web (Undertow) Reporter: Brian Stansberry Assignee: Brian Stansberry https://github.com/spullara/mustache.java/compare/mustache.java-0.9.4...m... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12313) Implement MP OpenAPI

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12313?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12313: ----------------------------------------- Hi [~michael.edgar], Glad to hear you've made progress! 1) Re: Jandex, this is dependency is controlled by WildFly Core: https://github.com/wildfly/wildfly-core/blob/master/pom.xml#L175 [~jmesnil] Are you aware of any reason not to upgrade Core to the latest Jandex? 2) Re: Phase, unfortunately, yes, that needs to be updated in WF Core. It's ok to initially use a value not from the Phase constant list but by the time work is done it should be a constant from Phase. 3) Re: docs, there's https://docs.wildfly.org/17/Extending_WildFly.html but TBH that's not really about adding new subsystems to WildFly's own codebase. I assume you're talking about all the feature-pack and galleon-pack stuff? Yeah, that's a pain. 4) Re the ServletContextListener, [~pferraro] or [~flavia.rainone] would be good resources to get specific input. https://github.com/wildfly/wildfly-capabilities/blob/master/registry.txt is a reasonably complete list of capability names, with the other files in that repo documenting each one. > Implement MP OpenAPI > -------------------- > > Key: WFLY-12313 > URL: https://issues.jboss.org/browse/WFLY-12313 > Project: WildFly > Issue Type: Feature Request > Reporter: Michael Edgar > Assignee: Brian Stansberry > Priority: Major > > Please integrate MicroProfile OpenAPI. > Details about MP OpenAPI: > https://github.com/eclipse/microprofile-open-api/releases/tag/1.1.2 > Maybe it is possible to use SmallRye implementation: > https://github.com/smallrye/smallrye-open-api -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12313) Implement MP OpenAPI

by Michael Edgar (Jira)

[ https://issues.jboss.org/browse/WFLY-12313?page=com.atlassian.jira.plugin... ] Michael Edgar commented on WFLY-12313: -------------------------------------- [~brian.stansberry], I have been able to make some progress on this (changes will be kept update to date in [my feature/WFLY-12313-openapi on Github|https://github.com/wildfly/wildfly/compare/master...MikeEdgar:feat...]. The module code itself it working _somewhat_ using the management port (which will change before a PR) and it still needs to be cleaned up significantly. At this point I do have a few questions (please let me know if there is a better forum for these types of questions other than Jira) - * SmallRye OpenAPI requires a newer version of Jandex (2.1.1) than what is currently in WF (2.0.5). I have added the newer version to the dependency management of the parent POM, but the older version is still being used in the generated Jandex module. Any pointers where that version may be coming from? I will continue to attempt to figure this one out. * It seems as though the other MP modules have several constants defined in a {{Phase}} class that is pulled in from the Wildfly Core project. I am assuming similar upstream changes need to be made for this change as well, but please confirm. * I had to do a ton of digging/scanning to determine all of the locations where references needed to be added to the new module and its new dependent modules. Is there a more up-to-date guide than this? https://developer.jboss.org/wiki/HackingOnWildFly. * I am trying to follow the same pattern used in Thorntail for OpenAPI integration, which makes use of a servlet context listener that is added to the web archive during deployment. Is there a similar API in Wildfly that would allow adding an artifact to the archive? The APIs require knowledge of the feature/capabilities/attachment names and I'm not sure how to find them easily. > Implement MP OpenAPI > -------------------- > > Key: WFLY-12313 > URL: https://issues.jboss.org/browse/WFLY-12313 > Project: WildFly > Issue Type: Feature Request > Reporter: Michael Edgar > Assignee: Brian Stansberry > Priority: Major > > Please integrate MicroProfile OpenAPI. > Details about MP OpenAPI: > https://github.com/eclipse/microprofile-open-api/releases/tag/1.1.2 > Maybe it is possible to use SmallRye implementation: > https://github.com/smallrye/smallrye-open-api -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12590) Integrate MP Fault Tolerance 2.0 into EAP

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12590?page=com.atlassian.jira.plugin... ] Radoslav Husar moved EAP7-1350 to WFLY-12590: --------------------------------------------- Project: WildFly (was: EAP 7 Planning Pilot) Key: WFLY-12590 (was: EAP7-1350) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) EAP PT Pre-Checked (PC): (was: TODO) Target Release: (was: 7.4.0.GA) EAP PT Community Docs (CD): (was: TODO) EAP PT Product Docs (PD): (was: New) EAP PT Test Dev (TD): (was: TODO) EAP PT Docs Analysis (DA): (was: TODO) EAP PT Test Plan (TP): (was: TODO) EAP PT Analysis Document (AD): (was: TODO) > Integrate MP Fault Tolerance 2.0 into EAP > ----------------------------------------- > > Key: WFLY-12590 > URL: https://issues.jboss.org/browse/WFLY-12590 > Project: WildFly > Issue Type: Feature Request > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > The goal of the RFE is to support MicroProfile (MP) Fault tolerance, exposing it as subsystem integrating MP Fault tolerance SmallRye implementation. > Smallrye project homepage: https://github.com/smallrye/smallrye-fault-tolerance (contains link to eclipse spec homepage, tck and implementation) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12590) Integrate MP Fault Tolerance 2.0

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12590?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12590: ---------------------------------- Summary: Integrate MP Fault Tolerance 2.0 (was: Integrate MP Fault Tolerance 2.0 into EAP) > Integrate MP Fault Tolerance 2.0 > -------------------------------- > > Key: WFLY-12590 > URL: https://issues.jboss.org/browse/WFLY-12590 > Project: WildFly > Issue Type: Feature Request > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > The goal of the RFE is to support MicroProfile (MP) Fault tolerance, exposing it as subsystem integrating MP Fault tolerance SmallRye implementation. > Smallrye project homepage: https://github.com/smallrye/smallrye-fault-tolerance (contains link to eclipse spec homepage, tck and implementation) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12590) Integrate MicroProfile Fault Tolerance 2.0

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12590?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12590: ---------------------------------- Summary: Integrate MicroProfile Fault Tolerance 2.0 (was: Integrate MP Fault Tolerance 2.0) > Integrate MicroProfile Fault Tolerance 2.0 > ------------------------------------------ > > Key: WFLY-12590 > URL: https://issues.jboss.org/browse/WFLY-12590 > Project: WildFly > Issue Type: Feature Request > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > The goal of the RFE is to support MicroProfile (MP) Fault tolerance, exposing it as subsystem integrating MP Fault tolerance SmallRye implementation. > Smallrye project homepage: https://github.com/smallrye/smallrye-fault-tolerance (contains link to eclipse spec homepage, tck and implementation) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 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 September 2019