(6) a seam-web module with:   * injection of FacesContext   * injection of servlet contexts

We already have: (1) weld-se (2) weld-servlet and weld-tomcat (3) weld-wicket These are all UEs, I suppose. Or are some of them PEs?

So, folks, I want us to get a plan together for the first raft of CDI extensions. I think there's three kinds of "things" we will be working on: * Unportable extensions (UEs), that integrate with proprietary SPIs in Weld * Portable extensions (PEs) with the Weld brand * Portable extensions (PEs) with the Seam brand I imagine that we will distribute UEs along with Weld and cover them in the Weld documentation. Hopefully there will not be too many of these. Weld PEs are going to be things that: * are general purpose, * are simple, and * don't pull in extra dependencies. Things which don't fit this description get the Seam brand. We already have: (1) weld-se (2) weld-servlet and weld-tomcat (3) weld-wicket These are all UEs, I suppose. Or are some of them PEs? So here's the things that I would like to see us release soon: (1) A weld-ext module with: * logger injection, * @Exact, * @Introduces, * abstract producer methods, * beans declared at constructor level, and * @Named packages. These are all very easy to implement except @Introduces, which requires a little javassist magic. (I would just package weld-logger in here, I don't see why it needs to be in its own module.) (2) A seam2-int module with: * use of @Inject to inject of Seam2 beans into CDI beans (i.e. Weld delegates bean instantiation to Seam when there is a @Name) * (hopefully) support for @Inject in Seam2 beans, if this is not too hard to implement I have already done a rough impl of the first part. (3) A spring-int module. (4) a seam-transactions module with: * support for declarative JPA EntityTransaction management * support for injection of the EntityTransaction * (hopefully) support for the same things with a UserTransaction provided by JBoss Transactions * support for the same things with a Hibernate Transaction I have already done a rough impl of the first part. (5) a seam-persistence module with: * support for injection of JPA EntityManagers with various scopes * (hopefully) support for injection of Hibernate Sessions with various scopes I have already done a rough impl of the first part. (6) a seam-web module with: * injection of FacesContext * injection of servlet contexts These are both easy. (7) a seam-jms module with: * injection of all the various JMS objects for a resource of type Topic or Queue Is there anything I'm missing? -- Gavin King gavin.king(a)gmail.com http://in.relation.to/Bloggers/Gavin http://hibernate.org http://seamframework.org _______________________________________________ weld-dev mailing list weld-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev

So, folks, I want us to get a plan together for the first raft of CDI extensions. I think there's three kinds of "things" we will be working on: * Unportable extensions (UEs), that integrate with proprietary SPIs in Weld * Portable extensions (PEs) with the Weld brand * Portable extensions (PEs) with the Seam brand I imagine that we will distribute UEs along with Weld and cover them in the Weld documentation. Hopefully there will not be too many of these. Weld PEs are going to be things that: * are general purpose, * are simple, and * don't pull in extra dependencies. Things which don't fit this description get the Seam brand. We already have: (1) weld-se (2) weld-servlet and weld-tomcat (3) weld-wicket These are all UEs, I suppose. Or are some of them PEs? So here's the things that I would like to see us release soon: (1) A weld-ext module with: * logger injection, * @Exact, * @Introduces, * abstract producer methods, * beans declared at constructor level, and * @Named packages. These are all very easy to implement except @Introduces, which requires a little javassist magic. (I would just package weld-logger in here, I don't see why it needs to be in its own module.) (2) A seam2-int module with: * use of @Inject to inject of Seam2 beans into CDI beans (i.e. Weld delegates bean instantiation to Seam when there is a @Name) * (hopefully) support for @Inject in Seam2 beans, if this is not too hard to implement I have already done a rough impl of the first part. (3) A spring-int module. (4) a seam-transactions module with: * support for declarative JPA EntityTransaction management * support for injection of the EntityTransaction * (hopefully) support for the same things with a UserTransaction provided by JBoss Transactions * support for the same things with a Hibernate Transaction I have already done a rough impl of the first part. (5) a seam-persistence module with: * support for injection of JPA EntityManagers with various scopes * (hopefully) support for injection of Hibernate Sessions with various scopes I have already done a rough impl of the first part. (6) a seam-web module with: * injection of FacesContext * injection of servlet contexts These are both easy. (7) a seam-jms module with: * injection of all the various JMS objects for a resource of type Topic or Queue Is there anything I'm missing?

BTW, is Seam 3 targeting Java 6? Can we e.g. use @WebServlet if we need autoregistering servlets? _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

wrote:

What about the XML configuration extension? I would be willing to have a got at this if no one else is going to do it.

What about the XML configuration extension? I would be willing to have a got at this if no one else is going to do it. Stuart ________________________________________ From: seam-dev-bounces(a)lists.jboss.org [seam-dev-bounces(a)lists.jboss.org] On Behalf Of denis.forveille(a)gmail.com [denis.forveille(a)gmail.com] Sent: Saturday, 21 November 2009 6:15 AM To: seam-dev(a)lists.jboss.org Subject: Re: [seam-dev] Next steps - What about a portal/portlet/portlet-bridge integration module? On 11/20/2009 01:35 PM, Gavin King wrote: > So, folks, I want us to get a plan together for the first raft of CDI > extensions. I think there's three kinds of "things" we will be working > on: > > * Unportable extensions (UEs), that integrate with proprietary SPIs in Weld > * Portable extensions (PEs) with the Weld brand > * Portable extensions (PEs) with the Seam brand > > I imagine that we will distribute UEs along with Weld and cover them > in the Weld documentation. Hopefully there will not be too many of > these. > > Weld PEs are going to be things that: > > * are general purpose, > * are simple, and > * don't pull in extra dependencies. > > Things which don't fit this description get the Seam brand. > > We already have: > > (1) weld-se > (2) weld-servlet and weld-tomcat > (3) weld-wicket > > These are all UEs, I suppose. Or are some of them PEs? > > So here's the things that I would like to see us release soon: > > (1) A weld-ext module with: > > * logger injection, > * @Exact, > * @Introduces, > * abstract producer methods, > * beans declared at constructor level, and > * @Named packages. > > These are all very easy to implement except @Introduces, which > requires a little javassist magic. > > (I would just package weld-logger in here, I don't see why it needs to > be in its own module.) > > (2) A seam2-int module with: > > * use of @Inject to inject of Seam2 beans into CDI beans (i.e. Weld > delegates bean instantiation to Seam when there is a @Name) > * (hopefully) support for @Inject in Seam2 beans, if this is not > too hard to implement > > I have already done a rough impl of the first part. > > (3) A spring-int module. > > (4) a seam-transactions module with: > > * support for declarative JPA EntityTransaction management > * support for injection of the EntityTransaction > * (hopefully) support for the same things with a UserTransaction > provided by JBoss Transactions > * support for the same things with a Hibernate Transaction > > I have already done a rough impl of the first part. > > (5) a seam-persistence module with: > > * support for injection of JPA EntityManagers with various scopes > * (hopefully) support for injection of Hibernate Sessions with various scopes > > I have already done a rough impl of the first part. > > (6) a seam-web module with: > > * injection of FacesContext > * injection of servlet contexts > > These are both easy. > > (7) a seam-jms module with: > > * injection of all the various JMS objects for a resource of type > Topic or Queue > > Is there anything I'm missing? > > > _______________________________________________ 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

It's *definitely* something we want, but it's quite a lot of work to implement everything that was defined in the older versions of 299 (and some of that should change slightly, given the slightly different injection syntax that we now use). If you want to take on this job, that's great, go for it! But I want us to focus initially on lower-hanging fruit. Stuff that adds a lot of value w/o having to write a lot of code :-) On Sat, Nov 21, 2009 at 1:18 AM, Stuart Douglas <stuart(a)baileyroberts.com.au&gt; wrote: > What about the XML configuration extension? I would be willing to have a got at this if no one else is going to do it. > > Stuart > ________________________________________ > From: seam-dev-bounces(a)lists.jboss.org [seam-dev-bounces(a)lists.jboss.org] On Behalf Of denis.forveille(a)gmail.com [denis.forveille(a)gmail.com] > Sent: Saturday, 21 November 2009 6:15 AM > To: seam-dev(a)lists.jboss.org > Subject: Re: [seam-dev] Next steps > > - What about a portal/portlet/portlet-bridge integration module? > > On 11/20/2009 01:35 PM, Gavin King wrote: >> So, folks, I want us to get a plan together for the first raft of CDI >> extensions. I think there's three kinds of "things" we will be working >> on: >> >> * Unportable extensions (UEs), that integrate with proprietary SPIs in Weld >> * Portable extensions (PEs) with the Weld brand >> * Portable extensions (PEs) with the Seam brand >> >> I imagine that we will distribute UEs along with Weld and cover them >> in the Weld documentation. Hopefully there will not be too many of >> these. >> >> Weld PEs are going to be things that: >> >>     * are general purpose, >>     * are simple, and >>     * don't pull in extra dependencies. >> >> Things which don't fit this description get the Seam brand. >> >> We already have: >> >> (1) weld-se >> (2) weld-servlet and weld-tomcat >> (3) weld-wicket >> >> These are all UEs, I suppose. Or are some of them PEs? >> >> So here's the things that I would like to see us release soon: >> >> (1) A weld-ext module with: >> >>     * logger injection, >>     * @Exact, >>     * @Introduces, >>     * abstract producer methods, >>     * beans declared at constructor level, and >>     * @Named packages. >> >> These are all very easy to implement except @Introduces, which >> requires a little javassist magic. >> >> (I would just package weld-logger in here, I don't see why it needs to >> be in its own module.) >> >> (2) A seam2-int module with: >> >>     * use of @Inject to inject of Seam2 beans into CDI beans (i.e. Weld >> delegates bean instantiation to Seam when there is a @Name) >>     * (hopefully) support for @Inject in Seam2 beans, if this is not >> too hard to implement >> >> I have already done a rough impl of the first part. >> >> (3) A spring-int module. >> >> (4) a seam-transactions module with: >> >>     * support for declarative JPA EntityTransaction management >>     * support for injection of the EntityTransaction >>     * (hopefully) support for the same things with a UserTransaction >> provided by JBoss Transactions >>     * support for the same things with a Hibernate Transaction >> >> I have already done a rough impl of the first part. >> >> (5) a seam-persistence module with: >> >>     * support for injection of JPA EntityManagers with various scopes >>     * (hopefully) support for injection of Hibernate Sessions with various scopes >> >> I have already done a rough impl of the first part. >> >> (6) a seam-web module with: >> >>     * injection of FacesContext >>     * injection of servlet contexts >> >> These are both easy. >> >> (7) a seam-jms module with: >> >>     * injection of all the various JMS objects for a resource of type >> Topic or Queue >> >> Is there anything I'm missing? >> >> >> > _______________________________________________ > 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 > -- Gavin King gavin.king(a)gmail.com http://in.relation.to/Bloggers/Gavin http://hibernate.org http://seamframework.org

I have been playing around with the first bit this weekend, and I have created a helper class that can generate AnnotationLiteral<T> at runtime (using javassist), which will be necessary for qualifiers that are specified via xml. I will try and get on IRC a bit in the next few days, to talk about this more.

I just posted the code in the forum in anyone is interested. IT has only been lightly tested inside weld-se, so there may still be bugs. Stuart ________________________________________ From: Gavin King [gavin.king(a)gmail.com] Sent: Sunday, 22 November 2009 11:39 AM To: Stuart Douglas Cc: seam-dev(a)lists.jboss.org Subject: Re: [seam-dev] Next steps On Sat, Nov 21, 2009 at 7:36 PM, Stuart Douglas <stuart(a)baileyroberts.com.au&gt; wrote: > I have been playing around with the first bit this weekend, and I have created a helper class > that can generate AnnotationLiteral<T> at runtime (using javassist), which will be necessary > for qualifiers that are specified via xml. I will try and get on IRC a bit in the next few days, to > talk about this more. Ahyes, that's a problem I had not really thought about... -- Gavin King gavin.king(a)gmail.com http://in.relation.to/Bloggers/Gavin http://hibernate.org http://seamframework.org

The original spec called for the ability to set default field values, however the AnnotatedType interface does not support this directly. Does anyone have any idea's about how to implement this without having to subclass Bean? Stuart ________________________________________ From: Gavin King [gavin.king(a)gmail.com] Sent: Sunday, 22 November 2009 12:27 PM To: Stuart Douglas Cc: seam-dev(a)lists.jboss.org Subject: Re: [seam-dev] Next steps Great, this is very useful. At one stage, Pete and I talked about implementing the whole XML facility this way: it would just generate subclasses of the bean classes, with the annotations added in. But I don't think this approach works for: * final classes and methods * fields So I think we're going to need my AnnotationTypeWrapper classes. I'll try to find time to work on them tomorrow, but I might have to wait til Monday. On Sat, Nov 21, 2009 at 7:45 PM, Stuart Douglas <stuart(a)baileyroberts.com.au&gt; wrote: > I just posted the code in the forum in anyone is interested. IT has > only been lightly tested inside weld-se, so there may still be bugs. > > Stuart > ________________________________________ > From: Gavin King [gavin.king(a)gmail.com] > Sent: Sunday, 22 November 2009 11:39 AM > To: Stuart Douglas > Cc: seam-dev(a)lists.jboss.org > Subject: Re: [seam-dev] Next steps > > On Sat, Nov 21, 2009 at 7:36 PM, Stuart Douglas > <stuart(a)baileyroberts.com.au&gt; wrote: > >> I have been playing around with the first bit this weekend, and I >> have created a helper class >> that can generate AnnotationLiteral<T> at runtime (using >> javassist), which will be necessary >> for qualifiers that are specified via xml. I will try and get on >> IRC a bit in the next few days, to >> talk about this more. > > Ahyes, that's a problem I had not really thought about... > > > -- > 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 _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

So, folks, I want us to get a plan together for the first raft of CDI extensions. I think there's three kinds of "things" we will be working on: * Unportable extensions (UEs), that integrate with proprietary SPIs in Weld * Portable extensions (PEs) with the Weld brand * Portable extensions (PEs) with the Seam brand I imagine that we will distribute UEs along with Weld and cover them in the Weld documentation. Hopefully there will not be too many of these. Weld PEs are going to be things that: * are general purpose, * are simple, and * don't pull in extra dependencies. Things which don't fit this description get the Seam brand. We already have: (1) weld-se (2) weld-servlet and weld-tomcat (3) weld-wicket These are all UEs, I suppose. Or are some of them PEs? So here's the things that I would like to see us release soon: (1) A weld-ext module with: * logger injection, * @Exact, * @Introduces, * abstract producer methods, * beans declared at constructor level, and * @Named packages. These are all very easy to implement except @Introduces, which requires a little javassist magic. (I would just package weld-logger in here, I don't see why it needs to be in its own module.) (2) A seam2-int module with: * use of @Inject to inject of Seam2 beans into CDI beans (i.e. Weld delegates bean instantiation to Seam when there is a @Name) * (hopefully) support for @Inject in Seam2 beans, if this is not too hard to implement I have already done a rough impl of the first part. (3) A spring-int module. (4) a seam-transactions module with: * support for declarative JPA EntityTransaction management * support for injection of the EntityTransaction * (hopefully) support for the same things with a UserTransaction provided by JBoss Transactions * support for the same things with a Hibernate Transaction I have already done a rough impl of the first part. (5) a seam-persistence module with: * support for injection of JPA EntityManagers with various scopes * (hopefully) support for injection of Hibernate Sessions with various scopes I have already done a rough impl of the first part. (6) a seam-web module with: * injection of FacesContext * injection of servlet contexts These are both easy. (7) a seam-jms module with: * injection of all the various JMS objects for a resource of type Topic or Queue Is there anything I'm missing? -- Gavin King gavin.king(a)gmail.com http://in.relation.to/Bloggers/Gavin http://hibernate.org http://seamframework.org _______________________________________________ weld-dev mailing list weld-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev

I started on the servlet event -> Weld event mappings and the FacesContext / WebStuff producers. Gotta grab the easy ones while their available ;-)

_______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

> * Unportable extensions (UEs), that integrate with proprietary SPIs in Weld These are primarily the things which support "other environments" like Servlet or Java SE, as there is no bootstrap SPI. Though things that want to reuse the conversation impl *outside JSF* from Weld also fall into this category :-/

> (2) A seam2-int module with: > >   * use of @Inject to inject of Seam2 beans into CDI beans (i.e. Weld > delegates bean instantiation to Seam when there is a @Name) >   * (hopefully) support for @Inject in Seam2 beans, if this is not > too hard to implement > > I have already done a rough impl of the first part. Great! We also discussed this at the meeting, so see that email. Norman is going to take the lead on this.

> (3) A spring-int module. Marius volunteered to take the lead on this months ago :-)

> (4) a seam-transactions module with: All sounds good. We didn't discuss this one in depth, and we do need a lead for it. > (5) a seam-persistence module with: > >   * support for injection of JPA EntityManagers with various scopes >   * (hopefully) support for injection of Hibernate Sessions with various scopes > > I have already done a rough impl of the first part. Likewise, we need a lead for this :-)

On 21 Nov 2009, at 18:47, Gavin King wrote: >>> (4) a seam-transactions module with: >> >> All sounds good. >> >> We didn't discuss this one in depth, and we do need a lead for it. >> >>> (5) a seam-persistence module with: >>> >>>   * support for injection of JPA EntityManagers with various scopes >>>   * (hopefully) support for injection of Hibernate Sessions with various scopes >>> >>> I have already done a rough impl of the first part. >> >> Likewise, we need a lead for this :-) > > Yes, this shit is actually critical. We already have user complaints. > i.e. also takes priority over everything apart f Any community volunteers for this? Going once... Otherwise, I suggest either you or I take this Gavin (if I do it, I will have to ask you or Emmanuel lots of questions about TXs, JPA etc)

>> (4) a seam-transactions module with: > > All sounds good. > > We didn't discuss this one in depth, and we do need a lead for it. > >> (5) a seam-persistence module with: >> >> * support for injection of JPA EntityManagers with various scopes >> * (hopefully) support for injection of Hibernate Sessions with various scopes >> >> I have already done a rough impl of the first part. > > Likewise, we need a lead for this :-) Yes, this shit is actually critical. We already have user complaints. i.e. also takes priority over everything apart f

Steven, sounds great, want to start by having a play with what Gavin wrote? http://seamframework.org/Community/HowDoIGetAJPAEntityManagerReferenceInW... On 21 Nov 2009, at 20:56, Boscarine, Steven wrote: > I'll volunteer to help on the TX and JPA piece. > > Someone else will need to be the lead. I can definitely help with coding, testing and documenting, though. > > > > ________________________________________ > From: weld-dev-bounces(a)lists.jboss.org [weld-dev-bounces(a)lists.jboss.org] On Behalf Of Pete Muir [pmuir(a)redhat.com] > Sent: Saturday, November 21, 2009 2:04 PM > To: Gavin King > Cc: Seam-Dev; Weld-Dev > Subject: Re: [weld-dev] [seam-dev] Next steps > > On 21 Nov 2009, at 18:47, Gavin King wrote: > > >>>> (4) a seam-transactions module with: >>>> >>> All sounds good. >>> >>> We didn't discuss this one in depth, and we do need a lead for it. >>> >>> >>>> (5) a seam-persistence module with: >>>> >>>> * support for injection of JPA EntityManagers with various scopes >>>> * (hopefully) support for injection of Hibernate Sessions with various scopes >>>> >>>> I have already done a rough impl of the first part. >>>> >>> Likewise, we need a lead for this :-) >>> >> Yes, this shit is actually critical. We already have user complaints. >> i.e. also takes priority over everything apart f >> > Any community volunteers for this? Going once... > > Otherwise, I suggest either you or I take this Gavin (if I do it, I will have to ask you or Emmanuel lots of questions about TXs, JPA etc) > _______________________________________________ > weld-dev mailing list > weld-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/weld-dev >