>
> So I guess we're suggesting making all the other settings
> optional? That is, any setting you do not include has a default, but you
> may choose to override any individual setting?
That's correct
One of the things we are doing with sebastien is to provide a "default"
metadata structure that gets overwriten when you supply information.
Right now it is a bit of a "all or nothing". We have a default if you don't
provide stuff, but If you provide a overwritting setting you need to provide
the *whole* shebang with container conf and all and if you miss, you are
dead.
In short if you (you being the deployer) want to provide the JNDI name in
jboss.xml to be different from the ejb-ref name I would want just the
<bean>
<ejb-ref>The Static Name from the Bean developer</ejb-ref>
<jndi-name>The name in my run-time deployment</jndi-name>
</bean>
and that's it, nothing else in the file, since that is *all* you want to
change.
Thinking on the documentation, ken, I do believe that this (and the
datasource) as you point out in another mail do deserve a "step4- specifying
the datasource" "step5- specifying jndi names" since they deal with
jboss.xml and will be used. The "step *- advanced container configuration"
should still be at the end.
I need to make sure that the current code and the new metadata rewrite
support this. It is not very complicated to do afaik, we just need to do it.
We should be done within the week.
marc
>
> Aaron
>
>
>
