You should probably give a little bit more information about what "the page
breaks" means, is the script not included? Does not run? The page does not
render?
The jsessionid is the servlet-containers session handling, it has nothing to
do with tapestry. Check the servlet specification for details but
essentially the servlet container tries to establish a session for the
browser. The servlet container does not know if the browser supports cookies
so for the first exchange it uses URL-rewriting to track the session.

On 4/17/07, Andrea Chiumenti <[EMAIL PROTECTED]> wrote:

This is exactly the problem I'm having (i.e. a session initialization
problem)

It's happening this: I'm accessing an External page an I have this method
fom IExternalPage:

public void activateExternalPage(Object[] parameters, IRequestCycle cycle)
{
        if ((parameters.length > 0) &&
(parameters[0].toString().equalsIgnoreCase("reset"))) {
            Wizard wizard = (Wizard) getComponent("wizard");
            wizard.reset();
            setPerson(new Person());
        }
        getPerson();
        getCities();
    }

where person and cities are injected ASO
<inject property="person" type="state" object="wizardPerson"/>
    <inject property="cities" type="state" object="cities"/>

all is in java 1.4

When I access the page for the first time I have the jsessionid problem.

How can I solve this issue ?

kiuma
On 4/17/07, Martino Piccinato < [EMAIL PROTECTED]> wrote:
>
> sorry just wanted to comment one thing more: if this session appending
is
> happening just the first time you hit the application (so you are
without
> a
> cookie) in this case I think the servlet container is doing the right
> thing
> (it does not know you support cookies on first hit). This might cause
> problems to some web server  (e.g. apache for mod_jk connector) to
resolve
> urls.
>
> I think this is all that comes to my mind given the informations you
gave
> :-)
>

Reply via email to