Presentation abstract

If you are one of the geeks attending this great Java conference, join me in Room 8 at 11:30 to learn how working remotely looks like and what happens when an agile team gets distributed.

See you there!

Why do you need to allocate time for gathering requirements/design/architecture work every iteration?

To make our meetings at SoftwareMill more interesting, we have implemented the idea of The Fourth Question, which I want to share here.

What is the question today?

Basically, apart from the usual three questions (Done yesterday. Plan for today. Blockers.) each member of the team answers additional one. What is the Fourth Question? Well, that is a good question

The question is announced by the ScrumMaster, who is free to come up with any question they like. This may be something connected with the project or personal.

Each day the question is different. Since in our team the person that leads the meetings changes every week, each member of the team has their chance to ask questions.

Examples

Here is a list of various questions that appeared on our Daily Scrums:

• How are you feeling today?
• Which day is the most effective day for you?
• How useful this meeting is for you?
• What have you learned recently?
• What is your favorite shortcut in our IDE?
• What should we do with people coming late for Scrum?
• What did you have for breakfast?
• What is your favorite movie?
• What board game did you play recently?
• What gadget have you bought or received recently?
• What sport did you practise recently? (And when it was? ;))
• Ideas to spend time with a child in winter.

Since we are a remote team, we have also asked each other questions like:

• What type of the office chair have you got?
• What have you got on your desk that is not connected with your work?
• Do you listen to the music when you work?
• How are you making notes?

(Authors: The Whole Team)

Areas of application

This technique

• is useful for coaching
• stimulates knowledge sharing
• will help team members to get to know each other
• will definitely introduce some fun and diversity

Guidelines

Of course having one more question might lead to the longer meetings, but with a little bit of discipline it is still possible to keep 15 minutes limit (If this gets difficult you can always ask “What can we do to keep the limit?” ;)).

It is a good practice to announce the question some time before the Daily Scrum. People will then come with the answers ready.

We favor simple questions that can be answered in one sentence.

Give it a try

If you like this idea, do not hesitate and introduce it on your next Daily Scrum meeting. Let me know how it worked in your team and what were your questions.

Have fun with the Fourth Question!

-Paweł

PS See also Łukasz’s post about this idea.

It is available since the 2.1.2 release of Seam, as a part of the IoC module, but if you happen to need it, the best choice is to grab the latest 2.2.0.GA version which includes a fix for the disinjection issue.

Disinjection

The problem with disinjection was that the implementation injected values to the fields annotated with @Inject, but did not clear those values after the method call. The disinjection step here is required for exactly the same reason that Seam itself performs it on @In- and @Out-jected fields - to prevent a long-scoped Seam component from holding a reference to a (possibly short-living) Guice component.

Also, the presence of disinjection allows you to @Inject non-serializable properties into serializable components without having to worry about making those properties transient.

Configuration and Docs

The configuration did not change, except for one detail, which is the “guice” namespace URL declaration in the components.xml file:

<components
xmlns="http://jboss.com/products/seam/components"
xmlns:guice="http://jboss.com/products/seam/guice">
...
</components>

All components are now in the org.jboss.seam.ioc.guice package.

If you feel like checking the latest documentation of the Seam-Guice module, here is the link:
http://docs.jboss.com/seam/2.2.0.GA/reference/en-US/html/guice.html.

Thanks to Dan Allen who reviewed my code and spotted the disinjection issue.

-Pawel

The presentation is called “Seam for Spring Developers” and will be a fast-track introduction to Seam and a “Seamish” way of thinking for those already experienced with other Java web frameworks, like Spring.

If you are around, make sure to choose Room 5 at 12.15

See you there.

-Pawel

Update: I’ve uploaded the presentation slides.

It verifies general understanding of the Seam 2.0 concepts, required to implement a simple Seam application.

The exam is now in the beta stage, which means it is available publicly and you can take the (beta) exam, which does not count for your belt progress. It will be released as soon as we collect enough stable questions in each category.

Like all exams available at JavaBlackBelt, it is free.

You are welcome to contribute your own questions and improve or rate existing ones.

Exam page

Cheers,
-Pawel

JBoss.org Statistics are powered by Kosmos, created by Aron Gombas. They run on JBoss Portal.

They come with a couple of interesting charts, which let you easily find out the most active commiters of the JBoss AS project:

JBoss Application Server - Most Active Commiters

or how new projects (like Envers) grow in size:

Envers project - Repository Entry History

Now, looking at the following chart, guess when the Seam Freamework releases occurred:

Seam Framework - Commit History

Well, 1.0 beta1 was out in September 2005, beta2 in February 2006, 1.0 GA in June. And so on Here is the full list.

On the “Most Active Files” diagrams I quickly discovered that usually the most frequently changed files are… Maven files

JBoss Microcontainer - Most Active Files

Needless to say, you will find more at stats.jboss.org.

Enjoy,
-Pawel

You may already have heard about Seam being a “deep integration framework” and Google Guice providing lightweight dependency injection. The news is that you can now easily use Seam together with Guice.

The WebBeans specification is built upon concepts from both of those frameworks. Since Seam provides Spring support in the IoC module, why not to integrate Guice as well? Thinking this way I have implemented Guice support for Seam.

Quick Howto

The rule is fairly simple - if you want to use Guice injection in your Seam component, annotate it with the @Guice annotation.

@Name("myGuicyComponent")
@Guice
public class MyGuicyComponent
{
  @Inject MyObject myObject
}

For all Seam components annotated with the @Guice annotation, Guice injection will be performed automatically.

Great, but wait… which Guice injector will be used? Well, the one you provide. Just edit components.xml:

<components
xmlns="http://jboss.com/products/seam/components"
xmlns:guice="http://jboss.org/jbosslabs/seam-guice">
  ...
  <guice:init injector="#{myGuiceInjector}/>
  ...
</components>

myGuiceInjector should be a Seam component that implements the Injector interface.

You may want to create it from a list of modules:

<guice:injector name="myGuiceInjector">
  <guice:modules>
    <value>com.example.guice.GuiceModule1</value>
    <value>com.example.guice.GuiceModule2</value>
  </guice:modules>
</guice:injector>

Of course you can also use an injector that is already used in other, possibly non-Seam, parts of you application. That was one of the reasons I implemented this integration - to tie other parts of an application that used Guice together with Seam.

To enable Seam and Guice integration, add seam-guice.jar library to your application. Do not forget to put guice-1.0.jar in as well

Give it a try!

I have included more information on the wiki page. You can download seam-guice library and browse the source code. It is implemented as a simple interceptor. Let me know if you find a bug or a place for improvement.

If you like this solution, you can vote to make it part of the Seam project. You may also want to have a look at Guice and plain JSF integration and the Guice extension to JBoss Microcontainer.

Many thanks to Tomek, who introduced Guice to me, Kamil, for feedback and Adam, for encouraging me to blog about it

-Paweł