12:35 p.m.
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
12:38 p.m.
On Fri, Nov 20, 2009 at 1:35 PM, Gavin King <gavin.king(a)gmail.com> wrote:
(6) a seam-web module with:
* injection of FacesContext
* injection of servlet contexts
Oh, and since it's easy enough to implement, servlet events on the CDI
event bus:
http://www.seamframework.org/Weld/PortableExtensionsPackage#H-EventsRelat...
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
12:40 p.m.
Oh and did I mention we need to decide who "owns" each of these
modules. This is the thing we need to do right now :-)
12:44 p.m.
New subject: [seam-dev] Next steps
On Fri, Nov 20, 2009 at 12:35 PM, Gavin King <gavin.king(a)gmail.com> wrote:
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?
weld-wicket is an UE because the api for manipulating the conversational
context which jsf and weld-wicket both use, isn't part of the SPI. However,
I'd like to see it become a PE at some point.
-Clint
--
Clint Popetz
http://42lines.net
Scalable Web Application Development
12:45 p.m.
New subject: [seam-dev] Next steps
On Fri, Nov 20, 2009 at 1:44 PM, Clint Popetz <cpopetz(a)gmail.com> wrote:
weld-wicket is an UE because the api for manipulating the
conversational
context which jsf and weld-wicket both use, isn't part of the SPI. However,
I'd like to see it become a PE at some point.
Yes, that's what I thought.
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
12:46 p.m.
As soon as Pete gets back online, we have a number of items we have
identified in the meeting at Devoxx. Those items should start to flow in
this weekend.
-Dan
On Fri, Nov 20, 2009 at 7:35 PM, Gavin King <gavin.king(a)gmail.com> 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?
--
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
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
4:27 p.m.
There's also the Scheduling extension which currently lives in the seam modules
sandbox. I guess it's a Seam PE as it drags in other dependencies (ie Quartz), but it
does work with plain Weld (well, at least in SE). For details and an example that's
not in the JBoss repos:
http://screamingcoder.com/life/2009/07/23/scheduling-in-web-beans-and-jsr...
Pete R
On 21/11/2009, at 4:35 AM, 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?
--
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
4:49 p.m.
That actually looks very cool. I did not know about it. Very much in
the spirit of CDI. I don't see any reason not to include this in the
first raft of releases.
Sent from my iPhone
On Nov 20, 2009, at 5:27 PM, Peter Royle
<howardmoon(a)screamingcoder.com> wrote:
There's also the Scheduling extension which currently lives in
the
seam modules sandbox. I guess it's a Seam PE as it drags in other
dependencies (ie Quartz), but it does work with plain Weld (well, at
least in SE). For details and an example that's not in the JBoss
repos:
http://screamingcoder.com/life/2009/07/23/scheduling-in-web-beans-and-jsr...
Pete R
On 21/11/2009, at 4:35 AM, 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?
>
>
> --
> 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
4:32 p.m.
New subject: [seam-dev] Next steps
I started on the servlet event -> Weld event mappings and the
FacesContext / WebStuff producers. Gotta grab the easy ones while
their available ;-)
4:50 p.m.
New subject: [seam-dev] Next steps
Haha :)
Sent from my iPhone
On Nov 20, 2009, at 5:32 PM, Nicklas Karlsson <nickarls(a)gmail.com>
wrote:
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
7:31 p.m.
New subject: [seam-dev] Next steps
On Fri, Nov 20, 2009 at 11:32 PM, Nicklas Karlsson <nickarls(a)gmail.com>wrote:
I started on the servlet event -> Weld event mappings and the
FacesContext / WebStuff producers. Gotta grab the easy ones while
their available ;-)
There is already a weld-faces extension with a FacesContext producer, though
the impl may change after talking about it at Devoxx. Details to follow.
-Dan
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
2:50 a.m.
New subject: [seam-dev] Next steps
As Dan mentioned, we spent a couple of hours on this at our face-to-face meeting in
Antwerp. I've commented inline with my thoughts. I have another email with the actual
meeting notes.
I also think we need to get this info onto a wiki page asap, and also prioritize stuff a
bit, so that volunteers know which things would be best to pick up...
On 20 Nov 2009, at 19:35, 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
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 :-/
* Portable extensions (PEs) with the Weld brand
* Portable extensions (PEs) with the Seam brand
I like this :-)
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
UE.
(2) weld-servlet and weld-tomcat
UE. NB We need to do a bit of simplification here. When we started, we had to package weld
as an application library, but we also need to access Tomcat APIs (which are hidden from
the war classloader) to perform servlet injection. Now that we can support Weld as a
shared library, we can probably merge these code bases. I'll also try to chat to Remy
or another Tomcat dev to figure out if there is a better way to achieve this...
(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.)
Agreed :-)
(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:
* 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
This should be possible from what I know of JBoss Transactions
* support for the same things with a Hibernate Transaction
I have already done a rough impl of the first part.
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 :-)
(6) a seam-web module with:
* injection of FacesContext
* injection of servlet contexts
These are both easy.
Looks like this has already started :-)
(7) a seam-jms module with:
* injection of all the various JMS objects for a resource of type
Topic or Queue
Shane was happy to take a lead on this, but if we can find a volunteer that would
definitely be good!
Is there anything I'm missing?
12:47 p.m.
New subject: [seam-dev] Next steps
On Sat, Nov 21, 2009 at 3:50 AM, Pete Muir <pmuir(a)redhat.com> wrote:
> * 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 :-/
Yes, these two things are both holes in CDI that we know probably
won't be fixed until CDI 1.1. So we're just going to have to live with
the lack of portability here for a while. It's not perfect, but we
could not do everything in 1.0.
> (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.
Perfect. Note that this shit is critical. i.e. takes priority over
everything apart from Weld bugfixes and container integration issues
:-)
> (3) A spring-int module.
Marius volunteered to take the lead on this months ago :-)
Cool.
> (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 from Weld bugfixes and
container integration issues :-)
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
1:04 p.m.
New subject: [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)
1:19 p.m.
New subject: [seam-dev] Next steps
On Sat, Nov 21, 2009 at 2:04 PM, Pete Muir <pmuir(a)redhat.com> wrote:
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)
I already posted some code for this here:
http://seamframework.org/Community/HowDoIGetAJPAEntityManagerReferenceInW...
But you're going to have to put it in svn, since I refuse to learn maven.
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
6:39 a.m.
New subject: [seam-dev] Next steps
On 21 Nov 2009, at 19:19, Gavin King wrote:
On Sat, Nov 21, 2009 at 2:04 PM, Pete Muir <pmuir(a)redhat.com>
wrote:
>
> 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)
I already posted some code for this here:
http://seamframework.org/Community/HowDoIGetAJPAEntityManagerReferenceInW...
But you're going to have to put it in svn, since I refuse to learn maven.
Haha, ok, its a deal :-)
2:56 p.m.
New subject: [seam-dev] Next steps
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
6:43 a.m.
New subject: [seam-dev] Next steps
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
6:47 a.m.
New subject: [seam-dev] Next steps
Sure. Would it make sense to give it a home first?
Do you have a SVN home and artifact/groupId in mind?
Pete Muir wrote:
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
>
8:28 a.m.
New subject: [seam-dev] Next steps
We already have a module called persistence in seam modules (see Seam trunk). You can use
that :-)
You'll want to delete all the existing classes that are there, we don't need
those.
I gave you commit on Seam, but please make sure you sign the CLA for Seam as well on
jboss.org
On 22 Nov 2009, at 12:47, Steven Boscarine wrote:
Sure. Would it make sense to give it a home first?
Do you have a SVN home and artifact/groupId in mind?
Pete Muir wrote:
> 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
>>
>
>
10:36 a.m.
New subject: seam modules questions: missing artifacts: webbeans-core-test & jboss-test-harness + is readme.txt correct?...missing parent?
I am trying to build https://svn.jboss.org/repos/seam/modules/trunk
Is parent missing?:
I followed the instructions in readme.txt and built version-matrix. I
couldn't follow the steps about building parent.
https://svn.jboss.org/repos/seam/modules/trunk/readme.txt Parent
appears to be deleted on 5/29 (
http://fisheye.jboss.org/browse/Seam/modules/trunk/parent). Am I
missing something?
When I checkout modules, I'm greeted with a build error (pasted below)
because it cannot find
org.jboss.webbeans:webbeans-core-test:jar:1.0.0-SNAPSHOT and
org.jboss.test-harness:jboss-test-harness:jar:1.0.0-SNAPSHOT.
Is it possible to have a CI build push webbeans-core-test &
jboss-test-harness to the jboss repos? When we did that for our
project, it was real helpful in reducing reported errors from people
forgetting to build our manual dependencies.
Missing:
----------
1) org.jboss.test-harness:jboss-test-harness:jar:1.0.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.jboss.test-harness
-DartifactId=jboss-test-harness -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.jboss.test-harness
-DartifactId=jboss-test-harness -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.jboss.seam:seam-parent:pom:3.0.0-SNAPSHOT
2) org.jboss.test-harness:jboss-test-harness:jar:1.0.0-SNAPSHOT
2) org.jboss.webbeans:webbeans-core-test:jar:1.0.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.jboss.webbeans
-DartifactId=webbeans-core-test -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.jboss.webbeans
-DartifactId=webbeans-core-test -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.jboss.seam:seam-parent:pom:3.0.0-SNAPSHOT
2) org.jboss.webbeans:webbeans-core-test:jar:1.0.0-SNAPSHOT
----------
2 required artifacts are missing.
for artifact:
org.jboss.seam:seam-parent:pom:3.0.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
repository.jboss.org (http://repository.jboss.org/maven2),
snapshots.jboss.org (http://snapshots.jboss.org/maven2)
7:40 a.m.
New subject: seam modules questions: missing artifacts: webbeans-core-test & jboss-test-harness + is readme.txt correct?...missing parent?
Hi Steven,
Looks like the build is very out of date, and we need to get it fixed up.
I've at least got the persistence module building.
On 22 Nov 2009, at 16:36, Steven Boscarine wrote:
I am trying to build https://svn.jboss.org/repos/seam/modules/trunk
Is parent missing?:
I followed the instructions in readme.txt and built version-matrix. I couldn't
follow the steps about building parent.
https://svn.jboss.org/repos/seam/modules/trunk/readme.txt Parent appears to be deleted on
5/29 ( http://fisheye.jboss.org/browse/Seam/modules/trunk/parent). Am I missing
something?
When I checkout modules, I'm greeted with a build error (pasted below) because it
cannot find org.jboss.webbeans:webbeans-core-test:jar:1.0.0-SNAPSHOT and
org.jboss.test-harness:jboss-test-harness:jar:1.0.0-SNAPSHOT.
Is it possible to have a CI build push webbeans-core-test & jboss-test-harness to the
jboss repos? When we did that for our project, it was real helpful in reducing reported
errors from people forgetting to build our manual dependencies.
Missing:
----------
1) org.jboss.test-harness:jboss-test-harness:jar:1.0.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.jboss.test-harness
-DartifactId=jboss-test-harness -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.jboss.test-harness
-DartifactId=jboss-test-harness -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.jboss.seam:seam-parent:pom:3.0.0-SNAPSHOT
2) org.jboss.test-harness:jboss-test-harness:jar:1.0.0-SNAPSHOT
2) org.jboss.webbeans:webbeans-core-test:jar:1.0.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.jboss.webbeans -DartifactId=webbeans-core-test
-Dversion=1.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.jboss.webbeans -DartifactId=webbeans-core-test
-Dversion=1.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]
Path to dependency:
1) org.jboss.seam:seam-parent:pom:3.0.0-SNAPSHOT
2) org.jboss.webbeans:webbeans-core-test:jar:1.0.0-SNAPSHOT
----------
2 required artifacts are missing.
for artifact:
org.jboss.seam:seam-parent:pom:3.0.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
repository.jboss.org (http://repository.jboss.org/maven2),
snapshots.jboss.org (http://snapshots.jboss.org/maven2)
10:25 a.m.
New subject: seam modules questions: missing artifacts: webbeans-core-test & jboss-test-harness + is readme.txt correct?...missing parent?
OK. I've got the sample Gavin provided in the forums working. Let me
know when you want them committed. I assume it'd be better for me to
wait till persistence is building.
Speaking of tests...for testing the module, do you have tests you'd like
for me to model the tests after?
If not, I'll just write put some standard TestNG + HSQLDB tests up to
get started.
Thanks,
Steven
Pete Muir wrote:
Hi Steven,
Looks like the build is very out of date, and we need to get it fixed up.
I've at least got the persistence module building.
On 22 Nov 2009, at 16:36, Steven Boscarine wrote:
> I am trying to build https://svn.jboss.org/repos/seam/modules/trunk
>
> Is parent missing?:
> I followed the instructions in readme.txt and built version-matrix. I couldn't
follow the steps about building parent.
https://svn.jboss.org/repos/seam/modules/trunk/readme.txt Parent appears to be deleted on
5/29 ( http://fisheye.jboss.org/browse/Seam/modules/trunk/parent). Am I missing
something?
>
>
> When I checkout modules, I'm greeted with a build error (pasted below) because it
cannot find org.jboss.webbeans:webbeans-core-test:jar:1.0.0-SNAPSHOT and
org.jboss.test-harness:jboss-test-harness:jar:1.0.0-SNAPSHOT.
> Is it possible to have a CI build push webbeans-core-test & jboss-test-harness to
the jboss repos? When we did that for our project, it was real helpful in reducing
reported errors from people forgetting to build our manual dependencies.
>
>
>
> Missing:
> ----------
> 1) org.jboss.test-harness:jboss-test-harness:jar:1.0.0-SNAPSHOT
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.jboss.test-harness
-DartifactId=jboss-test-harness -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file there:
> mvn deploy:deploy-file -DgroupId=org.jboss.test-harness
-DartifactId=jboss-test-harness -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) org.jboss.seam:seam-parent:pom:3.0.0-SNAPSHOT
> 2) org.jboss.test-harness:jboss-test-harness:jar:1.0.0-SNAPSHOT
>
> 2) org.jboss.webbeans:webbeans-core-test:jar:1.0.0-SNAPSHOT
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.jboss.webbeans
-DartifactId=webbeans-core-test -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file there:
> mvn deploy:deploy-file -DgroupId=org.jboss.webbeans
-DartifactId=webbeans-core-test -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) org.jboss.seam:seam-parent:pom:3.0.0-SNAPSHOT
> 2) org.jboss.webbeans:webbeans-core-test:jar:1.0.0-SNAPSHOT
>
> ----------
> 2 required artifacts are missing.
>
> for artifact:
> org.jboss.seam:seam-parent:pom:3.0.0-SNAPSHOT
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> repository.jboss.org (http://repository.jboss.org/maven2),
> snapshots.jboss.org (http://snapshots.jboss.org/maven2)
>
>
>
10:29 a.m.
New subject: seam modules questions: missing artifacts: webbeans-core-test & jboss-test-harness + is readme.txt correct?...missing parent?
Persistence is building now :-) So you can commit whenever you want...
I would suggest following the weld/tests module tests for now, as I guess all of these
tests should run in an EE env. I can walk you through setting this up if needed (I'll
use the exercise to write a wiki page).
On 23 Nov 2009, at 16:25, Steven Boscarine wrote:
OK. I've got the sample Gavin provided in the forums working.
Let me know when you want them committed. I assume it'd be better for me to wait till
persistence is building.
Speaking of tests...for testing the module, do you have tests you'd like for me to
model the tests after? If not, I'll just write put some standard TestNG + HSQLDB tests
up to get started.
Thanks,
Steven
Pete Muir wrote:
> Hi Steven,
>
> Looks like the build is very out of date, and we need to get it fixed up.
>
> I've at least got the persistence module building.
>
> On 22 Nov 2009, at 16:36, Steven Boscarine wrote:
>
>
>> I am trying to build https://svn.jboss.org/repos/seam/modules/trunk
>>
>> Is parent missing?:
>> I followed the instructions in readme.txt and built version-matrix. I
couldn't follow the steps about building parent.
https://svn.jboss.org/repos/seam/modules/trunk/readme.txt Parent appears to be deleted on
5/29 ( http://fisheye.jboss.org/browse/Seam/modules/trunk/parent). Am I missing
something?
>>
>>
>> When I checkout modules, I'm greeted with a build error (pasted below)
because it cannot find org.jboss.webbeans:webbeans-core-test:jar:1.0.0-SNAPSHOT and
org.jboss.test-harness:jboss-test-harness:jar:1.0.0-SNAPSHOT. Is it possible to have a CI
build push webbeans-core-test & jboss-test-harness to the jboss repos? When we did
that for our project, it was real helpful in reducing reported errors from people
forgetting to build our manual dependencies.
>>
>>
>> Missing:
>> ----------
>> 1) org.jboss.test-harness:jboss-test-harness:jar:1.0.0-SNAPSHOT
>>
>> Try downloading the file manually from the project website.
>>
>> Then, install it using the command:
>> mvn install:install-file -DgroupId=org.jboss.test-harness
-DartifactId=jboss-test-harness -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
>>
>> Alternatively, if you host your own repository you can deploy the file there:
>> mvn deploy:deploy-file -DgroupId=org.jboss.test-harness
-DartifactId=jboss-test-harness -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>
>> Path to dependency:
>> 1) org.jboss.seam:seam-parent:pom:3.0.0-SNAPSHOT
>> 2) org.jboss.test-harness:jboss-test-harness:jar:1.0.0-SNAPSHOT
>>
>> 2) org.jboss.webbeans:webbeans-core-test:jar:1.0.0-SNAPSHOT
>>
>> Try downloading the file manually from the project website.
>>
>> Then, install it using the command:
>> mvn install:install-file -DgroupId=org.jboss.webbeans
-DartifactId=webbeans-core-test -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
>>
>> Alternatively, if you host your own repository you can deploy the file there:
>> mvn deploy:deploy-file -DgroupId=org.jboss.webbeans
-DartifactId=webbeans-core-test -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>
>> Path to dependency:
>> 1) org.jboss.seam:seam-parent:pom:3.0.0-SNAPSHOT
>> 2) org.jboss.webbeans:webbeans-core-test:jar:1.0.0-SNAPSHOT
>>
>> ----------
>> 2 required artifacts are missing.
>>
>> for artifact:
>> org.jboss.seam:seam-parent:pom:3.0.0-SNAPSHOT
>>
>> from the specified remote repositories:
>> central (http://repo1.maven.org/maven2),
>> repository.jboss.org (http://repository.jboss.org/maven2),
>> snapshots.jboss.org (http://snapshots.jboss.org/maven2)
>>
>>
>>
>
>
10:08 p.m.
New subject: FYI: Code from forum committed in seam-persistence and seam-transaction.
I committed the code from
http://www.seamframework.org/Community/HowDoIGetAJPAEntityManagerReferenc...
to https://svn.jboss.org/repos/seam/modules/trunk/persistence
and https://svn.jboss.org/repos/seam/modules/trunk/transaction
I imported persistence into a trivial web app and it appears to work. I
haven't had time to write any useful tests yet.
The transaction project is not compiling. Perhaps it's older code? I
commented out the dependencies that are not on the repo and changed
jsr299-api to cdi-api. It was originally failing to validate because it
was missing ${webbeans.groupId}.
6:05 a.m.
New subject: FYI: Code from forum committed in seam-persistence and seam-transaction.
I think we can delete the transaction module, and just put all of this in persistence. I
can't see why you would want one module and not the other....
On 24 Nov 2009, at 04:08, Steven Boscarine wrote:
I committed the code from
http://www.seamframework.org/Community/HowDoIGetAJPAEntityManagerReferenc...
to https://svn.jboss.org/repos/seam/modules/trunk/persistence
and https://svn.jboss.org/repos/seam/modules/trunk/transaction
I imported persistence into a trivial web app and it appears to work. I haven't had
time to write any useful tests yet.
The transaction project is not compiling. Perhaps it's older code? I commented out
the dependencies that are not on the repo and changed jsr299-api to cdi-api. It was
originally failing to validate because it was missing ${webbeans.groupId}.
6:56 a.m.
New subject: FYI: Code from forum committed in seam-persistence and seam-transaction.
Agreed. We should view transactions+persistence as an atomic concern.
-Dan
On Tue, Nov 24, 2009 at 7:05 AM, Pete Muir <pmuir(a)redhat.com> wrote:
I think we can delete the transaction module, and just put all of
this in
persistence. I can't see why you would want one module and not the other....
On 24 Nov 2009, at 04:08, Steven Boscarine wrote:
> I committed the code from
http://www.seamframework.org/Community/HowDoIGetAJPAEntityManagerReferenc...
https://svn.jboss.org/repos/seam/modules/trunk/persistence
> and https://svn.jboss.org/repos/seam/modules/trunk/transaction
>
> I imported persistence into a trivial web app and it appears to work. I
haven't had time to write any useful tests yet.
>
> The transaction project is not compiling. Perhaps it's older code? I
commented out the dependencies that are not on the repo and changed
jsr299-api to cdi-api. It was originally failing to validate because it was
missing ${webbeans.groupId}.
>
>
>
>
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
7:55 a.m.
New subject: FYI: Code from forum committed in seam-persistence and seam-transaction.
That's ok by me.
Sent from my iPhone
On Nov 24, 2009, at 7:05 AM, Pete Muir <pmuir(a)redhat.com> wrote:
I think we can delete the transaction module, and just put all of
this in persistence. I can't see why you would want one module and
not the other....
On 24 Nov 2009, at 04:08, Steven Boscarine wrote:
> I committed the code from
http://www.seamframework.org/Community/HowDoIGetAJPAEntityManagerReferenc...
> to https://svn.jboss.org/repos/seam/modules/trunk/persistence
> and https://svn.jboss.org/repos/seam/modules/trunk/transaction
>
> I imported persistence into a trivial web app and it appears to
> work. I haven't had time to write any useful tests yet.
>
> The transaction project is not compiling. Perhaps it's older
> code? I commented out the dependencies that are not on the repo
> and changed jsr299-api to cdi-api. It was originally failing to
> validate because it was missing ${webbeans.groupId}.
>
>
>
>
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
6:58 a.m.
New subject: FYI: Code from forum committed in seam-persistence and seam-transaction.
Just a note, several of the Seam 3 modules were in need updating, so don't
be surprised if you run across one that doesn't compile. Just fix it and
bring it up to speed.
-Dan
On Mon, Nov 23, 2009 at 11:08 PM, Steven Boscarine <
steven.boscarine(a)childrens.harvard.edu> wrote:
I committed the code from
http://www.seamframework.org/Community/HowDoIGetAJPAEntityManagerReferenc...
to https://svn.jboss.org/repos/seam/modules/trunk/persistence
and https://svn.jboss.org/repos/seam/modules/trunk/transaction
I imported persistence into a trivial web app and it appears to work. I
haven't had time to write any useful tests yet.
The transaction project is not compiling. Perhaps it's older code? I
commented out the dependencies that are not on the repo and changed
jsr299-api to cdi-api. It was originally failing to validate because it
was missing ${webbeans.groupId}.
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
7 a.m.
New subject: FYI: Code from forum committed in seam-persistence and seam-transaction.
Right, treat most of these modules with a large amount of suspicion ;-)
On 24 Nov 2009, at 12:58, Dan Allen wrote:
Just a note, several of the Seam 3 modules were in need updating, so
don't be surprised if you run across one that doesn't compile. Just fix it and
bring it up to speed.
-Dan
On Mon, Nov 23, 2009 at 11:08 PM, Steven Boscarine
<steven.boscarine(a)childrens.harvard.edu> wrote:
I committed the code from
http://www.seamframework.org/Community/HowDoIGetAJPAEntityManagerReferenc...
to https://svn.jboss.org/repos/seam/modules/trunk/persistence
and https://svn.jboss.org/repos/seam/modules/trunk/transaction
I imported persistence into a trivial web app and it appears to work. I
haven't had time to write any useful tests yet.
The transaction project is not compiling. Perhaps it's older code? I
commented out the dependencies that are not on the repo and changed
jsr299-api to cdi-api. It was originally failing to validate because it
was missing ${webbeans.groupId}.
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
7:29 a.m.
New subject: seam modules questions: missing artifacts: webbeans-core-test & jboss-test-harness + is readme.txt correct?...missing parent?
Can we start using Arquillian+Shrinkwrap for Seam integration-style testing?
Btw, Christian informally suggested that he would lend a hand in porting his
DBUnit-style test extension to Arquillian. I'm not sure whether that belongs
in the Seam test module or in arquillian proper. That's your call, Pete.
-Dan
On Mon, Nov 23, 2009 at 11:29 AM, Pete Muir <pmuir(a)redhat.com> wrote:
Persistence is building now :-) So you can commit whenever you
want...
I would suggest following the weld/tests module tests for now, as I guess
all of these tests should run in an EE env. I can walk you through setting
this up if needed (I'll use the exercise to write a wiki page).
On 23 Nov 2009, at 16:25, Steven Boscarine wrote:
> OK. I've got the sample Gavin provided in the forums working. Let me
know when you want them committed. I assume it'd be better for me to wait
till persistence is building.
> Speaking of tests...for testing the module, do you have tests you'd like
for me to model the tests after? If not, I'll just write put some standard
TestNG + HSQLDB tests up to get started.
> Thanks,
> Steven
>
> Pete Muir wrote:
>> Hi Steven,
>>
>> Looks like the build is very out of date, and we need to get it fixed
up.
>>
>> I've at least got the persistence module building.
>>
>> On 22 Nov 2009, at 16:36, Steven Boscarine wrote:
>>
>>
>>> I am trying to build https://svn.jboss.org/repos/seam/modules/trunk
>>>
>>> Is parent missing?:
>>> I followed the instructions in readme.txt and built version-matrix. I
couldn't follow the steps about building parent.
https://svn.jboss.org/repos/seam/modules/trunk/readme.txt Parent appears
to be deleted on 5/29 (
http://fisheye.jboss.org/browse/Seam/modules/trunk/parent). Am I
missing something?
>>>
>>>
>>> When I checkout modules, I'm greeted with a build error (pasted below)
because it cannot find
org.jboss.webbeans:webbeans-core-test:jar:1.0.0-SNAPSHOT and
org.jboss.test-harness:jboss-test-harness:jar:1.0.0-SNAPSHOT. Is it possible
to have a CI build push webbeans-core-test & jboss-test-harness to the jboss
repos? When we did that for our project, it was real helpful in reducing
reported errors from people forgetting to build our manual dependencies.
>>>
>>>
>>> Missing:
>>> ----------
>>> 1) org.jboss.test-harness:jboss-test-harness:jar:1.0.0-SNAPSHOT
>>>
>>> Try downloading the file manually from the project website.
>>>
>>> Then, install it using the command:
>>> mvn install:install-file -DgroupId=org.jboss.test-harness
-DartifactId=jboss-test-harness -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
>>>
>>> Alternatively, if you host your own repository you can deploy the file
there:
>>> mvn deploy:deploy-file -DgroupId=org.jboss.test-harness
-DartifactId=jboss-test-harness -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>>
>>> Path to dependency:
>>> 1) org.jboss.seam:seam-parent:pom:3.0.0-SNAPSHOT
>>> 2) org.jboss.test-harness:jboss-test-harness:jar:1.0.0-SNAPSHOT
>>>
>>> 2) org.jboss.webbeans:webbeans-core-test:jar:1.0.0-SNAPSHOT
>>>
>>> Try downloading the file manually from the project website.
>>>
>>> Then, install it using the command:
>>> mvn install:install-file -DgroupId=org.jboss.webbeans
-DartifactId=webbeans-core-test -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
>>>
>>> Alternatively, if you host your own repository you can deploy the file
there:
>>> mvn deploy:deploy-file -DgroupId=org.jboss.webbeans
-DartifactId=webbeans-core-test -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>>
>>> Path to dependency:
>>> 1) org.jboss.seam:seam-parent:pom:3.0.0-SNAPSHOT
>>> 2) org.jboss.webbeans:webbeans-core-test:jar:1.0.0-SNAPSHOT
>>>
>>> ----------
>>> 2 required artifacts are missing.
>>>
>>> for artifact:
>>> org.jboss.seam:seam-parent:pom:3.0.0-SNAPSHOT
>>>
>>> from the specified remote repositories:
>>> central (http://repo1.maven.org/maven2),
>>> repository.jboss.org (http://repository.jboss.org/maven2),
>>> snapshots.jboss.org (http://snapshots.jboss.org/maven2)
>>>
>>>
>>>
>>
>>
>
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
7:49 a.m.
New subject: seam modules questions: missing artifacts: webbeans-core-test & jboss-test-harness + is readme.txt correct?...missing parent?
On 24 Nov 2009, at 13:29, Dan Allen wrote:
Can we start using Arquillian+Shrinkwrap for Seam integration-style
testing?
This would be ideal. Aslak, how far are we away from this being a reality? We need support
for at least one container I guess (Embedded JBoss should do, if it supports Weld yet,
this is on my todo list :-), a release, and probably some of the intelligent defaulting in
the @Deployment.
Pete
8:09 a.m.
New subject: seam modules questions: missing artifacts: webbeans-core-test & jboss-test-harness + is readme.txt correct?...missing parent?
I'm in the middle of a bit of reorg/abstracting atm, but this should be done
pretty soon.
If EmbeddedAS can handle Weld, the only thing we need is a
'WeldTestEnricher' to have support for test case field injection etc.. At
least when it comes to testing Weld components.
For JSF stuff, if any, we have to creating ...something...
-aslak-
2009/11/24 Pete Muir <pmuir(a)redhat.com>
On 24 Nov 2009, at 13:29, Dan Allen wrote:
> Can we start using Arquillian+Shrinkwrap for Seam integration-style
testing?
This would be ideal. Aslak, how far are we away from this being a reality?
We need support for at least one container I guess (Embedded JBoss should
do, if it supports Weld yet, this is on my todo list :-), a release, and
probably some of the intelligent defaulting in the @Deployment.
Pete
--
--
Aslak Knutsen; +47 952 38 791; fax +47 22 33 60 24
Kongens gate 14; Boks 805 Sentrum, 0104 Oslo;
http://www.conduct.no; mailto:aslak@conduct.no
Conduct AS - Professional Open Source Services
- Red Hat/JBoss Premier System Integrator
- Pentaho Preferred Integration Partner
- Atlassian Technology Partner
8:14 a.m.
New subject: seam modules questions: missing artifacts: webbeans-core-test & jboss-test-harness + is readme.txt correct?...missing parent?
On 24 Nov 2009, at 14:09, Aslak Knutsen wrote:
I'm in the middle of a bit of reorg/abstracting atm, but this
should be done pretty soon.
If EmbeddedAS can handle Weld, the only thing we need is a 'WeldTestEnricher' to
have support for test case field injection etc.. At least when it comes to testing Weld
components.
For JSF stuff, if any, we have to creating ...something...
We can use Alex Smirnov's mock JSF library he created for RichFaces 4 for this I hope.
Alex, what is the status of this?
Alternatively, it should be trivial to add "real" JBoss AS support to Arquillian
right?
-aslak-
2009/11/24 Pete Muir <pmuir(a)redhat.com>
On 24 Nov 2009, at 13:29, Dan Allen wrote:
> Can we start using Arquillian+Shrinkwrap for Seam integration-style testing?
This would be ideal. Aslak, how far are we away from this being a reality? We need
support for at least one container I guess (Embedded JBoss should do, if it supports Weld
yet, this is on my todo list :-), a release, and probably some of the intelligent
defaulting in the @Deployment.
Pete
--
--
Aslak Knutsen; +47 952 38 791; fax +47 22 33 60 24
Kongens gate 14; Boks 805 Sentrum, 0104 Oslo;
http://www.conduct.no; mailto:aslak@conduct.no
Conduct AS - Professional Open Source Services
- Red Hat/JBoss Premier System Integrator
- Pentaho Preferred Integration Partner
- Atlassian Technology Partner
8:19 a.m.
New subject: seam modules questions: missing artifacts: webbeans-core-test & jboss-test-harness + is readme.txt correct?...missing parent?
I have a Jboss 'Remote' Container up and running locally.. (much faster then
Embedded.. :)
I was more wondering how a testcase testing real JSF would look, running in
JUnit.
-aslak-
2009/11/24 Pete Muir <pmuir(a)redhat.com>
On 24 Nov 2009, at 14:09, Aslak Knutsen wrote:
> I'm in the middle of a bit of reorg/abstracting atm, but this should be
done pretty soon.
>
> If EmbeddedAS can handle Weld, the only thing we need is a
'WeldTestEnricher' to have support for test case field injection etc.. At
least when it comes to testing Weld components.
>
> For JSF stuff, if any, we have to creating ...something...
We can use Alex Smirnov's mock JSF library he created for RichFaces 4 for
this I hope. Alex, what is the status of this?
Alternatively, it should be trivial to add "real" JBoss AS support to
Arquillian right?
>
>
> -aslak-
>
>
>
> 2009/11/24 Pete Muir <pmuir(a)redhat.com>
>
> On 24 Nov 2009, at 13:29, Dan Allen wrote:
>
> > Can we start using Arquillian+Shrinkwrap for Seam integration-style
testing?
>
> This would be ideal. Aslak, how far are we away from this being a
reality? We need support for at least one container I guess (Embedded JBoss
should do, if it supports Weld yet, this is on my todo list :-), a release,
and probably some of the intelligent defaulting in the @Deployment.
>
> Pete
>
>
>
> --
> --
> Aslak Knutsen; +47 952 38 791; fax +47 22 33 60 24
> Kongens gate 14; Boks 805 Sentrum, 0104 Oslo;
> http://www.conduct.no; mailto:aslak@conduct.no
>
> Conduct AS - Professional Open Source Services
> - Red Hat/JBoss Premier System Integrator
> - Pentaho Preferred Integration Partner
> - Atlassian Technology Partner
--
--
Aslak Knutsen; +47 952 38 791; fax +47 22 33 60 24
Kongens gate 14; Boks 805 Sentrum, 0104 Oslo;
http://www.conduct.no; mailto:aslak@conduct.no
Conduct AS - Professional Open Source Services
- Red Hat/JBoss Premier System Integrator
- Pentaho Preferred Integration Partner
- Atlassian Technology Partner
8:31 a.m.
New subject: seam modules questions: missing artifacts: webbeans-core-test & jboss-test-harness + is readme.txt correct?...missing parent?
On 24 Nov 2009, at 14:19, Aslak Knutsen wrote:
I have a Jboss 'Remote' Container up and running locally..
(much faster then Embedded.. :)
I was more wondering how a testcase testing real JSF would look, running in JUnit.
You would use either HtmlUnit or JSFUnit. This executes the test in the local VM, and
mocks out the web browser. There is some of this in the TCK.
-aslak-
2009/11/24 Pete Muir <pmuir(a)redhat.com>
On 24 Nov 2009, at 14:09, Aslak Knutsen wrote:
> I'm in the middle of a bit of reorg/abstracting atm, but this should be done
pretty soon.
>
> If EmbeddedAS can handle Weld, the only thing we need is a
'WeldTestEnricher' to have support for test case field injection etc.. At least
when it comes to testing Weld components.
>
> For JSF stuff, if any, we have to creating ...something...
We can use Alex Smirnov's mock JSF library he created for RichFaces 4 for this I
hope. Alex, what is the status of this?
Alternatively, it should be trivial to add "real" JBoss AS support to
Arquillian right?
>
>
> -aslak-
>
>
>
> 2009/11/24 Pete Muir <pmuir(a)redhat.com>
>
> On 24 Nov 2009, at 13:29, Dan Allen wrote:
>
> > Can we start using Arquillian+Shrinkwrap for Seam integration-style testing?
>
> This would be ideal. Aslak, how far are we away from this being a reality? We need
support for at least one container I guess (Embedded JBoss should do, if it supports Weld
yet, this is on my todo list :-), a release, and probably some of the intelligent
defaulting in the @Deployment.
>
> Pete
>
>
>
> --
> --
> Aslak Knutsen; +47 952 38 791; fax +47 22 33 60 24
> Kongens gate 14; Boks 805 Sentrum, 0104 Oslo;
> http://www.conduct.no; mailto:aslak@conduct.no
>
> Conduct AS - Professional Open Source Services
> - Red Hat/JBoss Premier System Integrator
> - Pentaho Preferred Integration Partner
> - Atlassian Technology Partner
--
--
Aslak Knutsen; +47 952 38 791; fax +47 22 33 60 24
Kongens gate 14; Boks 805 Sentrum, 0104 Oslo;
http://www.conduct.no; mailto:aslak@conduct.no
Conduct AS - Professional Open Source Services
- Red Hat/JBoss Premier System Integrator
- Pentaho Preferred Integration Partner
- Atlassian Technology Partner
12:09 p.m.
New subject: [seam-dev] Next steps
Hello,
how is Hibernate Search going to be integrated? In the same way as it
did in Seam 1 and 2 (being provided by the persistence module) ?
Maybe it could be useful to design it as a separate module; in this
case it could be used to provide more useful tools than only injecting
a FullTextSession or FullTextEntityManager, like:
* providing query builder helpers
* low level index access
* search filters integrated with Seam security (hide unauthorized results)
* to store data in the index directly
* have indexReaders (and related search caches) interact with Seam/Weld events
just some ideas
regards,
Sanne
2009/11/22 Pete Muir <pmuir(a)redhat.com>:
We already have a module called persistence in seam modules (see Seam
trunk). You can use that :-)
You'll want to delete all the existing classes that are there, we don't need
those.
I gave you commit on Seam, but please make sure you sign the CLA for Seam as well on
jboss.org
On 22 Nov 2009, at 12:47, Steven Boscarine wrote:
> Sure. Would it make sense to give it a home first?
>
> Do you have a SVN home and artifact/groupId in mind?
>
> Pete Muir wrote:
>> 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
>>>
>>
>>
>
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
6:51 a.m.
New subject: [seam-dev] Next steps
These ideas sound great Sanne!
On 22 Nov 2009, at 18:09, Sanne Grinovero wrote:
Hello,
how is Hibernate Search going to be integrated? In the same way as it
did in Seam 1 and 2 (being provided by the persistence module) ?
Maybe it could be useful to design it as a separate module; in this
case it could be used to provide more useful tools than only injecting
a FullTextSession or FullTextEntityManager, like:
* providing query builder helpers
* low level index access
* search filters integrated with Seam security (hide unauthorized results)
* to store data in the index directly
* have indexReaders (and related search caches) interact with Seam/Weld events
just some ideas
regards,
Sanne
2009/11/22 Pete Muir <pmuir(a)redhat.com>:
> We already have a module called persistence in seam modules (see Seam trunk). You can
use that :-)
>
> You'll want to delete all the existing classes that are there, we don't need
those.
>
> I gave you commit on Seam, but please make sure you sign the CLA for Seam as well on
jboss.org
>
> On 22 Nov 2009, at 12:47, Steven Boscarine wrote:
>
>> Sure. Would it make sense to give it a home first?
>>
>> Do you have a SVN home and artifact/groupId in mind?
>>
>> Pete Muir wrote:
>>> 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
>>>>
>>>
>>>
>>
>
>
> _______________________________________________
> seam-dev mailing list
> seam-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
5479
days inactive
5483
days old
37 comments
10 participants
participants (10)
-
Aslak Knutsen -
Boscarine, Steven -
Clint Popetz -
Dan Allen -
Gavin King -
Nicklas Karlsson -
Pete Muir -
Peter Royle -
Sanne Grinovero -
Steven Boscarine