My vote on the issue is turn the feature OFF by default.
A JMS queue is like a database table: I don't want the thing getting
created and destroyed every time I deploy and undeploy a bean. This is
mainly doe to the time indepenent processing "feature" JMS usually gives
you. If you are creating and destroying a destination, the publisher
becomes time dependent on when the bean is deployed (does this make sense?).
Regards,
Hiram
----- Original Message -----
From: "Juha-P Lindfors" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 01, 2001 6:34 PM
Subject: RE: [JBoss-dev] JMSContainerInvoker.java
>
>
> On Fri, 1 Jun 2001, marc fleury wrote:
> > to clear fuck-ups... yet if you screw up it doesn't hide the mistake,
your
> > application won't work.
>
> yes... but I want to know exactly *WHY* it doesn't work :)
>
> > |I'd much rather see the lookup fail than have the server hide my fuck
ups.
> > |Because that very clearly indicates something's wrong in the
> > |configuration.
> >
> > and by doing so you prevent those that didn't fuck up from having a
> > convenient feature. Design by exception.
>
> hey, I just like my errors pointed out to me in a clear and unambiguous
> matter. It's because I make lots of them and have rarely fun time trying
> to find them... :P
>
>
> > |The proposed implementation requires me to go clean up the jbossmq.xml
> > |unless I like to have the naming space cluttered with stuff that wasn't
> > |supposed to go there. It also allows the application to silently fail,
as
> > |Peter pointed out.
> >
> > Please read my mails, point 7.
>
> you make too many, and they're repetitive and become boring :)
>
>
> > Also, I don't see the "silently" point, if you don't have the right name
you
> > get 2 things from us
> > 1- A "Creating topic"
> > 2- An exception in your application
>
> I mean, where I create a MDB and lookup 'bob' which isnt right
> or configured and the server then creates it, and then have a client
> that *correctly* looks up 'Bob' which was probably configured by some guy
> three years ago. Everyone's happy, except I'm tearing
> my hair out wondering why the fuck my messages arent getting through.
>
> See it?
>
> half my components talk to 'bob', the other half talks to 'Bob' and
> everyone refuses to talk to the other party.
>
> As long as its painfully obvious that the server is trying to be smart
> even in cases where it shouldnt, where it was my fault, its ok by me. And
> if it does destroy the topic so that I don't end up with bob, Bob, BoB and
> BOB in my config, then I can live with it.
>
> -- 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
