July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12299) More fine grain dependency for galleon basic layers

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12299?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12299: ----------------------------------------- bstansberry 8 days ago Member @jfdenise A question then would be whether we would provide other layers that depend on transactions but which don't also involve an a servlet container. Not just whether they might exist in theory, but whether we would provide them. If we don't provide them, then the user who would want that would be somehow doing fairly complex provisioning config manipulation anyway, and excluding the servlet container / undertow parts would just be another part of that. Not unreasonable. So what layer that would use transactions would we provide that doesn't have an HTTP endpoint? It would have to be something that involves some other remote access protocol (e.g. native remoting or IIOP or QPID.) Or something that doesn't involve listening for outside connections at all. For the 'other remote access protocol' case, I don't see us providing such a layer. Our standard configs aim toward having a single HTTP socket for application use with HTTP Upgrade used if needed. The "doesn't involve listening for outside connections at all" case is valid though. A server set up for batch jobs. Or a server that runs MDBs, where the messages processed by the MDB are pulled from a remote broker over a client socket, not a server socket. > More fine grain dependency for galleon basic layers > --------------------------------------------------- > > Key: WFLY-12299 > URL: https://issues.jboss.org/browse/WFLY-12299 > Project: WildFly > Issue Type: Enhancement > Components: Build System > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Major > > Having basic layers to only depend on the layers (and features) they do require will offer more flexibility than depending on web-server layer. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12299) More fine grain dependency for galleon basic layers

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12299?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12299: ----------------------------------------- bstansberry 10 days ago Member @jfdenise Does this need to depend on this aggregation layer, as opposed to specific detail layers from servlet f-p? There are a few in this category. Here's what depends on web-server: {code} $ git grep "layer name=\"web-server\"" galleon-pack/src/main/resources/layers/standalone/cdi/layer-spec.xml: <layer name="web-server"/> galleon-pack/src/main/resources/layers/standalone/h2-database/layer-spec.xml: <layer name="web-server"/> galleon-pack/src/main/resources/layers/standalone/jaxrs/layer-spec.xml: <layer name="web-server"/> galleon-pack/src/main/resources/layers/standalone/jms-activemq/layer-spec.xml: <layer name="web-server"/> galleon-pack/src/main/resources/layers/standalone/jpa/layer-spec.xml: <layer name="web-server"/> galleon-pack/src/main/resources/layers/standalone/observability/layer-spec.xml: <layer name="web-server"/> galleon-pack/src/main/resources/layers/standalone/resource-adapters/layer-spec.xml: <layer name="web-server"/> {code} Obviously jaxrs needs web-server. The others it's less obvious that HTTP is required. The advantage of doing it this way is for a servlet app with jpa support you can just say "jpa" instead of "web-server, jpa". And perhaps for compatibility reasons we have to leave it that way for the existing layers. But that doesn't apply to this 'transactions' one, since it is new. Apologies if we've discussed this and I've forgotten. The wildfly-dev "Wildfly layers" doesn't have any discussion, other than your initial post that stated it would work this way. > More fine grain dependency for galleon basic layers > --------------------------------------------------- > > Key: WFLY-12299 > URL: https://issues.jboss.org/browse/WFLY-12299 > Project: WildFly > Issue Type: Enhancement > Components: Build System > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Major > > Having basic layers to only depend on the layers (and features) they do require will offer more flexibility than depending on web-server layer. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12299) More fine grain dependency for galleon basic layers

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12299?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12299: ----------------------------------------- jfdenise 10 days ago Author Member The idea was that web-server would be the minimal layer any "full feature (cdi, ...)" would require. Making the layer "runnable" and reachable from http. transactions only requires elytron, so we could define the layer to only depend on elytron, but doing so it would have to be combined with other full features (if used outside cloud-profile or other layers that depend on it). transaction is perhaps not a feature you add alone in your config, it is a dependency for top level layers. I agree that having it depend on elytron should be sufficient. It should be still runnable and you could combine it with smaller layers. I would be ready to revisit them all and change documentation. They are not yet supported so changes can occur. > More fine grain dependency for galleon basic layers > --------------------------------------------------- > > Key: WFLY-12299 > URL: https://issues.jboss.org/browse/WFLY-12299 > Project: WildFly > Issue Type: Enhancement > Components: Build System > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Major > > Having basic layers to only depend on the layers (and features) they do require will offer more flexibility than depending on web-server layer. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12299) More fine grain dependency for galleon basic layers

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12299?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12299: ----------------------------------------- I'm going to copy the discussion between myself and Jean-Francois on https://github.com/wildfly/wildfly/pull/12417 into comments here so we can carry on the conversation and others can read it here. > More fine grain dependency for galleon basic layers > --------------------------------------------------- > > Key: WFLY-12299 > URL: https://issues.jboss.org/browse/WFLY-12299 > Project: WildFly > Issue Type: Enhancement > Components: Build System > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Major > > Having basic layers to only depend on the layers (and features) they do require will offer more flexibility than depending on web-server layer. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12269) Define a galleon layer for transactions

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12269?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12269: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/12417 > Define a galleon layer for transactions > --------------------------------------- > > Key: WFLY-12269 > URL: https://issues.jboss.org/browse/WFLY-12269 > Project: WildFly > Issue Type: Enhancement > Components: Build System > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Major > Fix For: 18.0.0.Beta1 > > > This layer would add some benefits: > 1) Avoid duplication of permissions we are observing with feature-groups in a cloud-profile context. > 2) Allow extension in other context. For example, transactions layer could be redefined in order to enable tx-recovery (add node-identifier=${jboss.node.name} and recovery-listener=true attributes added to the subsystem) and package needed JBOSS modules (eg: tooling for tx-recovery). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-11786) Wildfly 15 documentation missing images

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11786?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-11786: ----------------------------------------- I added the images to the WildFly 17 docs. They are also in master so when we generate 18 docs they will be there. > Wildfly 15 documentation missing images > --------------------------------------- > > Key: WFLY-11786 > URL: https://issues.jboss.org/browse/WFLY-11786 > Project: WildFly > Issue Type: Bug > Components: Documentation > Affects Versions: 15.0.0.Final > Reporter: Marco Rossi > Priority: Major > Fix For: 17.0.1.Final, 18.0.0.Beta1 > > Attachments: Screenshot_2019-02-27 Getting Started Developing Applications Guide.png > > > In getting started guide for Wildfly 15 some images are missing, for example reference to: http://docs.wildfly.org/15/images/gfx/Eclipse_Helloworld_Deploy_1.jpg return 404 not found > (see attached image) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12175) Broken links in "Description of the Management Model"

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12175?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12175: ------------------------------------ Fix Version/s: 17.0.1.Final > Broken links in "Description of the Management Model" > ----------------------------------------------------- > > Key: WFLY-12175 > URL: https://issues.jboss.org/browse/WFLY-12175 > Project: WildFly > Issue Type: Bug > Components: Documentation, Management > Affects Versions: 12.0.0.Final, 13.0.0.Final, 14.0.0.Final, 15.0.0.Final, 16.0.0.Final > Reporter: Robert Johnson > Assignee: Yeray Borges > Priority: Minor > Fix For: 17.0.1.Final, 18.0.0.Beta1 > > > In the section "http://docs.wildfly.org/16/Admin_Guide.html#Description_of_the_Management...", the links on the following text strings return 404 errors when clicked: > * Global operations > * Management Resource -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-11786) Wildfly 15 documentation missing images

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11786?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-11786: ------------------------------------ Fix Version/s: 17.0.1.Final > Wildfly 15 documentation missing images > --------------------------------------- > > Key: WFLY-11786 > URL: https://issues.jboss.org/browse/WFLY-11786 > Project: WildFly > Issue Type: Bug > Components: Documentation > Affects Versions: 15.0.0.Final > Reporter: Marco Rossi > Priority: Major > Fix For: 17.0.1.Final, 18.0.0.Beta1 > > Attachments: Screenshot_2019-02-27 Getting Started Developing Applications Guide.png > > > In getting started guide for Wildfly 15 some images are missing, for example reference to: http://docs.wildfly.org/15/images/gfx/Eclipse_Helloworld_Deploy_1.jpg return 404 not found > (see attached image) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4570) PathAddress.toCLIStyleString() can output badly formatted values

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFCORE-4570?page=com.atlassian.jira.plugi... ] Kabir Khan commented on WFCORE-4570: ------------------------------------ I think what confuses it is the appearance of "/" or "=" in the value > PathAddress.toCLIStyleString() can output badly formatted values > ---------------------------------------------------------------- > > Key: WFCORE-4570 > URL: https://issues.jboss.org/browse/WFCORE-4570 > Project: WildFly Core > Issue Type: Bug > Reporter: Kabir Khan > Assignee: Jeff Mesnil > Priority: Major > > Trying PathAddress.toCLIStyleString() on the output operations from https://github.com/keycloak/keycloak/blob/master/adapters/oidc/wildfly/wi... I end up with addresses with strange characters like > {code} > /subsystem=keycloak/secure-deployment=web-console/redirect-rewrite-rule=^/wsmaster/api/(.*)$ > {code} > If I try to add a system property with the same name in CLI I get an error, e.g.: > {code} > [standalone@embedded /] /system-property=^/wsmaster/api/(.*)$:add(value=xyx) > Node path format is wrong around 'wsmaster' (index=19). > {code} > It seems that these need to be quoted and it all works > {code} > [standalone@embedded /] /system-property="^/wsmaster/api/(.*)$":add(value=xyx) > {"outcome" => "success"} > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-835) Include operator-sdk on kiali-build slave image

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-835: --------------------------------------------- Summary: Include operator-sdk on kiali-build slave image Key: SWSQE-835 URL: https://issues.jboss.org/browse/SWSQE-835 Project: Kiali QE Issue Type: Dev Task Reporter: Guilherme Baufaker Rêgo Assignee: Guilherme Baufaker Rêgo Operator-SDK needs to be included on the kiali-build image -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

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 July 2019