we have recently migrated from VisualAge 3.5 to WSAD4.0. In our application previously when we make a call to a servlet from a JSP we include it as "/com.app.loginServlet" . Now when i export this application ito wsad and run the application in WSAD websphere test environment the Servlet cannot be located unless i give the path as "Servlet_proj/com.app.loginServlet" where Servlet_proj is the WebProject which contains the Servlet. In VAJ test environment if i had to invoke a JSP i used to give it as "http://localhost:8080/login.jsp" but now in WSAD i had to mention the name of the project folder also explicitly as "http://localhost:8080/JSPs/login.jsp" I want to invoke my JSPs without including the Project name in the path. Can i do that??? Is there any way to invoke my servlets and JSPs in the same way as it was before without changing the paths ?? Please help me out of this.............. Thanks in Advance
This really sounds like an IDE configuration question. I'll move it to the WAD forum for you.
Scott Duncan
Ranch Hand
Joined: Nov 01, 2002
Posts: 363
posted
0
but now in WSAD i had to mention the name of the project folder also explicitly as
You are not specifying the name of the project folder. What you are really specifying is the context root of the application. To change a context root, right click the project and go to properties or in your .ear file project change it in the application.xml file and in the .war file project change it in the .websettings file. This is how it works in 5.0. I have not used 4.0 in a while. As far as calling your servlet, don't you think it would be much better to map it in your deployment descriptor instead of using the fully qualified class name?
No more rhymes! I mean it!<br /> <br />Does anybody want a peanut?
Joe Pluta
Ranch Hand
Joined: Jun 23, 2003
Posts: 1376
posted
0
I'd like to highly recommend that you upgrade to WSAD5, which is based on Eclipse 2. I upgraded as soon as I could, and the difference is enormous. So much so that it's almost impossible for me to be of much help with previous versions.
Joe
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to
run our stuff on 16 servers instead of 3.