Yes, in fact we need to cover
1- JNDI name mapping, if you want something else than the ejb-ref name as
jndi
2- datasource (can't remember if it is there)
but we should take the container conf stuff out.
marc
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jeremy Clymer
> Sent: Saturday, August 05, 2000 10:23 AM
> To: jBoss Developer
> Subject: RE: [jBoss-Dev] Advanced container configuration
>
>
> Isn't the jboss.xml needed for resource management configuration, such as
> setting up a data source? Would this be considered an advanced
> configuration? Is there a way that the container configurations element
> could be removed from the beginners jboss.xml, but leave in the
> other stuff?
>
> Jeremy
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury
> > Sent: Friday, August 04, 2000 9:31 PM
> > To: jBoss Developer; jBoss
> > Cc: Ken Jenks
> > Subject: RE: [jBoss-Dev] Advanced container configuration
> >
> >
> > wow,
> >
> > I got where the problem was coming from it was the jboss.xml in the
> > "beginning jboss" online doco, this file doesn't specify the
> > stateful stuff
> > and yet is valid for the rest so we never default to the default
> > configurations. damn.
> >
> > I propose to take the "jboss.xml" file from the examples
> > altogether, so that
> > beginner users don't even muck with it and adding a last chapter called
> >
> > "Step 8 - Advanced container configurations"
> >
> > Where we take care of explaining the different plugins and what
> > they do and
> > how to add your own.
> >
> >
> > But all in all the jboss.xml should not be covered (at all ;-) in a
> > "beginning jboss" guide.
> >
> > I will try to fix it over the weekend.
> >
> > kind regards
> >
> > marc
> >
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury
> > > Sent: Friday, August 04, 2000 6:16 PM
> > > To: jBoss; jBoss Developer
> > > Subject: [jBoss-Dev] Advanced container configuration
> > >
> > >
> > > I was troubleshooting a problem due to a faulty jboss.xml file
> > > (missing one
> > > Stateful configuration in it) and I believe that the
> configuration file
> > > jboss.xml for jboss is overkill.
> > >
> > > The fact is that 95% users will *not* need to supply a jboss.xml
> > > describing
> > > in gory detail the kind of cache and pool they will need, the type of
> > > "ContainerInvoker" they need and the min and max sizes.
> > >
> > > In fact the "default files" already in do provide this and you
> > don't need
> > > the file almost always. Only if you are an advanced user or
> > sys-admin and
> > > you want to configure the container details differently for one
> > particular
> > > bean then supply your own jboss.xml file.
> > >
> > > If not, DON'T BOTHER. Don't EVEN supply a jboss.xml.
> > >
> > > I think this will *greatly* simplify the "user guide" as we
> only need to
> > > cover the jboss.xml in the following cases:
> > > 1- using 1.2.2 (invoker conf, although it could be automated)
> > > 2- advanced non-default cache
> > > 3- changing pool sizes
> > > 4- changing plugins (own TxManager etc etc)
> > >
> > > And that is all.
> > >
> > > This file can be tricky (one thing breaks, everything breaks) and
> > > I believe
> > > it will take care of 90% of our "bean not bound" problem
> reports that we
> > > have been seeing and are hard to troubleshoot.
> > >
> > > We probably will fix the doco accordingly...
> > > thanks
> > >
> > > marc
> > >
> > > ________________________
> > > Marc Fleury
> > > Chief Technology Officer
> > > Telkel, Inc.
> > > ________________________
> > >
> > >
> > >
> >
> >
>
>
>
