As you’ve mentioned above, the event org.jboss.seam.conversationTimeout allows me to get the conversation being timed out. This means that the conversation scoped component is already destroyed…

No, not yet. Actually the event is fired just before the conversation context is destroyed which means if you can get a handle to the object, you can perform any necessary operations.

Just looking through the details of it, it’s not that easy to get a handle to the object in the conversation being timed out. You have the details you need to do it (the cid), but it’s not trivial to pull an object from another conversation. If you decide to go this route, take a look at how the Contexts.destroyConversationContext() method temporarily retrieves a conversation context. I haven’t tested this, but I believe this should work for your needs.

Another option may be to annotate a method on the component to perform this cleanup as @Destroy. Since you want the cleanup to only occur on timeout, you could set an EVENT scoped variable that indicates a conversation timeout occurred for a particular cid:


@Observer(Manager.EVENT_CONVERSATION_TIMEOUT)
public void markTimeoutEvent(String cid)
{
Contexts.getEventContext().set("conversationTimeout", cid);
}


The disadvantage to this approach is that the component would need to know the id of the conversation it was created within to determine whether or not to act on this.

Thanks for the answer.

However, this does not allow me to get the conversation scoped component
so that I do some clean up (to remove a remote SFSB).

As you’ve mentioned above, the event org.jboss.seam.conversationTimeout allows me to get the conversation being timed out. This means that the conversation scoped component is already destroyed…

Is it possible to intercept the removal of a conversation scoped component just before its destruction because of a timeout ?

Thanks in advance,

You can always observe the event:

org.jboss.seam.conversationTimeout

The ID of the conversation being timed out is also provided as an optional parameter.

I have a simple question about conversation timeout:

Given that I have a conversational POJO component,
Is it possible to intercept timeout event of the conversation
into which my component lives ?

I need this to call some cleanup on the component itself.

thanks in advance

I found this article of yours very helpful. However when I try to implement the same, I am getting “session expired” message when user tries to log in for the first time into the application. After logging in, once the session expires, I am getting the session expired message as desired. Is there anything I need to do to see “session expired” message not appear when user logs into application.

Thanks.

What will be the best practice with-in seam framework, will L2 cache, Named query help..

Scenario :
We are sending Ajax request (using suggestionBox) to fetch itemNames when user enters text.
We have list of approximately 5000 item names, corresponding entity is Item.

What will be the best practice option to get list of itemNames on the basis of text entered in suggestion box by user (we want to query result only for the text entered)

a) Define framework:entity-query in components.xml, call this to fetch itemNames when user enters text.

b) Use built-in ejbql in corresponding itemList.java (default generated by seam)
@Override
public String getEjbql() {
return “select item from Item item”;
}

c) Create separate query using enityManager in some bean class, add where clause passing the text entered by user.
public List getItemsList(String itemName) {
List itemLst = entityManager.createQuery(”select item from Item item…. where
item.itemName=”).getResultList();
return itemLst;
}

Can you extend your template above to show how to model the following:


class Custom {
String[] ids;
AnotherClass[] entries;
}


I’m reasonably schema savvy but complex content models combined with various model groups and all the possible variations in between really gets hairy for me.

Thanks,

Ron