I have switched to Tomcat and the problem goes away. I don't think
jswdk-1.0.1 is supported anymore.
Although this problem has been resolved, I have run up against another
unusual problem. After receiving the login screen and entering in the
turbine username/password, I get a "document contains no data" from the
browser. The servlet actually hangs. I tracked the hanging location to
the following call in TurbineUser:
criteria.add( TurbineUserPeer.USERNAME, username );
If I try to print TurbineUserPeer.USERNAME, the servlet hangs. For some
reason, accessing the static member hangs the servlet. Has anybody seen
this behavior before? I suspect I have a bad JVM, but I am not quite
sure.
- MJW
John McNally wrote:
>
> This would appear to be a bug with jswdk-1.0.1. If it was written correctly
> to the spec, getServletPath() would return
>
> /examples/servlet/Turbine
>
> getRequestURI() may give you more info than you need. I think if you
> continue to run Turbine like this the screen/ScreenValue pair and any other
> pathInfo used to generate the current screen will be added to DynamicURI
> before the correct value given in the constructor. Your links will not
> work.
>
> John McNally
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
