marc fleury <[EMAIL PROTECTED]> wrote:
>Jaws dies because the metadata it needs come by default from the jaws.xml
>file... The dependency I want to remove is that one. No big deal just grudgy
>work...
>
>If you take the TestBeans.jar and deploy, it will deploy the stuff and die
>on jaws due to the TypeMapping missing.
If I understand you right, the TestBeans.jar is just lacking jBoss-2
compatible deployment descriptors.
Does ejboss (1.0) have a jaws.xml? Is it fully compatible (i.e. either
the same or a proper subset) with jBoss 2.0?
If so, it should be possible to make a jar that will deploy on either
ejboss (1.0) or jboss (2.0). If not, this needs to be fixed, either
by ensuring that they use same descriptor, or by introducing a jaws2.xml
for jboss 2.0.
>I will do it, if anything make sure the jaws.xml default is with the test
>beans. We need to remove the dependency to the graphic stuff IMHO.
Or get someone new up to speed on EJX maintenance & extension.
>
>If you have a simple way to provide the default in the graph you talk about
>that would be good. Let me know
Nope, sorry. Here's the graph, with the interfaces numbered:
caller
|
| (1)
(2) V (3)
bean metadata<------JAWSPersistenceManager-------->entityBean
|
| (4)
V
JDBC
You are working in the "bean metadata" space. I see you through
interface (2), which in principle is negotiable, but I am regarding that
interface as fixed (frozen) for now.
Interface (1) is fixed by the overall jBoss architecture.
Interface (3) is fixed by EJB.
Interface (4) is fixed by JDBC.
--
Justin Forder
