Wouldn't fixing EJX so that it doesn't leave a blank entry in Jboss.xml for the container configuration also solve the problem? The documentation could then simply refer users to EJX and ignore the details of the file. ----- Original Message ----- From: "marc fleury" <[EMAIL PROTECTED]> To: "jBoss Developer" <[EMAIL PROTECTED]> Sent: Saturday, August 05, 2000 10:30 PM Subject: RE: [jBoss-Dev] Advanced container configuration > In fact thinking some more about this, even in the case you DO change the > container configuration (say to use Tyrex for distributed tx, instead of the > fast lightweight JTS coming with jboss2) you would just specify that one and > not the rest. Again it needs to be done > > > marc
- RE: [jBoss-Dev] Advanced container configuration marc fleury
- RE: [jBoss-Dev] Advanced container configuration Aaron Mulder
- RE: [jBoss-Dev] Advanced container configuration marc fleury
- RE: [jBoss-Dev] Advanced container configurati... marc fleury
- [jBoss-Dev] RE: Exception in shutdown Dan OConnor
- Re: [jBoss-Dev] RE: Exception in shut... Rickard �berg
- Re: [jBoss-Dev] RE: Exception in ... Dan OConnor
- [jBoss-Dev] About to check in... Dan OConnor
- Re: [jBoss-Dev] About to check in... Dan OConnor
- Re: [jBoss-Dev] About to check in... Dan OConnor
- RE: [jBoss-Dev] Advanced container configu... Luan O'Carroll
- RE: [jBoss-Dev] Advanced container co... marc fleury
- RE: [jBoss-Dev] Advanced container configurati... Ken Jenks
- Re: [jBoss-Dev] Advanced container configuration Rickard �berg
- Re: [jBoss-Dev] Advanced container configuration Ole Husgaard
- RE: [jBoss-Dev] Advanced container configuration marc fleury
- RE: [jBoss-Dev] Advanced container configurati... marc fleury
- Re: [jBoss-Dev] Advanced container configu... Ole Husgaard
