December 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2612) The CLI should support property substitution for names of elements and not only for parameters

by Tom Fonteyne (JIRA)

[ https://issues.jboss.org/browse/WFLY-2612?page=com.atlassian.jira.plugin.... ] Tom Fonteyne updated WFLY-2612: ------------------------------- Description: My customer is using client side substitution in the CLI jboss-cli.xml: <resolve-parameter-values>true</resolve-parameter-values> This works fine for example with: /subsystem=datasources/data-source=oracleDS:add(connection-url=jdbc:oracle:thin:@server:1521:ora1, jndi-name=java:/jboss/${name}, driver-name=oracle) The "name" is provided in a property file at the command line for jboss-cli.sh This request is to extend this behaviour to allow for example: /subsystem=datasources/data-source=${datasourcename}:add(connection-url=jdbc:oracle:thin:@server:1521:ora1, jndi-name=java:/jboss/${name}, driver-name=oracle) In other words, have the actual element name be substituted as well based on a property value We know the easy workaround is to use bash embedded cli script, so the ${datasourcename} can be provided by a bash variable but it would be nice if the CLI could do that. was: My customer is using client side substitution in the CLI jboss-cli.xml: <resolve-parameter-values>true</resolve-parameter-values> This works fine for example with: /subsystem=datasources/data-source=oracleDS:add(connection-url=jdbc:oracle:thin:@server:1521:ora1, jndi-name=java:/jboss/${name}, driver-name=oracle) The "name" is provided in a property file at the command line for jboss-cli.sh This request is to extend this behaviour to allow for example: /subsystem=datasources/data-source=${datasourcename}:add(connection-url=jdbc:oracle:thin:@zen.usersys.redhat.com:1521:oracle, jndi-name=java:/jboss/${name}, driver-name=oracle) In other words, have the actual element name be substituted as well based on a property value We know the easy workaround is to use bash embedded cli script, so the ${datasourcename} can be provided by a bash variable but it would be nice if the CLI could do that. > The CLI should support property substitution for names of elements and not only for parameters > ---------------------------------------------------------------------------------------------- > > Key: WFLY-2612 > URL: https://issues.jboss.org/browse/WFLY-2612 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: CLI > Affects Versions: 8.0.0.Beta1 > Reporter: Tom Fonteyne > Assignee: Alexey Loubyansky > > My customer is using client side substitution in the CLI > jboss-cli.xml: > <resolve-parameter-values>true</resolve-parameter-values> > This works fine for example with: > /subsystem=datasources/data-source=oracleDS:add(connection-url=jdbc:oracle:thin:@server:1521:ora1, jndi-name=java:/jboss/${name}, driver-name=oracle) > The "name" is provided in a property file at the command line for jboss-cli.sh > This request is to extend this behaviour to allow for example: > /subsystem=datasources/data-source=${datasourcename}:add(connection-url=jdbc:oracle:thin:@server:1521:ora1, jndi-name=java:/jboss/${name}, driver-name=oracle) > In other words, have the actual element name be substituted as well based on a property value > We know the easy workaround is to use bash embedded cli script, so the ${datasourcename} can be provided by a bash variable but it would be nice if the CLI could do that. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2613) The CLI should support property substitution for names of elements and not only for parameters

by Tom Fonteyne (JIRA)

Tom Fonteyne created WFLY-2613: ---------------------------------- Summary: The CLI should support property substitution for names of elements and not only for parameters Key: WFLY-2613 URL: https://issues.jboss.org/browse/WFLY-2613 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: CLI Affects Versions: 8.0.0.Beta1 Reporter: Tom Fonteyne Assignee: Alexey Loubyansky My customer is using client side substitution in the CLI jboss-cli.xml: <resolve-parameter-values>true</resolve-parameter-values> This works fine for example with: /subsystem=datasources/data-source=oracleDS:add(connection-url=jdbc:oracle:thin:@server:1521:ora1, jndi-name=java:/jboss/${name}, driver-name=oracle) The "name" is provided in a property file at the command line for jboss-cli.sh This request is to extend this behaviour to allow for example: /subsystem=datasources/data-source=${datasourcename}:add(connection-url=jdbc:oracle:thin:@zen.usersys.redhat.com:1521:oracle, jndi-name=java:/jboss/${name}, driver-name=oracle) In other words, have the actual element name be substituted as well based on a property value We know the easy workaround is to use bash embedded cli script, so the ${datasourcename} can be provided by a bash variable but it would be nice if the CLI could do that. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2612) The CLI should support property substitution for names of elements and not only for parameters

by Tom Fonteyne (JIRA)

Tom Fonteyne created WFLY-2612: ---------------------------------- Summary: The CLI should support property substitution for names of elements and not only for parameters Key: WFLY-2612 URL: https://issues.jboss.org/browse/WFLY-2612 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: CLI Affects Versions: 8.0.0.Beta1 Reporter: Tom Fonteyne Assignee: Alexey Loubyansky My customer is using client side substitution in the CLI jboss-cli.xml: <resolve-parameter-values>true</resolve-parameter-values> This works fine for example with: /subsystem=datasources/data-source=oracleDS:add(connection-url=jdbc:oracle:thin:@server:1521:ora1, jndi-name=java:/jboss/${name}, driver-name=oracle) The "name" is provided in a property file at the command line for jboss-cli.sh This request is to extend this behaviour to allow for example: /subsystem=datasources/data-source=${datasourcename}:add(connection-url=jdbc:oracle:thin:@zen.usersys.redhat.com:1521:oracle, jndi-name=java:/jboss/${name}, driver-name=oracle) In other words, have the actual element name be substituted as well based on a property value We know the easy workaround is to use bash embedded cli script, so the ${datasourcename} can be provided by a bash variable but it would be nice if the CLI could do that. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2611) Support CDI injection in various JSF artifacts

by Tomas Remes (JIRA)

Tomas Remes created WFLY-2611: --------------------------------- Summary: Support CDI injection in various JSF artifacts Key: WFLY-2611 URL: https://issues.jboss.org/browse/WFLY-2611 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: CDI / Weld Reporter: Tomas Remes Assignee: Stuart Douglas If I understand correctly to the subchapter "5.4.1 JSF Managed Classes and Java EE Annotations" of JSF 2.2 specification, there should be opportunity to use a lot of (and not only) CDI annotations in various JSF artifacts (ActionListener, SystemEventListener, etc. - for full list, please see the spec). So far I tried locally this (will be filling the table during time): ||JSF artifact||CDI Injection|| |javax.el.ELResolver|| |javax.faces.application.ApplicationFactory|| |javax.faces.application.NavigationHandler|| |javax.faces.application.ResourceHandler|| |javax.faces.application.StateManager||| |javax.faces.component.visit.VisitContextFactory||| |javax.faces.context.ExceptionHandlerFactory||| |javax.faces.context.ExternalContextFactory||| |javax.faces.context.FacesContextFactory|works| |javax.faces.context.PartialViewContextFactory|| |javax.faces.event.ActionListener|works only when specified also in faces-config| |javax.faces.event.SystemEventListener|doesn't work| |javax.faces.lifecycle.ClientWindowFactory|| |javax.faces.lifecycle.LifecycleFactory|| |javax.faces.lifecycle.PhaseListener|| |javax.faces.render.RenderKitFactory|| |javax.faces.view.ViewDeclarationFactory|| |javax.faces.view.facelets.FaceletCacheFactory|| |javax.faces.view.facelets.FaceletFactory|| |javax.faces.view.facelets.TagHandlerDelegateFactory|| -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2610) Add the ability to take an external based password to the Vault tool

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-2610?page=com.atlassian.jira.plugin.... ] Ivo Studensky commented on WFLY-2610: ------------------------------------- https://github.com/istudens/wildfly/tree/WFLY-2610 > Add the ability to take an external based password to the Vault tool > -------------------------------------------------------------------- > > Key: WFLY-2610 > URL: https://issues.jboss.org/browse/WFLY-2610 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Scripts, Security > Affects Versions: 8.0.0.Beta1 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > > At the moment the Vault tool only supports plain text password as a parameter. With SECURITY-770 committed in it is also possible to configure the Vault to take an external password. Thus the Vault tool needs to support it too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2610) Add the ability to take an external based password to the Vault tool

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-2610?page=com.atlassian.jira.plugin.... ] Ivo Studensky commented on WFLY-2610: ------------------------------------- This is waiting for an upgrade of PicketBox to 4.0.20.Final. > Add the ability to take an external based password to the Vault tool > -------------------------------------------------------------------- > > Key: WFLY-2610 > URL: https://issues.jboss.org/browse/WFLY-2610 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Scripts, Security > Affects Versions: 8.0.0.Beta1 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > > At the moment the Vault tool only supports plain text password as a parameter. With SECURITY-770 committed in it is also possible to configure the Vault to take an external password. Thus the Vault tool needs to support it too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2610) Add the ability to take an external based password to the Vault tool

by Ivo Studensky (JIRA)

Ivo Studensky created WFLY-2610: ----------------------------------- Summary: Add the ability to take an external based password to the Vault tool Key: WFLY-2610 URL: https://issues.jboss.org/browse/WFLY-2610 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Scripts, Security Affects Versions: 8.0.0.Beta1 Reporter: Ivo Studensky Assignee: Ivo Studensky At the moment the Vault tool only supports plain text password as a parameter. With SECURITY-770 committed in it is also possible to configure the Vault to take an external password. Thus the Vault tool needs to support it too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2234) Infinispan subsystem transformers for 7.2.0

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2234?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-2234. ---------------------------- Resolution: Done > Infinispan subsystem transformers for 7.2.0 > ------------------------------------------- > > Key: WFLY-2234 > URL: https://issues.jboss.org/browse/WFLY-2234 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Kabir Khan > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1791) Unable to use Filter Expressions in filter-spec

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1791?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1791: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 982303|https://bugzilla.redhat.com/show_bug.cgi?id=982303] from ON_QA to VERIFIED > Unable to use Filter Expressions in filter-spec > ------------------------------------------------ > > Key: WFLY-1791 > URL: https://issues.jboss.org/browse/WFLY-1791 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CLI > Reporter: Emmanuel Hugonnet > Assignee: Alexey Loubyansky > Priority: Minor > Fix For: 8.0.0.Beta1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-363) Incremental compilation fails with declared types

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-363?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-363: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1037572|https://bugzilla.redhat.com/show_bug.cgi?id=1037572] from ASSIGNED to MODIFIED > Incremental compilation fails with declared types > ------------------------------------------------- > > Key: DROOLS-363 > URL: https://issues.jboss.org/browse/DROOLS-363 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.0.1.Final > > > Incremental compilation doesn't work if the newly added drl contains a declared type. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 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 December 2013