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.
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.
If you have a simple way to provide the default in the graph you talk about
that would be good. Let me know
marc
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Justin Forder
> Sent: Saturday, May 27, 2000 4:26 AM
> To: jBoss Developer
> Subject: Re: [jBoss-Dev] Providing defaults
>
>
> Hi
>
> marc fleury <[EMAIL PROTECTED]> writes
> >I moved the defaults in the ContainerConfiguration class, so
> that all type
> >have defaults...
> >It is not yet complete (jaws still dies due to some null pointer thingy).
> >will try to be done real soon now.
> >
> >I wan't to move on...
>
> Are these things I need to look at? I have been keeping my attention
> fixed inside JAWSPersistenceManager, and I believe that big structural
> improvements are possible, with no interface changes.
>
> caller
> |
> |
> V
> bean metadata<------JAWSPersistenceManager-------->entityBean
> |
> |
> V
> JDBC
>
> --
> Justin Forder
>
>
