[Design of JCA on JBoss] - Re: We need move JCA metadata to jboss-metadata project
by jesper.pedersen
"jeff.zhang" wrote : I am working about JIRA JBAS 5752(Testing of JCA xml parsing). I think we should move JCA metadata model code to jboss-metadata project . There are ear, war, etc... J2EE spec model metadata description.
jboss-metadata would be the place. Please, coordinate this with Alexey/Emanuel in regards to the CR2 time frame. You should only move the code if the task can be completed in time. Adrian has put a lot of work into making this work for the TCK setup, so breaking any code is not an option.
The POJO implementation should depend on the metadata being in the jboss-metadata project -- or in a sub-project. We need to limit the dependencies to the AS code base - and hopefully end up with zero. AS should depend on the JCA POJO implementation.
"jeff.zhang" wrote : I also think we should refactor ra-xml, jbossra-xml parser from MultipleObjectModelFactoryDeployer to XB parser using JAXB annotation, is it right approach?
The same goes here - look it over and see if it can be completed in time.
We will get the requirements for this area from the JCA 1.6 specification once published, so the refactoring can/will be done as part of the POJO implementation.
We will fire off the POJO development once AS-5 has gone GA.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168419#4168419
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168419
15 years, 9 months
[Design the new POJO MicroContainer] - MC roadmap - 2.0.0.CR1/GA, Post Final, 3.x
by alesj
Few notes from recent MC meeting:
Work/issues needed to be resolved for MC 2.0.0.C1/GA:
Reflect:
* JoinFactory + explicit MetaData - Kabir & testing
* Release
MDR:
* Component MetaData - Kabir & testing
* Release
MAN:
* Scott's tasks
* Release
MicroContainer:
* Finalize API; ExecutionEnvironment in Controller - Ales
* MC-AOP-int issues - Kabir & testing
* Release
ClassLoading:
* URLs and ResourceVisitor (resolved)
* ResourceContext as interface (resolved)
* Release
Deployers:
* Types remove - Ales
* Structure Context - Adrian
* Annotation based structure - Ales
* Release
VFS:
* URLs creation optimization - Scott or Marko
* Lazy VirtualFileHandler - Marko
* File.getChildren opt (resolved)
* Performance testing - Adrian
* Release
Work after GA, still in 2.x:
Reflect:
* Finishing missing Javassist impls
* Testing
MDR:
* New scopes; thread, request, conversation
* Testing
MAN:
* JSR 77 / 88
MicroContainer:
* Error handling
* Concurrent deployments
* Tree state mode
* Policies + Scopes in MDR
* Valves, container construction
* Move annotations handling to separate project
* Update Spring-int, Guice-int against the latest external dependencies
ClassLoading:
* Finish validation
* OSGi testing
Deployers:
* OSGi deployment Service Registry
* Testing
* Describe deployment dependency deployer
* Graceful shutdown handling
VFS:
* JBoss Zip framework
OSGi:
* Finish facade impl
* Pass OSGi TCK
* Release new OSS OSGi compliant framework
Current MC 3.x ideas:
Reflect:
* Javassist integration; AOP, MDR, CL, Deployers
MDR:
* AOP/Kernel scoping
OSGi:
* Component model
* Context CL
* JEE + OSGi
Other issues:
MC's Reliance module serves as sandbox environment.
Current Drools integration should be kept up-to-date with the Drools project.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168413#4168413
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168413
15 years, 9 months