Home » Language IDEs » ServerTools (WTP) » Questions about Server and Install Server Runtimes...
| Questions about Server and Install Server Runtimes... [message #67000] |
Fri, 21 January 2005 19:20  |
Eclipse User |
|
|
|
I just completed the WTP Tutorial - Building and Running Web. I post
some problems that I had with in bug report 83471. I wanted ask the
newsgroup why does the Server setup have to be so complex.
I've been using the Tomcat plugin for all my development, so I don't see
why this so much more complex to setup Tomcat in WTP than Tomcat plugin.
Here are the step as I see them for Tomcat.
1. Open the Preferences dialog.
2. Goto Server -> Install Runtimes
3. Click Add...
4. Open Apache and select the version Tomcat you are using. Click Next.
5. Click Browse... to locate the Tomcat installation. Change the JRE, if
you don't like the default selection.
6. Click Finish.
7. Click Ok to close the Preference dialog. We're done with it, but
we're far from done setting things up.
8. Open the Servers view. If it is not visible, go to Show Views. Then
under Server, select Servers. Click Ok.
9. You will not see a server in the Server view. Don't panic this is the
plan. Confused. You're not alone. In the Servers context menu, select New...
10. Ok. You now must select Server that you setup in step 4. If you
select any other version, you'll have to setup the runtime for it. Click
next. If I can set the runtime information here, why do I need the
runtime information in the Preferences dialog.
11. Select your project from Available projects. Click Add >
12. Click Finish.
13. Right mouse click on project in the Project Explorer. Select Server
to make sure that Tomcat is select as default and not <None> Click ok.
Ok here are the steps for Tomcat plugin
1. Open the Preferences dialog.
2. Goto Tomcat
3. Select the version
4. Browser to the Tomcat Home using the Browser... button.
5. Click Browse... to locate the Tomcat installation. Change the JRE, if
you don't like the default selection.
6. Select Tomcat Manager App. Enter the Manager App setting into the
dialog.
7. Click Ok.
8. Right click on Project in the Package Explorer
9. Under Tomcat, Check the Is a Tomcat Project. Enter you Context Name.
Click Ok.
10. If you don't have the Tomcat libraries, Right Click on the Project
in the Package Explorer. Select Add Tomcat Libraries.
11. Add the Tomcat project to the Context.
While the number of step seem close, the complexity isn't. There is only
one place for Tomcat Server settings compared the two.
I'm sure there is some reason why I would use a different run with a
server, but I don't see it as the norm. I would think that when you pick
a server, that is the runtime library you wish to use. I see only two
exceptions, if you have no server on your workstation. And if you wish
to stick to the J2EE standard. In both cases, you would pick J2EE Runtime.
To me what this means is that Install Server Runtime Environments is
more complexity than you need. This should be merged with the Server
view. This can stay as a view or move to the Preferences. I favor moving
it all to the Server view and rename the Server to Application Server View.
Or am I missing some huge value of this complexity that everyone will need.
I looked at IntelliJ and they are closer to the design that I'm suggesting.
Regards,
Jeff Duska
|
|
|
| Re: Questions about Server and Install Server Runtimes... [message #67485 is a reply to message #67000] |
Tue, 25 January 2005 08:43  |
| Eclipse User |
|
|
|
Hi Jeff,
The complexity difference is that we support targeting projects to compile
against the server (that's what the installed server runtimes are) as a
separate concept from running a server (where you may have multiple servers
running off of the same runtime on disk). With Tomcat you have the option of
modifying your Tomcat installation, or using a "test environment" where you
can run everything without touching the installation. There's also a lot of
other features like targetting projects to a particular runtime, and Run on
Server support. I agree that we've got work to do to simplify this for the
user, and to do things like automatically creating a corresponding server
when you define the runtime. We've also had lots of cases (e.g. step 13)
where different sets of users expect different default settings/actions. If
you are interested in being involved, please continue to provide feedback,
suggestions, bug reports, or code.
In our defense, you took the worst possible path to setup the runtime and
server. The Servers view is already available in all of the J2EE
perspectives, and defining a server will prompt you for the Tomcat
installation path and automatically create a runtime. That alone will give
you less steps than the Tomcat plugin, but there is a simpler path that
takes even less steps:
1. Right click on Web project or JSP file or Servlet, etc.
2. Select Run > Run on Server.
3. Select the Tomcat version you are using.
4. Click Next.
5. Browse to the Tomcat installation directory.
6. Click Finish.
The Web app is deployed to Tomcat, Tomcat is started, and a browser is
opened with the file that you selected.
|
|
|
| Re: Questions about Server and Install Server Runtimes... [message #67585 is a reply to message #67485] |
Tue, 25 January 2005 11:50 |
| Eclipse User |
|
|
|
Tim deBoer wrote:
> Hi Jeff,
>
> The complexity difference is that we support targeting projects to compile
> against the server (that's what the installed server runtimes are) as a
> separate concept from running a server (where you may have multiple servers
> running off of the same runtime on disk).
I guess I don't understand this, but then I only with with Tomcat and
Jetty. The problem I see is that this make this very complex. If I have
to take a moment to think about this, I would expect more junior
programmers to be confused and lost.
With Tomcat you have the option of
> modifying your Tomcat installation, or using a "test environment" where you
> can run everything without touching the installation. There's also a lot of
> other features like targetting projects to a particular runtime, and Run on
> Server support. I agree that we've got work to do to simplify this for the
> user, and to do things like automatically creating a corresponding server
> when you define the runtime. We've also had lots of cases (e.g. step 13)
> where different sets of users expect different default settings/actions. If
> you are interested in being involved, please continue to provide feedback,
> suggestions, bug reports, or code.
>
The set as default does appear to work, so I created bug 83627 for it,
see https://bugs.eclipse.org/bugs/show_bug.cgi?id=83627. Don't worry,
you'll keep hearing from me.
> In our defense, you took the worst possible path to setup the runtime and
> server.
I'm pretty lazy, so if there is a simpler way I typically use it. Thus
this simpler solution was either not shown in the tutorial or not very
clear in the tutorial. I'll look at it again when I try this on my
PowerBook.
The Servers view is already available in all of the J2EE
> perspectives, and defining a server will prompt you for the Tomcat
> installation path and automatically create a runtime. That alone will give
> you less steps than the Tomcat plugin, but there is a simpler path that
> takes even less steps:
>
> 1. Right click on Web project or JSP file or Servlet, etc.
> 2. Select Run > Run on Server.
> 3. Select the Tomcat version you are using.
> 4. Click Next.
> 5. Browse to the Tomcat installation directory.
> 6. Click Finish.
>
> The Web app is deployed to Tomcat, Tomcat is started, and a browser is
> opened with the file that you selected.
>
>
Regards,
Jeff Duska
|
|
|
Goto Forum:
Current Time: Thu Jun 05 18:41:55 EDT 2025
Powered by FUDForum. Page generated in 0.03749 seconds |
Home