[pmuir]

Shervin, yes, I am refering to the seam-dev list. If you are really that interested in the way we work, then the face to face meetings look like:

• We normally have a team meeting f2f once a year, this year around Devoxx (see my blog)


• I saw Rodney, Gavin and Dan at JBoss World


• I saw Rodney and Marek in Brno at the RichFaces team meeting


• Gavin and Dan have done a few JUGs together


• I speak to Gavin on the phone about once a month, it is exclusively about JSR-299


• We have a bi-weekly telephone call at which we generally discuss team organization, what we've been working on etc. No design discussions here


• We chat on IM

That is it, trust me. And if an important design discussion happens, then it gets posted to the list.

Seam 3 wise, you can find the objectives in many presentations, as well as the major differences to Seam 2. We don't do formal architecture discussions, and certainly don't do UML or other stuff like that. There is no due date, it is an open source project. The svn is https://svn.jboss.org/repos/seam, just as it's always been, and has been described on this site.

[pmuir]

Arbi, ratchet down that paranoia a level ;-) We have no closed doors sessions that discuss architecture.

Clearly we get goals coming up internally, and as a lot of the developers are employed by Red Hat, that is completely fair in my mind. We take a lot of feedback from the community and distill it into the requirements for a new version, trust me.

[cash1981]

Hi Pete. Thanks for the response.
I will see you at Devoox and then we can chat some more. From what you say and what I have followed on the commit logs and the dev list, (which I have tried to email multiple times without my email getting through), there hasn't been so much work on Seam 3. I guess you guys have mostly used your resources to finish up JSR 299 and other related projects (JSF 2 etc).

Hopefully when Java EE 6 is out, then you will focus more attention and resources towards the development of Seam 3. There have been some discussion around how and what Seam 3 will look like, since much of the core will be replaced by Weld or another JSR 299 implementation, and will have the useful functionality of seam pdf, excel etc?

Anyways, thanks for shedding some light on this. See you all next week!
PS: I did signup for that Seam/Infinispan meeting, however I haven't gotten any more info or even a confirmation email. Any updates on time/place? Can you maybe also confirm that I have signed up? I had to change my flight just so I could attend this meeting on friday :-)

[asookazian]

http://blogs.jboss.org/blog/mlittle/2009/11/11/The_future_of_component_models.txt

so i pretty much read most of this article (skimming some of it).  doesn't really address my concerns about funding for Seam project (actual number of developers on the core team and responsiveness on the forum) and the advanced Seam training and a strategy/vision for how JBoss is going to sell more service contracts to enterprises, large and small, running Seam applications on various platforms and thus make Seam more ubiquitous in the Java space and enterprises.

he doesn't discuss any planned new features for Seam 3 either.

So I'm glad he posted this blog but not sure how much it helps, not much substance/meat to it.  I must say that MLittle is quite responsive, however...

btw, keyword adoption is missing in that blog!

[asookazian]

if the future of JBoss is Seam, then why is JBoss using Blosjom (http://wiki.blojsom.com/wiki/display/blojsom3/About+blojsom) as the technology for the blog where the MLittle article was posted, rather than something similar to the wiki project which is the technology behind this forum?

Seems like it should be a Seam app, no?

Therefore, that future for all of our projects and platform is Seam.

for all of our projects?

Why would all JBoss projects be concerned with JSF, EJB, Seam, JPA, etc.?

What does Infinispan, for example, have to do with that component model and that technology stack??

[pmuir]

Arbi, we give you want, and you still complain - talk about ungrateful ;-) BTW we like small teams - they are far more efficient than a big team :-)

Anyway, your point about infinspan is good - yes, even if you write a clustered app you want to write some business code to go with it. That code would be written using CDI, and Seam would provide an easy way to integrate with it (e.g. inject the datagrid provider).

[asookazian]

I complain even when I'm satisfied.  My family hates that part of my personality, too bad.  You can always do better, generally speaking.  I complain and GKing goes irate, from time to time anyways.  :)

Now I really need to stop posting so much and asking stupid questions (hey, go read the spec!) and dive into the 1.0.0 example code.

[nickarls]

Could be the other way around, too. That Seam will integrate with those, where applicable.