Integrate proper ClassLoading spi into JBossAS
----------------------------------------------
Key: JBAS-5319
URL: http://jira.jboss.com/jira/browse/JBAS-5319
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: ClassLoading
Affects Versions: JBossAS-5.0.0.Beta4
Reporter: Adrian Brock
Assigned To: Adrian Brock
Fix For: JBossAS-5.0.0.CR1
Integrate the JBoss ClassLoading SPI in jboss-head
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Update to the new VFS classloader and resolve issues found
----------------------------------------------------------
Key: JBAS-5119
URL: http://jira.jboss.com/jira/browse/JBAS-5119
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: ClassLoading
Reporter: Adrian Brock
Assigned To: Adrian Brock
Fix For: JBossAS-5.0.0.Beta4
Change over to the new classloader in jboss head.
Please add any issues found as subtasks to links to this issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
BankBean does not implement its remote interface
------------------------------------------------
Key: EJBTHREE-1111
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1111
Project: EJB 3.0
Issue Type: Bug
Reporter: Adrian Brock
Assigned To: Adrian Brock
Fix For: AS 5.0.0.Beta3
The BankBean in the ejb3 testsuite doesn't implement its remote interface as required by spec (section 4.4)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Make DeploymentContext totally invisible
----------------------------------------
Key: JBMICROCONT-189
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-189
Project: JBoss MicroContainer
Issue Type: Task
Components: Deployment
Reporter: Adrian Brock
Assigned To: Adrian Brock
Fix For: JBossMC-2.0.0.GA
The DeploymentContext should be totally invisble
(possible still exposed for testing/debugging purposes as a deprecated method on the main deployer?)
There's still a number of places where it is showing up.
See the attached forum thread for a discussion.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.jboss.com/jira/browse/JBMICROCONT-71?page=all ]
Adrian Brock closed JBMICROCONT-71.
-----------------------------------
Resolution: Done
Closing this issue. The remaining issues are deferred until after 2.0.0.GA
> JMX Decorator for POJOs
> -----------------------
>
> Key: JBMICROCONT-71
> URL: http://jira.jboss.com/jira/browse/JBMICROCONT-71
> Project: JBoss MicroContainer
> Issue Type: Task
> Components: General
> Reporter: Adrian Brock
> Assigned To: Adrian Brock
> Fix For: JBossMC-2.0.0.Beta11
>
>
> Complete the prototype JMX Decorator for POJOs
> This needs to include links into JSR77 not just JMX
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.jboss.com/jira/browse/JBMICROCONT-77?page=all ]
Ales Justin resolved JBMICROCONT-77.
------------------------------------
Resolution: Done
This was done.
All the context states that already have target instantiated are possible candidates for KCCA callback.
> Make a proper version of the KernelControllerContextAware protocol
> ------------------------------------------------------------------
>
> Key: JBMICROCONT-77
> URL: http://jira.jboss.com/jira/browse/JBMICROCONT-77
> Project: JBoss MicroContainer
> Issue Type: Sub-task
> Components: Dependency
> Reporter: Adrian Brock
> Assigned To: Ales Justin
> Fix For: JBossMC-2.0.0.Beta11
>
>
> The KernelControllerContextAware needs completing such it allows hooks into
> all parts of the controller context lifecycle.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.jboss.com/jira/browse/JBMICROCONT-77?page=all ]
Ales Justin reassigned JBMICROCONT-77:
--------------------------------------
Assignee: Ales Justin
> Make a proper version of the KernelControllerContextAware protocol
> ------------------------------------------------------------------
>
> Key: JBMICROCONT-77
> URL: http://jira.jboss.com/jira/browse/JBMICROCONT-77
> Project: JBoss MicroContainer
> Issue Type: Sub-task
> Components: Dependency
> Reporter: Adrian Brock
> Assigned To: Ales Justin
> Fix For: JBossMC-2.0.0.Beta11
>
>
> The KernelControllerContextAware needs completing such it allows hooks into
> all parts of the controller context lifecycle.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Create a generic describing deployer for dependencies
-----------------------------------------------------
Key: JBMICROCONT-201
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-201
Project: JBoss MicroContainer
Issue Type: Sub-task
Components: Deployment
Reporter: Adrian Brock
There should be a generic describing stage deployer that looks
at all the metadata and creates dependencies from it,
either via an interface implemented by the metadata
or a annotation on the metadata describing an adapter/factory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.jboss.com/jira/browse/JBMICROCONT-26?page=all ]
Adrian Brock closed JBMICROCONT-26.
-----------------------------------
Resolution: Done
I'm closing this issue otherwise it is going to stay open forever.
Raise specific issues for other items.
> Implement Deployers for other IOC frameworks
> --------------------------------------------
>
> Key: JBMICROCONT-26
> URL: http://jira.jboss.com/jira/browse/JBMICROCONT-26
> Project: JBoss MicroContainer
> Issue Type: Task
> Components: Deployment
> Reporter: Adrian Brock
> Assigned To: Ales Justin
> Priority: Optional
> Fix For: JBossMC-2.0.0.Beta11
>
>
> As a sanity check for the IOC features we should implement deployers
> that translate other IOC xml into JBoss MC metadata.
> This will allow us to detect missing features we might want to support.
> It will also test these other IOC frameworks to see whether they are truely portable :-)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.jboss.com/jira/browse/JBMICROCONT-25?page=all ]
Adrian Brock updated JBMICROCONT-25:
------------------------------------
Fix Version/s: JBossMC.2.0.0.CR1
(was: JBossMC-2.0.0.Beta11)
> Configurator tidyup
> -------------------
>
> Key: JBMICROCONT-25
> URL: http://jira.jboss.com/jira/browse/JBMICROCONT-25
> Project: JBoss MicroContainer
> Issue Type: Task
> Components: Configurator
> Reporter: Adrian Brock
> Assigned To: Ales Justin
> Priority: Minor
> Fix For: JBossMC.2.0.0.CR1
>
>
> The Configurator api is largely being replaced by the JoinPointFactory api.
> There is still a usecase for some of the Configurator api as a convenience mechanism
> on top of the JoinPointFactory.
> This needs cleaning up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira