November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1961) Tab completion suggest all attributes for operations specific for list or map

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-1961: -------------------------------------------- Summary: Tab completion suggest all attributes for operations specific for list or map Key: WFCORE-1961 URL: https://issues.jboss.org/browse/WFCORE-1961 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-729) Provide an utility to perform Subject - SecurityIdentity conversions

by Stefan Guilhen (JIRA)

Stefan Guilhen created ELY-729: ---------------------------------- Summary: Provide an utility to perform Subject - SecurityIdentity conversions Key: ELY-729 URL: https://issues.jboss.org/browse/ELY-729 Project: WildFly Elytron Issue Type: Enhancement Components: API / SPI Affects Versions: 1.0.3.Final Reporter: Stefan Guilhen Assignee: Stefan Guilhen In WildFly there are subsystems that rely on Subject instances to fulfill their security requirements. We thus need an API to allow for the conversion of SecurityIdentity instances to Subject and vice versa. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1960) Get rid of attributes of type LIST of PROPERTY; use OBJECT of STRING

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1960?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1960: ------------------------------------- Attachment: rrd.txt > Get rid of attributes of type LIST of PROPERTY; use OBJECT of STRING > -------------------------------------------------------------------- > > Key: WFCORE-1960 > URL: https://issues.jboss.org/browse/WFCORE-1960 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Ken Wills > Fix For: 3.0.0.Beta1 > > Attachments: rrd.txt > > > A read-resource-description output of a standalone-full-ha.xml server (see attached) shows a couple attributes that are of type LIST, value-type PROPERTY. (Just text search for PROPERTY.) We should convert those to OBJECT, value-type STRING. Both represent a resource address. An object of string is equivalent to a LinkedHashMap<String, String>, with ordering based on insertion. So such a description is fine for a path address attribute. > I'd like to get rid of the notion of PROPERTY in our spec definition of how to describe attributes, parameters and value-types (https://docs.jboss.org/author/display/WFLY/Description+of+the+Management+...) so removing the only usage of it will help. > We should still accept PROPERTY as inputs when we can do conversion to the defined type. This is all about tightening up the spec to remove the not-really-necessary PROPERTY concept. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1960) Get rid of attributes of type LIST of PROPERTY; use OBJECT of STRING

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1960: ---------------------------------------- Summary: Get rid of attributes of type LIST of PROPERTY; use OBJECT of STRING Key: WFCORE-1960 URL: https://issues.jboss.org/browse/WFCORE-1960 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Ken Wills Fix For: 3.0.0.Beta1 A read-resource-description output of a standalone-full-ha.xml server (see attached) shows a couple attributes that are of type LIST, value-type PROPERTY. (Just text search for PROPERTY.) We should convert those to OBJECT, value-type STRING. Both represent a resource address. An object of string is equivalent to a LinkedHashMap<String, String>, with ordering based on insertion. So such a description is fine for a path address attribute. I'd like to get rid of the notion of PROPERTY in our spec definition of how to describe attributes, parameters and value-types (https://docs.jboss.org/author/display/WFLY/Description+of+the+Management+...) so removing the only usage of it will help. We should still accept PROPERTY as inputs when we can do conversion to the defined type. This is all about tightening up the spec to remove the not-really-necessary PROPERTY concept. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1959) Deploying an empty managed exploded deployment to server group in domain fails

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1959?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet moved JBEAP-6991 to WFCORE-1959: -------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-1959 (was: JBEAP-6991) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Domain Management (was: Domain Management) Affects Version/s: 3.0.0.Alpha11 (was: 7.1.0.DR5) (was: 7.1.0.DR6) (was: 7.1.0.DR7) > Deploying an empty managed exploded deployment to server group in domain fails > ------------------------------------------------------------------------------ > > Key: WFCORE-1959 > URL: https://issues.jboss.org/browse/WFCORE-1959 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Alpha11 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > Deploying an empty exploded deployment created on domain controller fails with the following: > {code} [domain@localhost:9990 /] /deployment=empty-deployment.jar:add(content=[{empty=true}]) > { > "outcome" => "success", > "result" => undefined, > "server-groups" => undefined > } > [domain@localhost:9990 /] /server-group=main-server-group/deployment=empty-deployment.jar:add() > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"main-server-group" => {"host" => {"master" => { > "server-one" => "WFLYSRV0201: Cannot have more than one of [bytes, input-stream-index, hash, url, empty]", > "server-two" => "WFLYSRV0201: Cannot have more than one of [bytes, input-stream-index, hash, url, empty]" > }}}}}}, > "rolled-back" => true, > "server-groups" => {"main-server-group" => {"host" => {"master" => { > "server-one" => {"response" => { > "outcome" => "failed", > "failure-description" => "WFLYSRV0201: Cannot have more than one of [bytes, input-stream-index, hash, url, empty]", > "rolled-back" => true > }}, > "server-two" => {"response" => { > "outcome" => "failed", > "failure-description" => "WFLYSRV0201: Cannot have more than one of [bytes, input-stream-index, hash, url, empty]", > "rolled-back" => true > }} > }}}} > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7523) Add hibernate-spatial to hibernate module

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-7523?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-7523: ------------------------------- Fix Version/s: (was: 10.2.0.Final) > Add hibernate-spatial to hibernate module > ----------------------------------------- > > Key: WFLY-7523 > URL: https://issues.jboss.org/browse/WFLY-7523 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Affects Versions: 10.1.0.Final > Environment: Linux / OpenJDK 8 / Wildfly 10.1.0.Final > Reporter: Dennis Gesker > Labels: hibernate_persistance_layer > > The use of GIS extensions is becoming more prevalent. It would be very helpful if org.hibernate:hibernate-spatial was added to the the hibernate module. > hibernate-spatial SEEMS to also require the following jars/packages : > org.hibernate:hibernate-spatial > org.geolatte:geolatte-geom > com.vividsolutions:jts-parent > So, jars would need to be added to modules/system/layers/base/org/hibernate/main and associated <resource-root> tags in module.xml > I believe <dependencies> would also require <module name="org.slf4j"/> entry > Note: The "Create Issue" page defaulted this item to "Major" but it is labeled as (FOR USE BY COMMITTERS ONLY) so I did not change it. I would have chosen "Minor" as this would be really useful but of course doesn't break or stop anything. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7523) Add hibernate-spatial to hibernate module

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-7523?page=com.atlassian.jira.plugin.... ] Scott Marlow reassigned WFLY-7523: ---------------------------------- Assignee: (was: Scott Marlow) > Add hibernate-spatial to hibernate module > ----------------------------------------- > > Key: WFLY-7523 > URL: https://issues.jboss.org/browse/WFLY-7523 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Affects Versions: 10.1.0.Final > Environment: Linux / OpenJDK 8 / Wildfly 10.1.0.Final > Reporter: Dennis Gesker > Labels: hibernate_persistance_layer > Fix For: 10.2.0.Final > > > The use of GIS extensions is becoming more prevalent. It would be very helpful if org.hibernate:hibernate-spatial was added to the the hibernate module. > hibernate-spatial SEEMS to also require the following jars/packages : > org.hibernate:hibernate-spatial > org.geolatte:geolatte-geom > com.vividsolutions:jts-parent > So, jars would need to be added to modules/system/layers/base/org/hibernate/main and associated <resource-root> tags in module.xml > I believe <dependencies> would also require <module name="org.slf4j"/> entry > Note: The "Create Issue" page defaulted this item to "Major" but it is labeled as (FOR USE BY COMMITTERS ONLY) so I did not change it. I would have chosen "Minor" as this would be really useful but of course doesn't break or stop anything. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1912) Redeploy deployment if all missing dependencies for deployment are corrected

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1912?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1912: ------------------------------------------ I changed this to Feature Request as it involves user interaction and documentation of that. > Redeploy deployment if all missing dependencies for deployment are corrected > ----------------------------------------------------------------------------- > > Key: WFCORE-1912 > URL: https://issues.jboss.org/browse/WFCORE-1912 > Project: WildFly Core > Issue Type: Feature Request > Components: Server > Reporter: Miroslav Novak > Assignee: Jason Greene > Labels: user_experience > > If deployment failed to deploy and later all missing dependencies for deployment are corrected then deployment would redeploy automatically. This behavior could be configurable. > For example if you deploy EJB which injects queue like: > {code} > @Resource(mappedName = "java:/jms/queue/OutQueue") > private Queue outQueue; > {code} > and administrator deploys queue later then EJB would automatically get redeployed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1912) Redeploy deployment if all missing dependencies for deployment are corrected

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1912?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1912: ------------------------------------- Issue Type: Feature Request (was: Enhancement) > Redeploy deployment if all missing dependencies for deployment are corrected > ----------------------------------------------------------------------------- > > Key: WFCORE-1912 > URL: https://issues.jboss.org/browse/WFCORE-1912 > Project: WildFly Core > Issue Type: Feature Request > Components: Server > Reporter: Miroslav Novak > Assignee: Jason Greene > Labels: user_experience > > If deployment failed to deploy and later all missing dependencies for deployment are corrected then deployment would redeploy automatically. This behavior could be configurable. > For example if you deploy EJB which injects queue like: > {code} > @Resource(mappedName = "java:/jms/queue/OutQueue") > private Queue outQueue; > {code} > and administrator deploys queue later then EJB would automatically get redeployed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7524) Add Hibernate-Spatial to WildFly Feature Pack

by Dennis Gesker (JIRA)

Dennis Gesker created WFLY-7524: ----------------------------------- Summary: Add Hibernate-Spatial to WildFly Feature Pack Key: WFLY-7524 URL: https://issues.jboss.org/browse/WFLY-7524 Project: WildFly Issue Type: Feature Request Affects Versions: 10.1.0.Final Environment: Linux / OpenJDK 8 / WildFly 10.1.0.Final Reporter: Dennis Gesker Assignee: Jason Greene Fix For: 10.2.0.Final If possible kindly add jars need to make use of hibernate-spatial to WildFly-Feature-Pack org.hibernate:hibernate-spatial org.geolatte:geolatte-geom com.vividsolutions:jts-parent BTW, thank you for this package. It saves a HUGE amount of time with dependencies. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 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 November 2016