Ah ha, that makes more sense now. Does this mean that if I want to create an all new implementation, I DO have to specify all the other internals of container-configuration? I was under the impression from the docs that these would be defaulted.
My problem is that I have some beans I want to be commit option A and some that are commit option B. I'd like to not have to create such a huge jboss.xml file in order to modify those certain beans but as far as I can tell there isn't another way. Thanks for the input. -Dennis On Tue, 2002-04-30 at 11:12, Sacha Labourey wrote: > In <container-name>, you have to write of the *actual* definition that you want to >override. Otherwise, JBoss won't be able to know which definition to override. > > Cheers, > > > Sacha > > > -----Message d'origine----- > > De : [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]De la part de Dennis > > Muhlestein > > Envoyé : mardi, 30 avril 2002 19:02 > > À : [EMAIL PROTECTED] > > Objet : Re: [JBoss-user] Custom Container Configuration in jboss.xml > > > > > > Let me rephrase the question. > > > > If I only want to create a new container-configuration with commit > > option A instead of B, do I have to include all the internals? The dtd > > refers to defaults on most of the options and specifies them as optional > > tags. > > > > I copied and pasted from standardjboss.xml to my jboss.xml and changed > > the one line but that seams kind of "klutzy". I would like to specify > > only the one line to differ. Most likely I'll have lots of beans and > > each one will need some customization to achieve optimum performance. I > > don't want to have to have a massive jboss.xml to accomplish this though > > if I don't have to. > > > > Right now, if I try with the configuration below, jboss > > croaks/groans/whines and the app is not deployed (I posted this as a bug > > too by the way) > > > > > <container-configuration> > > > <container-name>Commit A</container-name> > > > <commit-option>A</commit-option> > > > </container-configuration> > > > > Any comments? Someone with experience in this area? >
signature.asc
Description: This is a digitally signed message part
