September 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9308) Wrong license for jboss-saaj-api_1.3_spec in licenses.xml

by Martin Minar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9308?page=com.atlassian.jira.plugin.... ] Martin Minar reassigned WFLY-9308: ---------------------------------- Assignee: Martin Minar (was: Paul Gier) > Wrong license for jboss-saaj-api_1.3_spec in licenses.xml > --------------------------------------------------------- > > Key: WFLY-9308 > URL: https://issues.jboss.org/browse/WFLY-9308 > Project: WildFly > Issue Type: Bug > Components: Build System > Reporter: Martin Minar > Assignee: Martin Minar > Priority: Critical > Labels: downstream_dependency > > licenses.xml contains: > <dependency> > <groupId>org.jboss.spec.javax.xml.soap</groupId> > <artifactId>jboss-saaj-api_1.3_spec</artifactId> > <licenses> > <license> > <name>Apache License 2.0</name> > <url>http://www.apache.org/licenses/LICENSE-2.0</url> > <distribution>repo</distribution> > </license> > </licenses> > </dependency> > while artifact itself is: > <licenses> > <license> > <name>Common Development and Distribution License</name> > <url>http://repository.jboss.org/licenses/cddl.txt</url> > <distribution>repo</distribution> > </license> > <license> > <name>GNU General Public License, Version 2 with the Classpath Exception</name> > <url>http://repository.jboss.org/licenses/gpl-2.0-ce.txt</url> > <distribution>repo</distribution> > </license> > </licenses> > we need to make it consistent -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9308) Wrong license for jboss-saaj-api_1.3_spec in licenses.xml

by Martin Minar (JIRA)

Martin Minar created WFLY-9308: ---------------------------------- Summary: Wrong license for jboss-saaj-api_1.3_spec in licenses.xml Key: WFLY-9308 URL: https://issues.jboss.org/browse/WFLY-9308 Project: WildFly Issue Type: Bug Components: Build System Reporter: Martin Minar Assignee: Paul Gier Priority: Critical licenses.xml contains: <dependency> <groupId>org.jboss.spec.javax.xml.soap</groupId> <artifactId>jboss-saaj-api_1.3_spec</artifactId> <licenses> <license> <name>Apache License 2.0</name> <url>http://www.apache.org/licenses/LICENSE-2.0</url> <distribution>repo</distribution> </license> </licenses> </dependency> while artifact itself is: <licenses> <license> <name>Common Development and Distribution License</name> <url>http://repository.jboss.org/licenses/cddl.txt</url> <distribution>repo</distribution> </license> <license> <name>GNU General Public License, Version 2 with the Classpath Exception</name> <url>http://repository.jboss.org/licenses/gpl-2.0-ce.txt</url> <distribution>repo</distribution> </license> </licenses> we need to make it consistent -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9287) ReferencingDeploymentsHandler is doing runtime work in Stage.MODEL

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-9287?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski reassigned WFLY-9287: ---------------------------------------- Assignee: Bartosz Baranowski > ReferencingDeploymentsHandler is doing runtime work in Stage.MODEL > ------------------------------------------------------------------ > > Key: WFLY-9287 > URL: https://issues.jboss.org/browse/WFLY-9287 > Project: WildFly > Issue Type: Bug > Components: EJB, Web (Undertow) > Affects Versions: 11.0.0.CR1 > Reporter: Brian Stansberry > Assignee: Bartosz Baranowski > > The handler is reading services in Stage.MODEL. It should add a RUNTIME step, being careful that it's running on a non-admin-only-server (check OperationContext.isDefaultRequiresRuntime()). > This applies to the variant in ejb3 and the one in undertow. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1724) DRL compilation error on a generic type property

by Ryo Murai (JIRA)

Ryo Murai created DROOLS-1724: --------------------------------- Summary: DRL compilation error on a generic type property Key: DROOLS-1724 URL: https://issues.jboss.org/browse/DROOLS-1724 Project: Drools Issue Type: Bug Affects Versions: 6.5.0.Final Environment: drools 6.5.0.Final / java 1.8.0_131 Reporter: Ryo Murai Assignee: Edson Tirelli I got a DRL compilation error on accessing through a generic type property. Minimized object definition is below. {code:borderStyle=solid} public interface OrderLine<T extends Product> { T getProduct(); } public interface Product { String getId(); String getCategory(); } // and I have concrete classes, ex. Book, BookOrderLine<Book>, DVD, DVDOrderLine<DVD>, ... etc {code} DRL(snippet) is here {code:borderStyle=solid} when $orderLine: OrderLine() // compilation failed Product( id == $orderLine.product.id || category == $orderLine.product.category ) from discountProducts {code} This causes below exception. {panel} java.lang.RuntimeException: [Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules/checkorder-not-compiled.drl, line=15, column=0 text=Unable to Analyse Expression id == $orderLine.product.id || category == $orderLine.product.category: [Error: unable to resolve method using strict-mode: java.lang.Object.category()] [Near : {... Line.product.id || category == $orderLine.product.category ....}] ^ [Line: 15, Column: 2]]] {panel} This is weird because it won't occur when the restriction has single condition like below. Drools could analyze this expression. {code:borderStyle=solid} when $orderLine: OrderLine() // this is compiled, even if `Product(id == $orderLine.product.id)` Product( category == $orderLine.product.category ) from discountProducts {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1516) GAV names are not coming properly when running the tomcat as Service

by Arunraj SRM (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1516?page=com.atlassian.jira.plugi... ] Arunraj SRM commented on DROOLS-1516: ------------------------------------- Sure. Can you please share your startup values. > GAV names are not coming properly when running the tomcat as Service > -------------------------------------------------------------------- > > Key: DROOLS-1516 > URL: https://issues.jboss.org/browse/DROOLS-1516 > Project: Drools > Issue Type: Bug > Components: build, kie server, tools > Affects Versions: 6.5.0.Final > Environment: Windows > Reporter: Arunraj SRM > Assignee: Toni Rikkola > Priority: Critical > Labels: Drools, GAV,, Maven > Attachments: gav_issue.png > > > Deploy Drools Work Bench and KIE Server in Tomcat Server configured with SSL and started via service. All the artifacts populated under the GAV are displaying as > <undetermined>:<undetermined>:<undetermined> > instead of actual path including the guvnor > Start-up values: > -Dcatalina.home=C:\apache-tomcat-9.0.0.M19 > -Dcatalina.base=C:\apache-tomcat-9.0.0.M19 > -Djava.io.tmpdir=C:\apache-tomcat-9.0.0.M19\temp > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > -Djava.util.logging.config.file=C:\apache-tomcat-9.0.0.M19\conf\logging.properties > -Xmx256M > -XX:MaxPermSize=2048m > -Dbtm.root=C:\apache-tomcat-9.0.0.M19\ > -Dbitronix.tm.configuration=C:\apache-tomcat-9.0.0.M19\conf\btm-config.properties > -Dbitronix.tm.resource.configuration=C:\apache-tomcat-9.0.0.M19\conf\resources.properties > -Djbpm.tsr.jndi.lookup=java:comp/env/TransactionSynchronizationRegistry > -Djava.security.auth.login.config=C:\apache-tomcat-9.0.0.M19\webapps\kie-wb\WEB-INF\classes\login.config > -Dorg.jboss.logging.provider=jdk > -Dorg.jbpm.cdi.bm=java:comp/env/BeanManager > -Dorg.kie.server.persistence.ds=java:comp/env/jdbc/jbpm > -Dorg.kie.server.persistence.tm=org.hibernate.service.jta.platform.internal.BitronixJtaPlatform > -Dorg.uberfire.nio.git.dir=C:\drools\repositories\git\ > -Dorg.guvnor.m2repo.dir=C:\drools\repositories\kie\ > -Dorg.uberfire.metadata.index.dir=C:\drools\runtime\ > -Dorg.uberfire.nio.git.ssh.cert.dir=C:\drools\runtime\ > -Dorg.kie.demo=false > -Dorg.kie.example=false > -Dorg.kie.server.id=default-kieserver > -Dorg.kie.server.location=https://localhost/kie-server/services/rest/server > -Dorg.kie.server.controller=https://localhost/kie-wb/rest/controller > -Dorg.jbpm.server.ext.disabled=true > -Dorg.drools.server.filter.classes=true -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1516) GAV names are not coming properly when running the tomcat as Service

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1516?page=com.atlassian.jira.plugi... ] Toni Rikkola commented on DROOLS-1516: -------------------------------------- [~casterjose64] Hi, can you say what Tomcat and Drools/KIE version and war you have? > GAV names are not coming properly when running the tomcat as Service > -------------------------------------------------------------------- > > Key: DROOLS-1516 > URL: https://issues.jboss.org/browse/DROOLS-1516 > Project: Drools > Issue Type: Bug > Components: build, kie server, tools > Affects Versions: 6.5.0.Final > Environment: Windows > Reporter: Arunraj SRM > Assignee: Toni Rikkola > Priority: Critical > Labels: Drools, GAV,, Maven > Attachments: gav_issue.png > > > Deploy Drools Work Bench and KIE Server in Tomcat Server configured with SSL and started via service. All the artifacts populated under the GAV are displaying as > <undetermined>:<undetermined>:<undetermined> > instead of actual path including the guvnor > Start-up values: > -Dcatalina.home=C:\apache-tomcat-9.0.0.M19 > -Dcatalina.base=C:\apache-tomcat-9.0.0.M19 > -Djava.io.tmpdir=C:\apache-tomcat-9.0.0.M19\temp > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > -Djava.util.logging.config.file=C:\apache-tomcat-9.0.0.M19\conf\logging.properties > -Xmx256M > -XX:MaxPermSize=2048m > -Dbtm.root=C:\apache-tomcat-9.0.0.M19\ > -Dbitronix.tm.configuration=C:\apache-tomcat-9.0.0.M19\conf\btm-config.properties > -Dbitronix.tm.resource.configuration=C:\apache-tomcat-9.0.0.M19\conf\resources.properties > -Djbpm.tsr.jndi.lookup=java:comp/env/TransactionSynchronizationRegistry > -Djava.security.auth.login.config=C:\apache-tomcat-9.0.0.M19\webapps\kie-wb\WEB-INF\classes\login.config > -Dorg.jboss.logging.provider=jdk > -Dorg.jbpm.cdi.bm=java:comp/env/BeanManager > -Dorg.kie.server.persistence.ds=java:comp/env/jdbc/jbpm > -Dorg.kie.server.persistence.tm=org.hibernate.service.jta.platform.internal.BitronixJtaPlatform > -Dorg.uberfire.nio.git.dir=C:\drools\repositories\git\ > -Dorg.guvnor.m2repo.dir=C:\drools\repositories\kie\ > -Dorg.uberfire.metadata.index.dir=C:\drools\runtime\ > -Dorg.uberfire.nio.git.ssh.cert.dir=C:\drools\runtime\ > -Dorg.kie.demo=false > -Dorg.kie.example=false > -Dorg.kie.server.id=default-kieserver > -Dorg.kie.server.location=https://localhost/kie-server/services/rest/server > -Dorg.kie.server.controller=https://localhost/kie-wb/rest/controller > -Dorg.jbpm.server.ext.disabled=true > -Dorg.drools.server.filter.classes=true -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3256) Filters.filterToFilterSpec fails if ANY or ALL include legal undefined fields

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3256: ---------------------------------------- Summary: Filters.filterToFilterSpec fails if ANY or ALL include legal undefined fields Key: WFCORE-3256 URL: https://issues.jboss.org/browse/WFCORE-3256 Project: WildFly Core Issue Type: Bug Components: Logging Reporter: Brian Stansberry Assignee: James Perkins Priority: Minor Say you have a filter value like this: {code} { "any" => { "match" => ".*", "change-level" => undefined, "level" => undefined, "level-range" => undefined, "not" => undefined }, "all" => undefined, "change-level" => undefined, "level" => undefined, "level-range" => undefined, "not" => undefined } {code} Writing that will fail with "WFLYLOG0025: Filter ("change-level" => undefined) is invalid". This is because filterToFilterSpec will process the "any" node by iterating over its fields and recursing, and as soon as it gets to one of the 'undefined' ones it will fail. But the overall structure should be fine. I hit this when testing a WFCORE-3255 fix, one that had the effect of adding "change-level" => undefined, etc to the params used by LoggingOperationsSubsystemTestCase.testLegacyFilters. I can probably work around this easily enough and IIRC this 'filter' stuff is real old, so this is no big deal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1516) GAV names are not coming properly when running the tomcat as Service

by CasterJose CasterJose (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1516?page=com.atlassian.jira.plugi... ] CasterJose CasterJose commented on DROOLS-1516: ----------------------------------------------- Hey, I have the same problem but your answer doesn't solve mine... Can you please assist. > GAV names are not coming properly when running the tomcat as Service > -------------------------------------------------------------------- > > Key: DROOLS-1516 > URL: https://issues.jboss.org/browse/DROOLS-1516 > Project: Drools > Issue Type: Bug > Components: build, kie server, tools > Affects Versions: 6.5.0.Final > Environment: Windows > Reporter: Arunraj SRM > Assignee: Toni Rikkola > Priority: Critical > Labels: Drools, GAV,, Maven > Attachments: gav_issue.png > > > Deploy Drools Work Bench and KIE Server in Tomcat Server configured with SSL and started via service. All the artifacts populated under the GAV are displaying as > <undetermined>:<undetermined>:<undetermined> > instead of actual path including the guvnor > Start-up values: > -Dcatalina.home=C:\apache-tomcat-9.0.0.M19 > -Dcatalina.base=C:\apache-tomcat-9.0.0.M19 > -Djava.io.tmpdir=C:\apache-tomcat-9.0.0.M19\temp > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > -Djava.util.logging.config.file=C:\apache-tomcat-9.0.0.M19\conf\logging.properties > -Xmx256M > -XX:MaxPermSize=2048m > -Dbtm.root=C:\apache-tomcat-9.0.0.M19\ > -Dbitronix.tm.configuration=C:\apache-tomcat-9.0.0.M19\conf\btm-config.properties > -Dbitronix.tm.resource.configuration=C:\apache-tomcat-9.0.0.M19\conf\resources.properties > -Djbpm.tsr.jndi.lookup=java:comp/env/TransactionSynchronizationRegistry > -Djava.security.auth.login.config=C:\apache-tomcat-9.0.0.M19\webapps\kie-wb\WEB-INF\classes\login.config > -Dorg.jboss.logging.provider=jdk > -Dorg.jbpm.cdi.bm=java:comp/env/BeanManager > -Dorg.kie.server.persistence.ds=java:comp/env/jdbc/jbpm > -Dorg.kie.server.persistence.tm=org.hibernate.service.jta.platform.internal.BitronixJtaPlatform > -Dorg.uberfire.nio.git.dir=C:\drools\repositories\git\ > -Dorg.guvnor.m2repo.dir=C:\drools\repositories\kie\ > -Dorg.uberfire.metadata.index.dir=C:\drools\runtime\ > -Dorg.uberfire.nio.git.ssh.cert.dir=C:\drools\runtime\ > -Dorg.kie.demo=false > -Dorg.kie.example=false > -Dorg.kie.server.id=default-kieserver > -Dorg.kie.server.location=https://localhost/kie-server/services/rest/server > -Dorg.kie.server.controller=https://localhost/kie-wb/rest/controller > -Dorg.jbpm.server.ext.disabled=true > -Dorg.drools.server.filter.classes=true -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3255) Complex type AttributeDefinition variants don't handle ParameterCorrector properly

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3255?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3255: ------------------------------------- Description: If a field in a complex attribute (i.e. one that uses Object...AttributeDefinition) has a ParameterCorrector configured, that corrector never gets called. That's because only a corrector on the top level attribute gets called. These classes should automatically use an internal corrector that first calls any corrector configured for fields, and then, if one is present, calls any top level corrector. was: If a field in a complex attribute (i.e. one that uses Object...AttributeDefinition) has a ParameterCorrector configured, that corrector new gets called. That's because only a corrector on the top level attribute gets called. These classes should automatically use an internal corrector that first calls any corrector configured for fields, and then, if one is present, calls any top level corrector. > Complex type AttributeDefinition variants don't handle ParameterCorrector properly > ---------------------------------------------------------------------------------- > > Key: WFCORE-3255 > URL: https://issues.jboss.org/browse/WFCORE-3255 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.1.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 4.0.0.Alpha1 > > > If a field in a complex attribute (i.e. one that uses Object...AttributeDefinition) has a ParameterCorrector configured, that corrector never gets called. That's because only a corrector on the top level attribute gets called. > These classes should automatically use an internal corrector that first calls any corrector configured for fields, and then, if one is present, calls any top level corrector. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3255) Complex type AttributeDefinition variants don't handle ParameterCorrector properly

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3255: ---------------------------------------- Summary: Complex type AttributeDefinition variants don't handle ParameterCorrector properly Key: WFCORE-3255 URL: https://issues.jboss.org/browse/WFCORE-3255 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 3.0.1.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 4.0.0.Alpha1 If a field in a complex attribute (i.e. one that uses Object...AttributeDefinition) has a ParameterCorrector configured, that corrector new gets called. That's because only a corrector on the top level attribute gets called. These classes should automatically use an internal corrector that first calls any corrector configured for fields, and then, if one is present, calls any top level corrector. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 September 2017