All,
I am trying to understand the work that will be required to use
OWB to implement JSR 299 and JSR 330 for an application server.
I'll present my current understanding and ask some questions.
I've identified the following SPI interface packages and the
implementing classes found in the OWB source.
webbeans-impl: org.apache.webbeans.spi
Interfaces and implementations:
JNDIService
JNDIServiceEnterpriseImpl
JNDIServiceStaticImpl
LifeCycle
StandaloneLifeCycle
EnterpriseLifeCycle
TransactionService
TransactionServiceJndiImpl
TransactionServiceNonJTA
webbeans-impl: org.apache.webbeans.spi.conversation
Interfaces and implementations:
ConversationService
JSFConversationServiceImpl
webbeans-impl: org.apache.webbeans.spi.deployer
Interfaces and implementations:
MetaDataDiscoveryService
AbstractMetaDataDiscovery
EJBMetaDataDiscoveryImpl
MetaDataDiscoveryStandard
WarMetaDataDiscoveryImpl
webbeans-resource: org.apache.webbeans.resource.spi
Interfaces and implementations:
ResourceService
ResourceServiceImpl
OpenEjbResourceServiceImpl
Questions:
1. Have I identified all the SPI interfaces that need to be
implemented?
2. For an application server other than Geronimo, how useful is
the code in the following modules likely to be?
webbeans-jsf
webbeans-jms
webbeans-openejb
webbeans-geronimo
3. For test driven development, I'm thinking of using the two
TCKs for a test suite. Does this strategy seem reasonable?
4. How useful will webbeans-porting be in implementing a TCK
harness for another app server?
5. I believe that webbeans-tck has been deprecated, and the TCK
source is now found in the Geronimo repository. Is that correct?
Is that its official residence?
6. Is the atinject-tck the TCK for JSR 299? Is this the official
residence of that TCK?
I would very much appreciate specific answers and perhaps, if
necessary, a mini-tutorial of 2-3 paragraphs.
Thanks,
David
