> -----Original Message-----
> From: Jason Dillon [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 20, 2002 5:04 PM
> To: Bill Burke
> Cc: Francisco Reverbel; marc fleury;
> [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] Multiple server configurations
>
>
> >
> >
> >This is already the case, Jason. Invokers are configured as an MBean.
> >standardjboss.xml binds the ProxyFactory to the container. Implicitly, a
> >default invoker is bound to the container. You can bind your
> own invoker to
> >the container by specifying <home-invoker> or <bean-invoker>
> with an MBean
> >name in jboss.xml.
> >
>
> Just for my own clarity, these can be specified with out having to put
> in the entire container config?
>
> It was my impression that you need to specify the entire container
> config... though I don't know if that has changed in 3.x.
>
You do have to change the proxy factory right now, so I guess you have to
specify the entire container config. I'll bring this up in a separate email
because this kind of sucks....
> >In the future we'll need to expand things so that you can bind multiple
> >invokers to the same container via standardjboss.xml and jboss.xml.
> >
>
> Do we really want to have people changing standardjboss.xml? Seems like
> it would be better to have a user flip a switch somewhere in
> jboss-service.xml (or some other deployed xml) rather than need to touch
> this file... but that is just my preference.
>
Well, if they want to change standardjboss.xml they can. I've done so
myself in the past. It's easy to change the default commit-option this way
for instance.
You can't just flip a switch in jboss-server.xml. This is because we'll
want the developer to be able to pick and chose how their bean is
accessable, and because they will have to provide a different JNDI name for
each invoker they are binding to the container. At least, that's the way I
think it will work.
> I try to keep users from mucking with standard configurations, as they
> just tend to break things... or when upgrading there is more work for
> them to make sure there hacked configs make it over to the new files.
>
> Any ways, just a thought... =)
>
> --jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
