October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9267) Upgrade Hibernate Validator to 6.0.3.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-9267?page=com.atlassian.jira.plugin.... ] James Perkins closed WFLY-9267. ------------------------------- Resolution: Out of Date > Upgrade Hibernate Validator to 6.0.3.Final > ------------------------------------------- > > Key: WFLY-9267 > URL: https://issues.jboss.org/browse/WFLY-9267 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Leandro Kersting de Freitas > Assignee: Jason Greene > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9268) Upgrade Hibernate Search to 5.8.1 with Elasticsearch Support

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-9268?page=com.atlassian.jira.plugin.... ] James Perkins closed WFLY-9268. ------------------------------- Resolution: Out of Date > Upgrade Hibernate Search to 5.8.1 with Elasticsearch Support > ------------------------------------------------------------ > > Key: WFLY-9268 > URL: https://issues.jboss.org/browse/WFLY-9268 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Leandro Kersting de Freitas > Assignee: Jason Greene > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2303) RELAY2: notification when a site is up/down on all cluster nodes

by Bela Ban (Jira)

Bela Ban created JGRP-2303: ------------------------------ Summary: RELAY2: notification when a site is up/down on all cluster nodes Key: JGRP-2303 URL: https://issues.jboss.org/browse/JGRP-2303 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Fix For: 4.0.16 Provide a callback that's invoked on *all nodes* when a site is up/down, and possibly an initial view of the sites. Could be something like a 'sites view', e.g. \{"LON", "SFO"\}, \{"LON"\}, \{"LON", "SFO", "NYC\} etc -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9266) Upgrade Hibernate ORM to 5.2.12.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-9266?page=com.atlassian.jira.plugin.... ] James Perkins closed WFLY-9266. ------------------------------- Resolution: Out of Date > Upgrade Hibernate ORM to 5.2.12.Final > ------------------------------------- > > Key: WFLY-9266 > URL: https://issues.jboss.org/browse/WFLY-9266 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Leandro Kersting de Freitas > Assignee: Jason Greene > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3152) [DMN Designer] Context Expression can not be saved

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3152?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3152: ----------------------------------- Story Points: 3 Sprint: 2018 Week 42-44 > [DMN Designer] Context Expression can not be saved > -------------------------------------------------- > > Key: DROOLS-3152 > URL: https://issues.jboss.org/browse/DROOLS-3152 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2018-10-16 15-03-23.png, error.log > > > User can not save DMN diagram if it contains a decision node with *Context* as top level expression. > Spotted during DROOLS-3109 review, however not 100% sure it is the root cause. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10036) Any tool to mirgrate my Jboss 5.1 project to Wildfly 10

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-10036?page=com.atlassian.jira.plugin... ] James Perkins closed WFLY-10036. -------------------------------- Resolution: Rejected Please use the forums for questions https://developer.jboss.org/en/wildfly. > Any tool to mirgrate my Jboss 5.1 project to Wildfly 10 > ------------------------------------------------------- > > Key: WFLY-10036 > URL: https://issues.jboss.org/browse/WFLY-10036 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Hanuman Kumawat > Assignee: Jason Greene > Priority: Critical > > Hi team, > I got a task to current project migrate to WildFly, so please need your help on this. > Below are my current project details- > JBoss 5.1 > JDK 6 > EJB 3 > Hibernate 3 > Oracle 11g > Thank you in advance! > Thanks & Regards, > Hanuman -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2302) Default ASYM_ENCRYPT asym_keylength is considered breakable

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2302?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2302: --------------------------- Fix Version/s: 4.0.16 > Default ASYM_ENCRYPT asym_keylength is considered breakable > ----------------------------------------------------------- > > Key: JGRP-2302 > URL: https://issues.jboss.org/browse/JGRP-2302 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.15 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 4.0.16 > > > JGroups default asym_keylength is 512, however RSA keys less than 1024 bits are considered breakable (e.g. https://www.oracle.com/technetwork/java/javase/8-compatibility-guide-2156... ) > We should baseline the default to a secure size universally supported in our supported JDKs. Also, since JDK8 the default is 2048. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11178) WSTrustTestCase failing on IBM

by David Lloyd (Jira)

[ https://issues.jboss.org/browse/WFLY-11178?page=com.atlassian.jira.plugin... ] David Lloyd commented on WFLY-11178: ------------------------------------ Sure, just use the JMX MBean for the "ServiceModuleLoader" and you can get all dependency info for a given deployment. There isn't a good general way to get class init order information, but you can print a log/stack trace when the property is modified *or* when it's read. Then compare the sequence between OpenJDK and IBM to see if that accounts for the difference. Another possibility is that somehow the IBM JAXP APIs don't conform to spec. > WSTrustTestCase failing on IBM > ------------------------------ > > Key: WFLY-11178 > URL: https://issues.jboss.org/browse/WFLY-11178 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 14.0.0.Final > Reporter: Jan Blizňák > Assignee: Alessio Soldano > Priority: Major > Attachments: log.txt > > > As discovered during investigation in WFLY-10336, we are now getting test failures in WSTrustTestCase when IBM JDK is used. The relevant part of the exception is: > {code:java} > Caused by: java.lang.IllegalArgumentException: Provider org.apache.xerces.jaxp.validation.XMLSchemaFactory not found > at javax.xml.validation.SchemaFactory.newInstance(Unknown Source) > at org.opensaml.core.xml.config.XMLConfigurator.<init>(XMLConfigurator.java:94) > at org.apache.wss4j.common.saml.OpenSAMLBootstrap.bootstrap(OpenSAMLBootstrap.java:85) > at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:91) > at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:75) > at org.apache.wss4j.common.saml.SamlAssertionWrapper.<init>(SamlAssertionWrapper.java:184) > at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createSamlToken(SAMLTokenProvider.java:308) > at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createToken(SAMLTokenProvider.java:120) > ... 102 more > {code} > It turned out the issue is in wildfly for some time, the breaking change was identified as https://github.com/wildfly/wildfly-core/pull/3201/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11193) Upgrade Hibernate ORM from 5.3.6 to 5.3.7

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11193?page=com.atlassian.jira.plugin... ] James Perkins moved JBEAP-15672 to WFLY-11193: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11193 (was: JBEAP-15672) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JPA / Hibernate (was: Build System) > Upgrade Hibernate ORM from 5.3.6 to 5.3.7 > ----------------------------------------- > > Key: WFLY-11193 > URL: https://issues.jboss.org/browse/WFLY-11193 > Project: WildFly > Issue Type: Component Upgrade > Components: JPA / Hibernate > Reporter: Gail Badner > Assignee: Gail Badner > Priority: Blocker > Fix For: 15.0.0.Alpha1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11193) Upgrade Hibernate ORM from 5.3.6 to 5.3.7

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11193?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11193: --------------------------------- Fix Version/s: 15.0.0.Alpha1 > Upgrade Hibernate ORM from 5.3.6 to 5.3.7 > ----------------------------------------- > > Key: WFLY-11193 > URL: https://issues.jboss.org/browse/WFLY-11193 > Project: WildFly > Issue Type: Component Upgrade > Components: JPA / Hibernate > Reporter: Gail Badner > Assignee: Gail Badner > Priority: Blocker > Fix For: 15.0.0.Alpha1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

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