<div>Thanks for your reply.</div>
<div> </div>
<div>But my project did can't work under websphere.</div>
<div>When i don't check on the url rewriting ,i can't login because of no session found and can't pass the filter.</div>
<div>When i check on the url rewriting, it can automatically create jsessionid, but still works wrong</div>
<div><span class="gmail_quote">Error 500: [ETDA0029]屡にリダイレクトされています。</span></div>
<div><span class="gmail_quote"></span> </div>
<div><span class="gmail_quote">Are you sure i don't need to do any special programming for this?</span></div>
<div><span class="gmail_quote"><font style="BACKGROUND-COLOR: #33ff33">Then how should i do the WAS session configuration?</font></span></div>
<div><span class="gmail_quote">It seems useless only check on the url rewriting and cookie.</span></div>
<div><span class="gmail_quote"></span> </div>
<div><span class="gmail_quote">Or these's something wrong within teeda-sp2 (the teeda version i'm using)that caused my problem.</span></div>
<div><span class="gmail_quote"></span> </div>
<div><span class="gmail_quote">2007/12/28, YASUO HIGA <<a href="mailto:higa@isid.co.jp">higa@isid.co.jp</a>>:</span></div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi guys,<br>><br>> Accroding to the ibm site , it is said that<br>> "<br>><br>> An application that uses URL rewriting to track sessions must adhere to
<br>> certain programming guidelines. The application developer needs to do the<br>> following:<br>><br>> - Program servlets to encode URLs<br>> - Supply a servlet or JavaServer Pages (JSP) file as an entry point to
<br>> the application<br>><br>><br>> Must i "adhere to certain programming guidelines"?<br>> When i use tomcat as my application server, it runs well. The url ended with<br>> jsessionid, and it is automatically added.
<br>> So i wander if the "seasar + teeda" has already done it for<br>> us?(automatically rewrite url)<br>><br>Teeda uses HttpServletResponse#encodeURL(), encodeRedirectURL().<br>So, if WebSphere implements Servlet API completely,
<br>your application will works well.<br>You don't need to use response.encodeRedirectURL(...).<br>_______________________________________________<br>Seasar-user mailing list<br><a href="mailto:Seasar-user@ml.seasar.org">
Seasar-user@ml.seasar.org</a><br><a href="https://ml.seasar.org/mailman/listinfo/seasar-user">https://ml.seasar.org/mailman/listinfo/seasar-user</a><br></blockquote><br>