On 7/31/06, Dhananjay Prasanna <[EMAIL PROTECTED]> wrote:
There is no special support for "namespaces" in JSF 1.2 (the most recent finalized spec), but nothing really stops you from simulating this. I tend to use "$" instead of ":" as a separator, because it is a legal character in identifiers so you don't have to go quoting things.
I don't know of any Hivemind integration, but it's already there for Spring. In 1.2.5 they started offering a custom variable resolver that can use Spring to create singletons or a new bean on each request -- and it happens transparently to your usage of value binding and method binding expressions. In Spring 2, the story is even better since they've added the concept of scopes, so you can tell Spring to create a new session scoped bean. From the JSF perspective, you just use expressions like you always have ... it's just that Spring will be used instead of managed beans to construct and return the instances.
Craig
Craig, is there any thought to add namespace support to the EL? Example:
#{myBean.blah}
As opposed to:
#{myModule:myBean}
This would help greatly, especially for those of us who have huge numbers of managed beans.
There is no special support for "namespaces" in JSF 1.2 (the most recent finalized spec), but nothing really stops you from simulating this. I tend to use "$" instead of ":" as a separator, because it is a legal character in identifiers so you don't have to go quoting things.
Or the more adventurous of us who want to try (or need) and delegate some DI to spring or hivemind. ;)
I don't know of any Hivemind integration, but it's already there for Spring. In 1.2.5 they started offering a custom variable resolver that can use Spring to create singletons or a new bean on each request -- and it happens transparently to your usage of value binding and method binding expressions. In Spring 2, the story is even better since they've added the concept of scopes, so you can tell Spring to create a new session scoped bean. From the JSF perspective, you just use expressions like you always have ... it's just that Spring will be used instead of managed beans to construct and return the instances.
Craig
