December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBMETA-398) The jboss-web_7_1.xsd and 7.2.xsd file cause validation errors in Eclipse

by Radovan Netuka (JIRA)

Radovan Netuka created JBMETA-398: ------------------------------------- Summary: The jboss-web_7_1.xsd and 7.2.xsd file cause validation errors in Eclipse Key: JBMETA-398 URL: https://issues.jboss.org/browse/JBMETA-398 Project: JBoss Metadata Issue Type: Bug Components: web Affects Versions: 7.2.0.Final Reporter: Radovan Netuka Assignee: Radovan Netuka The jboss-web_7_2.xsd file cause validation errors in eclipse. The following error from line 261: src-ct.2.1: Complex Type Definition Representation Error for type 'symbolic-linked-allowedType'. When <simpleContent> is used, the base type must be a complexType whose content type is simple, or, only if restriction is specified, a complex type with mixed content and emptiable particle, or, only if extension is specified, a simple type. 'boolean' satisfies none of these conditions This also happens in jboss-web_7_1.xsd -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2094) HC is unaware when managed server's MSC is unstable

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2094?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2094: ------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2012 > HC is unaware when managed server's MSC is unstable > --------------------------------------------------- > > Key: WFCORE-2094 > URL: https://issues.jboss.org/browse/WFCORE-2094 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 3.0.0.Alpha15 > > > The HC should be aware if a managed server has a service container that cannot stabilize. > What it will do with this information can evolve over time, but it should at least log it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7776) maven archetype-subsytem not available

by Teresa Miyar (JIRA)

Teresa Miyar created WFLY-7776: ---------------------------------- Summary: maven archetype-subsytem not available Key: WFLY-7776 URL: https://issues.jboss.org/browse/WFLY-7776 Project: WildFly Issue Type: Bug Components: Documentation Affects Versions: 10.0.0.Final Reporter: Teresa Miyar This page needs update since there is no archetype for this version and is misleading for users https://docs.jboss.org/author/display/WFLY10/Example+subsystem -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1378) Option: Force reading String from a Numeric type cell in SpreadSheet

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1378?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-1378: ------------------------------------- [~tkobayashi] I don't understand why an user may want to put a text into a cell with Numeric type. Is there a valid use for this? In general we should stop trying to parse any sort of garbage thrown in by users. This sort of guesses and type coercions causes many more damages than benefit on the long term and once they are in you cannot get rid of them anymore, otherwise you'll break compatibility. > Option: Force reading String from a Numeric type cell in SpreadSheet > -------------------------------------------------------------------- > > Key: DROOLS-1378 > URL: https://issues.jboss.org/browse/DROOLS-1378 > Project: Drools > Issue Type: Feature Request > Components: decision tables > Affects Versions: 7.0.0.Beta4 > Reporter: Toshiya Kobayashi > Assignee: Mario Fusco > > org.drools.decisiontable.parser.xls.ExcelParser reads a double value from a Numeric type cell. But some users expect as-is String representation rather than a double value. Users may force String type by adding heading ' (apostrophe) in the cell but sometimes it could be cumbersome. > This JIRA requests an option to force reading String from a Numeric type cell in SpreadSheet. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1376) OOPath 2+ notifyModification() result only the 1st being effective

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1376?page=com.atlassian.jira.plugi... ] Matteo Mortari reassigned DROOLS-1376: -------------------------------------- Assignee: Matteo Mortari (was: Mario Fusco) > OOPath 2+ notifyModification() result only the 1st being effective > ------------------------------------------------------------------ > > Key: DROOLS-1376 > URL: https://issues.jboss.org/browse/DROOLS-1376 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta3 > Reporter: Matteo Mortari > Assignee: Matteo Mortari > > Reproducible by adding in XPathTest: > {code:java} > @Test > public void testDoubleAdd() { > String drl = > "import org.drools.compiler.xpath.*;\n" + > "\n" + > "rule R2 when\n" + > " Group( $id: name, $p: /members{age >= 20} )\n" + > "then\n" + > " System.out.println( $id + \".\" + $p.getName() );\n" + > " insertLogical( $id + \".\" + $p.getName() );\n" + > "end\n"; > KieSession ksession = new KieHelper().addContent( drl, ResourceType.DRL ) > .build() > .newKieSession(); > > Group x = new Group("X"); > Group y = new Group("Y"); > ksession.insert( x ); > ksession.insert( y ); > ksession.fireAllRules(); > assertFalse (factsCollection(ksession).contains("X.Ada")); > assertFalse (factsCollection(ksession).contains("X.Bea")); > assertFalse (factsCollection(ksession).contains("Y.Ada")); > assertFalse (factsCollection(ksession).contains("Y.Bea")); > > Adult ada = new Adult("Ada", 20); > Adult bea = new Adult("Bea", 20); > x.addPerson(ada); > x.addPerson(bea); > y.addPerson(ada); > y.addPerson(bea); > ksession.fireAllRules(); > assertTrue (factsCollection(ksession).contains("X.Ada")); > assertTrue (factsCollection(ksession).contains("X.Bea")); > assertTrue (factsCollection(ksession).contains("Y.Ada")); > assertTrue (factsCollection(ksession).contains("Y.Bea")); > > x.removePerson(ada); > x.removePerson(bea); > y.removePerson(ada); > y.removePerson(bea); > ksession.fireAllRules(); > assertFalse (factsCollection(ksession).contains("X.Ada")); > assertFalse (factsCollection(ksession).contains("X.Bea")); > assertFalse (factsCollection(ksession).contains("Y.Ada")); > assertFalse (factsCollection(ksession).contains("Y.Bea")); > } > > @Test > public void testDoubleRemove() { > String drl = > "import org.drools.compiler.xpath.*;\n" + > "\n" + > "rule R2 when\n" + > " Group( $id: name, $p: /members{age >= 20} )\n" + > "then\n" + > " System.out.println( $id + \".\" + $p.getName() );\n" + > " insertLogical( $id + \".\" + $p.getName() );\n" + > "end\n"; > KieSession ksession = new KieHelper().addContent( drl, ResourceType.DRL ) > .build() > .newKieSession(); > > Adult ada = new Adult("Ada", 20); > Adult bea = new Adult("Bea", 20); > Group x = new Group("X"); > Group y = new Group("Y"); > x.addPerson(ada); > x.addPerson(bea); > y.addPerson(ada); > y.addPerson(bea); > ksession.insert( x ); > ksession.insert( y ); > ksession.fireAllRules(); > assertTrue (factsCollection(ksession).contains("X.Ada")); > assertTrue (factsCollection(ksession).contains("X.Bea")); > assertTrue (factsCollection(ksession).contains("Y.Ada")); > assertTrue (factsCollection(ksession).contains("Y.Bea")); > > x.removePerson(ada); > x.removePerson(bea); > y.removePerson(ada); > y.removePerson(bea); > ksession.fireAllRules(); > assertFalse (factsCollection(ksession).contains("X.Ada")); > assertFalse (factsCollection(ksession).contains("X.Bea")); > assertFalse (factsCollection(ksession).contains("Y.Ada")); > assertFalse (factsCollection(ksession).contains("Y.Bea")); > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7775) Upgrade to Hibernate Validator 5.3.4

by Gunnar Morling (JIRA)

Gunnar Morling created WFLY-7775: ------------------------------------ Summary: Upgrade to Hibernate Validator 5.3.4 Key: WFLY-7775 URL: https://issues.jboss.org/browse/WFLY-7775 Project: WildFly Issue Type: Component Upgrade Reporter: Gunnar Morling Assignee: Gunnar Morling -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7112) Allow optional tag virtual-host (and others) inside jboss-app.xml

by Guido Jäkel (JIRA)

[ https://issues.jboss.org/browse/WFLY-7112?page=com.atlassian.jira.plugin.... ] Guido Jäkel commented on WFLY-7112: ----------------------------------- Is there any progress on this? I just found, that this issue is unresolved for years ([JBAS-7658|https://issues.jboss.org/browse/JBAS-7658]). > Allow optional tag virtual-host (and others) inside jboss-app.xml > ----------------------------------------------------------------- > > Key: WFLY-7112 > URL: https://issues.jboss.org/browse/WFLY-7112 > Project: WildFly > Issue Type: Feature Request > Components: EE > Affects Versions: 10.1.0.Final > Reporter: Guido Jäkel > Assignee: Jason Greene > > With undertow, the assignment of a web-application to a virtual host must be set in {{$WAR/META-INF/jboss-web.xml}}. A very adjacent parameter, the context-root, might be defined or overridden here, too. > In practice, for a concrete deployment generally one have to adapt both parts of the URL, the (virtual) host and the context-root part and may use this file and e.g. apply it with the overlay feature. > In case of an EAR, its components are declared inside {{$EAR/META-INF/application.xml}}. For an web application, the {{context-root}} is defined here. I found, that this have precedence to a {{$WAR/WEB-INF/jboss-web.xml}}. I don't expect this, but it might be defined by JEE specifications in that way. If not, this feature request should be converted to a bug report concerning a wrong preference order. > To my knowledge, at the moment this file seems the only way to set the {{virtual-host}} to use. And this looks very inconsistent to me, because you have to use two different "far-out" files to controll this very associated informations. > The informations in application.xml may be overridden and enriched by {{jboss-appl.xml}} in a similar manner as with {{web.xml}} and {{jboss-web.xml}}. I would expect (and suggest it as a feature) to define the virtual host here in an analogous way as the context root in {{application.xml}} may be overriden here. > {code} > <module> > <web> > <web-uri>a.war</web-uri> > <context-root>/foo</context-root> > <virtual-host>a.domain.tld</virtual-host> > ... > </web> > </module> > {code} > This concept should be probably expanded to the complete feature set controlled by the {{jboss-web.xml}}, like undertow-related like {{server-instance}} or others like {{security-domain}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2101) Ensure the default configurations used by clients will be compatible with stronger authentication mechanisms

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2101: ---------------------------------------- Summary: Ensure the default configurations used by clients will be compatible with stronger authentication mechanisms Key: WFCORE-2101 URL: https://issues.jboss.org/browse/WFCORE-2101 Project: WildFly Core Issue Type: Task Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Blocker Fix For: 3.0.0.Beta1 i.e. a later AS release will start to enable mechs like SCRAM, client should work without additional configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7774) Make an EL 2.2 backward compatible switch "javax.el.bc2.2" configurable

by Masafumi Miura (JIRA)

[ https://issues.jboss.org/browse/WFLY-7774?page=com.atlassian.jira.plugin.... ] Masafumi Miura moved JBEAP-7791 to WFLY-7774: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7774 (was: JBEAP-7791) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: EE (was: EE) Target Release: (was: 7.1.0.GA) Affects Version/s: 10.1.0.Final (was: 7.0.3.GA) > Make an EL 2.2 backward compatible switch "javax.el.bc2.2" configurable > ----------------------------------------------------------------------- > > Key: WFLY-7774 > URL: https://issues.jboss.org/browse/WFLY-7774 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: 10.1.0.Final > Reporter: Masafumi Miura > Assignee: Tomaz Cerar > > [UEL-38|https://java.net/jira/browse/UEL-38] introduced an EL 2.2 backward compatible switch {{"javax.el.bc2.2"}}. However, it's currently unable to enable this in EAP 7. Improve this and expose this properly via configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7773) Old way Colocated HA topology with HTTP connectors/acceptors

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-7773?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-7787 to WFLY-7773: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7773 (was: JBEAP-7787) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: JMS) Affects Version/s: (was: 7.0.0.GA) (was: 7.1.0.DR7) > Old way Colocated HA topology with HTTP connectors/acceptors > ------------------------------------------------------------ > > Key: WFLY-7773 > URL: https://issues.jboss.org/browse/WFLY-7773 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Critical > > I try to configure old way colocated HA topology with HTTP connectors/acceptors but something goes wrong and I see repeated WARN message \[1\] on the first node and on the second I see the \[2\]. Maybe it is misconfiguration, but I have no idea what I do wrong. I attached XML configurations of both nodes, please review it. > \[1\] > {code} > 12:55:47,789 WARN [org.apache.activemq.artemis.core.client] (Thread-10 (ActiveMQ-client-global-threads-487873773)) AMQ212006: Waiting 2 000 milliseconds before next retry. RetryInterval=2 000 and multiplier=1 > {code} > \[2\] > {code} > 12:56:39,054 WARN [org.apache.activemq.artemis.core.client] (Thread-10 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@4766f9b3-516179796)) AMQ212006: Waiting 500 milliseconds before next retry. RetryInterval=500 and multiplier=1 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2016