Rickard �berg wrote:
>
> Because it is an unnecessary restriction. Different vendors use
> different tree structures, and one shouldn't limit in a specification
> how the tree should be formed. Also, when you say "serverspecific code",
> what do you mean? You're note implying that you're hardcoding JNDI names
> in your app, are you?!? ;-)
>
Of course not! You know me =)
> Break it out into .properties files and this should not be a problem.
>
Well, one could argue that it's more work for the deployer (or whoever connects
the resource to the server). On the other hand, not using it would hardcode the
JNDI-name (allthough a standardized name) which isn't very nice. So, I have to
agree, it shouldn't be standardized. =(
> ps.
> > Polish Tourist Brochure: "As for the tripes serves you at the Hotel Monopol, you
> > will be singing its praise to your children as you lie on your deathbed."
> Jikes, how many of these do you have?? ;-)
>
I have about 80. I should point out that if anyone is offended, don't be, I have
Swedish versions as well. Nobody is spared from the fun =)
/Kalle
--
Polish Tourist Brochure: "As for the tripes serves you at the Hotel Monopol, you
will be singing its praise to your children as you lie on your deathbed."
Karl-Fredrik Blixt
Computer Science student at LiTH, Sweden
Homepage: http://o44.ryd.student.liu.se/
Telephone: +46-(0)13-47 39 206
Cellular: +46-(0)739-87 11 03
ICQ: 4744258
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
