Hi,
I would have to agree with Peter on this one. I believe this goes
against the spirit of the JMS spec, where JMS destinations are to be
created EXPLICITLY using a vendor-defined administration interface.
Having your app silently create destinations brings up nightmarish
visions
of BAD THINGS HAPPENING AND YOU DON'T KNOW WHY! I would vote +1 for this
change to be rolled back.
This does not mean that I am against an app being able to dynamically
create a JMS destination, and I am working on a simple interface that
can be used within an application to do just that, but I really don't
think the MDB container is the place for that functionality.
cheers,
Joel
Peter Antman wrote:
>
> Hey, what is THIS? Have you discussed this feature with anybody! You
> certainly have not discussed it with me!
>
> Why have you made those changes? Is it for your personal needs? Is it
> because it is a generally good thing?
>
> My first impression is that this is NOT a good thing. Why, when it looks
> so tempting to be able to say to beginner: well just write a destination
> name, if it don't exist it will be created for you.
>
> But why it is also a BAD thing? Well, simply because you loose controll
> over what is actually happening.
>
> In client code: lookup("topic/MySpecialImportantTopic");
>
> In MDB deployment descriptor: topic/MySpecialImpotantTopic
>
> 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?
>
> //Peter
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
