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 commented on WFLY-4171: ----------------------------------- And the ear-plugin configuration have : {noformat}  <version>6</version> {noformat} instead of version 7 > 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, 3 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 edited comment on WFLY-4171 at 1/27/15 5:20 PM: ------------------------------------------------------------ And the ear-plugin configuration have : {noformat}  <version>6</version> {noformat} instead of version 7 and also an unnecessary empty modules sections was (Author: fbricon): And the ear-plugin configuration have : {noformat}  <version>6</version> {noformat} instead of version 7 > 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, 3 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 edited comment on WFLY-4171 at 1/27/15 5:16 PM: ------------------------------------------------------------ html5 archetype is fine, finally! But checking the javaee7 web archetype, I saw the kitchensink name was not replaced with ${artifactId} in the cheatsheet : title="CDI + JSF + EJB + JTA + Bean Validation + JAX-RS + Arquillian: Kitchensink quickstart" Also, the ee7 projects reference resources/gfx/wildfly_400x130.jpg which is missing making it look bad once deployed. Should use the same logo as in html5 was (Author: fbricon): html5 archetype is fine, finally! But checking the javaee7 web archetype, I saw the kitchensink name was not replaced with ${artifactId} in the cheatsheet : title="CDI + JSF + EJB + JTA + Bean Validation + JAX-RS + Arquillian: Kitchensink quickstart" > 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, 3 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: ----------------------------------- html5 archetype is fine, finally! But checking the javaee7 web archetype, I saw the kitchensink name was not replaced with ${artifactId} in the cheatsheet : title="CDI + JSF + EJB + JTA + Bean Validation + JAX-RS + Arquillian: Kitchensink quickstart" > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-457) Replace mod_cluster proxy-list attribute with list of outbound socket bindings

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-457?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-457: ---------------------------------------------- Michal Babacek <mbabacek(a)redhat.com> changed the Status of [bug 954017|https://bugzilla.redhat.com/show_bug.cgi?id=954017] from NEW to CLOSED > Replace mod_cluster proxy-list attribute with list of outbound socket bindings > ------------------------------------------------------------------------------ > > Key: WFLY-457 > URL: https://issues.jboss.org/browse/WFLY-457 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 8.0.0.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Priority: Critical > Fix For: 9.0.0.Alpha1 > > > Currently, the mod_cluster subsystem defines proxies using a comma separated string of address:port. This attribute needs to be deprecated in favor of an attribute, call it "proxies" that defines an xs:list of outbound socket binding names. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4254) Symbolic links within web applications do not work

by James Roos (JIRA)

[ https://issues.jboss.org/browse/WFLY-4254?page=com.atlassian.jira.plugin.... ] James Roos edited comment on WFLY-4254 at 1/27/15 4:27 PM: ----------------------------------------------------------- Is there any possibility of a patch for 8.2.0 being created to address this issue. I've got a dead line and can't wait for 9.x to be released and I would rather not role back to 8.1.0. I have both exploded and unexploded wars that utilize symbolic links. I'm working with multiple RAIDs and multiple sub-directories that would be a nightmare to try and mount all under the document base. was (Author: roosjr): Is there any possibility of a patch for 8.2.0 being created to address this issue. I've got a dead line and can't wait for 9.x to be released and I would rather not role back to 8.1.0. > Symbolic links within web applications do not work > -------------------------------------------------- > > Key: WFLY-4254 > URL: https://issues.jboss.org/browse/WFLY-4254 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 8.2.0.Final > Reporter: Kris Iyer > Assignee: Stuart Douglas > Fix For: 9.0.0.Beta1 > > > Symbolic Linking under exploded web-apps to files and/or directories outside the web-app do not work. > Here is what I tried under an exploded war: > <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd" > version="8.0"> > <symbolic-linking-enabled>true</symbolic-linking-enabled> > </jboss-web> > Does not follow links and results in a 404. > HTTP/?.? 404 Not Found > Connection: keep-alive > X-Powered-By: Undertow/1 > Server: WildFly/8 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4254) Symbolic links within web applications do not work

by James Roos (JIRA)

[ https://issues.jboss.org/browse/WFLY-4254?page=com.atlassian.jira.plugin.... ] James Roos commented on WFLY-4254: ---------------------------------- Is there any possibility of a patch for 8.2.0 being created to address this issue. I've got a dead line and can't wait for 9.x to be released and I would rather not role back to 8.1.0. > Symbolic links within web applications do not work > -------------------------------------------------- > > Key: WFLY-4254 > URL: https://issues.jboss.org/browse/WFLY-4254 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 8.2.0.Final > Reporter: Kris Iyer > Assignee: Stuart Douglas > Fix For: 9.0.0.Beta1 > > > Symbolic Linking under exploded web-apps to files and/or directories outside the web-app do not work. > Here is what I tried under an exploded war: > <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd" > version="8.0"> > <symbolic-linking-enabled>true</symbolic-linking-enabled> > </jboss-web> > Does not follow links and results in a 404. > HTTP/?.? 404 Not Found > Connection: keep-alive > X-Powered-By: Undertow/1 > Server: WildFly/8 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-868) Multithread issue when validate with cached hased password + nonce credential info from JBossCachedAuthenticationManager

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-868?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-868: -------------------------------------------------- Ondrej Kotek <okotek(a)redhat.com> changed the Status of [bug 1181084|https://bugzilla.redhat.com/show_bug.cgi?id=1181084] from ON_QA to VERIFIED > Multithread issue when validate with cached hased password + nonce credential info from JBossCachedAuthenticationManager > -------------------------------------------------------------------------------------------------------------------------- > > Key: SECURITY-868 > URL: https://issues.jboss.org/browse/SECURITY-868 > Project: PicketBox > Issue Type: Task > Components: PicketBox > Reporter: Jim Ma > Assignee: Stefan Guilhen > Fix For: PicketBox_4_9_0.Beta3 > > > When the new security domain is configured with catch-type=default in standalone.xml, the validated credential will be put in the JBossCachedAuthenticationManager with principal and domaininfo value pair. In multithread environment, a new validated credential can overwrite the previous thread cached domain info. This will cause even in the same thread , the cached authentication info could not work. For example if one user login with username , password and nonce in two threads : thread A and thread B ;thread A caches the validated credential(hased password +nonce) in JBossCachedAuthenticationMessager, thread B does the authentication, then caches the validated credential (hashed password + nonce) , even it's the same user and passoword, the credential is different because the nonce is diffrent. So the new credential created in thread B will overwrite the previous value created by thread A . So in thread A, the cached validation info won't work and following validation with cached credential will all fail. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-185) ClassCastException at ConditionEvaluator

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-185?page=com.atlassian.jira.plugin... ] Davide Sottara commented on DROOLS-185: --------------------------------------- The problem was identified long after 5.5 was released officially. Please try a more recent version Best Davide > ClassCastException at ConditionEvaluator > ---------------------------------------- > > Key: DROOLS-185 > URL: https://issues.jboss.org/browse/DROOLS-185 > Project: Drools > Issue Type: Bug > Affects Versions: 5.5.0.Final > Reporter: Sergey Alaev > Assignee: Mario Fusco > > Stacktrace: > Caused by: java.lang.ClassCastException: ***** cannot be cast to ****** > at ConditionEvaluator443abf2927ca4f64a4ad86407ae34799.evaluate(Unknown Source) > at org.drools.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:200) > at org.drools.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:157) > at org.drools.reteoo.FromNode.checkConstraintsAndPropagate(FromNode.java:318) > at org.drools.reteoo.FromNode.assertLeftTuple(FromNode.java:164) > at org.drools.reteoo.CompositeLeftTupleSinkAdapter.doPropagateAssertLeftTuple(CompositeLeftTupleSinkAdapter.java:232) > at org.drools.reteoo.CompositeLeftTupleSinkAdapter.createAndPropagateAssertLeftTuple(CompositeLeftTupleSinkAdapter.java:116) > at org.drools.reteoo.LeftInputAdapterNode.assertObject(LeftInputAdapterNode.java:154) > at org.drools.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:59) > Reason: > ConditionEvaluator seems to be using lazy initializing and then caches generated class to evaluate this expression with another arguments. > Given following: > interface A { > String getString(); > } > interface B { > String getString(); > } > class X implements B, A {} > class Y implements A{} > rule "test rule" > when: > A(string != null) > then: > end > When rule engine is called for the first time with instance of class X, ConditionEvaluator will bind itself to first found interface implementing method getString(), i.e. interface B. > Thus second call with instance of class Y will cause ClassCastException of casting Y to B. > Solution: force MVEL to bind bytecode generated methods to class/interface declared in the rule explicitly, in our case - to interface A. > Quickfix: use following declaration of class X: > class X implements A, B {} > Because ConditionEvaluator binds to first available interface, it will bind now to correct interface - to interface A. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4290) Datasource template operation

by Jesper Pedersen (JIRA)

Jesper Pedersen created WFLY-4290: ------------------------------------- Summary: Datasource template operation Key: WFLY-4290 URL: https://issues.jboss.org/browse/WFLY-4290 Project: WildFly Issue Type: Task Components: JCA Reporter: Jesper Pedersen Assignee: Stefano Maestri {noformat} /subsystem=datasources/datasource=<datasource-name>:add(type=”postgresql”, url=””, driver=””) {noformat} Could have an optional capacity profile -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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