[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 #{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)
9 years, 10 months
[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)
9 years, 10 months
[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)
9 years, 10 months
[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)
9 years, 10 months
[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)
9 years, 10 months
[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)
9 years, 10 months
[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)
9 years, 10 months