We may change engine name from localhost to solve it. So you have to keep users session in client side cache and not with jsessionid ! You may inside app1 if app1 same as app2 you may after login by server side session automatically can login to app2 ?! In this approach also for same type apps user sessions has not good isolation ! The other way is put ROOT.xml file that has context tag with full path such : Īnd deploy war file as ROOT.war inside webappsfoldername I faced this problem for one month,Putting context tag inside server.xml is not safe it affect context elements deploying for all other host ,for big apps it take connection errors also not good isolation for example you may access other sites by folder name /domain1Folder !! also database session connections loaded twice ! ![]() Also it only needs uncompressed war folder which is a headache. The second option is (double) loading the wars from Webapps folder as well. func (s routeGuideServer) ListFeatures(rect pb. This is better way to handle ROOT ("/**") context path. ListFeatures is a server-side streaming RPC, so we need to send back multiple Feature s to our client. So now unmatched url requests from other wars(contextpaths) will land into this war.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |