Ok, I'm fine with this being an optional behavior. I'm not fine with that
being the only way it is.
----- Original Message -----
From: "marc fleury" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 01, 2001 2:20 PM
Subject: RE: [JBoss-dev] JMSContainerInvoker.java
> |Its not redundant as there are many provider specific properties
> |that an admin
> |has to set: security, clustering, etc. You don't create database
> |connection pools
> |automatically because there are too many provider specific options that an
> |admin familiar with the database has to set. In general the same
> |is true with
> |JMS.
>
> Time out,
>
> I am not saying that this should be the ONLY way to do it, just that if you
> don't specify anything in jbossmq.xml we provide a default behavior.
>
> If you want to specify the name the security the clustering then *of course*
> you need to do it by hand. I will agree that my first point was maybe
> missleading on this.
>
> Now, if you don't specify anything in jbossmq.xml then the default kicks in,
> and we notify the user "Creating TOPIC", simple. If there is something
> specified and the stuff already exists in the naming space then *of course*
> you use that topic.
>
> Makes sense, Makes playing with MDBs simple. An MDB can create the Topic he
> is listening to at deployment time and delete it at undeployment... simple,
> why is it such an issue?
>
> marc
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
