Seam and Web Beans: Not just evolutionary, revolutionary

Date September 29, 2008

Just a quick note to let you know that I will be speaking next week on October 8 at the Java MUG in Dallas. I will be talking about how Seam has simplified JEE web development and influenced the revolutionary Web Beans specification (JSR-299). Hope to see you there!

[Presentation Slides]

Enjoyed this post? Share it!

  • DZone
  • del.icio.us
  • Digg
  • Google Bookmarks
  • Technorati
  • StumbleUpon
  • Furl
  • Reddit

6 Responses to “Seam and Web Beans: Not just evolutionary, revolutionary”

  1. Ajay Gupta said:

    Mr. Orshalick,

    Good luck on the presentation..see you there on the 8th.

  2. David Dietz said:

    I heard the talk at JavaMug and I am very interested in it. I would like to show it to some peers. Can you please send me the PDF and/or have it placed on the JavaMug site. We have an immediate use case for SEAM with Spring and you PDF might help me encourage the development group to look into it.

    Thanks and thanks for the great talk.
    ddietz

  3. jacob.orshalick said:

    I’m glad you enjoyed the talk. I have posted the PDF to the following link:

    http://solutionsfit.com/blog/wp-content/uploads/2008/10/seam-and-web-beans.pdf

  4. Radu Popa said:

    Just wanted to say thanks for the presentation. It was great and I have enjoyed it quite a lot.
    Small question: the business process context is supported just for jBoss jBPM or other BPM can be used as well?
    Also, contexts are replicated across a distributed environment? Meaning a conversation started on a server in a cluster will be having the same context if a next request goes to a different server?

    10x,
    Radu

  5. jacob.orshalick said:

    the business process context is supported just for jBoss jBPM or other BPM can be used as well?

    At the moment only jBPM is supported, but if you have a specific BPM you would like supported, feel free to request it in JIRA! We’re always looking to add support for new integration points.

    contexts are replicated across a distributed environment? Meaning a conversation started on a server in a cluster will be having the same context if a next request goes to a different server?

    Yes, Seam was developed from the ground up to support clustering. Conversation state is maintained in the HTTPSession so data replication will need to be enabled. If you are using EJBs, stateful session bean replication may also need to be enabled. Simply refer to the documentation of your AS to find out the details.

  6. Chris said:

    You did a good job! Too bad Seam isn’t as good as a rules engine….

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>