[JBoss JIRA] (AS7-5101) Support unmanaged deployments in the console
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-5101:
-------------------------------------
Summary: Support unmanaged deployments in the console
Key: AS7-5101
URL: https://issues.jboss.org/browse/AS7-5101
Project: Application Server 7
Issue Type: Feature Request
Components: Console
Reporter: Brian Stansberry
Assignee: Heiko Braun
The AS supports the notion of "unmanaged" deployments, where, rather than uploading the deployment content to the server, which then serves it from its internal content repo, instead the filesystem path to the content is provided and the content is served directly from that location.
This mechanism is particularly helpful with exploded deployments; it's what the filesystem deployment scanner uses when it detects an exploded deployment.
The CLI supports this via the --unmanaged flag that can be passed to the "deploy" command.
The console should expose this functionality as well.
If this were used in a managed domain, it's the responsibility of the user to ensure that the content is available at the provided path on all relevant hosts in the domain. EAP itself takes no responsibility for managing that content.
--
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, 9 months
[JBoss JIRA] (AS7-4615) Define a database of system modules
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-4615:
-----------------------------------
Summary: Define a database of system modules
Key: AS7-4615
URL: https://issues.jboss.org/browse/AS7-4615
Project: Application Server 7
Issue Type: Task
Components: OSGi, Server
Reporter: Thomas Diesler
Assignee: Thomas Diesler
The OSGi configuration supports ModuleIdentifiers. So for example
{code}
<capability name="javax.transaction.api"/>
{code}
references the JTA API module. This actually delegates to the repository implementations which in turn delegates to the ModuleIdentityArtifactProvider.
If the AppServer supports the notion of multiple directories where modules can get loaded from, the ServerEnvironment should reflect that properly. I cannot just load a module on trial/error basis because we use the Repository for impact ananlysis. i.e. Find the modules/bundles that provide the transitive set of capabilities for a given set of requirements (without modifying the runtime).
--
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, 9 months
[JBoss JIRA] (AS7-5051) Allow EE deployments to define dependency requirements with OSGi metadata
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-5051:
-----------------------------------
Summary: Allow EE deployments to define dependency requirements with OSGi metadata
Key: AS7-5051
URL: https://issues.jboss.org/browse/AS7-5051
Project: Application Server 7
Issue Type: Task
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
This essentially means that you can put OSGi metadata into an EE deployment manifest, which essentially makes it an OSGi bundle.
Deployment unit processing should be such that the EE bundle gets resolved according to it's defined capabilities/requirements. Subsystem processors should not need to care whether the Module was created as a result of OSGi resolution or by the ModuleSpecProcessor.
This task is complete when we can do this with the EE core technologies (i.e. webapp, ejb3, cdi)
--
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, 9 months
[JBoss JIRA] (AS7-5437) Failed to load messaging connections
by Heiko Braun (JIRA)
Heiko Braun created AS7-5437:
--------------------------------
Summary: Failed to load messaging connections
Key: AS7-5437
URL: https://issues.jboss.org/browse/AS7-5437
Project: Application Server 7
Issue Type: Feature Request
Reporter: Heiko Braun
profile = full
{noformat}
[ERROR] java.lang.IllegalArgumentException
[ERROR] at org.jboss.dmr.client.ModelValue.asObject(ModelValue.java:98)
[ERROR] at org.jboss.dmr.client.ModelNode.asObject(ModelNode.java:252)
[ERROR] at org.jboss.as.console.client.shared.subsys.messaging.LoadJMSCmd$1.onSuccess(LoadJMSCmd.java:59)
[ERROR] at org.jboss.as.console.client.shared.subsys.messaging.LoadJMSCmd$1.onSuccess(LoadJMSCmd.java:1)
{noformat}
--
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, 9 months