October 2018 - jboss-jira - Jboss List Archives

[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: ------------------------------------ If it is unspecified, it _should_ be using the default which we install at boot. This is done by JBoss Modules, which adds a "virtual" service implementation to every module that contains the "__redirected" class, which in turn calls the implementation class. In this case, it will be the Xerces we bundle, even though it is not actually on the deployment class path. > 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-11178) WSTrustTestCase failing on IBM

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFLY-11178?page=com.atlassian.jira.plugin... ] Jan Blizňák commented on WFLY-11178: ------------------------------------ OK will try to get some input on picketlink side when I determine who is responsible for it. Still, wildfly bundles own xerces module so I thought we would want to use it. If problem of not finding particular class with IBM JDK is fixed by adding xerces module dependency whereas OpenJDK can find it without dependency that could indicate that the class is actually not loaded from our xerces module but is loaded from JDK libraries itself. > 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-11219) Apply CXF Fix managing closing of temp queues (CXF-7768)

by Tomas Hofman (Jira)

[ https://issues.jboss.org/browse/WFLY-11219?page=com.atlassian.jira.plugin... ] Tomas Hofman commented on WFLY-11219: ------------------------------------- Merged in CXF 3.2.6. > Apply CXF Fix managing closing of temp queues (CXF-7768) > -------------------------------------------------------- > > Key: WFLY-11219 > URL: https://issues.jboss.org/browse/WFLY-11219 > Project: WildFly > Issue Type: Bug > Components: Web Services > Environment: JBoss 7.1, newer > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Priority: Major > > CXF has a problem with closing of temporary JMS queues when using SOAP/JMS. > Please apply the necessary fix [1] (CXF-7768) to EAP 7.1 and newer. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11219) Apply CXF Fix managing closing of temp queues (CXF-7768)

by Tomas Hofman (Jira)

[ https://issues.jboss.org/browse/WFLY-11219?page=com.atlassian.jira.plugin... ] Tomas Hofman moved JBEAP-15696 to WFLY-11219: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11219 (was: JBEAP-15696) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Web Services (was: Web Services) Affects Version/s: (was: 7.1.5.CR2) Fix Version/s: (was: 7.2.1.GA) > Apply CXF Fix managing closing of temp queues (CXF-7768) > -------------------------------------------------------- > > Key: WFLY-11219 > URL: https://issues.jboss.org/browse/WFLY-11219 > Project: WildFly > Issue Type: Bug > Components: Web Services > Environment: JBoss 7.1, newer > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Priority: Major > > CXF has a problem with closing of temporary JMS queues when using SOAP/JMS. > Please apply the necessary fix [1] (CXF-7768) to EAP 7.1 and newer. -- 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: ------------------------------------ bq. The next question is - is it ok for the linked picketlink sources to set the system property? I guess we can't restrict users from doing so even in application code so jboss-modules should handle that somehow, right? I'd say, no that's not OK, unless picketlink is also ensuring that the dependency is available. Application code is certainly allowed to do so, but in that case it's up to them to ensure the dependency is added to the deployment. > 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] (DROOLS-3154) Minor UI improvements/bugfixes for Scenario

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3154?page=com.atlassian.jira.plugi... ] Gabriele Cardosi commented on DROOLS-3154: ------------------------------------------ [~Rikkola] I'm already fixing the following right panel issues with [~srambach] Add some padding to right panel the tab titles: work with Sarah Rambacher to have a new HTML/CSS Remove scrolling bar from right panel: I don't know if it is a problem of div size or CSS, I think it something on code side Review expression editor component HTML/CSS (paddings, indents, etc): work with Sarah Rambacher to have a new HTML/CSS Review right panel padding (now it is hardcoded): work with Sarah Rambacher to have a new HTML/CSS that removes my hardcoded padding > Minor UI improvements/bugfixes for Scenario > ------------------------------------------- > > Key: DROOLS-3154 > URL: https://issues.jboss.org/browse/DROOLS-3154 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Toni Rikkola > Priority: Critical > Labels: UX-CSS > > This item contains a list of general UI bugs to be fixed: > - Use grey borders for all the grid and not only for the header > - Add some padding to the cells of the grid > - Add some padding to right panel the tab titles > - Remove scrolling bar from right panel > - Review expression editor component HTML/CSS (paddings, indents, etc) > - Review right panel padding (now it is hardcoded) > - Use text area inputs instead of text box for inline editing > - Reduce the width of Index column -- 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 reassigned DROOLS-3152: -------------------------------------- Assignee: Matteo Mortari (was: Daniel José dos Santos) > [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: Matteo Mortari > Priority: Blocker > Labels: drools-tools > Attachments: CE-LEs.dmn, 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] (DROOLS-3152) [DMN Designer] Context Expression can not be saved

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3152?page=com.atlassian.jira.plugi... ] Matteo Mortari edited comment on DROOLS-3152 at 10/19/18 9:14 AM: ------------------------------------------------------------------ To summarize meeting: case 3 is indeed FEEL {code:java} { a : "" } {code} equivalent of Java {code:java} {{Object a = "";}} {code} should be already supported case 1 cannot be supported XSD of DMN requires a ContextEntry to have an Expression. Will reinstantiate the "mocked" LiteralExpression. was (Author: tari_manga): To summarize meeting: case 3 is indeed FEEL {{ { a : "" } }} equivalent of Java {{Object a = "";}} should be already supported case 1 cannot be supported XSD of DMN requires a ContextEntry to have an Expression. Will reinstantiate the "mocked" LiteralExpression. > [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: Daniel José dos Santos > Priority: Blocker > Labels: drools-tools > Attachments: CE-LEs.dmn, 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] (DROOLS-3152) [DMN Designer] Context Expression can not be saved

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3152?page=com.atlassian.jira.plugi... ] Matteo Mortari edited comment on DROOLS-3152 at 10/19/18 9:14 AM: ------------------------------------------------------------------ To summarize meeting: case 3 is indeed FEEL {code:java} { a : "" } {code} equivalent of Java {code:java} Object a = ""; {code} should be already supported case 1 cannot be supported XSD of DMN requires a ContextEntry to have an Expression. Will reinstantiate the "mocked" LiteralExpression. was (Author: tari_manga): To summarize meeting: case 3 is indeed FEEL {code:java} { a : "" } {code} equivalent of Java {code:java} {{Object a = "";}} {code} should be already supported case 1 cannot be supported XSD of DMN requires a ContextEntry to have an Expression. Will reinstantiate the "mocked" LiteralExpression. > [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: Daniel José dos Santos > Priority: Blocker > Labels: drools-tools > Attachments: CE-LEs.dmn, 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] (DROOLS-3152) [DMN Designer] Context Expression can not be saved

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3152?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-3152: ---------------------------------------- To summarize meeting: case 3 is indeed FEEL {{ { a : "" } }} equivalent of Java {{Object a = "";}} should be already supported case 1 cannot be supported XSD of DMN requires a ContextEntry to have an Expression. Will reinstantiate the "mocked" LiteralExpression. > [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: Daniel José dos Santos > Priority: Blocker > Labels: drools-tools > Attachments: CE-LEs.dmn, 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

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