|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
|
|> 1- If it is not there, right now we have to manually go and
|create the damn
|> thing, very redundant.
|> 2- If you miss the spelling.. we should put a message saying "Creating
|> topic" and that's it.. very convenient.
|> 3- What is the big fuss about...?
|> 4- You guys are designing by exception, i.e. "haaaa but what happens if
|> someone FUCKS up and mis-spells the topic. Well someone FUCKED
|up... and we
|> SAY "Creating Topic" so we give all the information, where is
|the harm done?
|> 5- You are saying, because of this possible fuck-up we should
|not permit the
|> feature that will be very useful for most people.... design by exception
|> 6- design by exception == bad
|> 7- Re: creating the topic, **uncreate** it at undeployment and basta! no
|> more non-sense.
|> 8- ANYTHING THAT IS ADMIN FRIENDLY IS GOOD
|>
|> Oka?
|>
|> but I am open to discussion and will stick by dug on this one...
|I thought
|> it was a good proposition and I still do.
|>
|> marc
|
|
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
