Article on Ajax and JSF

Hi!

When I use Ajax for JSF, I can use EventQueue to make sure I never get a concurrent call to a conversation, so the concurrent call to conversation exception does not happen if I use A4J for everything. However I now need to use SEAM remoting for certain things that make the site much quicker than using A4J, but it does not have support for event queue so it can clash with an a4j request or another remoting request. Would you have any ideas that I'm completely ignorant of?

Thanks!

Long and painful hours can be applied to many jobs, not necessarily software related. And same about the voice of experience. The rest is probably a myth, I agree. But another thing about youngsters is that they are less likely to keep a job for a long time, that's another disadvantage for the employer.

I have been tasked with putting together a new web application stack for future projects. So far I have decided on going with the fundamentals of the JEE 6 stack, except for one major piece: the web framework. The problem is that we currently use Wicket, so going to JSF would mean abandoning our expertise with Wicket. If we were using a action based framework, JSF would be a no brainer due to the ease of integration with the rest of the stack, the widely available component libraries, the tooling, etc, etc.

But... we already use a beautiful component framework. And we make HEAVY use of custom components (well, in Wicket that's just how you do things), and get a pretty good amount of reuse. I don't even think about pages anymore (or navigation, thank god). Everything is a component, most of the time with components nested underneath.

When I read articles like the series listed above, it seems like using JSF a battle... one is constantly fighting against the design of the framework in order to accomplish things. Certainly everyone agrees that JSF 1 was, well, bad. I was really hoping JSF 2 would be awesome, but when I read articles like the linked series, what I feel is that even the people close to JSF 2 are only saying Hey! JSF 2 is a great release because X, Y, Z don't totally suck anymore! And in the next release it might be possible for A, B, and C to suck less too!

Now, there are certainly pain points with Wicket. And I would love to have the beautiful, functional component libraries available for JSF to pick and choose from, as well as built in integration with the rest of the stack...

...But the question is, how much do you give up to get that?