Seam 2.2.0.CR1 release
|
View:
New views
9 Messages
—
Rating Filter:
Alert me
|
 |
Seam 2.2.0.CR1 release
by Norman Richards
::
Rate this Message:
As per discussions off list, the Seam 2.2.0.CR1 release countdown is
starting. I've moved all Seam 2.2 issues to 2.2.1 in JIRA. If you have any fixes for 2.2.0, you should get them in today. We'll most likely be tagging tomorrow. _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.2.0.CR1 release
by Dan Allen (mojavelinux)
::
Rate this Message:
Wow, you weren't kidding that you're going to turn this release around quick.
-Dan On Thu, Jun 11, 2009 at 12:39 PM, Norman Richards <orb@...> wrote: As per discussions off list, the Seam 2.2.0.CR1 release countdown is starting. I've moved all Seam 2.2 issues to 2.2.1 in JIRA. If you have any fixes for 2.2.0, you should get them in today. We'll most likely be tagging tomorrow._______________________________________________ -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction http://in.relation.to/Bloggers/Dan NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention. _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.2.0.CR1 release
by Pete Muir-2
::
Rate this Message:
:-)
Some background - JBoss ship Seam as part of the EAP platform, and have requested a couple of library upgrades (Drools 5, RichFaces 3.3, Hibernate 3.3) which warrant bumping the version number. Otherwise this release will simply be a continuation of the 2.1 series... On 11 Jun 2009, at 17:59, Dan Allen wrote: > Wow, you weren't kidding that you're going to turn this release > around quick. > > -Dan > > On Thu, Jun 11, 2009 at 12:39 PM, Norman Richards <orb@... > > wrote: > As per discussions off list, the Seam 2.2.0.CR1 release countdown is > starting. I've moved all Seam 2.2 issues to 2.2.1 in JIRA. If you > have any fixes for 2.2.0, you should get them in today. We'll most > likely be tagging > tomorrow._______________________________________________ > seam-dev mailing list > seam-dev@... > https://lists.jboss.org/mailman/listinfo/seam-dev > > > > -- > Dan Allen > Senior Software Engineer, Red Hat | Author of Seam in Action > > http://mojavelinux.com > http://mojavelinux.com/seaminaction > http://in.relation.to/Bloggers/Dan > > NOTE: While I make a strong effort to keep up with my email on a daily > basis, personal or other work matters can sometimes keep me away > from my email. If you contact me, but don't hear back for more than > a week, > it is very likely that I am excessively backlogged or the message was > caught in the spam filters. Please don't hesitate to resend a > message if > you feel that it did not reach my attention. > _______________________________________________ > seam-dev mailing list > seam-dev@... > https://lists.jboss.org/mailman/listinfo/seam-dev _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
RE: Seam 2.2.0.CR1 release
by Stuart Douglas
::
Rate this Message:
Is there any chance that multi war app's will be fixed properly this release? _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.2.0.CR1 release
by Pete Muir-2
::
Rate this Message:
Stuart, I agree, this is long overdue.
I took a look at your patch, there seems to be a number of problems (System.out.println, changing of SPIs with no changes made to the JBoss5 int project at least), and it is essentially a workaround for a mistake in the underlying architecture, as a result I would prefer to defer this to 299, which does correctly scope all components to the relevant JEE module. If you can provide links to the relevant patches for the smaller stuff you mention below here, someone will look. On 12 Jun 2009, at 00:05, Stuart Douglas wrote: > > Is there any chance that multi war app's will be fixed properly this > release? > > If this is not possible I would like to submit some small patches to > fix some of the things that can be fixed easily, namely: > - problems with the identity component scoping (I already have a > patch for this, it just needs minor modification) > - The shared ResourceLoader problem > - A chapter in the docs to let people know exactly how multi-war > apps work in seam (there are two copies of every app scoped > component, asynchronous calls can't be sure witch context they are > actually executing in etc). > > Stuart > > -----Original Message----- > From: seam-dev-bounces@... on behalf of Pete Muir > Sent: Fri 12/06/2009 6:22 AM > To: Dan Allen > Cc: seam-dev@... Development List > Subject: Re: [seam-dev] Seam 2.2.0.CR1 release > > :-) > > Some background - JBoss ship Seam as part of the EAP platform, and > have requested a couple of library upgrades (Drools 5, RichFaces 3.3, > Hibernate 3.3) which warrant bumping the version number. Otherwise > this release will simply be a continuation of the 2.1 series... > > On 11 Jun 2009, at 17:59, Dan Allen wrote: > > > Wow, you weren't kidding that you're going to turn this release > > around quick. > > > > -Dan > > > > On Thu, Jun 11, 2009 at 12:39 PM, Norman Richards <orb@... > > > wrote: > > As per discussions off list, the Seam 2.2.0.CR1 release countdown is > > starting. I've moved all Seam 2.2 issues to 2.2.1 in JIRA. If you > > have any fixes for 2.2.0, you should get them in today. We'll most > > likely be tagging > > tomorrow._______________________________________________ > > seam-dev mailing list > > seam-dev@... > > https://lists.jboss.org/mailman/listinfo/seam-dev > > > > > > > > -- > > Dan Allen > > Senior Software Engineer, Red Hat | Author of Seam in Action > > > > http://mojavelinux.com > > http://mojavelinux.com/seaminaction > > http://in.relation.to/Bloggers/Dan > > > > NOTE: While I make a strong effort to keep up with my email on a > daily > > basis, personal or other work matters can sometimes keep me away > > from my email. If you contact me, but don't hear back for more than > > a week, > > it is very likely that I am excessively backlogged or the message > was > > caught in the spam filters. Please don't hesitate to resend a > > message if > > you feel that it did not reach my attention. > > _______________________________________________ > > seam-dev mailing list > > seam-dev@... > > https://lists.jboss.org/mailman/listinfo/seam-dev > > _______________________________________________ > seam-dev mailing list > seam-dev@... > https://lists.jboss.org/mailman/listinfo/seam-dev > > _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.2.0.CR1 release
by Dan Allen (mojavelinux)
::
Rate this Message:
On Fri, Jun 12, 2009 at 6:10 AM, Pete Muir <pmuir@...> wrote: Stuart, I agree, this is long overdue. Hmm, I was thinking this was going to get into 2.2 as well...or at least 2.2.1. I know that solving problems like this one is much easier and cleaner w/ 299 given that we have a chance to start over, but I worry that there are enough folks that really need this capability w/o refactoring the rest of their code. Even with 299 in place, if there is any Seam 2 code, users are still going to have the same issue (assuming that this problem is baggage that Seam 2 brings with it). Stuart, would you be willing to work through this piecemeal? That will make success much more likely. And this really would be huge for Seam 2 if we could get it fixed. -Dan -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction http://in.relation.to/Bloggers/Dan NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention. _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.2.0.CR1 release
by Pete Muir-2
::
Rate this Message:
On 13 Jun 2009, at 02:21, Dan Allen wrote: > On Fri, Jun 12, 2009 at 6:10 AM, Pete Muir <pmuir@...> wrote: > Stuart, I agree, this is long overdue. > > I took a look at your patch, there seems to be a number of problems > (System.out.println, changing of SPIs with no changes made to the > JBoss5 int project at least), and it is essentially a workaround for > a mistake in the underlying architecture, as a result I would prefer > to defer this to 299, which does correctly scope all components to > the relevant JEE module. > > Hmm, I was thinking this was going to get into 2.2 as well...or at > least 2.2.1. I know that solving problems like this one is much > easier and cleaner w/ 299 given that we have a chance to start over, > but I worry that there are enough folks that really need this > capability w/o refactoring the rest of their code. Even with 299 in > place, if there is any Seam 2 code, users are still going to have > the same issue (assuming that this problem is baggage that Seam 2 > brings with it). No, the problem is around incorrect attachment of the servlet context to the application. Well written modular extensions to 299 won't be dealing with this stuff, so it's not a problem. > > Stuart, would you be willing to work through this piecemeal? That > will make success much more likely. And this really would be huge > for Seam 2 if we could get it fixed. > > -Dan > > -- > Dan Allen > Senior Software Engineer, Red Hat | Author of Seam in Action > > http://mojavelinux.com > http://mojavelinux.com/seaminaction > http://in.relation.to/Bloggers/Dan > > NOTE: While I make a strong effort to keep up with my email on a daily > basis, personal or other work matters can sometimes keep me away > from my email. If you contact me, but don't hear back for more than > a week, > it is very likely that I am excessively backlogged or the message was > caught in the spam filters. Please don't hesitate to resend a > message if > you feel that it did not reach my attention. _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.2.0.CR1 release
by Pete Muir-2
::
Rate this Message:
On 14 Jun 2009, at 17:37, Pete Muir wrote: > > On 13 Jun 2009, at 02:21, Dan Allen wrote: > >> On Fri, Jun 12, 2009 at 6:10 AM, Pete Muir <pmuir@...> wrote: >> Stuart, I agree, this is long overdue. >> >> I took a look at your patch, there seems to be a number of problems >> (System.out.println, changing of SPIs with no changes made to the >> JBoss5 int project at least), and it is essentially a workaround >> for a mistake in the underlying architecture, as a result I would >> prefer to defer this to 299, which does correctly scope all >> components to the relevant JEE module. >> >> Hmm, I was thinking this was going to get into 2.2 as well...or at >> least 2.2.1. I know that solving problems like this one is much >> easier and cleaner w/ 299 given that we have a chance to start over, BTW this isn't the point, the point is that 299's design correctly allows for this, whilst the Seam 2 model doesn't, so without significant changes to semantics we can't fix it. >> but I worry that there are enough folks that really need this >> capability w/o refactoring the rest of their code. Even with 299 in >> place, if there is any Seam 2 code, users are still going to have >> the same issue (assuming that this problem is baggage that Seam 2 >> brings with it). > > No, the problem is around incorrect attachment of the servlet > context to the application. Well written modular extensions to 299 > won't be dealing with this stuff, so it's not a problem. > >> >> Stuart, would you be willing to work through this piecemeal? That >> will make success much more likely. And this really would be huge >> for Seam 2 if we could get it fixed. >> >> -Dan >> >> -- >> Dan Allen >> Senior Software Engineer, Red Hat | Author of Seam in Action >> >> http://mojavelinux.com >> http://mojavelinux.com/seaminaction >> http://in.relation.to/Bloggers/Dan >> >> NOTE: While I make a strong effort to keep up with my email on a >> daily >> basis, personal or other work matters can sometimes keep me away >> from my email. If you contact me, but don't hear back for more than >> a week, >> it is very likely that I am excessively backlogged or the message was >> caught in the spam filters. Please don't hesitate to resend a >> message if >> you feel that it did not reach my attention. > _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
|
| Free embeddable forum powered by Nabble | Forum Help |
