Giancarlo Pinerolo wrote:
> Hi all,
>
> I am pretty new to servlets, and to this list also. So excuse if some
> question may seem inappropriate or OT.
>
> I've tried to install Jrun and IBM WebSphere on NT, and gave a quick try
> at them.
> Lately I installed Jserv as an Apache DSO under Linux. Then I tried to
> move some of the servlets shipped with JRun into a Jserv zone, and found
> that most of them do work. Even the session management in one of JRun's
> demos, surprisingly, generates a session id under jserv. Is it because
> there an equally named 'Session' class in both of them?
>
> The Q is: what are the real tricks to succeed in 'using everywhere'?
> What the hard spots to look for?
> I can imagine that classes have to be present, zones configured etc...
> But, apart anything related to different configurations, is there any
> limit in using a servlet-engine (and it's protocol) instead of another,
> or is it completely transparent?
>
> Enlightments are welcome.
>
> gian
>
There's only one real "trick" to maintaining portability: stick to the
functionality that is mandated in the API specification, and stay away from
proprietary extensions. The reason that sessions worked is that this
behavior is mandated in the spec, and both JRun and Apache JServ implement
it. Internally they do things in different ways, but they provide a common
platform for servlet authors.
In the case of servlets, the documents you want to read are the servlet API
specs, available at the JavaSoft web site (http://ajva.sun.com) under the
"Products and APIs" section. Apache JServ implements the 2.0 version of
the specification. Another good place to learn is the Servlets trail in
the Java Language Tutorial, also available at JavaSoft's site.
Craig McClanahan
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
READ THE FAQ!!!! <http://java.apache.org/faq/>
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
