[JBoss JIRA] (AS7-4642) mechanism to load tag libraries from module
by Ivica Loncar (JIRA)
Ivica Loncar created AS7-4642:
---------------------------------
Summary: mechanism to load tag libraries from module
Key: AS7-4642
URL: https://issues.jboss.org/browse/AS7-4642
Project: Application Server 7
Issue Type: Feature Request
Components: Class Loading, Web
Affects Versions: 7.1.1.Final
Reporter: Ivica Loncar
Assignee: David Lloyd
Priority: Critical
tag libraries are scanned only if they appear in jar inside WEB-INF/lib or are defined in tld under WEB-INF.
The simplest scenario to explain why this is a problem: portlet 2 defines standard portlet taglib, but the classes in this file come from concrete implementations. Currently I see no way to use 2 different portals in a portable way.
Please provide a way to notify a web application that module contains .tld.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (AS7-4090) Opimize organization and management of the Infinispan subsystem
by Richard Achmatowicz (JIRA)
Richard Achmatowicz created AS7-4090:
----------------------------------------
Summary: Opimize organization and management of the Infinispan subsystem
Key: AS7-4090
URL: https://issues.jboss.org/browse/AS7-4090
Project: Application Server 7
Issue Type: Task
Components: Clustering
Affects Versions: 7.1.0.Final
Reporter: Richard Achmatowicz
Assignee: Paul Ferraro
Fix For: 7.1.2.Final
There are a number of areas where the Infinispan subsystem is organizationally deficient:
- does not make use of ResourceDefinitions to (i) simplify the generation of DescriptionProviders and (ii) localize the definition of AttributeDefinitions
- handlers are in some cases written from scratch rather than subclassing helper handlers such as AbstractWriteAttributeHandler, AbstractAddStepHandler, AbstractRemoveStepHandler, etc.
- collections of services are defined monolithically, rather than in distinct units which makes stopping/restarting them error prone (c.f. CacheContainerAdd, CacheAdd install three or four services each with complex processing - stopping and restarting this in another handler is next to impossible)
- ServiceNames are not always easy to reconstruct
These issues make maintenance of the subsystem hard. These matters can be helped by:
- making use of ResourceDefinitions
- defining for each service X a static method installX(context, operation, model) and removeX(context, operation, model) which can be made use of in installServices(context, operation, model) and removeServices(operation, context, model)
- define the static method populate(), used to populate a model from an operation, which can be reused in populateModel(), creating describe operations, as well as other contexts
- define a static method installServices(context, operation, model) which can be used in performRuntime(), and in contexts where all services for a resource need to be stopped and restarted; similarly define removeServices(context, operation, model)
- make sure each ServiceName can be regenerated easily (c.f. regenerating JNDI names can involve model processing)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (AS7-5133) "Once a process is reloaded, always reloaded" exception when reloading AS7
by Galder Zamarreño (JIRA)
Galder Zamarreño created AS7-5133:
-------------------------------------
Summary: "Once a process is reloaded, always reloaded" exception when reloading AS7
Key: AS7-5133
URL: https://issues.jboss.org/browse/AS7-5133
Project: Application Server 7
Issue Type: Feature Request
Reporter: Galder Zamarreño
Assignee: Brian Stansberry
In a master build, once an server started in admin mode is reloaded, it throws:
{code}16:52:31,576 ERROR [org.jboss.msc.service] MSC00002: Invocation of listener "org.jboss.as.controller.operations.common.ProcessReloadHandler$1$1@16e3a921" failed: java.lang.AssertionError: Once a process is reloaded, always reloaded!
at org.jboss.as.controller.RunningModeControl.setReloaded(RunningModeControl.java:53) [jboss-as-controller-7.x.incremental.432.jar:7.x.incremental.432]
at org.jboss.as.server.operations.ServerProcessReloadHandler$1.doReload(ServerProcessReloadHandler.java:72)
at org.jboss.as.server.operations.ServerProcessReloadHandler$1.doReload(ServerProcessReloadHandler.java:63)
at org.jboss.as.controller.operations.common.ProcessReloadHandler$1$1.transition(ProcessReloadHandler.java:95) [jboss-as-controller-7.x.incremental.432.jar:7.x.incremental.432]
at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1416) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl.access$2700(ServiceControllerImpl.java:49) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1954) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_31]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_31]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_31]{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months