On Fri, 1 Jun 2001, marc fleury wrote:
> 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.
In this case, no, its not very convenient in my opinion. My application
won't work since the MDB is subscribed to the wrong topic. So why bother
deploying it at all. It's not going to receive anything anyhow, cause no
other component in my app is going to publish anything to it.
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.
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.
> 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
This piece of code gets called by exception anyhow. It creates
configuration changes that live longer than the MDB it created them for,
and it has no way of knowing if the fix its trying to make is the right
one or if its just messing things up more.
There are two clear cases where you reach this exception code. Either the
admin didn't configure the server correctly, or the developer made a mistake.
The admin mistake would be easy to notice at deployment time because
there's a failed lookup. The developer mistake will be made more difficult
to notice since the app can fail silently.
> 7- Re: creating the topic, **uncreate** it at undeployment and basta! no
> more non-sense.
No that won't work. The MDB is just one client to the topic. You don't
want to delete the topic because one subscriber decides to leave.
> 8- ANYTHING THAT IS ADMIN FRIENDLY IS GOOD
>
> Oka?
I admit I wear the developer hat more than the admin hat. But anything
that makes it easier for me to find my own bugs saves my time and my
nerves and someone else's money, and that is also good in my book.
If I make a mistake, I'd rather know about it right away, and I'd rather
not go clean up configuration files because of it.
-- Juha
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
