[JBoss JIRA] (AS7-3772) Regularize expression handling in the interface resources
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-3772:
-------------------------------------
Summary: Regularize expression handling in the interface resources
Key: AS7-3772
URL: https://issues.jboss.org/browse/AS7-3772
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Affects Versions: 7.1.0.Final
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.2.0.Alpha1
The interface resource code predates the evolution of the AttributeDefinition classes. Convert it over to that and make sure the xml parsers, operation step handlers and ParsedInterfaceCriteria follow the standard practices. Basically,
1) Use AD.parseAndSet() in the parsers. This will ensure parsing any criteria type that supports expressions will result in values of type EXPRESSION if appropriate.
2) Use AD.validateAndSet() in the MODEL stage of the OSH. This will ensure reading in input values from the CLI/console etc for any criteria type that supports expressions will result in values of type EXPRESSION if appropriate.
3) Pass the OperationContext into ParsedInterfaceCriteria and use AD.resolveModelAttribute() for resolution.
This may not be entirely possible, as interface criteria as a bit unusual types of attributes. But the general intent here should be followed.
--
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, 11 months
[JBoss JIRA] Created: (AS7-1976) WAR file using WAR_BUNDLES_JSF_IMPL embedded in an EAR file fails deployment
by Oren Samuel (JIRA)
WAR file using WAR_BUNDLES_JSF_IMPL embedded in an EAR file fails deployment
----------------------------------------------------------------------------
Key: AS7-1976
URL: https://issues.jboss.org/browse/AS7-1976
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.0.2.Final, 7.0.1.Final
Reporter: Oren Samuel
Assignee: Remy Maucherat
EAR file containing a WAR file that bundles Myfaces 1.2.7 fails deployment (trying to load JSF 2 libraries although WAR_BUNDLES_JSF_IMPL is set)
15:27:59,585 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.subunit."MyFacesTest.ear"."myfacesTest.war".INSTALL: org
.jboss.msc.service.StartException in service jboss.deployment.subunit."MyFacesTest.ear"."myfacesTest.war".INSTALL: Failed to process phase INSTALL of subdeployment "myfacesTest.war
" of deployment "MyFacesTest.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.0.2.Final.jar:7.0.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_21]
Caused by: java.lang.RuntimeException: Failed to load class com.sun.faces.config.ConfigureListener
at org.jboss.as.ee.component.deployers.EEClassConfigurationProcessor$1.compute(EEClassConfigurationProcessor.java:141)
at org.jboss.as.ee.component.deployers.EEClassConfigurationProcessor$1.compute(EEClassConfigurationProcessor.java:122)
at org.jboss.as.ee.component.LazyValue.get(LazyValue.java:40)
at org.jboss.as.ee.component.EEApplicationDescription.getClassConfiguration(EEApplicationDescription.java:183)
at org.jboss.as.ee.component.ComponentDescription.createConfiguration(ComponentDescription.java:153)
at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:70)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.0.2.Final.jar:7.0.2.Final]
... 5 more
Caused by: java.lang.ClassNotFoundException: com.sun.faces.config.ConfigureListener from [Module "deployment.MyFacesTest.ear.myfacesTest.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:191)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:361)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:333)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:310)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:103)
at java.lang.Class.forName0(Native Method) [:1.6.0_21]
at java.lang.Class.forName(Class.java:247) [:1.6.0_21]
at org.jboss.as.ee.component.deployers.EEClassConfigurationProcessor$1.compute(EEClassConfigurationProcessor.java:139)
... 11 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-2325) Get rid of reflection configuring the ProtocolHandler in WebConnectorService
by Kabir Khan (Created) (JIRA)
Get rid of reflection configuring the ProtocolHandler in WebConnectorService
----------------------------------------------------------------------------
Key: AS7-2325
URL: https://issues.jboss.org/browse/AS7-2325
Project: Application Server 7
Issue Type: Feature Request
Components: Web
Reporter: Kabir Khan
Assignee: Remy Maucherat
Fix For: 7.1.0.CR1
A lot of the set methods do
{code}
if (ssl.hasDefined(Constants.PASSWORD)) {
Method m = connector.getProtocolHandler().getClass().getMethod("setSSLPassword", String.class);
m.invoke(connector.getProtocolHandler(), ssl.get(Constants.PASSWORD).asString());
}
if (ssl.hasDefined(Constants.CERTIFICATE_KEY_FILE)) {
Method m = connector.getProtocolHandler().getClass().getMethod("setSSLCertificateKeyFile", String.class);
m.invoke(connector.getProtocolHandler(), ssl.get(Constants.CERTIFICATE_KEY_FILE).asString());
}
//etc.
{code}
The ProtocolHandler inteface does not expose them, so maybe they should go there or another common interface for configuring PH's
--
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, 11 months