July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3966) JwtValidator jku and kid header parameters

by Martin Mazanek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3966?page=com.atlassian.jira.plugi... ] Martin Mazanek moved ELY-1610 to WFCORE-3966: --------------------------------------------- Project: WildFly Core (was: WildFly Elytron) Key: WFCORE-3966 (was: ELY-1610) > JwtValidator jku and kid header parameters > ------------------------------------------ > > Key: WFCORE-3966 > URL: https://issues.jboss.org/browse/WFCORE-3966 > Project: WildFly Core > Issue Type: Enhancement > Reporter: Martin Mazanek > Assignee: Martin Mazanek > Priority: Minor > > JwtValidator implementation is missing some useful header parameters: kid for supporting multiple keys and jku for using remotes as a source of public keys. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ELY-1610) JwtValidator jku and kid header parameters

by Martin Mazanek (JIRA)

Martin Mazanek created ELY-1610: ----------------------------------- Summary: JwtValidator jku and kid header parameters Key: ELY-1610 URL: https://issues.jboss.org/browse/ELY-1610 Project: WildFly Elytron Issue Type: Enhancement Reporter: Martin Mazanek Assignee: Martin Mazanek Priority: Minor JwtValidator implementation is missing some useful header parameters: kid for supporting multiple keys and jku for using remotes as a source of public keys. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10708) (7.1.z) Upgrade jboss-vfs to 3.2.13.Final

by Tomas Hofman (JIRA)

Tomas Hofman created WFLY-10708: ----------------------------------- Summary: (7.1.z) Upgrade jboss-vfs to 3.2.13.Final Key: WFLY-10708 URL: https://issues.jboss.org/browse/WFLY-10708 Project: WildFly Issue Type: Component Upgrade Components: VFS Reporter: Tomas Hofman -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10707) Upgrade jboss-vfs to 3.2.13.Final

by Tomas Hofman (JIRA)

Tomas Hofman created WFLY-10707: ----------------------------------- Summary: Upgrade jboss-vfs to 3.2.13.Final Key: WFLY-10707 URL: https://issues.jboss.org/browse/WFLY-10707 Project: WildFly Issue Type: Component Upgrade Components: VFS Reporter: Tomas Hofman -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10706) URL.getContent() returns VirtualFile instead of ImageProducer

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFLY-10706?page=com.atlassian.jira.plugin... ] Tomas Hofman moved JBEAP-15071 to WFLY-10706: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-10706 (was: JBEAP-15071) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: VFS (was: VFS) Affects Version/s: 13.0.0.Final (was: 7.1.3.GA) > URL.getContent() returns VirtualFile instead of ImageProducer > ------------------------------------------------------------- > > Key: WFLY-10706 > URL: https://issues.jboss.org/browse/WFLY-10706 > Project: WildFly > Issue Type: Bug > Components: VFS > Affects Versions: 13.0.0.Final > Environment: Windows XP > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > URL.getContent() behaves differently within JBoss than it does in a normal JVM. In our case, when a jar is used in a normal JVM, URL.getContent() returns an ImageProducer. When the same jar is used from within JBoss, a VirtualFile is returned which then causes a ClassCastException. > Note: This worked fine in JBoss 4.2.3.GA. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBVFS-206) URL.getContent() returns VirtualFile instead of ImageProducer

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/JBVFS-206?page=com.atlassian.jira.plugin.... ] Tomas Hofman updated JBVFS-206: ------------------------------- Summary: URL.getContent() returns VirtualFile instead of ImageProducer (was: [GSS](7.1.z) URL.getContent() returns VirtualFile instead of ImageProducer) > URL.getContent() returns VirtualFile instead of ImageProducer > ------------------------------------------------------------- > > Key: JBVFS-206 > URL: https://issues.jboss.org/browse/JBVFS-206 > Project: JBoss VFS > Issue Type: Bug > Affects Versions: 3.2.12.Final > Environment: Windows XP > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > URL.getContent() behaves differently within JBoss than it does in a normal JVM. In our case, when a jar is used in a normal JVM, URL.getContent() returns an ImageProducer. When the same jar is used from within JBoss, a VirtualFile is returned which then causes a ClassCastException. > Note: This worked fine in JBoss 4.2.3.GA. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBVFS-206) [GSS](7.1.z) URL.getContent() returns VirtualFile instead of ImageProducer

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/JBVFS-206?page=com.atlassian.jira.plugin.... ] Tomas Hofman commented on JBVFS-206: ------------------------------------ master PR: https://github.com/jbossas/jboss-vfs/pull/28 3.2 PR: https://github.com/jbossas/jboss-vfs/pull/29 > [GSS](7.1.z) URL.getContent() returns VirtualFile instead of ImageProducer > -------------------------------------------------------------------------- > > Key: JBVFS-206 > URL: https://issues.jboss.org/browse/JBVFS-206 > Project: JBoss VFS > Issue Type: Bug > Affects Versions: 3.2.12.Final > Environment: Windows XP > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > URL.getContent() behaves differently within JBoss than it does in a normal JVM. In our case, when a jar is used in a normal JVM, URL.getContent() returns an ImageProducer. When the same jar is used from within JBoss, a VirtualFile is returned which then causes a ClassCastException. > Note: This worked fine in JBoss 4.2.3.GA. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2743) [DMN Designer] Download as toolbar button

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2743?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2743: ------------------------------------- [~manstis] [~roger600] Hi, got another idea, rename all to "Download source", "Download plain source" ...., however sure, explicit extensions (DMN, BPMN) are definitely better, just in case hard to fix. > [DMN Designer] Download as toolbar button > ----------------------------------------- > > Key: DROOLS-2743 > URL: https://issues.jboss.org/browse/DROOLS-2743 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > > The stunner based designers contain "Download as" button. The problem of this button for DMN Designer is that it contains option "Download as BPMN" instead of "Download as DMN". -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFWIP-61) Description of the elements in newly introduced microprofile-config-smallrye subsystem could be more informative

by Michal Jurc (JIRA)

[ https://issues.jboss.org/browse/WFWIP-61?page=com.atlassian.jira.plugin.s... ] Michal Jurc commented on WFWIP-61: ---------------------------------- [~jmesnil], [~jstourac]: My suggestion would be to keep consistent with the spec, for example to use [ConfigSource|https://github.com/eclipse/microprofile-config/blob/master/a...] and [ConfigSourceProvider|https://github.com/eclipse/microprofile-config/blob/...] JavaDoc description. WDYT? > Description of the elements in newly introduced microprofile-config-smallrye subsystem could be more informative > ---------------------------------------------------------------------------------------------------------------- > > Key: WFWIP-61 > URL: https://issues.jboss.org/browse/WFWIP-61 > Project: WildFly WIP > Issue Type: Bug > Components: MP Config > Environment: git@github.com:jmesnil/wildfly.git:WFLY-10522_microprofile-config-smallrye_extension > Reporter: Jan Stourac > Assignee: Jeff Mesnil > > Description of the elements in /subsystem=microprofile-config-smallrye could give more info, so far it states just: > {code:title=/subsystem=microprofile-config-smallrye:read-resource-description} > "config-source-provider" => { > "description" => "Config Source Provider", > "config-source" => { > "description" => "Config Source", > {code} > Maybe adding also information about what those elements are used for could improve user experience, e.g.: > {code} > "config-source-provider" => { > "description" => "Config Source Provider can be used to register own implementation for config-source with your specific way of configuration", > "config-source" => { > "description" => "Config Source contains configured configuration sources that are utilized for configuration", > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8954) Wildfly 10 with eclipselink Onscucess observer gets stale entity

by Tomas Kraus (JIRA)

[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ] Tomas Kraus commented on WFLY-8954: ----------------------------------- Hi Scott, my changes are in master branch only and they will be available in EclipseLink 3.0.0. https://bugs.eclipse.org/bugs/attachment.cgi?id=271794&action=diff will tell you what has to be modified in server platform and related transaction controller. I alredy made those changes in JbossPlatform which is part of EclipseLink. > Wildfly 10 with eclipselink Onscucess observer gets stale entity > ---------------------------------------------------------------- > > Key: WFLY-8954 > URL: https://issues.jboss.org/browse/WFLY-8954 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.0.0.Final > Reporter: Nuno Godinho de Matos > Assignee: Scott Marlow > > Hi, > In widlfly there seems to be an important issue concerning CDI events and observing these events during onsuccess. At least while using eclipselink. > When using wildfly 10.0.0.Final together with eclipselink, if an application modifies an entity A, fires an event stating entity A has been modified, and an observer consumes this event during transaction success. > Then the observer will be working with stale entities that do not reflect the modifications done to the entity. > A sample application for this issue is available in: > https://github.com/99sono/wildfly10-observe-on-success-stale-entity > The widlfly configuration xml for the sample application, is available in the application itself, as can be seen in the readme documentation. > Many thanks for taking a look. > Kindest regards. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2018