[JBoss JIRA] (WFLY-2611) Support CDI injection in various JSF artifacts
by Tomas Remes (JIRA)
[ https://issues.jboss.org/browse/WFLY-2611?page=com.atlassian.jira.plugin.... ]
Tomas Remes updated WFLY-2611:
------------------------------
Description:
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|works|
|javax.faces.render.RenderKitFactory||
|javax.faces.view.ViewDeclarationFactory||
|javax.faces.view.facelets.FaceletCacheFactory||
|javax.faces.view.facelets.FaceletFactory||
|javax.faces.view.facelets.TagHandlerDelegateFactory||
was:
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||
> 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|works|
> |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
10 years, 10 months
[JBoss JIRA] (WFLY-2612) The CLI should support property substitution for names of elements and not only for parameters
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFLY-2612?page=com.atlassian.jira.plugin.... ]
Alexey Loubyansky commented on WFLY-2612:
-----------------------------------------
This is already supported.
> 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
> Priority: Minor
>
> 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
10 years, 10 months
[JBoss JIRA] (WFLY-2612) The CLI should support property substitution for names of elements and not only for parameters
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFLY-2612?page=com.atlassian.jira.plugin.... ]
Alexey Loubyansky resolved WFLY-2612.
-------------------------------------
Resolution: Duplicate Issue
> 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
> Priority: Minor
>
> 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
10 years, 10 months
[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:
-------------------------------
Priority: Minor (was: Major)
> 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
> Priority: Minor
>
> 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
10 years, 10 months
[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
10 years, 10 months
[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
10 years, 10 months
[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
10 years, 10 months
[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
10 years, 10 months