Help

Controls

PermLinkWikiLink

Built with Seam

You can find the full source code for this website in the Seam package in the directory /examples/wiki. It is licensed under the LGPL.

Forum: Seam Users Forum ListTopic List
02. Feb 2008, 20:22 CET | Link

We deployed our web site at amazinggates using JBoss Seam. I would lie if I said it was it easy, but the reason I had some issues is that I didn't believe a lot of documentation.

  • I had refused to use Facelets, instead I used JSP. All I can say to newbies is don't do it. You owe to yourself to drop JSP like a bad habit.
  • I had refused to use Seam Managed Persistence and ended with LIES.
  • I had refused to use Seam-Gen, and used my own folder structure. I still use my folder structure, but only after I used Seam-Gen and learned what I had to do to make my integration tests work.
  • I had used 2.0 when it was still in CR and Beta releases. Although that is neither my fault or the Seam's fault, the greatest result was that I learned tremendously what Seam had to offer, and I was able to provide JBoss with some bugs, and help users in the forum.
  • It took 8 hours to learn that Seam's AJAX4JSF solution was the best solution on the planet.
  • I used faces-config for page navigation. Ok, and that was just stupid.
  • I didn't know what components.xml was for the longest time. I'm really going to take part of the blame on this one. I read the documentation and even after reading it I still had no idea what components.xml was for. I realized that if the documentation said that components.xml maps components to names the way it does in Spring XML configuration. I wouldn't have spent that much time.
  • I had refused to use Renderer.render for email, because I didn't believe that the view should be the place for the rendering. So I was going to use a StringTemplate solution. That was dumb, it took a while for me to realize that generating emails in the view was the BEST place to do so.
  • Integration testing was a bitch. That wasn't my fault, or Seam's fault. It really was the Microcontainer's fault, and I hope that that ends up better in the long run. I heard through the grapevine that really no one is working on the EJB Microcontainer and it is still stuck in Alpha. Redhat needs to invest some people into it. It really is THAT important.

So, all in all, I love the new website, and I love what JBoss Seam has to offer. I am excited with what it has to offer, and I will still continue to build my business around it. Good work to the team that made JBoss Seam possible.

Danno!

 
Dan Hinojosa Seam :: Groovy :: Swing Developer/Consultant/Instructor Albuquerque, NM
12 Replies:
13. Feb 2008, 08:03 CET | Link

Can we have this listed in wiki? I think it is very important for decision maker to know how many people have used seam in production.
13. Feb 2008, 11:15 CET | Link

If there is any interest in this.. we currently have 7 websites/applications using Seam in production.. any advances on that? ;-)

Mostly without issues (bar the one I posted on this forum today!! - Link here)

13. Feb 2008, 13:10 CET | Link
Phil Haigh wrote on Feb 13, 2008 11:15 AM:
If there is any interest in this.. we currently have 7 websites/applications using Seam in production.. any advances on that? ;-) Mostly without issues (bar the one I posted on this forum today!! - Link here)

Yes I think list of application created with Seam along with it's links would be useful for others that is thinking about using seam. Could you give me those links?
13. Feb 2008, 13:52 CET | Link

Sure: 

1.  http://www.ganeandmarshall.com
2.  http://www.charitychallenge.com
2a. http://www.communitychallenge.co.uk (actually part of the same application as #2 - just skinned the UI)
3.  http://www.wildfrontiers.co.uk
4.  http://www.canvinbrown.com
5.  http://www.raglanhall.com
6.  http://www.artofexposure.co.uk
7.  http://www.sundialworldwide.co.uk

We have another 3 shortly to launch.
13. Feb 2008, 15:48 CET | Link

This is a great post! Very helpful information and a very nice website. Thank you for providing this information.

-LeoD
14. Feb 2008, 03:39 CET | Link
I had refused to use Seam Managed Persistence and ended with LIES.

Can I ask for a bit of elaboration here?

What do you mean by this statement?

Are you saying Seam development without using Seam Managed Persistence doesn't work, or what?
14. Feb 2008, 03:57 CET | Link

I think he meant LazyInitializationExceptions.
14. Feb 2008, 06:16 CET | Link

OOOOoooohhhhh. I see.

Silly me.
14. Feb 2008, 15:36 CET | Link

It took me a while too. A little too cute, maybe. :P
14. Feb 2008, 16:53 CET | Link

Ooops. ;)

 
Dan Hinojosa Seam :: Groovy :: Swing Developer/Consultant/Instructor Albuquerque, NM
14. Feb 2008, 18:40 CET | Link

:) Once you get it, it's really quite clever, but just not as obvious. Is it LIES! like Kirk's KHAAAAAN! (I can't believe I just made a Star Trek reference :( hehe ) or is it an abbreviation? Maybe LIEs would have been more obvious. Either way, it was a great post. Informative and entertaining. Thanks. :)
20. Feb 2008, 18:42 CET | Link

Thanks Daniel, Very nice post. As far as JBoss Embedded is concerned. This is definitely in our radar. Pete worked a bit with the MC/Embedded team to fix some issues for Seam 2.0. The embedded ejb 3 container share most of it's code from the regular EJB 3 container. We still have some work to do on the EJB 3 container per se. Once done, JBoss Embedded will be the top priority.

You're bitching on it, but really you should see us bitching ;)

 

Check out my book: Hibernate Search in Action