On Sat, Nov 28, 2009 at 11:12 AM, Shane Bryzak<sbryzak(a)redhat.com> wrote: > I'm pleased to say that Seam Remoting 3.0.0 is now compiling and works > with the ported hello world example in CDI. > Cool :-) > Since bean names are now an optional thing, I was wondering whether I > should support remoting with non-named beans. I could probably do it by > just allowing a fully qualified class name, what do you guys think? > It would be better to use a combination of bean type and qualifiers.

Stuart has some code to do this using javassist. On Sun, Nov 29, 2009 at 2:00 AM, Shane Bryzak<sbryzak(a)redhat.com> wrote: > Almost got this working, however I need to be able to reflectively create an > AnnotationLiteral, given a String containing the fully qualified name of the > qualifier. Anyone done this before? >

You used a jdk dynamicproxy? Probably a better idea. Sent from my iPhone On Nov 29, 2009, at 1:01 PM, Shane Bryzak <sbryzak(a)redhat.com&gt; wrote: > Done, although I didn't need to use Javassist. ;) > > On 30/11/09 02:38, Gavin King wrote: >> Stuart has some code to do this using javassist. >> >> On Sun, Nov 29, 2009 at 2:00 AM, Shane Bryzak&lt;sbryzak(a)redhat.com&gt; >> wrote: >> >> >>> Almost got this working, however I need to be able to reflectively >>> create an >>> AnnotationLiteral, given a String containing the fully qualified >>> name of the >>> qualifier. Anyone done this before? >>> >> >> >> >

Done, although I didn't need to use Javassist. ;) On 30/11/09 02:38, Gavin King wrote: > Stuart has some code to do this using javassist. > > On Sun, Nov 29, 2009 at 2:00 AM, Shane Bryzak&lt;sbryzak(a)redhat.com&gt; > wrote: > > >> Almost got this working, however I need to be able to reflectively >> create an >> AnnotationLiteral, given a String containing the fully qualified >> name of the >> qualifier. Anyone done this before? >> > > >

Right but Annotation and every annotation type are all interfaces. You would not be able to extend AnnotationLiteral, but you don't really need that. All you need is to be able to implement all the interfaces. On Sun, Nov 29, 2009 at 7:54 PM, Stuart Douglas <stuart(a)baileyroberts.com.au&gt; wrote: > I don't think that this would be possible as the jdk proxy only allows you to implement SomeInterface, not SomeInterface<Foo> (i.e. there is no mechanism for generating a signature attribute in the proxy). When weld tries to get this information a GenericSignatureFormatError would result (I saw this in my code before I added the SignitureAttribute ). I may be wrong on this, but I can't see any way around it. > > Stuart > ________________________________________ > From: seam-dev-bounces(a)lists.jboss.org [seam-dev-bounces(a)lists.jboss.org] On Behalf Of Gavin King [gavin.king(a)gmail.com] > Sent: Monday, 30 November 2009 5:32 AM > To: Shane Bryzak > Cc: seam-dev(a)lists.jboss.org > Subject: Re: [seam-dev] First cab off the rank! > > You used a jdk dynamicproxy? Probably a better idea. > > Sent from my iPhone > > On Nov 29, 2009, at 1:01 PM, Shane Bryzak <sbryzak(a)redhat.com&gt; wrote: > >> Done, although I didn't need to use Javassist. ;) >> >> On 30/11/09 02:38, Gavin King wrote: >>> Stuart has some code to do this using javassist. >>> >>> On Sun, Nov 29, 2009 at 2:00 AM, Shane Bryzak&lt;sbryzak(a)redhat.com&gt; >>> wrote: >>> >>> >>>> Almost got this working, however I need to be able to reflectively >>>> create an >>>> AnnotationLiteral, given a String containing the fully qualified >>>> name of the >>>> qualifier.  Anyone done this before? >>>> >>> >>> >>> >> > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev > -- Gavin King gavin.king(a)gmail.com http://in.relation.to/Bloggers/Gavin http://hibernate.org http://seamframework.org

That makes sense. I don't know what I was thinking as you couldn't have a JDK proxy extend AnnotationLiteral anyway.  I will look at redoing mine using JDK proxies to remove the javassist dependency. Stuart ________________________________________ From: Gavin King [gavin.king(a)gmail.com] Sent: Monday, 30 November 2009 11:58 AM To: Stuart Douglas Cc: seam-dev(a)lists.jboss.org Subject: Re: [seam-dev] First cab off the rank! By "all the interfaces", I mean both interfaces. On Sun, Nov 29, 2009 at 7:58 PM, Gavin King <gavin.king(a)gmail.com&gt; wrote: > Right but Annotation and every annotation type are all interfaces. You > would not be able to extend AnnotationLiteral, but you don't really > need that. All you need is to be able to implement all the interfaces. > > On Sun, Nov 29, 2009 at 7:54 PM, Stuart Douglas > <stuart(a)baileyroberts.com.au&gt; wrote: >> I don't think that this would be possible as the jdk proxy only allows you to implement SomeInterface, not SomeInterface<Foo> (i.e. there is no mechanism for generating a signature attribute in the proxy). When weld tries to get this information a GenericSignatureFormatError would result (I saw this in my code before I added the SignitureAttribute ). I may be wrong on this, but I can't see any way around it. >> >> Stuart >> ________________________________________ >> From: seam-dev-bounces(a)lists.jboss.org [seam-dev-bounces(a)lists.jboss.org] On Behalf Of Gavin King [gavin.king(a)gmail.com] >> Sent: Monday, 30 November 2009 5:32 AM >> To: Shane Bryzak >> Cc: seam-dev(a)lists.jboss.org >> Subject: Re: [seam-dev] First cab off the rank! >> >> You used a jdk dynamicproxy? Probably a better idea. >> >> Sent from my iPhone >> >> On Nov 29, 2009, at 1:01 PM, Shane Bryzak <sbryzak(a)redhat.com&gt; wrote: >> >>> Done, although I didn't need to use Javassist. ;) >>> >>> On 30/11/09 02:38, Gavin King wrote: >>>> Stuart has some code to do this using javassist. >>>> >>>> On Sun, Nov 29, 2009 at 2:00 AM, Shane Bryzak&lt;sbryzak(a)redhat.com&gt; >>>> wrote: >>>> >>>> >>>>> Almost got this working, however I need to be able to reflectively >>>>> create an >>>>> AnnotationLiteral, given a String containing the fully qualified >>>>> name of the >>>>> qualifier.  Anyone done this before? >>>>> >>>> >>>> >>>> >>> >> _______________________________________________ >> seam-dev mailing list >> seam-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/seam-dev >> > > > > -- > Gavin King > gavin.king(a)gmail.com > http://in.relation.to/Bloggers/Gavin > http://hibernate.org > http://seamframework.org > -- Gavin King gavin.king(a)gmail.com http://in.relation.to/Bloggers/Gavin http://hibernate.org http://seamframework.org

Good point - isn't this simply a case though of implementing the equals() and hashCode() methods and checking that the members are equal, i.e. the same way that AnnotationLiteral does it? On 30/11/09 06:36, Stuart Douglas wrote: > Does it still work when the annotation has members? That was why I > needed the javassist. > > Stuart > > ________________________________________ > From: seam-dev-bounces(a)lists.jboss.org [seam-dev- > bounces(a)lists.jboss.org] On Behalf Of Shane Bryzak > [sbryzak(a)redhat.com] > Sent: Monday, 30 November 2009 5:34 AM > To: Gavin King > Cc: seam-dev(a)lists.jboss.org > Subject: Re: [seam-dev] First cab off the rank! > > Nope, just wrote my own impl of Annotation which I could then pass > into > BeanManager.getBeans(). > > On 30/11/09 04:32, Gavin King wrote: > >> You used a jdk dynamicproxy? Probably a better idea. >> >> Sent from my iPhone >> >> On Nov 29, 2009, at 1:01 PM, Shane Bryzak&lt;sbryzak(a)redhat.com&gt; >> wrote: >> >> >>> Done, although I didn't need to use Javassist. ;) >>> >>> On 30/11/09 02:38, Gavin King wrote: >>> >>>> Stuart has some code to do this using javassist. >>>> >>>> On Sun, Nov 29, 2009 at 2:00 AM, Shane Bryzak&lt;sbryzak(a)redhat.com&gt; >>>> wrote: >>>> >>>> >>>> >>>>> Almost got this working, however I need to be able to >>>>> reflectively >>>>> create an >>>>> AnnotationLiteral, given a String containing the fully qualified >>>>> name of the >>>>> qualifier. Anyone done this before? >>>>> >>>>> >>>> >>>> >>>> >>> > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev > _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

Remoting now has full support for looking up qualified beans, so you can now do cool stuff like this:

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.

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&lt;sbryzak(a)redhat.com&gt;  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>? > >

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&lt;sbryzak(a)redhat.com&gt;  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&lt;sbryzak(a)redhat.com&gt; >>>  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>? >>> >>> >>> >> >> > > >