Seam 3: webbeans-logging/webbeans-logger
by Pete Muir
You should probably depend on webbeans-logger, not webbeans-logging (-
logging simply provides the logging core, so that the RI can depend on
it, -logger is the portable module).
17 years
Re: [seam-dev] Seam 2.2.0.CR1 release
by Pete Muir
I've applied your patch - looks good, please test at your end.
On 15 Jun 2009, at 01:46, Stuart Douglas wrote:
>
> I have submitted a patch that should fix the issues in JIRA, but
> there are still quite a few that have not been reported yet,
> probably because there are not very many multi-war seam apps in
> production. Most of these issues can be fixed piecemeal, and the
> ones that can't are probably obscure enough that people will not run
> into them (e.g. selecting which app context you want to use when
> injecting seam components into spring beans).
>
> A few of the cases where the wrong application context can be used:
>
> - async methods may use the wrong app context
> - all users of ContextualHttpRequest may run in the wrong app
> context (remoting and resteasy are the main ones)
> - Message Driven beans will always run in an arbitary application
> context (this can't really be fixed, but I don't really like the
> idea that the context that they run in is undefined, depending on
> the order that the apps are deployed)
> - Spring integration (not really fixable)
> - There may be some problems with the Jbpm SeamUserCodeInterceptor
>
> If there are no problems with the last patch I will do up a patch
> for the ContextualHttpRequest and async method issues later this
> week. The async method patch will probably be a bit messy, because
> it will involve passing the application context around inside all
> the dispatchers.
>
>
> Stuart
>
>
>
> -----Original Message-----
> From: Dan Allen [mailto:dan.j.allen@gmail.com]
> Sent: Sat 13/06/2009 10:21 AM
> To: Pete Muir
> Cc: Stuart Douglas; seam-dev(a)lists.jboss.org
> Subject: Re: [seam-dev] Seam 2.2.0.CR1 release
>
> On Fri, Jun 12, 2009 at 6:10 AM, Pete Muir <pmuir(a)redhat.com> 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).
>
> 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.
>
>
17 years
Seam 2.2.0.CR1 release
by Norman Richards
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.
17 years
build before restore
by Ian Michell
Hi All,
I'm new to the list...
Hash anyone noticed that the facelet parameter BUILD_BEFORE_RESTORE breaks
pageflow (as in, using a normal JSF form refuses to continue run the
pageflow)? Once the parameter is removed from the web xml pageflow starts
working again.
I'm not sure if I should raise this in Jira as it's not really got a lot to
do with seam itself but seems from my own research that facelets is doing
something funny with the view state or killing the old one...
Ian
17 years
Upgrade of hibernate-core -> missing
by Marek Novotny
I have noticed that the build in 2_2 branch is broken due missing
transitive dependency org.slf4j:slf4j:1.5.2
I had to add exclusion to hibernate-core dependency on my local disk:
<exclusion>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
</exclusion>
to finish build.
What version of slf4j-api should be in Seam 2.2 if we have specified
version 1.4.2 of slf4j-log4j12?
--
Marek Novotny
--
JBoss Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
Email: mnovotny(a)redhat.com
Office phone: +420 532 294 287, ext. 82-62 087
mobile: +420 608 509 230
------------------------------------------------------
Looking to carve out IT costs?
www.europe.redhat.com/promo/carveoutcosts/
17 years
Classdef not found NoClassDefFoundError: org/drools/decisiontable/SpreadsheetCompiler
by Jay Balunas
I probably caught this in between changes (since I'm updating RF version now
too), but seam gen ear project threw this when I deployed to AS 5.0.1
Caused by: java.lang.NoClassDefFoundError:
org/drools/decisiontable/SpreadsheetCompiler
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2427)
at java.lang.Class.privateGetPublicMethods(Class.java:2547)
Also I noticed that there were additional changes to the root.pom.xml that
we not in the ivy files (afaict) in seam-gen.
Once I can deploy seam-gen to AS 5 I'll be ready with RichFaces upgrade for
2.2
-Jay
--
blog: http://in.relation.to/Bloggers/Jay
17 years
Seam 2.1.2 release
by Norman Richards
It's out. I'm still waiting on IT to updated the latest/latest-2/
latest-2.1 docs links, but otherwise the release process should be
done.
17 years
New JBoss Tools with Seam refactoring
by Max Rydahl Andersen
Hi,
http://in.relation.to/Bloggers/JBossTools31MilestoneReleased
Would be great if you guys could try out the seam refactoring and let us
know if it works as you expect it to.
For now it is only for @Name and <component> - not for other ways to
declare a name (i.e. parameters etc.)
(we already found one bug when you rename components that comes from a
.jar, i.e. the builtin ones, so
either use nightly build or only rename seam components that are from
your own project :)
p.s. It is still a M1 build so be gentle :)
//max
17 years
Seam 2.2 branch
by Norman Richards
I've created the Seam_2_2 branch, and I think I've bumped all the
version numbers. It looks good to go for 2.2 issues...
17 years
