This is the case today (the spec requires this name, the TCK enforces
it).
On 9 May 2009, at 00:28, Dan Allen wrote:
It would seem very useful if certain components had standard names.
For instance, it is quite common to consult the conversation object
in JSF via the EL. I would hate for different implementations to use
different names making the reference to the conversation non-
portable. Would it be reasonable to make javax.context.conversation
the standard name?
e.g. #{javax.context.conversation.longRunning}
-Dan
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than
a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a
message if
you feel that it did not reach my attention.
_______________________________________________
webbeans-dev mailing list
webbeans-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/webbeans-dev