On Feb 27, 2007, at 5:55 AM, Rick McGuire wrote:
David Blevins wrote:
On Feb 23, 2007, at 7:08 AM, Dain Sundstrom wrote:
On Feb 23, 2007, at 5:06 AM, Rick McGuire wrote:
To do that part just implement the ModuleBuilderExtension
interface and you can hook into all phases of the
EjbModuleBuilder.
This is probably the part I have the most questions on. Based
on what I see in the two extensions that Geronimo currently has,
I *think* the corba extension will need to do the following:
1) In createModule(), handle merging of the default
environments if we have one. Should this be unconditional, or
should we make it conditional on the presence of TSSLinks as in
done in 1.2.
Conditional on the presence of the TSSLink seems optimal.
2) In addGBeans(), create the TSSLink GBeans as is currently
done in TSSLinkBuilder. djencks and I couldn't figure out where
we need to look to find the TSSLink plan entries. I'm guessing
we retrieve it from the Module somehow, but I'm not sure how or
in what form it will be in when retrieved.
We just need to add that data to the geronimo-openejb.xml schema,
which is available at EjbModule.getVendorDD(). In the v2 plan I
see that we have two different elements, tss and tss-link.
I'm about 99.9999% certain that tss was a very old element type
that was never deleted from the schema. The only one I'm aware is
still getting used is the tss-link, so that should be the only
thing that needs to be added. The tss-link element is used to hook
an ejb instance to the appropriate POA to export this as a CORBA
object. My experience with schema is pretty limited (i.e.,
approaching zero), so any assistance in that phase would be greatly
appreciated.
Ok. How about something like:
<tss-link ejb-name="" poa-name=""/>
Not sure if poa-name is really the right name (not my area of
expertise). And of course we can go with elements instead of
attributes, your choice. Let me know what you want for elements/
attributes and I'll throw it in today and get the data converted over
into it.
-David
