[JBoss JIRA] (AS7-6334) Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/AS7-6334?page=com.atlassian.jira.plugin.s... ]
Jeff Mesnil updated AS7-6334:
-----------------------------
Description:
Task to track the work we've all been doing on expressions/transformers.
See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
2) Basic transformation testing against 7.1.2 and 7.1.3
3) Reject-expression testing against 7.1.2 and 7.1.3
Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
Please edit this description and put an OK after the subsystem name to indicate it's good to go.
clustering/jgroups
clustering/infinispan
cmp
configadmin
connector
deployment-scanner
ee
ee-deployment
ejb3
jacorb
jaxr OK
jaxrs - nothing to do, empty subsystem
jdr - nothing to do, empty subsystem
jmx
jpa
jsf
jsr77 - nothing to do, empty subsystem
logging
mail
messaging - PR https://github.com/jbossas/jboss-as/pull/3887
modcluster
naming
osgi
pojo - nothing to do, empty subsystem
remoting - PR: https://github.com/jbossas/jboss-as/pull/3882
sar - nothing to do, empty subsystem
security
threads
transactions (just needs AS7-6336)
web
webservices
weld - nothing to do, empty subsystem
xts
was:
Task to track the work we've all been doing on expressions/transformers.
See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
2) Basic transformation testing against 7.1.2 and 7.1.3
3) Reject-expression testing against 7.1.2 and 7.1.3
Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
Please edit this description and put an OK after the subsystem name to indicate it's good to go.
clustering/jgroups
clustering/infinispan
cmp
configadmin
connector
deployment-scanner
ee
ee-deployment
ejb3
jacorb
jaxr OK
jaxrs - nothing to do, empty subsystem
jdr - nothing to do, empty subsystem
jmx
jpa
jsf
jsr77 - nothing to do, empty subsystem
logging
mail
messaging WIP
modcluster
naming
osgi
pojo - nothing to do, empty subsystem
remoting - PR: https://github.com/jbossas/jboss-as/pull/3882
sar - nothing to do, empty subsystem
security
threads
transactions (just needs AS7-6336)
web
webservices
weld - nothing to do, empty subsystem
xts
> Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6334
> URL: https://issues.jboss.org/browse/AS7-6334
> Project: Application Server 7
> Issue Type: Task
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 7.2.0.Alpha1
>
>
> Task to track the work we've all been doing on expressions/transformers.
> See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
> 1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
> 2) Basic transformation testing against 7.1.2 and 7.1.3
> 3) Reject-expression testing against 7.1.2 and 7.1.3
> Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
> Please edit this description and put an OK after the subsystem name to indicate it's good to go.
> clustering/jgroups
> clustering/infinispan
> cmp
> configadmin
> connector
> deployment-scanner
> ee
> ee-deployment
> ejb3
> jacorb
> jaxr OK
> jaxrs - nothing to do, empty subsystem
> jdr - nothing to do, empty subsystem
> jmx
> jpa
> jsf
> jsr77 - nothing to do, empty subsystem
> logging
> mail
> messaging - PR https://github.com/jbossas/jboss-as/pull/3887
> modcluster
> naming
> osgi
> pojo - nothing to do, empty subsystem
> remoting - PR: https://github.com/jbossas/jboss-as/pull/3882
> sar - nothing to do, empty subsystem
> security
> threads
> transactions (just needs AS7-6336)
> web
> webservices
> weld - nothing to do, empty subsystem
> xts
--
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
13 years, 3 months
[JBoss JIRA] (AS7-6305) ModuleClassLoader breaks Aspect-J non-load-time-weaving aspects
by jarkko rantavuori (JIRA)
[ https://issues.jboss.org/browse/AS7-6305?page=com.atlassian.jira.plugin.s... ]
jarkko rantavuori edited comment on AS7-6305 at 1/16/13 3:24 AM:
-----------------------------------------------------------------
Ok, I found out what I needed to do - to add "Dependencies: org.jboss.ironjacamar.jdbcadapters" in the manifest. Then it works. I don't know from where I should've got that information - found the module name via debugger inspection of the classloader used.
was (Author: jrantav):
Ok, I found out what I needed to do - to add "Dependencies: org.jboss.ironjacamar.jdbcadapters" in the manifest. Then it works. I don't know from where I would've got that information.
> ModuleClassLoader breaks Aspect-J non-load-time-weaving aspects
> ----------------------------------------------------------------
>
> Key: AS7-6305
> URL: https://issues.jboss.org/browse/AS7-6305
> Project: Application Server 7
> Issue Type: Bug
> Components: Class Loading, Web
> Affects Versions: 7.1.1.Final, 7.2.0.Alpha1
> Environment: Windows 7
> Reporter: jarkko rantavuori
> Assignee: David Lloyd
> Attachments: MyMethodTrace.java, MyMethodTraceAspect.java, spring-app-aop-datasource-1.0.0-BUILD-SNAPSHOT.war, spring-mvc-aop-datasource-app.zip
>
>
> Special measures need to be taken for load-time-weaving with aspects, but using them without load-time weaving works normally OOB. However, if this kind of Spring configuration is used:
> <!-- Test to get a data source -->
> <jee:jndi-lookup id="dataSource" jndi-name="jboss/datasources/ExampleDS"/>
> <!-- AOP part -->
> <bean id="methodTraceAspect" class="fi.eis.applications.jboss.poc.gemini.spring.aop.support.api.MyMethodTraceAspect"/>
> <aop:aspectj-autoproxy />
> <!-- end AOP -->
> <bean class="fi.eis.applications.controllers.HomeController">
> <constructor-arg ref="dataSource" />
> </bean>
> JBoss tries to use methodTraceAspect also on the data source. Data source is loaded by ModuleClassLoader that in has only visibility to org.jboss.jca.adapters* classes (confirmed with a debugger), so it cannot find the aspect class anymore, making aspect-j throw org.aspectj.weaver.reflect.ReflectionWorld$ReflectionWorldException: warning can't determine implemented interfaces of missing type
> fi.eis.applications.jboss.poc.gemini.spring.aop.support.api.MyMethodTraceAspect [Xlint:cantFindType].
> This has large problems in bigger applications, where general AOP pointcuts are used - no jboss-module stuff can be used as beans, anywhere. I'm aware of no workaround for this.
--
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
13 years, 3 months
[JBoss JIRA] (AS7-6305) ModuleClassLoader breaks Aspect-J non-load-time-weaving aspects
by jarkko rantavuori (JIRA)
[ https://issues.jboss.org/browse/AS7-6305?page=com.atlassian.jira.plugin.s... ]
jarkko rantavuori commented on AS7-6305:
----------------------------------------
Ok, I found out what I needed to do - to add "Dependencies: org.jboss.ironjacamar.jdbcadapters" in the manifest. Then it works. I don't know from where I would've got that information.
> ModuleClassLoader breaks Aspect-J non-load-time-weaving aspects
> ----------------------------------------------------------------
>
> Key: AS7-6305
> URL: https://issues.jboss.org/browse/AS7-6305
> Project: Application Server 7
> Issue Type: Bug
> Components: Class Loading, Web
> Affects Versions: 7.1.1.Final, 7.2.0.Alpha1
> Environment: Windows 7
> Reporter: jarkko rantavuori
> Assignee: David Lloyd
> Attachments: MyMethodTrace.java, MyMethodTraceAspect.java, spring-app-aop-datasource-1.0.0-BUILD-SNAPSHOT.war, spring-mvc-aop-datasource-app.zip
>
>
> Special measures need to be taken for load-time-weaving with aspects, but using them without load-time weaving works normally OOB. However, if this kind of Spring configuration is used:
> <!-- Test to get a data source -->
> <jee:jndi-lookup id="dataSource" jndi-name="jboss/datasources/ExampleDS"/>
> <!-- AOP part -->
> <bean id="methodTraceAspect" class="fi.eis.applications.jboss.poc.gemini.spring.aop.support.api.MyMethodTraceAspect"/>
> <aop:aspectj-autoproxy />
> <!-- end AOP -->
> <bean class="fi.eis.applications.controllers.HomeController">
> <constructor-arg ref="dataSource" />
> </bean>
> JBoss tries to use methodTraceAspect also on the data source. Data source is loaded by ModuleClassLoader that in has only visibility to org.jboss.jca.adapters* classes (confirmed with a debugger), so it cannot find the aspect class anymore, making aspect-j throw org.aspectj.weaver.reflect.ReflectionWorld$ReflectionWorldException: warning can't determine implemented interfaces of missing type
> fi.eis.applications.jboss.poc.gemini.spring.aop.support.api.MyMethodTraceAspect [Xlint:cantFindType].
> This has large problems in bigger applications, where general AOP pointcuts are used - no jboss-module stuff can be used as beans, anywhere. I'm aware of no workaround for this.
--
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
13 years, 3 months
[JBoss JIRA] (AS7-6340) Vault usage in a master-slave setup in AS7/EAP6
by Roland Räz (JIRA)
[ https://issues.jboss.org/browse/AS7-6340?page=com.atlassian.jira.plugin.s... ]
Roland Räz commented on AS7-6340:
---------------------------------
In the JBoss domain mode, dmr exposed credential management should be provided. The management of the credentials would be on domain instead of host level. The management (add, change, remove) of credentials should be possible while the domain and the servers are running.
JBoss could use internally a single vault per domain. One possibility would be that JBoss distributes on each update the vault to all hosts. Another approach would be to rewrite the implementation to use the domain configuration file (used as a replacement for Shared.dat & ENC.dat) files) as backend and expect the same keystore (for the encryption key) on all hosts.
> Vault usage in a master-slave setup in AS7/EAP6
> -----------------------------------------------
>
> Key: AS7-6340
> URL: https://issues.jboss.org/browse/AS7-6340
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Hisanobu Okuda
> Assignee: Anil Saldhana
>
> In domain mode, you need to copy over the vault files(keystore, Shared.dat, ENC.dat) to each machine within the domain. This is a very bad solution when your security policy requires password updates frequently.
--
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
13 years, 3 months
[JBoss JIRA] (AS7-6341) EJB2 CMP - 'JBAS014172: Instance not found in cache' after remove and recreate an entity in the same Tx
by Wolf-Dieter Fink (JIRA)
Wolf-Dieter Fink created AS7-6341:
-------------------------------------
Summary: EJB2 CMP - 'JBAS014172: Instance not found in cache' after remove and recreate an entity in the same Tx
Key: AS7-6341
URL: https://issues.jboss.org/browse/AS7-6341
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.3.Final (EAP)
Reporter: Wolf-Dieter Fink
Assignee: Wolf-Dieter Fink
Priority: Minor
If an entity is removed and new created within the same transaction the 'afterCompletition' procedure try to sync it twice.
It looks like that the entity is registered twice in this case.
The Exception is shown in the server.log, nevertheless the transactions and method execution will be succeed.
The following Exception can be safely ignored.
08:17:10,005 ERROR [org.jboss.as.ejb3] (EJB default - 4) JBAS014138: Exception releasing entity: java.lang.IllegalStateException: JBAS014172: Instance [org.jboss.as.cmp.component.CmpEntityBeanComponentInstance@31b489ae] not found in cache
at org.jboss.as.ejb3.component.entity.entitycache.ReferenceCountingEntityCache.release(ReferenceCountingEntityCache.java:86) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanSynchronizationInterceptor.releaseInstance(EntityBeanSynchronizationInterceptor.java:154) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanSynchronizationInterceptor.access$200(EntityBeanSynchronizationInterceptor.java:56) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanSynchronizationInterceptor$EntityBeanSynchronization.afterCompletion(EntityBeanSynchronizationInterceptor.java:219) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96)
at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:402)
at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:103)
at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162)
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1165)
at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126)
at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:91) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:252) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:315) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:214) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:79) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$1.processInvocation(EjbExceptionTransformingInterceptorFactories.java:65) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:65) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:321) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:69) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:202) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_09-icedtea]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_09-icedtea]
at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_09-icedtea]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09-icedtea]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09-icedtea]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
--
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
13 years, 3 months
[JBoss JIRA] (AS7-6340) Vault usage in a master-slave setup in AS7/EAP6
by Hisanobu Okuda (JIRA)
Hisanobu Okuda created AS7-6340:
-----------------------------------
Summary: Vault usage in a master-slave setup in AS7/EAP6
Key: AS7-6340
URL: https://issues.jboss.org/browse/AS7-6340
Project: Application Server 7
Issue Type: Feature Request
Components: Security
Affects Versions: 7.1.3.Final (EAP)
Reporter: Hisanobu Okuda
Assignee: Anil Saldhana
In domain mode, you need to copy over the vault files(keystore, Shared.dat, ENC.dat) to each machine within the domain. This is a very bad solution when your security policy requires password updates frequently.
--
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
13 years, 3 months
[JBoss JIRA] (AS7-6120) Expand support for System Property substitution
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6120?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry commented on AS7-6120:
---------------------------------------
Jeff, could you have a look at the various 'entries' attributes in messaging?
In a standalone server it looks like those could support expressions (and we allow them from jndi names elsewhere in the AS). Biggest question is how big of a PITA it would be to add the transformation and testing thereof.
> Expand support for System Property substitution
> -----------------------------------------------
>
> Key: AS7-6120
> URL: https://issues.jboss.org/browse/AS7-6120
> Project: Application Server 7
> Issue Type: Task
> Components: Domain Management
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Jimmy Wilson
> Assignee: Brian Stansberry
> Priority: Blocker
> Labels: eap-6.1-prd, rhq
> Fix For: 7.2.0.Alpha1
>
> Attachments: expressions.ods
>
>
> Audit the core AS and all subsystems shipped in the AS distribution for suport for expression in management resource attributes.
> The basic philosophy toward expressions in previous releases was to only push devs to add support if there was a clear important use case. Devs could choose to add support beyond that, but we wouldn't push that. This JIRA and PRODMGT-195 from which it is derived reflects a change in philosophy. Now the philosophy is to support expressions unless the dev foresees a technical or future compatibility problem arising from doing so.
> This task DOES NOT advocate adding expression support to attributes that represent references to other model elements. Such references may prove problematic in the future and should not be added. We already have some model ref attributes that support expressions; this task DOES NOT advocate removing such support, unless the support has never been provided in a Final release (i.e. it was added during 7.2 development.)
--
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
13 years, 3 months
[JBoss JIRA] (AS7-6120) Expand support for System Property substitution
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6120?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6120:
----------------------------------
Attachment: expressions.ods
> Expand support for System Property substitution
> -----------------------------------------------
>
> Key: AS7-6120
> URL: https://issues.jboss.org/browse/AS7-6120
> Project: Application Server 7
> Issue Type: Task
> Components: Domain Management
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Jimmy Wilson
> Assignee: Brian Stansberry
> Priority: Blocker
> Labels: eap-6.1-prd, rhq
> Fix For: 7.2.0.Alpha1
>
> Attachments: expressions.ods
>
>
> Audit the core AS and all subsystems shipped in the AS distribution for suport for expression in management resource attributes.
> The basic philosophy toward expressions in previous releases was to only push devs to add support if there was a clear important use case. Devs could choose to add support beyond that, but we wouldn't push that. This JIRA and PRODMGT-195 from which it is derived reflects a change in philosophy. Now the philosophy is to support expressions unless the dev foresees a technical or future compatibility problem arising from doing so.
> This task DOES NOT advocate adding expression support to attributes that represent references to other model elements. Such references may prove problematic in the future and should not be added. We already have some model ref attributes that support expressions; this task DOES NOT advocate removing such support, unless the support has never been provided in a Final release (i.e. it was added during 7.2 development.)
--
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
13 years, 3 months
[JBoss JIRA] (AS7-6120) Expand support for System Property substitution
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6120?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6120:
----------------------------------
Attachment: (was: expressions.ods)
> Expand support for System Property substitution
> -----------------------------------------------
>
> Key: AS7-6120
> URL: https://issues.jboss.org/browse/AS7-6120
> Project: Application Server 7
> Issue Type: Task
> Components: Domain Management
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Jimmy Wilson
> Assignee: Brian Stansberry
> Priority: Blocker
> Labels: eap-6.1-prd, rhq
> Fix For: 7.2.0.Alpha1
>
> Attachments: expressions.ods
>
>
> Audit the core AS and all subsystems shipped in the AS distribution for suport for expression in management resource attributes.
> The basic philosophy toward expressions in previous releases was to only push devs to add support if there was a clear important use case. Devs could choose to add support beyond that, but we wouldn't push that. This JIRA and PRODMGT-195 from which it is derived reflects a change in philosophy. Now the philosophy is to support expressions unless the dev foresees a technical or future compatibility problem arising from doing so.
> This task DOES NOT advocate adding expression support to attributes that represent references to other model elements. Such references may prove problematic in the future and should not be added. We already have some model ref attributes that support expressions; this task DOES NOT advocate removing such support, unless the support has never been provided in a Final release (i.e. it was added during 7.2 development.)
--
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
13 years, 3 months
[JBoss JIRA] (AS7-4917) paths need to allow expressions in its 'path' attribute
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-4917?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry resolved AS7-4917.
-----------------------------------
Resolution: Done
> paths need to allow expressions in its 'path' attribute
> -------------------------------------------------------
>
> Key: AS7-4917
> URL: https://issues.jboss.org/browse/AS7-4917
> Project: Application Server 7
> Issue Type: Sub-task
> Components: Logging
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Tom Fonteyne
> Assignee: Brian Stansberry
> Fix For: 7.2.0.Alpha1
>
>
> The "paths" section should allow expressions for "path" elements
> Rationale is the fact that customers often want the log files to be send to another directory "outside" of the JBoss directory.
> <periodic-rotating-file-handler name="FILE">
> ...
> <file relative-to="jboss.server.log.dir" path="server.log"/>
> You can change the above and hardcode to : <file path="/logs/jboss/server.log"/>
> but that means that as soon as you have two servers on the same machine, using the same profile, they will write to a single logfile.
> The "file"s "path" attribute does not allow expressions; this RFE is however not for this attribute.
> As relative-to="jboss.server.log.dir" can use self-defined names paths, we looked at the "paths" section.
> <paths>
> <path name="my.log" path="/logs/jboss/${my.system.propery}"/>
> </paths>
> but as it turns out, the "path" attribute of the "path" tag also does not allow expressions, and the above entry fails.
> Hence: please allow the "path" attribute of the "path" tag to allow expressions so that the above "paths" example works.
> Note that we consider this "Major" as customer do/want this functionality often.
--
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
13 years, 3 months