January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4171) Provide an html5 archetype for wildfly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/WFLY-4171?page=com.atlassian.jira.plugin.... ] Fred Bricon edited comment on WFLY-4171 at 1/30/15 4:25 PM: ------------------------------------------------------------ so {code}#{members}{code} is filtered to {code}#members{code} I would say the quickest way to fix that is to limit filtering to default.xhtml, not all *.xhtml was (Author: fbricon): so {code}#{members}{code} is filtered to {code}#members{code}. I would say the quickest way to fix that is to limit filtering to default.xhtml, not all *.xhtml > Provide an html5 archetype for wildfly > -------------------------------------- > > Key: WFLY-4171 > URL: https://issues.jboss.org/browse/WFLY-4171 > Project: WildFly > Issue Type: Feature Request > Reporter: Fred Bricon > Assignee: Rafael Benevides > > We'd like to provide a Wildfly-ified version of the html5 archetype in JBoss Central, for JBoss Tools and Developer Studio, The current versions we serve right now are : > * org.jboss.aerogear.archetypes:jboss-html5-mobile-archetype:7.1.3.Final > * org.jboss.archetype.wfk:jboss-html5-mobile-archetype:2.6.0.Final -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4171) Provide an html5 archetype for wildfly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/WFLY-4171?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on WFLY-4171: ----------------------------------- so #{members} is filtered to #members. I would say the quickest way to fix that is to limit filtering to default.xhtml, not all *.xhtml > Provide an html5 archetype for wildfly > -------------------------------------- > > Key: WFLY-4171 > URL: https://issues.jboss.org/browse/WFLY-4171 > Project: WildFly > Issue Type: Feature Request > Reporter: Fred Bricon > Assignee: Rafael Benevides > > We'd like to provide a Wildfly-ified version of the html5 archetype in JBoss Central, for JBoss Tools and Developer Studio, The current versions we serve right now are : > * org.jboss.aerogear.archetypes:jboss-html5-mobile-archetype:7.1.3.Final > * org.jboss.archetype.wfk:jboss-html5-mobile-archetype:2.6.0.Final -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4171) Provide an html5 archetype for wildfly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/WFLY-4171?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on WFLY-4171: ----------------------------------- Something bad happened. The pages can't be displayed anymore without an error : {noformat} Caused by: javax.el.ELException: /index.xhtml: The class 'java.lang.String' does not have the property 'id'. at com.sun.faces.facelets.compiler.TextInstruction.write(TextInstruction.java:88) [jsf-impl-2.2.8-jbossorg-1.jar:] at com.sun.faces.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:82) [jsf-impl-2.2.8-jbossorg-1.jar:] {noformat} It's probably caused by the filtering on xhtml files. I'm not sure exactly what causes the error. > Provide an html5 archetype for wildfly > -------------------------------------- > > Key: WFLY-4171 > URL: https://issues.jboss.org/browse/WFLY-4171 > Project: WildFly > Issue Type: Feature Request > Reporter: Fred Bricon > Assignee: Rafael Benevides > > We'd like to provide a Wildfly-ified version of the html5 archetype in JBoss Central, for JBoss Tools and Developer Studio, The current versions we serve right now are : > * org.jboss.aerogear.archetypes:jboss-html5-mobile-archetype:7.1.3.Final > * org.jboss.archetype.wfk:jboss-html5-mobile-archetype:2.6.0.Final -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-702) Rule Inheritance fired the sub rule even the condition doen't match

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-702?page=com.atlassian.jira.plugin... ] Davide Sottara resolved DROOLS-702. ----------------------------------- Assignee: Davide Sottara (was: Mark Proctor) Resolution: Rejected When a rule extends another, patterns will not be merged. If you have: {code} rule "parent" when $p : Person() then end {code} and {code} rule "child" when Person() then end {code} the engine cannot safely infer that those two patterns should match the SAME fact, so you end up with a cross-product of two patterns. In your reproducer, the number of firings is consistent with the cross product of the facts you inserted, so I don't see any bug here. As an alternative to "from", you can use unification: {code} $p := Person() {code} in both rules (parent and child) to ensure the two patterns are linked. > Rule Inheritance fired the sub rule even the condition doen't match > ------------------------------------------------------------------- > > Key: DROOLS-702 > URL: https://issues.jboss.org/browse/DROOLS-702 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final > Environment: Windows, Java6.0.29 > Reporter: Yacine Jaber > Assignee: Davide Sottara > Priority: Critical > Attachments: wod-drools-test.7z > > > You can find the attached a simple maven project that shows this error. > You can run ExampleDrools class as main java application. > The sub rules are fired even if the condition is not matched. > There are a work arround by using <from $fact> into a sub rule to avoid firing this one. > This simple project shows the failed and work arround test. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4300) Different behaviour for jboss-ejb-client.xml configuration when undeploy/deploy or server restart

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/WFLY-4300?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink commented on WFLY-4300: ---------------------------------------- Quickstart can not be used before fix WFLY-4301 or the install-domain need to be changed. remove the "txNodeIdentifier" expression within the install-domain.cli, the QS will work but the server start will show warnings > Different behaviour for jboss-ejb-client.xml configuration when undeploy/deploy or server restart > ------------------------------------------------------------------------------------------------- > > Key: WFLY-4300 > URL: https://issues.jboss.org/browse/WFLY-4300 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Jason Greene > > If remote-outbound-connection to a cluster is used and the application contain a jboss-ejb-client.xml with <clusters> element and this element must be changed a simple undeploy/deploy will not change the behavior. A full server restart is needed! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4301) Quickstart ejb-multi-server does not work

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/WFLY-4301?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink commented on WFLY-4301: ---------------------------------------- WFLY-4299 need to be fixed to run this quickstart without error > Quickstart ejb-multi-server does not work > ----------------------------------------- > > Key: WFLY-4301 > URL: https://issues.jboss.org/browse/WFLY-4301 > Project: WildFly > Issue Type: Bug > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > > After changing the maven artifactId of the project the created application ear/war files are named different and the deployment script deploy-domain.cli will not work. > Also the ejb lookup names has change because of this and need to be adapted. > related commit 10f95488c0a6f765c25d70a7dcbd566e59230fd2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4301) Quickstart ejb-multi-server does not work

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created WFLY-4301: -------------------------------------- Summary: Quickstart ejb-multi-server does not work Key: WFLY-4301 URL: https://issues.jboss.org/browse/WFLY-4301 Project: WildFly Issue Type: Bug Reporter: Wolf-Dieter Fink Assignee: Wolf-Dieter Fink After changing the maven artifactId of the project the created application ear/war files are named different and the deployment script deploy-domain.cli will not work. Also the ejb lookup names has change because of this and need to be adapted. related commit 10f95488c0a6f765c25d70a7dcbd566e59230fd2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4300) Different behaviour for jboss-ejb-client.xml configuration when undeploy/deploy or server restart

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created WFLY-4300: -------------------------------------- Summary: Different behaviour for jboss-ejb-client.xml configuration when undeploy/deploy or server restart Key: WFLY-4300 URL: https://issues.jboss.org/browse/WFLY-4300 Project: WildFly Issue Type: Bug Affects Versions: 9.0.0.Alpha1 Reporter: Wolf-Dieter Fink Assignee: Jason Greene If remote-outbound-connection to a cluster is used and the application contain a jboss-ejb-client.xml with <clusters> element and this element must be changed a simple undeploy/deploy will not change the behavior. A full server restart is needed! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4299) transaction subsystem node-identifier can not resolve expression

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/WFLY-4299?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink commented on WFLY-4299: ---------------------------------------- Seems like a general issue for expression use in domain mode as the same appears if remote-outbound-conection user contain an expression. Will not be resolved as in former builds > transaction subsystem node-identifier can not resolve expression > ---------------------------------------------------------------- > > Key: WFLY-4299 > URL: https://issues.jboss.org/browse/WFLY-4299 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 9.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Brian Stansberry > Priority: Critical > Labels: configuration, configuration_management, domain > > If the transaction subsystem should use an expression as node-identifier this will not work in domain mode: > ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 36) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "transactions")]) - failure description: "WFLYCTL0211: Cannot resolve expression '${txNodeIdentifier}'" > This was possible in former builds with the same configuration. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2879) Remove duplicated code from test cases where custom modules are needed

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/WFLY-2879?page=com.atlassian.jira.plugin.... ] Pedro Igor updated WFLY-2879: ----------------------------- Fix Version/s: 9.0.0.Alpha1 > Remove duplicated code from test cases where custom modules are needed > ---------------------------------------------------------------------- > > Key: WFLY-2879 > URL: https://issues.jboss.org/browse/WFLY-2879 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 8.1.0.Final > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 9.0.0.Alpha1 > > > When writing some integration tests for the PicketLink subsystem, I've noticed that there is no utility class or API to make easier create and remove custom modules from the modules directory. > There are a few tests with this requirement, and most of them are replicating code. > After discussing with [~kabirkhan], he suggested to open this JIRA to review those test cases and make them use a reusable component to work with custom modules. > I've already wrote a class that I think can satisfy all test cases requiring a custom module. > See https://github.com/pedroigor/wildfly/blob/WFLY-2733/testsuite/integration.... > Usage example: https://github.com/pedroigor/wildfly/blob/WFLY-2733/testsuite/integration... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 January 2015