August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2870) [DMN Designer] Can not build project with multiple models

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2870?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2870: -------------------------------- Description: If the project contains multiple dmn models, it can not be built. h3. Manual acceptance test - Prepare three models -- Empty -- Just graph nodes -- Login inside graph nodes - Check Deployment successful was:If the project contains multiple dmn models, it can not be built. > [DMN Designer] Can not build project with multiple models > --------------------------------------------------------- > > Key: DROOLS-2870 > URL: https://issues.jboss.org/browse/DROOLS-2870 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2018-08-09 10-20-16.png > > > If the project contains multiple dmn models, it can not be built. > h3. Manual acceptance test > - Prepare three models > -- Empty > -- Just graph nodes > -- Login inside graph nodes > - Check Deployment successful -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-199) Reinitialize the output stream when it fails on Windows

by Teresa Miyar (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-199?page=com.atlassian.jira.plugin... ] Teresa Miyar commented on LOGMGR-199: ------------------------------------- I'm also trying to duplicate, on windows 10 it does not happen or I was not able to reproduce it there, I've installed today windows 2012 that is were the problem was reported, I will let you know the results. > Reinitialize the output stream when it fails on Windows > ------------------------------------------------------- > > Key: LOGMGR-199 > URL: https://issues.jboss.org/browse/LOGMGR-199 > Project: JBoss Log Manager > Issue Type: Bug > Components: core > Affects Versions: 2.0.8.Final, 2.1.0.Final > Reporter: Teresa Miyar > Assignee: James Perkins > > After the fix https://issues.jboss.org/browse/LOGMGR-154 we can still observe that the log file when using periodic file size rotation on Windows it stops logging, one solution discussed is to reinitialize the output stream when this happens. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-267) ProxyFactory will not invoke MethodHandler on methods having same name declared in non-public parent classes

by Ning Zhang (JIRA)

[ https://issues.jboss.org/browse/JASSIST-267?page=com.atlassian.jira.plugi... ] Ning Zhang updated JASSIST-267: ------------------------------- Git Pull Request: https://github.com/jboss-javassist/javassist/pull/210 > ProxyFactory will not invoke MethodHandler on methods having same name declared in non-public parent classes > ------------------------------------------------------------------------------------------------------------ > > Key: JASSIST-267 > URL: https://issues.jboss.org/browse/JASSIST-267 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.21.0-GA, 3.22.0-CR1 > Environment: Linux/Windows 7, Java 1.7 and 1.8 > Reporter: Ning Zhang > Assignee: Shigeru Chiba > Priority: Critical > Attachments: IssueMethodsHaveSameNameInParent.java > > > As in the attachment, if there are multiple methods in non-public parent class,then the MethodHandler will not take effect. > If use 3.12.0-GA, this issue will be gone. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-267) ProxyFactory will not invoke MethodHandler on methods having same name declared in non-public parent classes

by Ning Zhang (JIRA)

[ https://issues.jboss.org/browse/JASSIST-267?page=com.atlassian.jira.plugi... ] Ning Zhang commented on JASSIST-267: ------------------------------------ New pull request: https://github.com/jboss-javassist/javassist/pull/210 > ProxyFactory will not invoke MethodHandler on methods having same name declared in non-public parent classes > ------------------------------------------------------------------------------------------------------------ > > Key: JASSIST-267 > URL: https://issues.jboss.org/browse/JASSIST-267 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.21.0-GA, 3.22.0-CR1 > Environment: Linux/Windows 7, Java 1.7 and 1.8 > Reporter: Ning Zhang > Assignee: Shigeru Chiba > Priority: Critical > Attachments: IssueMethodsHaveSameNameInParent.java > > > As in the attachment, if there are multiple methods in non-public parent class,then the MethodHandler will not take effect. > If use 3.12.0-GA, this issue will be gone. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10415) Upgrade to ironjacamar 1.4.10 Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10415?page=com.atlassian.jira.plugin... ] James Perkins commented on WFLY-10415: -------------------------------------- Is there a reason for this and the 1.4.11.Final release (WFLY-10675)? > Upgrade to ironjacamar 1.4.10 Final > ----------------------------------- > > Key: WFLY-10415 > URL: https://issues.jboss.org/browse/WFLY-10415 > Project: WildFly > Issue Type: Component Upgrade > Components: JCA > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Priority: Blocker > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1630) Ignore any blank lines in between the certificates in the certificate chain returned by an ACME server to avoid parsing issues on IBM JDK

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-1630?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1630: ---------------------------- Description: Currently, {{AcmeClientSpiTest#testObtainCertificateChainWithKeySize}} and {{AcmeClientSpiTest#testObtainCertificateChainWithECPublicKey}} fail when run with IBM JDK with the following error: {code} org.wildfly.security.x500.cert.acme.AcmeException: ELY10049: Unable to download certificate chain from ACME server at org.wildfly.security.x500.cert.acme.AcmeClientSpi.getPemCertificateChain(AcmeClientSpi.java:988) at org.wildfly.security.x500.cert.acme.AcmeClientSpi.obtainCertificateChain(AcmeClientSpi.java:519) at org.wildfly.security.x500.cert.acme.AcmeClientSpiTest.obtainCertificateChain(AcmeClientSpiTest.java:284) at org.wildfly.security.x500.cert.acme.AcmeClientSpiTest.testObtainCertificateChainWithKeySize(AcmeClientSpiTest.java:260) Caused by: java.security.cert.CertificateException: Unable to initialize, java.io.IOException: insufficient data at com.ibm.security.x509.X509CertImpl.<init>(X509CertImpl.java:268) at java.security.cert.CertificateFactory.generateCertificates(CertificateFactory.java:448) at org.wildfly.security.x500.cert.acme.AcmeClientSpi.getPemCertificateChain(AcmeClientSpi.java:984) ... 3 more {code} The underlying issue is that the PEM certificate chain returned by the ACME server has a blank line in between the two certificates in the chain. This causes parsing issues on IBM JDK when {{CertificateFactory.generateCertificates()}} is called. To fix this, we can just ignore any blank lines in the chain. was: Currently, {{AcmeClientSpiTest#testObtainCertificateChainWithKeySize}} and {{AcmeClientSpiTest#testObtainCertificateChainWithECPublicKey}} fail when run with IBM JDK with the following error: {code} org.wildfly.security.x500.cert.acme.AcmeException: ELY10049: Unable to download certificate chain from ACME server at org.wildfly.security.x500.cert.acme.AcmeClientSpi.getPemCertificateChain(AcmeClientSpi.java:988) at org.wildfly.security.x500.cert.acme.AcmeClientSpi.obtainCertificateChain(AcmeClientSpi.java:519) at org.wildfly.security.x500.cert.acme.AcmeClientSpiTest.obtainCertificateChain(AcmeClientSpiTest.java:284) at org.wildfly.security.x500.cert.acme.AcmeClientSpiTest.testObtainCertificateChainWithKeySize(AcmeClientSpiTest.java:260) Caused by: java.security.cert.CertificateException: Unable to initialize, java.io.IOException: insufficient data at com.ibm.security.x509.X509CertImpl.<init>(X509CertImpl.java:268) at java.security.cert.CertificateFactory.generateCertificates(CertificateFactory.java:448) at org.wildfly.security.x500.cert.acme.AcmeClientSpi.getPemCertificateChain(AcmeClientSpi.java:984) ... 3 more {code} The underlying issue is that the PEM certificate chain returned by the ACME server has a blank line in between the two certificates in the chain. This causes parsing issues on IBM JDK. To fix this, we can just ignore any blank lines in the chain. > Ignore any blank lines in between the certificates in the certificate chain returned by an ACME server to avoid parsing issues on IBM JDK > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: ELY-1630 > URL: https://issues.jboss.org/browse/ELY-1630 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI > Reporter: Farah Juma > Assignee: Farah Juma > > Currently, {{AcmeClientSpiTest#testObtainCertificateChainWithKeySize}} and {{AcmeClientSpiTest#testObtainCertificateChainWithECPublicKey}} fail when run with IBM JDK with the following error: > {code} > org.wildfly.security.x500.cert.acme.AcmeException: ELY10049: Unable to download certificate chain from ACME server > at org.wildfly.security.x500.cert.acme.AcmeClientSpi.getPemCertificateChain(AcmeClientSpi.java:988) > at org.wildfly.security.x500.cert.acme.AcmeClientSpi.obtainCertificateChain(AcmeClientSpi.java:519) > at org.wildfly.security.x500.cert.acme.AcmeClientSpiTest.obtainCertificateChain(AcmeClientSpiTest.java:284) > at org.wildfly.security.x500.cert.acme.AcmeClientSpiTest.testObtainCertificateChainWithKeySize(AcmeClientSpiTest.java:260) > Caused by: java.security.cert.CertificateException: Unable to initialize, java.io.IOException: insufficient data > at com.ibm.security.x509.X509CertImpl.<init>(X509CertImpl.java:268) > at java.security.cert.CertificateFactory.generateCertificates(CertificateFactory.java:448) > at org.wildfly.security.x500.cert.acme.AcmeClientSpi.getPemCertificateChain(AcmeClientSpi.java:984) > ... 3 more > {code} > The underlying issue is that the PEM certificate chain returned by the ACME server has a blank line in between the two certificates in the chain. This causes parsing issues on IBM JDK when {{CertificateFactory.generateCertificates()}} is called. To fix this, we can just ignore any blank lines in the chain. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1630) Ignore any blank lines in between the certificates in the certificate chain returned by an ACME server to avoid parsing issues on IBM JDK

by Farah Juma (JIRA)

Farah Juma created ELY-1630: ------------------------------- Summary: Ignore any blank lines in between the certificates in the certificate chain returned by an ACME server to avoid parsing issues on IBM JDK Key: ELY-1630 URL: https://issues.jboss.org/browse/ELY-1630 Project: WildFly Elytron Issue Type: Bug Components: API / SPI Reporter: Farah Juma Assignee: Farah Juma Currently, {{AcmeClientSpiTest#testObtainCertificateChainWithKeySize}} and {{AcmeClientSpiTest#testObtainCertificateChainWithECPublicKey}} fail when run with IBM JDK with the following error: {code} org.wildfly.security.x500.cert.acme.AcmeException: ELY10049: Unable to download certificate chain from ACME server at org.wildfly.security.x500.cert.acme.AcmeClientSpi.getPemCertificateChain(AcmeClientSpi.java:988) at org.wildfly.security.x500.cert.acme.AcmeClientSpi.obtainCertificateChain(AcmeClientSpi.java:519) at org.wildfly.security.x500.cert.acme.AcmeClientSpiTest.obtainCertificateChain(AcmeClientSpiTest.java:284) at org.wildfly.security.x500.cert.acme.AcmeClientSpiTest.testObtainCertificateChainWithKeySize(AcmeClientSpiTest.java:260) Caused by: java.security.cert.CertificateException: Unable to initialize, java.io.IOException: insufficient data at com.ibm.security.x509.X509CertImpl.<init>(X509CertImpl.java:268) at java.security.cert.CertificateFactory.generateCertificates(CertificateFactory.java:448) at org.wildfly.security.x500.cert.acme.AcmeClientSpi.getPemCertificateChain(AcmeClientSpi.java:984) ... 3 more {code} The underlying issue is that the PEM certificate chain returned by the ACME server has a blank line in between the two certificates in the chain. This causes parsing issues on IBM JDK. To fix this, we can just ignore any blank lines in the chain. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4009) Upgrade VFS to 3.2.13

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4009?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-4009: ---------------------------------------- Assignee: Radovan Stancel > Upgrade VFS to 3.2.13 > --------------------- > > Key: WFCORE-4009 > URL: https://issues.jboss.org/browse/WFCORE-4009 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Radovan Stancel > Assignee: Radovan Stancel > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10822) Provision core as a transitive dependency explicitly

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created WFLY-10822: ---------------------------------------- Summary: Provision core as a transitive dependency explicitly Key: WFLY-10822 URL: https://issues.jboss.org/browse/WFLY-10822 Project: WildFly Issue Type: Task Components: Build System Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Currently core is installed implicitly as a dependency of wildfly and servlet. We use resolve-local elements in provision goal config for core and servlet feature-packs. Those are shortcuts to avoid the universe-based feature-pack resolver. If instead of resolve-local elements we use feature-pack/transitive elements we will achieve the same effect avoiding the universe-based resolver and it will also allow us to specify the version of core using a system property. The only difference will show up in .galleon/provisioning.xml, which will change from (based on build module) {code:java} <installation xmlns="urn:jboss:galleon:provisioning:2.0"> <feature-pack location="wildfly@maven(org.jboss.universe:community-universe):current#14.0.0.Beta2-SNAPSHOT"> <packages> <include name="docs.examples.configs"/> </packages> </feature-pack> </installation> {code} to {code:java} <installation xmlns="urn:jboss:galleon:provisioning:2.0"> <transitive> <feature-pack location="wildfly-core@maven(org.jboss.universe:community-universe):current#6.0.0.Alpha5"/> <feature-pack location="wildfly-servlet@maven(org.jboss.universe:community-universe):current#14.0.0.Beta2-SNAPSHOT"/> </transitive> <feature-pack location="wildfly@maven(org.jboss.universe:community-universe):current#14.0.0.Beta2-SNAPSHOT"> <packages> <include name="docs.examples.configs"/> </packages> </feature-pack> </installation> {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ] Liz Clayton resolved DROOLS-2787. --------------------------------- Resolution: Done marking as Resolved, verified with PO. > "Data Type" tree-grid table interactions. > ----------------------------------------- > > Key: DROOLS-2787 > URL: https://issues.jboss.org/browse/DROOLS-2787 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DROOLS-2738.bmpr, Manage1.png, Manage2.png, Screen Shot 2018-07-24 at 3.51.03 PM.png, Screen Shot 2018-07-27 at 11.48.34 AM.png, Screen Shot 2018-07-27 at 12.24.49 PM.png, Screen Shot 2018-07-27 at 12.27.13 PM.png, Screen Shot 2018-08-09 at 2.09.21 PM.png, add_basic.png, treegrid.png, type_definitions.pdf > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > As a user I want to: > * *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.) > * *Add* a new data type, which might be a nested or otherwise complex object as defined by the (ItemDefinition.) > * *Remove* Data Types from the list of available selections. > * be prevented from making selections that are not valid or would cause an error. > * know that when I edit a data type the changes will be updated in the DMN model. > Functional considerations/ pre conditions: > * Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same. > * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 5 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 August 2018