WTF... the create the MDB topic on deployment if not present?
I think it is a kick ass feature...
let me explain:
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
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Juha
|Lindfors
|Sent: Friday, June 01, 2001 11:40 AM
|To: [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] JMSContainerInvoker.java
|
|
|
|poo poo!
|
|;-D
|
|--Juha
|
|At 07:08 1.6.2001 -0700, you wrote:
|>This is something that was suggested at the Atlanta training and Marc
|liked so
|>you need to slap him around. I was not particularly in favor of it and
|that seems
|>to be the general feeling so let's roll the change back.
|>
|>----- Original Message -----
|>From: "Juha-P Lindfors" <[EMAIL PROTECTED]>
|>To: <[EMAIL PROTECTED]>
|>Sent: Friday, June 01, 2001 3:15 AM
|>Subject: Re: [JBoss-dev] JMSContainerInvoker.java
|>
|>
|>
|>
|>On Fri, 1 Jun 2001, Peter Antman wrote:
|>>
|>> You see what will happen? Yes, the client will send its messages to one
|>> topic (no automatic creation here), and the MDB will listen on ANOTHER
|>> topic, namely a to the system unknown destination, since it was not
|>> correctly spelled.
|>>
|>> What do you other guys say on the list? Hiram?
|>
|>I agree with you it's not a good change. If the developer has made a
|>mistake in his code or forgot to add the topic he should be warned during
|>the deployment, instead of allowing the application to silently fail.
|>
|>Also, since the created topics are persistent, this requires the developer
|>to go clean up the jbossmq configuration file from time to time to make
|>sure resources aren't wasted on topics that never meant to be there in the
|>first place. I think thats worse than the requirement of having to create
|>the topic upfront, especially since the developer may not even be
|aware he is
|>accidentally creating new topics.
|>
|>So if the idea was to help the developer to avoid finding out about our
|>obscure configuration files, I think this change may have made the problem
|>even worse. Now you HAVE TO go browse them, just to fix your typos that
|>won't go away.
|>
|>-- Juha
|>
|>
|>
|>
|>_______________________________________________
|>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
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
