envv-entry-value looks like a typo to me.
Seam is not doing anything with that - it is purely the EJB3 container. If it isn't working right, you should check the EJB3 forums and/or open an EJB3 JIRA issue.
Out of curiosity, what do you see as the advantages of trying to use this as opposed to using a configuration property in components.xml?
Thxs. I corrected the typo, but it's still not working. I also can't see it in the JNDI Tree of the MX console so it seems to be a binding problem. It should appear there, right?
Well, there is no real argument for using this over that. But I read the oreilly books and follow standards. So, I guess if there is a standard way of doing something, and I mean industry standard, I rather use it.
But since seam and many other things are proprietary in the first place there is really no point in not using what you suggest. I guess it's just a prefence to choose standards over propiertary software.