[JBoss JIRA] (JBOSGI-720) Complete support for HttpService on JBossWeb
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-720?page=com.atlassian.jira.plugin... ]
Thomas Diesler moved WFLY-1243 to JBOSGI-720:
---------------------------------------------
Project: JBoss OSGi (was: WildFly)
Key: JBOSGI-720 (was: WFLY-1243)
Workflow: jira (was: GIT Pull Request workflow )
Component/s: (was: OSGi)
> Complete support for HttpService on JBossWeb
> --------------------------------------------
>
> Key: JBOSGI-720
> URL: https://issues.jboss.org/browse/JBOSGI-720
> Project: JBoss OSGi
> Issue Type: Task
> Reporter: Thomas Diesler
> Labels: roadmap
>
> #1 Add support for MimeType, Content-Lenght, etc
> #2 Delegate authentication/authorisation to HttpContext
> #3 Add support for "/" root context
> #4 Make HttpService an optional capability
> #5 Make virtual host/port configurable
> This issue is complete when the TCK passes
--
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
12 years, 9 months
[JBoss JIRA] (JBOSGI-729) Allign deployment phases with OSGi terminology
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-729?page=com.atlassian.jira.plugin... ]
Thomas Diesler moved WFLY-1222 to JBOSGI-729:
---------------------------------------------
Project: JBoss OSGi (was: WildFly)
Key: JBOSGI-729 (was: WFLY-1222)
Workflow: jira (was: GIT Pull Request workflow )
Component/s: (was: OSGi)
(was: Server)
> Allign deployment phases with OSGi terminology
> ----------------------------------------------
>
> Key: JBOSGI-729
> URL: https://issues.jboss.org/browse/JBOSGI-729
> Project: JBoss OSGi
> Issue Type: Task
> Reporter: Thomas Diesler
>
> In OSGi we have
> * INSTALLED
> * RESOLVED
> * ACTIVE
> * UNINSTALLED
> It'd be useful to talk about modules and osgi bundles in the same jagon - i.e
> If a deployment is INSTALLED it has valid metadata
> If a deployment is RESOLVED it has Module/ClassLoader associated
> If a deployment is ACTIVE it can perform its normal operation
> If a deployment is UNINSTALLED it can be removed from the system
> The task here is mainly to rename/revisit the deployment phases
--
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
12 years, 9 months
[JBoss JIRA] (JBOSGI-726) Decouple naming & transaction from OSGi
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-726?page=com.atlassian.jira.plugin... ]
Thomas Diesler moved WFLY-1233 to JBOSGI-726:
---------------------------------------------
Project: JBoss OSGi (was: WildFly)
Key: JBOSGI-726 (was: WFLY-1233)
Workflow: jira (was: GIT Pull Request workflow )
Component/s: (was: OSGi)
> Decouple naming & transaction from OSGi
> ---------------------------------------
>
> Key: JBOSGI-726
> URL: https://issues.jboss.org/browse/JBOSGI-726
> Project: JBoss OSGi
> Issue Type: Task
> Reporter: Thomas Diesler
>
> Currently the naming & transaction subsystem register services on behalf of OSGi
> {code}
> [tdiesler@tdvaio jboss-as]$ git grep "\"xservice\""
> naming/src/main/java/org/jboss/as/naming/subsystem/NamingSubsystemOSGiService.java: ServiceName serviceName = ServiceName.of("jbosgi", "xservice", regi
> transactions/src/main/java/org/jboss/as/txn/service/TransactionManagerService.java: serviceBuilder.addAliases(ServiceName.of("jbosgi", "xservice", Tran
> transactions/src/main/java/org/jboss/as/txn/service/UserTransactionService.java: serviceBuilder.addAliases(ServiceName.of("jbosgi", "xservice", UserTra
> {code}
--
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
12 years, 9 months