JBossDeveloper

Btw lcotzee. You do not need this dummy call to your templates. That is a question of logic.
Because you do not need user entity bean before you really use it, you needn`t put it into session scope...
Anyway got it working quite good.

Btw I use Stateless FactoryBean because the thing happens only once.(pulling entity bean)

Excellent. Glad that it works.

Louis

Hi Louis,

Great to hear it's going well for you, especially considering the scale/nature of your project. I've spent a couple of weeks delving into various aspects of Seam, and am planning to move forward with pretty much the same stack you're using. I've 100,000 users to support initially, but this is set to grow quickly.

I've a couple of questions for you, if you can help. Is the content management subsystem part of what you've developed in-house, or something external? I've got to tackle it at some stage & am casting my eye around. Also, did you find many corner cases needing manual API usage for Seam?

I'm also watching the JIRA bug you mentioned. I can foresee many stale conversations building up over time for my project - and attempts to re-enter conversations too.

Anyway, good to hear about your project. Best of luck with it

Simon

Hi,

I've 100,000 users to support initially

Is the content management subsystem part of what you've developed in-house, or something external?

Also, did you find many corner cases needing manual API usage for Seam?

I'm also watching the JIRA bug you mentioned. I can foresee many stale conversations building up over time for my project - and attempts to re-enter conversations too.

<pages>
 <page view-id="/secure/structure/management/service/services.xhtml" action="#{conversation.end}"/>
 <page view-id="/secure/structure/management/topic/servicesTopicManagement.xhtml" action="#{conversation.end}"/>
 <page view-id="/secure/structure/management/grouping/servicesGroupingManagement.xhtml" action="#{conversation.end}"/>
 <page view-id="/secure/content/approval/servicesList.xhtml" action="#{conversation.end}"/>
 <page view-id="/secure/discussion/management/forum/forums.xhtml" action="#{conversation.end}"/>
 <page view-id="/secure/structure/management/adminHome.xhtml" action="#{conversation.end}"/>

</pages>

With regards to API use, I meant manual Seam context & component management.
I'm using it in a few places where I'm trying out finer control over the components created & their outjection
(usually from upstream actions)

Your pages.xml use does look interesting, & that's a good tip.
I'm guessing that actions on pages.xml came in for the RESTful blog example (a great example addition I think).
Thanks for the info!

I meant manual Seam context & component management

Just an update on the usage of pages.xml and conversation.end .... I have removed it again, seems that it did not do as I wished it would.

Regards

L

"lcoetzee" wrote:
Just an update on the usage of pages.xml and conversation.end .... I have removed it again, seems that it did not do as I wished it would.

When the conversations was just joined things worked. However, with the pages.xml conversation.end things got a bit confusing. Using a @Factory with an @Begin to start the new conversation, later on (a few methods calls down in the same conversation and same stateful bean) I get this:

org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: csir.structure.par.CMSTopic.groupings, no session or session was closed

I also doubt if the conversation has really ended. If I click a link specified in my pages.xml (with the conversation.end) (with a running conversation), (and if the action I am going to is annotated only with an @Begin and the @Factory) I get the following exception:

Caused by: javax.faces.el.EvaluationException: /WEB-INF/tags/adminLeftNavigation.xhtml @34,28 action="#{groupingManagementBean.loadAllServices}": javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: begin method invoked from a long running conversation, try using @Begin(join=true)
 at com.sun.facelets.el.LegacyMethodBinding.invoke(LegacyMethodBinding.java:73)
 at org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:63)
 ... 35 more

Dear Louis,

if this exception is the only problem then please turn your code back. This exception is caused by a very common shortcome of hibernate. Portaluser roles does not get initialized when portaluser is initiliazed. You should do smth. like creating portaluser and after that calling user.roles.size(); or smth, which initializes the list.
I still think that Seam`s documentation is very poor. Are there any improvements going on?
And does community need more tutorial type of things? I`m creating a Hardware-shop management/front-end with seam+facelets+jaas and day-by-day it seems to get more working:P
So if you need help with documentation, please do not hestitate to contant me.

Of course, we can use the the help we can get.

Example application are *always* useful, especially if they come with a tutorial explaining how they work and what they do.

Note that I spent all week updating the booking example.

gavin, is there any way to talk with you more real-time? I would start with tutorial then, but I have few questions.

"lcoetzee" wrote:
I also doubt if the conversation has really ended.