This week's book giveaway is in the Kotlin forum.
We're giving away four copies of Kotlin in Action and have Dmitry Jemerov & Svetlana Isakova on-line!
See this thread for details.
Win a copy of Kotlin in Action this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Prototyping on J2EE 1.3  RSS feed

Michael Morett
Posts: 28
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Quick question...I just downloaded the SDK 1.3 and got a few of the example programs to work. I took a look at the new J2EE Tutorial and all of the examples seem to share a common theme: they are all already built, tested and debugged and waiting to be deployed.
For example, I'm just interested in playing around with JSPs for now, though this would apply to EJBs as well. In Tomcat, you place the JSPs in a specific directory and go about making modifications in an iterative manner until the JSP works the way you expect it to.
The J2EE Tutorial, however, begins the discussion on web components (page 211) with *packaging* web components. I took a look at all of the relevant documentation (Configuration Guide, Release Notes, etc.) as well as the directory structure of E:\j2sdkee1.3, and it is not stated, nor obvious where we should put our JSPs (or EJBs or servlets or HTML files, though there is a public_html--actually there are 2 public_html directories with no explanation for this).
I was going to just prototype in Tomcat 4.0, but that defeats the purpose and doesn't answer my question. According to Sun, they have a version of Tomcat 4.0 included in the SDK. Where is it? Where is the WEB-INF directory? Or the Webapps directory?

How does one go about prototyping and doing iterative development using the J2EE SDK 1.3? On page 66 of the Tutorial, it states...
"Since the J2EE SDK is intended for experimentation, it supports iterative development. Whenever you make a change to a J2EE application, you must redeploy the application."
Are they serious? Is this practical? This is not iterative as I would envision it. Everytime I compile in JBuilder, I need to switch over to the DeployTool window? Doesn't this break the role-based division of labor Sun mentions (Application Component Provider, Application Assembler, etc?)
Any thoughts on this are appreciated.

With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!