October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-864) NameNotFoundException due to policyRegistration -- service jboss.naming.context.java.policyRegistration

by Philippe Marschall (JIRA)

[ https://issues.jboss.org/browse/SECURITY-864?page=com.atlassian.jira.plug... ] Philippe Marschall commented on SECURITY-864: --------------------------------------------- @c2swapnil the work around has been working fine for us for quite some time now > NameNotFoundException due to policyRegistration -- service jboss.naming.context.java.policyRegistration > ------------------------------------------------------------------------------------------------------- > > Key: SECURITY-864 > URL: https://issues.jboss.org/browse/SECURITY-864 > Project: PicketBox > Issue Type: Bug > Components: PicketBox > Reporter: Chao Wang > Assignee: Stefan Guilhen > > "NameNotFoundException due to policyRegistration -- service jboss.naming.context.java.policyRegistration" is recorded in server.log during quickstart example run by changing log level: > {noformat} > <logger category="org.jboss.as.security"> > <level name="TRACE"/> > </logger> > <logger category="org.jboss.security"> > <level name="TRACE"/> > </logger> > {noformat} > See detailed description in community discussion [#907134|https://developer.jboss.org/message/907134] > I choose Jira component picketbox since the exception is titled as "PBOX000293: Exception caught: javax.naming.NameNotFoundException" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9439) Datasources are registered as singletons

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9439?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-9439: ---------------------------------------- That's unfortunately the way it works. Very early one we made the mistake of not coming up with some unambiguous way to distinguish the '*' in non-singleton resource type name from the '*' used in wildcard read ops, where it means show me all addresses that match this pattern. The result is the '*' is treated as meaning "show me all addresses that match this pattern". > Datasources are registered as singletons > ---------------------------------------- > > Key: WFLY-9439 > URL: https://issues.jboss.org/browse/WFLY-9439 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Michal Petrov > Assignee: Stefano Maestri > > {code} > /subsystem=datasources:read-children-types(include-singletons) > {code} > returns this > {code} > { > "outcome" => "success", > "result" => [ > "data-source", > "data-source=ExampleDS", > "jdbc-driver", > "xa-data-source" > ] > } > {code} > This happens for any (xa-)data-source, not just the default one. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1766) Useless ClassLoader cloning during kieproject compilation

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1766?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-1766. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/802da1f78 > Useless ClassLoader cloning during kieproject compilation > --------------------------------------------------------- > > Key: DROOLS-1766 > URL: https://issues.jboss.org/browse/DROOLS-1766 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1398) Verify public API signatures during build.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1398?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1398: --------------------------------------- Some other options mentioned in HipChat [3:24 PM] Tomaz Cerar: other tool i know about is https://lvc.github.io/japi-compliance-checker/ [3:24 PM] Tomaz Cerar: but it doesn't have any maven plugins [3:25 PM] Tomaz Cerar: you can get nice reports [3:25 PM] Tomaz Cerar: https://abi-laboratory.pro/java/tracker/compat_report/slf4j/1.5.11/1.6.0/.... [3:25 PM] Tomaz Cerar: but it is much more manual work [3:27 PM] Tomaz Cerar: there is some comercial tooling [3:27 PM] Tomaz Cerar: but they come with *lots* more stuff [3:28 PM] Tomaz Cerar: so just BAPI diff is rarely avalible as standalone tool [3:31 PM] Tomaz Cerar: @DarranLofthouse JT harness (from openjdk toolkit) also has signature check [3:31 PM] Tomaz Cerar: https://wiki.openjdk.java.net/display/CodeTools/JT+Harness [3:32 PM] Tomaz Cerar: https://wiki.openjdk.java.net/display/CodeTools/sigtest > Verify public API signatures during build. > ------------------------------------------ > > Key: ELY-1398 > URL: https://issues.jboss.org/browse/ELY-1398 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.6.CR1, 1.2.0.Beta7 > > > This task will involve adding the ability to generate a signature for a specific version and verify them during the build - we only want this to apply to packages identified as public API. > Animal Sniffer seems a good candidate http://www.mojohaus.org/animal-sniffer/ > Generation of a signature we can likely make on-demand as we only really need that at the point we tag a release. > We would definitely want checking to run for CI PR processing but can decide if all builds should be checking with an option to disable or all disabled with an option to enable. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-864) NameNotFoundException due to policyRegistration -- service jboss.naming.context.java.policyRegistration

by c2swapnil c2swapnil (JIRA)

[ https://issues.jboss.org/browse/SECURITY-864?page=com.atlassian.jira.plug... ] c2swapnil c2swapnil commented on SECURITY-864: ---------------------------------------------- Any solution to this > NameNotFoundException due to policyRegistration -- service jboss.naming.context.java.policyRegistration > ------------------------------------------------------------------------------------------------------- > > Key: SECURITY-864 > URL: https://issues.jboss.org/browse/SECURITY-864 > Project: PicketBox > Issue Type: Bug > Components: PicketBox > Reporter: Chao Wang > Assignee: Stefan Guilhen > > "NameNotFoundException due to policyRegistration -- service jboss.naming.context.java.policyRegistration" is recorded in server.log during quickstart example run by changing log level: > {noformat} > <logger category="org.jboss.as.security"> > <level name="TRACE"/> > </logger> > <logger category="org.jboss.security"> > <level name="TRACE"/> > </logger> > {noformat} > See detailed description in community discussion [#907134|https://developer.jboss.org/message/907134] > I choose Jira component picketbox since the exception is titled as "PBOX000293: Exception caught: javax.naming.NameNotFoundException" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1766) Useless ClassLoader cloning during kieproject compilation

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1766: ----------------------------------- Summary: Useless ClassLoader cloning during kieproject compilation Key: DROOLS-1766 URL: https://issues.jboss.org/browse/DROOLS-1766 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1765) Move FEEL type annotation to API

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-1765: -------------------------------------- Summary: Move FEEL type annotation to API Key: DROOLS-1765 URL: https://issues.jboss.org/browse/DROOLS-1765 Project: Drools Issue Type: Task Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1398) Verify public API signatures during build.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1398?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1398: --------------------------------------- Whilst animal sniffer is easy to use to generate a signature the verification seems to be that API outside of the signature has not been used rather than checking backwards compatibility. > Verify public API signatures during build. > ------------------------------------------ > > Key: ELY-1398 > URL: https://issues.jboss.org/browse/ELY-1398 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.6.CR1, 1.2.0.Beta7 > > > This task will involve adding the ability to generate a signature for a specific version and verify them during the build - we only want this to apply to packages identified as public API. > Animal Sniffer seems a good candidate http://www.mojohaus.org/animal-sniffer/ > Generation of a signature we can likely make on-demand as we only really need that at the point we tag a release. > We would definitely want checking to run for CI PR processing but can decide if all builds should be checking with an option to disable or all disabled with an option to enable. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

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

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-8954: ------------------------------------ I will look soon, thanks for your patience! > 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 > Fix For: 12.0.0.Alpha1 > > > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1404) SASL property com.sun.security.sasl.digest.utf8 does not behave as default when its default value is explicitely configured

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/ELY-1404?page=com.atlassian.jira.plugin.s... ] Yeray Borges moved JBEAP-13514 to ELY-1404: ------------------------------------------- Project: WildFly Elytron (was: JBoss Enterprise Application Platform) Key: ELY-1404 (was: JBEAP-13514) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: (was: Security) Affects Version/s: 1.2.0.Beta6 1.1.5.Final (was: 7.1.0.CR2) > SASL property com.sun.security.sasl.digest.utf8 does not behave as default when its default value is explicitely configured > ---------------------------------------------------------------------------------------------------------------------------- > > Key: ELY-1404 > URL: https://issues.jboss.org/browse/ELY-1404 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.2.0.Beta6, 1.1.5.Final > Reporter: Yeray Borges > Assignee: Yeray Borges > > SASL property *com.sun.security.sasl.digest.utf8* does not behave as default when its default value is explicitely configured. > When we ommit this explicit property setting then everything is fine. > This property is described here [1] and *true* is default value. Property is defined in wildfly-core project org.wildfly.security.sasl.WildFlySasl.USE_UTF8. > Here is how to set it [2]. > Please check Steps to Reproduce, there is how to update test. > [1] https://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_jboss_en... > [2] https://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_jboss_en... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 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 October 2017