March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11891) Add tests that enable JPA entity class bytecode enhancment

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-11891?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-11891: -------------------------------- Description: Pick a few unit tests and add the following settings to enable [entity bytecode enhancement|http://docs.jboss.org/hibernate/orm/5.3/userguide/html_single...]: {code} <property name="hibernate.ejb.use_class_enhancer" value="true"/> <property name="hibernate.enhancer.enableDirtyTracking" value="true"/> <property name="hibernate.enhancer.enableLazyInitialization" value="true"/> <property name="hibernate.enhancer.enableAssociationManagement" value="true"/> {code} was: Pick a few unit tests and add the following settings to enable entity bytecode enhancement: {code} <property name="hibernate.ejb.use_class_enhancer" value="true"/> <property name="hibernate.enhancer.enableDirtyTracking" value="true"/> <property name="hibernate.enhancer.enableLazyInitialization" value="true"/> <property name="hibernate.enhancer.enableAssociationManagement" value="true"/> {code} > Add tests that enable JPA entity class bytecode enhancment > ---------------------------------------------------------- > > Key: WFLY-11891 > URL: https://issues.jboss.org/browse/WFLY-11891 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Minor > > Pick a few unit tests and add the following settings to enable [entity bytecode enhancement|http://docs.jboss.org/hibernate/orm/5.3/userguide/html_single...]: > {code} > <property name="hibernate.ejb.use_class_enhancer" value="true"/> > <property name="hibernate.enhancer.enableDirtyTracking" value="true"/> > <property name="hibernate.enhancer.enableLazyInitialization" value="true"/> > <property name="hibernate.enhancer.enableAssociationManagement" value="true"/> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2332) Port of JGroups to Quarkus

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2332?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-2332 at 3/21/19 1:03 PM: --------------------------------------------------------- The tasks that were identified this morning are: * TP.timer needs to be created in TP.start(), _not_ TP.init(). The issue is that other protocols fetch a ref to timer in their init()/start() methods and throw an exception if null * The MulticastSocket() constructor throw an exception on setOption(REUSE_ADDRESS) [IIRC!]. This is probably a GraalVM issue, but we're using TCP for now. Alternatively find a Multicast constructor which doesn't call setOption() on the socket * Diagnostics needs to be disable as it's also using a MulticastSocket * Protocol.setValue()/getValue() uses reflection: either provide setters/getters or list these 2 methods in a reflection JSON file, to be used with {{native-image}}. * JMX needs to be disabled. This was not an issue in the port, as the demo doesn't enable JMX. Probably split the impl out into interfaces and provide a real- and a mock-implementation. * ClassConfigurator.init() loads all classes defined in protocol-ids.xml and magic-map.xml. This is not a showstopper, but increases the size of the executable. * Look into logging (use the JDK logger?) * Next step: port back as many changes as possible and port UPerf as well: measure perf run in native versus Java mode * Include resources (such as log42.xml): https://github.com/oracle/graal/blob/master/substratevm/RESOURCES.md was (Author: belaban): The tasks that were identified this morning are: * TP.timer needs to be created in TP.start(), _not_ TP.init(). The issue is that other protocols fetch a ref to timer in their init()/start() methods and throw an exception if null * The MulticastSocket() constructor throw an exception on setOption(REUSE_ADDRESS) [IIRC!]. This is probably a GraalVM issue, but we're using TCP for now. Alternatively find a Multicast constructor which doesn't call setOption() on the socket * Diagnostics needs to be disable as it's also using a MulticastSocket * Protocol.setValue()/getValue() uses reflection: either provide setters/getters or list these 2 methods in a reflection JSON file, to be used with {{native-image}}. * JMX needs to be disabled. This was not an issue in the port, as the demo doesn't enable JMX. Probably split the impl out into interfaces and provide a real- and a mock-implementation. * ClassConfigurator.init() loads all classes defined in protocol-ids.xml and magic-map.xml. This is not a showstopper, but increases the size of the executable. * Look into logging (use the JDK logger?) * Next step: port back as many changes as possible and port UPerf as well: measure perf run in native versus Java mode > Port of JGroups to Quarkus > -------------------------- > > Key: JGRP-2332 > URL: https://issues.jboss.org/browse/JGRP-2332 > Project: JGroups > Issue Type: Patch > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.0 > > > Port JGroups to Quarkus [1]. > This is a quick and dirty port, to see what needs to be done. > The goal is to identify changes which can be ported back to JGroups proper to make this port as easy as possible. > Example: since JMX is not supported, separate JMX into a set of interfaces and 2 implementations: the default impl which is used when JGroups runs on a regular JVM, and another one used when run on GraalVM. > This is currently scheduled for 4.x, but may as well end up being done in 5.x > [1] https://quarkus.io -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1774) WildFlyElytronHttpBearerProvider references the mechanism instead of it's factory

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1774: ------------------------------------- Summary: WildFlyElytronHttpBearerProvider references the mechanism instead of it's factory Key: ELY-1774 URL: https://issues.jboss.org/browse/ELY-1774 Project: WildFly Elytron Issue Type: Bug Components: HTTP Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.9.0.CR2 This means the mechanism is unavailable. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11892) With Elytron the legacy RunAsLoginModule no longer works

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-11892?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFLY-11892: ------------------------------------ Priority: Major (was: Critical) > With Elytron the legacy RunAsLoginModule no longer works > -------------------------------------------------------- > > Key: WFLY-11892 > URL: https://issues.jboss.org/browse/WFLY-11892 > Project: WildFly > Issue Type: Bug > Reporter: Brian Loss > Assignee: Brian Stansberry > Priority: Major > > When using the legacy jaas configuration, the RunAsLoginModule no longer works. While the module is invoked, there is no SecurityContext, so the login module cannot do any work and the temporary identity is never pushed on to the stack. > It seems that previously, [this line|https://github.com/wildfly/wildfly/blob/16.0.0.Final/undertow/src/ma...] was responsible for setting up the security context. However, that action is no longer executed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11892) With Elytron the legacy RunAsLoginModule no longer works

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-11892?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFLY-11892: ------------------------------------ Component/s: Security > With Elytron the legacy RunAsLoginModule no longer works > -------------------------------------------------------- > > Key: WFLY-11892 > URL: https://issues.jboss.org/browse/WFLY-11892 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Loss > Assignee: Brian Stansberry > Priority: Major > > When using the legacy jaas configuration, the RunAsLoginModule no longer works. While the module is invoked, there is no SecurityContext, so the login module cannot do any work and the temporary identity is never pushed on to the stack. > It seems that previously, [this line|https://github.com/wildfly/wildfly/blob/16.0.0.Final/undertow/src/ma...] was responsible for setting up the security context. However, that action is no longer executed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11892) With Elytron the legacy RunAsLoginModule no longer works

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-11892?page=com.atlassian.jira.plugin... ] Darran Lofthouse reassigned WFLY-11892: --------------------------------------- Assignee: (was: Brian Stansberry) > With Elytron the legacy RunAsLoginModule no longer works > -------------------------------------------------------- > > Key: WFLY-11892 > URL: https://issues.jboss.org/browse/WFLY-11892 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Loss > Priority: Major > > When using the legacy jaas configuration, the RunAsLoginModule no longer works. While the module is invoked, there is no SecurityContext, so the login module cannot do any work and the temporary identity is never pushed on to the stack. > It seems that previously, [this line|https://github.com/wildfly/wildfly/blob/16.0.0.Final/undertow/src/ma...] was responsible for setting up the security context. However, that action is no longer executed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11892) With Elytron the legacy RunAsLoginModule no longer works

by Brian Loss (Jira)

Brian Loss created WFLY-11892: --------------------------------- Summary: With Elytron the legacy RunAsLoginModule no longer works Key: WFLY-11892 URL: https://issues.jboss.org/browse/WFLY-11892 Project: WildFly Issue Type: Bug Reporter: Brian Loss Assignee: Brian Stansberry When using the legacy jaas configuration, the RunAsLoginModule no longer works. While the module is invoked, there is no SecurityContext, so the login module cannot do any work and the temporary identity is never pushed on to the stack. It seems that previously, [this line|https://github.com/wildfly/wildfly/blob/16.0.0.Final/undertow/src/ma...] was responsible for setting up the security context. However, that action is no longer executed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11891) Add tests that enable JPA bytecode enhancing

by Scott Marlow (Jira)

Scott Marlow created WFLY-11891: ----------------------------------- Summary: Add tests that enable JPA bytecode enhancing Key: WFLY-11891 URL: https://issues.jboss.org/browse/WFLY-11891 Project: WildFly Issue Type: Enhancement Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Pick a few unit tests and add the following settings to enable entity bytecode enhancement: {code} <property name="hibernate.ejb.use_class_enhancer" value="true"/> <property name="hibernate.enhancer.enableDirtyTracking" value="true"/> <property name="hibernate.enhancer.enableLazyInitialization" value="true"/> <property name="hibernate.enhancer.enableAssociationManagement" value="true"/> {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11891) Add tests that enable JPA entity class bytecode enhancment

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-11891?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-11891: -------------------------------- Summary: Add tests that enable JPA entity class bytecode enhancment (was: Add tests that enable JPA bytecode enhancing) > Add tests that enable JPA entity class bytecode enhancment > ---------------------------------------------------------- > > Key: WFLY-11891 > URL: https://issues.jboss.org/browse/WFLY-11891 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Minor > > Pick a few unit tests and add the following settings to enable entity bytecode enhancement: > {code} > <property name="hibernate.ejb.use_class_enhancer" value="true"/> > <property name="hibernate.enhancer.enableDirtyTracking" value="true"/> > <property name="hibernate.enhancer.enableLazyInitialization" value="true"/> > <property name="hibernate.enhancer.enableAssociationManagement" value="true"/> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4377) Support passing properties and environment variables to the Windows server.bat

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4377?page=com.atlassian.jira.plugi... ] James Perkins edited comment on WFCORE-4377 at 3/21/19 12:11 PM: ----------------------------------------------------------------- Yes looks like a duplicate to me. Sorry about that I missed it when I created this JIRA. > Support passing properties and environment variables to the Windows server.bat > ------------------------------------------------------------------------------ > > Key: WFCORE-4377 > URL: https://issues.jboss.org/browse/WFCORE-4377 > Project: WildFly Core > Issue Type: Feature Request > Components: Scripts > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > Script is missing few features, which WildFly/Commons Daemon provide: > # it is not possible to pass properties file to WildFly instance > # it is not possible to pass environment variables to WildFly instance(more concretely - {{JBOSS_MODULEPATH}} to specify one or more external module directories) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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