> marc fleury wrote:
> >> Okay, I'll not commit the empty defaultjboss.xml right now, but
> >> I don't understand your words about differential metadata.
> >> I looked at *MetaData sources and tried to deploy beans with empty
> >> jboss.xml - all works perfectly.
>
> mf> differential means that the EJX stuff needs to be capable of
> working from an
> mf> empty file and can add only what the user specified (not the
> ton of stuff it
> mf> used to). Yes the beans will deploy since the container
> metadata is already
> mf> differential. Does EJX work with an empty defaultjboss.xml ?
> I don't think
> mf> so... until that is changed at least.
> Yes, it does. I'll commit and you may check it yourself :-)
Ok but then it doesn't save any information back does it (it doesn't have
it) at least we have found a simple way to keep these files down to a
minimum :)
marc
>
> mf> amrc
>
> >>
> >> Best regards,
> >> Oleg
> >>
> >> >> -----Original Message-----
> >> >> From: [EMAIL PROTECTED]
> >> >> [mailto:[EMAIL PROTECTED]]On Behalf Of Oleg Nitz
> >> >> Sent: Thursday, October 05, 2000 9:51 AM
> >> >> To: jBoss Developer
> >> >> Subject: Re[2]: [jBoss-Dev] EJX
> >> >>
> >> >>
> >> >> marc fleury wrote:
> >> >> mf> Ok it is EJX that uses the old defaultjboss.xml.
> >> >>
> >> >> mf> Rickard can you update the stuff so that it uses
> standardjboss.xml?
> >> >> Wait a minute, defaultjboss.xml is copied as an original state of
> >> >> jboss.xml for the bean. I thing it should rather be
> almost-empty than
> >> >> to contain a copy of standardjboss.xml, because jBoss will take from
> >> >> standardjboss.xml all info that is not found in jboss.xml.
> >> >> I was going to commit such almost-empty defaultjboss.xml to CVS, but
> >> >> forgot about it. I'll do this after your consent.
> >> >>
> >> >> Best regards,
> >> >> Oleg
> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
> >>
>
>
>
>
> Best regards,
> Oleg
>
>
>
>
