Aaron Mulder wrote:
Is it true that the DD information will now be specific to OpenEJB, Tomcat, Jetty, etc? That each module will provide its own DConfigBeans, and use own DDs, etc.?
I believe this is necessary yes.
We will make available a sub-schema that the modules can include if they chose for common elements - just like the way the standard DDs include the j2ee schema. For example, a module can use the common sub-schema and ENCHelper to handle all the ENC entries.
For more complex configurations, I believe that there will need to be module specific elements that would not fit in a unified global DD. It may not be an issue for the web modules as Greg Wilkins believes one common one will be adequate. However, modules for EJB or Connector are likely to have many more vendor specific elements - think of the issues with defining a common schema for CMP between OpenEJB and JOnAS.
So the architecture is: * deployment provides sub-schemas and DConfigBeans that other modules can use * modules decide whether to use deployment's or their own * modules are free to add whatever they like to the schema as they are in control
-- Jeremy
