July 2019 - jboss-jira - Jboss List Archives

[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 updated WFCORE-4570: ------------------------------- Summary: PathAddress.toCLIStyleString() can output badly formatted values (was: PathAddress.toCLIStyleString() should quote the values) > 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] (WFCORE-4570) PathAddress.toCLIStyleString() should quote the values

by Kabir Khan (Jira)

Kabir Khan created WFCORE-4570: ---------------------------------- Summary: PathAddress.toCLIStyleString() should quote the values Key: WFCORE-4570 URL: https://issues.jboss.org/browse/WFCORE-4570 Project: WildFly Core Issue Type: Bug Reporter: Kabir Khan Assignee: Jeff Mesnil 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] (WFLY-12303) Hibernate integration should set AvailableSettings.CLASSLOADERS instead of AvailableSettings.APP_CLASSLOADER

by Scott Marlow (Jira)

Scott Marlow created WFLY-12303: ----------------------------------- Summary: Hibernate integration should set AvailableSettings.CLASSLOADERS instead of AvailableSettings.APP_CLASSLOADER Key: WFLY-12303 URL: https://issues.jboss.org/browse/WFLY-12303 Project: WildFly Issue Type: Task Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Since Hibernate ORM 5.0, AvailableSettings.CLASSLOADERS has been available to to define a {@link java.util.Collection} of the {@link ClassLoader} instances Hibernate should use for class-loading and resource-lookups. I think that we could switch to using that instead of the: {code} properties.put(AvailableSettings.APP_CLASSLOADER, pu.getClassLoader()); {code} that we do now. Also see the code to be changed [https://github.com/wildfly/wildfly/blob/master/jpa/hibernate5_3/src/main/...], since APP_CLASSLOADER is deprecated and will be dropped at some point, so we should start preparing for that. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12303) Hibernate integration should set AvailableSettings.CLASSLOADERS instead of deprecated AvailableSettings.APP_CLASSLOADER

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-12303?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-12303: -------------------------------- Summary: Hibernate integration should set AvailableSettings.CLASSLOADERS instead of deprecated AvailableSettings.APP_CLASSLOADER (was: Hibernate integration should set AvailableSettings.CLASSLOADERS instead of AvailableSettings.APP_CLASSLOADER) > Hibernate integration should set AvailableSettings.CLASSLOADERS instead of deprecated AvailableSettings.APP_CLASSLOADER > ----------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12303 > URL: https://issues.jboss.org/browse/WFLY-12303 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > > Since Hibernate ORM 5.0, AvailableSettings.CLASSLOADERS has been available to to define a {@link java.util.Collection} of the {@link ClassLoader} instances Hibernate should use for class-loading and resource-lookups. > I think that we could switch to using that instead of the: > {code} > properties.put(AvailableSettings.APP_CLASSLOADER, pu.getClassLoader()); > {code} > that we do now. > Also see the code to be changed [https://github.com/wildfly/wildfly/blob/master/jpa/hibernate5_3/src/main/...], since APP_CLASSLOADER is deprecated and will be dropped at some point, so we should start preparing for that. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-834) Jenkins Slave Base needs to be updated for upgrade packages.

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-834?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo commented on SWSQE-834: ----------------------------------------------- https://quay.io/repository/openshift/origin-jenkins-agent-base/manifest/s... Actually git still the same version :( > Jenkins Slave Base needs to be updated for upgrade packages. > ------------------------------------------------------------ > > Key: SWSQE-834 > URL: https://issues.jboss.org/browse/SWSQE-834 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > Priority: Critical > > [~fbrychta] Jenkins Slave Base Centos7 available on (https://hub.docker.com/r/openshift/jenkins-slave-base-centos7/) is now considered deprecated. > All the new ones are on > I tried two simple commands that would work on git > Expected: > {code:bash} > git clone https://github.com/kiali/kiali-ui.git kiali-ui > cd kiali-ui > git fetch origin pull/1322/head:1322 > remote: Enumerating objects: 1, done. > remote: Counting objects: 100% (1/1), done. > remote: Total 1 (delta 0), reused 1 (delta 0), pack-reused 0 > Unpacking objects: 100% (1/1), done. > From https://github.com/kiali/kiali-ui > * [new ref] refs/pull/1322/head -> 1322 > {code} > Actual: > {code:bash} > git fetch origin pull/1322/head:1322 > fatal: Couldn't find remote ref pull/1322/head > Unexpected end of command stream > {code} > I think we migrate to new images that would solve our problem. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-834) Jenkins Slave Base needs to be updated for upgrade packages.

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-834?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-834: ------------------------------------------ Description: [~fbrychta] Jenkins Slave Base Centos7 available on (https://hub.docker.com/r/openshift/jenkins-slave-base-centos7/) is now considered deprecated. All the new ones are on I tried two simple commands that would work on git Expected: {code:bash} git clone https://github.com/kiali/kiali-ui.git kiali-ui cd kiali-ui git fetch origin pull/1322/head:1322 remote: Enumerating objects: 1, done. remote: Counting objects: 100% (1/1), done. remote: Total 1 (delta 0), reused 1 (delta 0), pack-reused 0 Unpacking objects: 100% (1/1), done. >From https://github.com/kiali/kiali-ui * [new ref] refs/pull/1322/head -> 1322 {code} Actual: {code:bash} git fetch origin pull/1322/head:1322 fatal: Couldn't find remote ref pull/1322/head Unexpected end of command stream {code} I think we migrate to new images that would solve our problem. was: [~fbrychta] Jenkins Slave Base Centos7 available on (https://hub.docker.com/r/openshift/jenkins-slave-base-centos7/) is now considered deprecated. I tried two simple commands that would work on git Expected: {code:bash} git clone https://github.com/kiali/kiali-ui.git kiali-ui cd kiali-ui git fetch origin pull/1322/head:1322 remote: Enumerating objects: 1, done. remote: Counting objects: 100% (1/1), done. remote: Total 1 (delta 0), reused 1 (delta 0), pack-reused 0 Unpacking objects: 100% (1/1), done. >From https://github.com/kiali/kiali-ui * [new ref] refs/pull/1322/head -> 1322 {code} Actual: {code:bash} git fetch origin pull/1322/head:1322 fatal: Couldn't find remote ref pull/1322/head Unexpected end of command stream {code} I think we use new-images that would solve our problem. > Jenkins Slave Base needs to be updated for upgrade packages. > ------------------------------------------------------------ > > Key: SWSQE-834 > URL: https://issues.jboss.org/browse/SWSQE-834 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > Priority: Critical > > [~fbrychta] Jenkins Slave Base Centos7 available on (https://hub.docker.com/r/openshift/jenkins-slave-base-centos7/) is now considered deprecated. > All the new ones are on > I tried two simple commands that would work on git > Expected: > {code:bash} > git clone https://github.com/kiali/kiali-ui.git kiali-ui > cd kiali-ui > git fetch origin pull/1322/head:1322 > remote: Enumerating objects: 1, done. > remote: Counting objects: 100% (1/1), done. > remote: Total 1 (delta 0), reused 1 (delta 0), pack-reused 0 > Unpacking objects: 100% (1/1), done. > From https://github.com/kiali/kiali-ui > * [new ref] refs/pull/1322/head -> 1322 > {code} > Actual: > {code:bash} > git fetch origin pull/1322/head:1322 > fatal: Couldn't find remote ref pull/1322/head > Unexpected end of command stream > {code} > I think we migrate to new images that would solve our problem. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12302) CallerPrincipal will be anonymous (randomly) if EJB2 is called

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created WFLY-12302: --------------------------------------- Summary: CallerPrincipal will be anonymous (randomly) if EJB2 is called Key: WFLY-12302 URL: https://issues.jboss.org/browse/WFLY-12302 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 17.0.1.Final Reporter: Wolf-Dieter Fink Assignee: Cheng Fang An EJB application which call an EJB2 SLSB will fail (randomly) to show the correct user if getCallerPrincipal is used inside. Also the roles are not set. The EJB2 Bean is secured by ejb-jar.xml so it is not expected that it will be called without role <assembly-descriptor> <method-permission> <role-name>testRole</role-name> <method> <ejb-name>simpleejb.server.SomeEJB2Bean</ejb-name> <method-intf>Remote</method-intf> <method-name>*</method-name> </method> </method-permission> This error is constant seen if the server is up and running but each restart will change the behaviour randomly. Note that an EJB3 bean of the same EAR file will work always correctly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12301) CallerPrincipal will be anonymous (randomly) if EJB2 is called

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created WFLY-12301: --------------------------------------- Summary: CallerPrincipal will be anonymous (randomly) if EJB2 is called Key: WFLY-12301 URL: https://issues.jboss.org/browse/WFLY-12301 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 17.0.1.Final Reporter: Wolf-Dieter Fink Assignee: Cheng Fang Attachments: reproducer.zip An EJB application which call an EJB2 SLSB will fail (randomly) to show the correct user if getCallerPrincipal is used inside. Also the roles are not set. The EJB2 Bean is secured by ejb-jar.xml so it is not expected that it will be called without role <assembly-descriptor> <method-permission> <role-name>testRole</role-name> <method> <ejb-name>simpleejb.server.SomeEJB2Bean</ejb-name> <method-intf>Remote</method-intf> <method-name>*</method-name> </method> </method-permission> This error is constant seen if the server is up and running but each restart will change the behaviour randomly. Note that an EJB3 bean of the same EAR file will work always correctly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-834) Jenkins Slave Base needs to be updated for upgrade packages.

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-834: --------------------------------------------- Summary: Jenkins Slave Base needs to be updated for upgrade packages. Key: SWSQE-834 URL: https://issues.jboss.org/browse/SWSQE-834 Project: Kiali QE Issue Type: Bug Reporter: Guilherme Baufaker Rêgo Assignee: Filip Brychta [~fbrychta] Jenkins Slave Base Centos7 available on (https://hub.docker.com/r/openshift/jenkins-slave-base-centos7/) is now considered deprecated. I tried two simple commands that would work on git Expected: {code:bash} git clone https://github.com/kiali/kiali-ui.git kiali-ui cd kiali-ui git fetch origin pull/1322/head:1322 remote: Enumerating objects: 1, done. remote: Counting objects: 100% (1/1), done. remote: Total 1 (delta 0), reused 1 (delta 0), pack-reused 0 Unpacking objects: 100% (1/1), done. >From https://github.com/kiali/kiali-ui * [new ref] refs/pull/1322/head -> 1322 {code} Actual: {code:bash} git fetch origin pull/1322/head:1322 fatal: Couldn't find remote ref pull/1322/head Unexpected end of command stream {code} I think we use new-images that would solve our problem. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4342) Using BigDecimal with From Accumulate causes an "Error: argument type mismatch"

by Karina Varela (Jira)

[ https://issues.jboss.org/browse/DROOLS-4342?page=com.atlassian.jira.plugi... ] Karina Varela moved RHPAM-2270 to DROOLS-4342: ---------------------------------------------- Project: Drools (was: Red Hat Process Automation Manager) Key: DROOLS-4342 (was: RHPAM-2270) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Component/s: kie server (was: Kie-Server) QE Status: NEW > Using BigDecimal with From Accumulate causes an "Error: argument type mismatch" > ------------------------------------------------------------------------------- > > Key: DROOLS-4342 > URL: https://issues.jboss.org/browse/DROOLS-4342 > Project: Drools > Issue Type: Bug > Components: kie server > Environment: Red Hat Process Automation Manager (RHPAM) 7.2.0 > Reporter: Rodrigo Ribeiro > Assignee: Maciej Swiderski > Priority: Major > Labels: BigDecimal, DRL, bigdecimal, drl, kie-server, rhpam, rule > Attachments: reproducer-02425606.zip, request.json, testSum.scenario > > > When written a rule that does a sum using ‘from accumulate’. The rule validates successfully. However, when trying to test it, is returned a very generic error message: Error: argument type mismatch. -- 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