Thanks for the reference, but maybe I'm do dull to understand. The following paragraph suggests that the conversationId is supplied in a request parameter by the client.

The context filter expects to find the conversation id of any conversation context in a request parameter named conversationId. You are responsible for ensuring that it gets sent in the request.

I don't have any control over the content of the request the client sends to the HttpServlet. Or did I miss-understand the last 2 paragraphs of the section you referenced.

That sentences only relates to the conversation context which of course is not available if you do not tell seam which conversation is active.

To access the application context you only need to make sure that Seam's context filter gets wrapped around you own servlet.

Stephen Thanks, I was clearly trying to make this too hard.

I write servlet. I need get access to seam context.

component.xml:

<web:context-filter url-pattern="/x/*" />

web.xml:

<servlet>
    <servlet-name>My Servlet</servlet-name>
    <servlet-class>com.x.MyServlet</servlet-class>
</servlet>

<servlet-mapping>
    <servlet-name>My Servlet</servlet-name>
    <url-pattern>/x/multipleUpload</url-pattern>
</servlet-mapping>

User.java:

@Entity
@Name("logginedUser")
@Scope(ScopeType.SESSION)
public class User implements Serializable { ... }

MyServlet.java:

public class MyServlet extends HttpServlet {
    protected void doPost(HttpServletRequest request, HttpServletResponse response)
            throws ServletException, IOException {
        User user = (User) Component.getInstance("logginedUser"); // null
        AnyAction action = (AnyAction) Component.getInstance("anyAction"); // ok
        ...
    }
}

LogginedUser exist in session context after login but is not available in my servlet. If seam component is not entity then i can get it successfully. Why? How can i get logginedUser from seam context?

It's work OK. I just didn't send JSESSIONID from my flash-application by request.