Well, I wasn't trying to tell you to do it my way, it was just a suggestion...
Do what you think is most natural in .js land...
On Tue, Dec 1, 2009 at 7:38 PM, Shane Bryzak <sbryzak(a)redhat.com> wrote:
No problem, I can do that. For @Named beans, would it just be:
Seam.instance.select("helloAction").get() ?
On 02/12/09 10:22, Gavin King wrote:
>
> hrm I suppose so. I was thinking more like:
>
>
>
Seam.instance.select("org.jboss.seam.remoting.examples.helloworld.HelloAction",
> "@HelloQualifier(foo = 123)").get()
>
>
> On Tue, Dec 1, 2009 at 7:03 PM, Shane Bryzak<sbryzak(a)redhat.com> wrote:
>
>>
>> Hmm, interesting idea... so something like this?
>>
>>
>>
Seam.Instance("org.jboss.seam.remoting.examples.helloworld.HelloAction").select("@HelloQualifier(foo
>> = 123)")
>>
>>
>> On 02/12/09 09:58, Gavin King wrote:
>>
>>>
>>> On Tue, Dec 1, 2009 at 6:53 PM, Shane Bryzak<sbryzak(a)redhat.com>
>>> wrote:
>>>
>>>
>>>>
>>>> Remoting now has full support for looking up qualified beans, so you
>>>> can
>>>> now do cool stuff like this:
>>>>
>>>>
>>>
>>> Nice.
>>>
>>>
>>>
>>>>
>>>> If the bean is @Named then you can simply pass in the name to
>>>> Seam.Component.create() in JavaScript, otherwise you can use a
>>>> combination of bean type and qualifiers. I need to still do some work
>>>> on the API, instead of Seam.Component.create() I'm thinking
>>>> Seam.Bean.instance() instead.
>>>>
>>>>
>>>
>>> Perhaps you could make the API look like Instance<X>?
>>>
>>>
>>>
>>
>>
>
>
>
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org