Thanks for the ideas. Still no joy.

The behavior is consistent between three different clients, all running
different versions of IE (6,7 and 8).
I was able to use the debugging feature built in to IE 8 to see that the
wicket ajax javascript was gettting called. At some point in that process it
lost the value of the field and it got set to an empty field.

I have the feeling that there is something different with the environment on
this particular server - but I have no idea what at this point.

On Fri, Jun 4, 2010 at 1:32 PM, gnul <> wrote:

> >
> > Essentially, part of the process generates dynamic web forms based on xml
> > configuration files. We noticed that on one of our servers when we
> deployed
> > the war file that the fields would not hold their values, and as soon as
> you
> > tabbed out, the entry would disappear. Taking the same war file and
> > deploying it to another server the form acts as expected.
> >
> If it works on one server, but not the other, and they are configured
> the same (meaning same appserver/tomcat version, same jvm, same
> user/group/perms, etc.), the first thing I do is "clean" the appserver
> and do a fresh deploy.
> For example, say you are deploying to /var/lib/tomcat/webapps/, I
> would shutdown both tomcats, remove the exploded directories (e.g.
> myapp.war => myapp/ ) and re-deploy the war files to each server.  I
> would also clean out tomcat's temp directory (e.g.
> /var/cache/tomcat5/temp), then restart them both.
>  -gnul
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Reply via email to