- This topic has 3 replies, 2 voices, and was last updated 21 years ago by
.
-
Posts
-
Hi there,
I am pretty new to both, MyEclipse and Eclipse and wonder whether you can possibly help:
I create a very simple web module project. I create a Java class with a simple method returning a string.
I create a JSP page / file. The question is: Obviously once I want to deploy to Tomcat 4.x the .jsp file location either
1. needs to be mapped via one of the .xml config files of tomcat
2. needs to be placed into the appropriate webapps directory within the Tomcat directory structureI noticed that the default file location suggested by MyEclipse seems to depend on which item is highlighted in the Package Explorer once you select the NEW – JSP.
Once the project root element is highlighted, Eclipse suggest (e.g.):
/HelloWorld/Web Root
(which is correct).As far as I have understood webapps and Tomcat’s way of dealing with them, this is only method 1 of deployment. Assume I want to put my .jsp files anywhere else, maybe outside the Tomcat directory structure and want to map to the via the .xml config-files. Is there any chance of having MyEclipse doing it for me? Or is the only way to do it manually. If the latter is true: How do I remap within Tomcat 4.1?
Regards
RalfI noticed that the default file location suggested by MyEclipse seems to depend on which item is highlighted in the Package Explorer once you select the NEW – JSP.
Once the project root element is highlighted, Eclipse suggest (e.g.):
/HelloWorld/Web Root
(which is correct).This is correct. The default JSP creation location when the project node is selected is the project’s <web-root> folder. Otherwise the current folder is the target location. Did you expect it to work in some other manner (explain)?
As far as I have understood webapps and Tomcat’s way of dealing with them, this is only method 1 of deployment. Assume I want to put my .jsp files anywhere else, maybe outside the Tomcat directory structure and want to map to the via the .xml config-files. Is there any chance of having MyEclipse doing it for me? Or is the only way to do it manually.
Presently, MyEclipse deployment does not support arbitrary locations. We have a scheduled enhancement request for development late this month that will enable specification of any location to support the very use-case you identify. In fact the codebase already supports this capability but we were not sure if it would be confusing for many users that also expect MyEclipse to automatically revise their server’s configuration files (too risky). Expect to see this as an advanced deployment feature in very soon.
Regards,
Michael
MyEclipse Support@support wrote:
I noticed that the default file location suggested by MyEclipse seems to depend on which item is highlighted in the Package Explorer once you select the NEW – JSP.
Once the project root element is highlighted, Eclipse suggest (e.g.):
/HelloWorld/Web Root
(which is correct).This is correct. The default JSP creation location when the project node is selected is the project’s <web-root> folder. Otherwise the current folder is the target location. Did you expect it to work in some other manner (explain)?
As far as I have understood webapps and Tomcat’s way of dealing with them, this is only method 1 of deployment. Assume I want to put my .jsp files anywhere else, maybe outside the Tomcat directory structure and want to map to the via the .xml config-files. Is there any chance of having MyEclipse doing it for me? Or is the only way to do it manually.
Presently, MyEclipse deployment does not support arbitrary locations. We have a scheduled enhancement request for development late this month that will enable specification of any location to support the very use-case you identify. In fact the codebase already supports this capability but we were not sure if it would be confusing for many users that also expect MyEclipse to automatically revise their server’s configuration files (too risky). Expect to see this as an advanced deployment feature in very soon.
Regards,
Michael
MyEclipse SupportFirst of all: thanks for the fast answer!
This is correct. The default JSP creation location when the project node is selected is the project’s <web-root> folder. Otherwise the current folder is the target location. Did you expect it to work in some other manner (explain)?
No. I just wanted to make sure that this is the intended behavior.
[…] but we were not sure if it would be confusing for many users that also expect MyEclipse to automatically revise their server’s configuration files (too risky). Expect to see this as an advanced deployment feature in very soon.
I believe it would be a major enhancement if MyEclipse would *offer* to modify the .xml configuration files once a location other than the server specific .jsp deployment path is chosen as a save path for any .jsp file. The best way to do it would possibly be to open the .xml file(s), do the changes and let the user confirm prior to saving back.
This way for the once who want MyEclipse to do the changes, it is a simple two-click process and all the others can simply abort MyEclipse from changing server config files. It could also be added to the preferences in order to define a default behavior.
