December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-459) Account for attribute groups in CLI behavior

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-459?page=com.atlassian.jira.plugin... ] Alexey Loubyansky commented on WFCORE-459: ------------------------------------------ Let's start with what we have. The default behaviour of ls -l wrt attributes is that it adds the rows (an attribute is a row) into the table in the order they appear in the response of read-resource. But before printing the table it sorts the rows by attribute name, so they appear in the alphabetical order. So, if the plan is to return attributes ordered by groups in the response of read-resource (it was mentioned as a possibility in the thread) then we'll just need to skip the sorting in the CLI handler. If the CLI still has to re-order the result, sorting by another column won't be difficult at all (it's not yet supported but it's a change practically in one line). Adding another column. That's currently supported actually. It's described in the help of ls, see --attribute-description-property. The default/hardcoded properties displayed are name, value and type. But a user may extend that by simply adding the property name as an argument, e.g. ls -l --nillable --storage. So, if the group column should be displayed on demand then we don't need to change anything here. If it should be added to the default properties displayed, it will be another simple line of code. So, overall, this issue is not problematic. A possible complication is if we decide to give the user a choice and let him specify how to sort the table, which won't be that difficult to do, it's just more than one line of code :) I'll be fine with either doing it myself or letting somebody contribute the change. > Account for attribute groups in CLI behavior > -------------------------------------------- > > Key: WFCORE-459 > URL: https://issues.jboss.org/browse/WFCORE-459 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Brian Stansberry > Assignee: Alexey Loubyansky > Fix For: 1.0.0.Beta1 > > > See http://lists.jboss.org/pipermail/wildfly-dev/2014-December/003414.html > This JIRA is for reflecting the attribute group notion in CLI behavior. > I think this is just reflecting it in the output of the "ls -l" command, although there may be other places I'm not thinking of. For "ls -l" simplest is just to add a GROUP column to the right, and then sort the attributes by group and then by name, but perhaps something else is better. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3818) Update to HAL 2.4.0.Final

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-3818?page=com.atlassian.jira.plugin.... ] Heiko Braun resolved WFLY-3818. ------------------------------- Fix Version/s: (was: 9.0.0.Beta1) Resolution: Out of Date > Update to HAL 2.4.0.Final > ------------------------- > > Key: WFLY-3818 > URL: https://issues.jboss.org/browse/WFLY-3818 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3817) Update to HAL 2.4.0.Beta3

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-3817?page=com.atlassian.jira.plugin.... ] Heiko Braun resolved WFLY-3817. ------------------------------- Fix Version/s: (was: 9.0.0.Beta1) Resolution: Out of Date > Update to HAL 2.4.0.Beta3 > ------------------------- > > Key: WFLY-3817 > URL: https://issues.jboss.org/browse/WFLY-3817 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1470) Usage of finalize() needs extra guards due to a flaw in the language feature (mostly affects IBM)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1470?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1470: ----------------------------------------------- Marek Kopecky <mkopecky(a)redhat.com> changed the Status of [bug 901231|https://bugzilla.redhat.com/show_bug.cgi?id=901231] from ON_QA to VERIFIED > Usage of finalize() needs extra guards due to a flaw in the language feature (mostly affects IBM) > ------------------------------------------------------------------------------------------------- > > Key: WFLY-1470 > URL: https://issues.jboss.org/browse/WFLY-1470 > Project: WildFly > Issue Type: Task > Reporter: Carlo de Wolf > Assignee: Jason Greene > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4083) Upgrade Infinispan to 6.0.3.Final

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4083?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-4083: --------------------------------- Fix Version/s: (was: 9.0.0.Beta1) This was intended for 8.x since WildFly 9.x is already using Infinispan 7.x, but there is no such version managed in Jira... we may close this as out of date. > Upgrade Infinispan to 6.0.3.Final > --------------------------------- > > Key: WFLY-4083 > URL: https://issues.jboss.org/browse/WFLY-4083 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 8.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

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 updated WFLY-4171: ------------------------------ Description: 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 was: We'd like to provide a Wildfly-ified version of the html5 archetype in JBoss Central, for JBoss Tools and Developer Studio, The current version 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 > 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)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3805) JGroupsBroadcastGroupConfiguration Serialization Problem

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3805?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-3805: --------------------------------- Component/s: JMS (was: Clustering) > JGroupsBroadcastGroupConfiguration Serialization Problem > -------------------------------------------------------- > > Key: WFLY-3805 > URL: https://issues.jboss.org/browse/WFLY-3805 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 8.1.0.Final > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > Fix For: 9.0.0.Beta1 > > > When configuring JMS connection factories using jgroups discovery group, the client will get serialization exceptions because we pass a JChannel which is not serializable. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-460) Extended sytnax for read/write-attribute

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFCORE-460: ---------------------------------- Summary: Extended sytnax for read/write-attribute Key: WFCORE-460 URL: https://issues.jboss.org/browse/WFCORE-460 Project: WildFly Core Issue Type: Feature Request Components: Domain Management Affects Versions: 1.0.0.Alpha14 Reporter: Tomaz Cerar Assignee: Tomaz Cerar Fix For: 1.0.0.CR1 :write-attribute enhancements for complex attributes Map write enhancements :write-attribute(name=map-attribute.myKey value="newValue") List write enhancements :write-attribute(name=list-attribute[1] value="new-element-value") :write-attribute(name=list-attribute.element-value value="new-element-value") Map read enhancements # return value of map-attribute with key "myKey" :read-attribute(name=map-attribute.myKey) List read enhancements # return element under index 5 of list-attribute :read-attribute(name=list-attribute[5]) Generic complex attributes enhancments # return property.subproperty from complex attribute :read-attribute(name=complex-attribute.property.subproperty) # return subproperty of 5th property from complex attribute :read-attribute(name=complex-attribute[5].subproperty) # set subproperty of 5th property of complex attribute :write-attribute(name=complex-attribute[5].subproperty, value="new-value") # set property.subproperty.subsubproperty of attribute "complext-attribute to "new-value" :write-attribute(name=complex-attribute.property.subproperty.subsubproperty, value="new-value") # return value of complex attribute with key "myKey" :read-attribute(name=complex-attribute.myKey) # return "property" of complex-attribute element on index 5 :read-attribute(name=complex-attribute[5].property) # return object of complex-attribute element on index 5 :read-attribute(name=complex-attribute[5]) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-455) Include additional sun.jdk dependencies

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-455?page=com.atlassian.jira.plugin... ] Tomaz Cerar commented on WFCORE-455: ------------------------------------ Great, as JDK6 is bit different and you mention problem on EAP as well. Just making sure JDK7+ fixes get to upstream. > Include additional sun.jdk dependencies > ---------------------------------------- > > Key: WFCORE-455 > URL: https://issues.jboss.org/browse/WFCORE-455 > Project: WildFly Core > Issue Type: Bug > Components: Modules > Affects Versions: 1.0.0.Alpha14 > Reporter: Mustafa Musaji > Assignee: David Lloyd > > Include the following out of the box for sun.jdk module > - for working with javax.sql.rowset.RowSetProvider > <path name="com/sun/rowset"/> > <path name="com/sun/rowset/providers"/> > - for working with java.lang.invoke.MethodHandleProxies > <path name="sun/invoke"/> > This affects EAP customers using CP releases when overlays override changes made in the original module.xml. For sun.jdk classes, the above packages should be included out of the box. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-665) Cannot extends rule from another one with the same package name

by Yacine Jaber (JIRA)

[ https://issues.jboss.org/browse/DROOLS-665?page=com.atlassian.jira.plugin... ] Yacine Jaber updated DROOLS-665: -------------------------------- Attachment: wod-drools-test.7z > Cannot extends rule from another one with the same package name > --------------------------------------------------------------- > > Key: DROOLS-665 > URL: https://issues.jboss.org/browse/DROOLS-665 > Project: Drools > Issue Type: Bug > Affects Versions: 6.0.0.Final > Reporter: Yacine Jaber > Assignee: Mark Proctor > Attachments: wod-drools-test.7z > > > When I extends a rule from another one with the same package, but into two differents .drl files. I got the following message : > Unable to resolve parent rule, please check that both rules are in the same package. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

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 2014