Re: Support and development of versions

2008-02-28 Thread David kerber

Stephen Nelson-Smith wrote:

Hi,

So, I'm running an app which the development house say *has* to run on
4.1.31.  I'm not especially happy about this, and will try running it
under 4.1.37, but the developers say they *might* be able to get it to
run under 5.5.  I seem to recall a conversation in which I was told
that 5.5 isn't really actively supported or developed any more either.
 Is this the case?

Am I best to try to pressure the  developers to get the system to run
on 6?  Or will 4.1 be sound for a while yet, as long as I can keep on
top of bug/security fixes?
  
4.1.37 is probably your best short-term solution, and work toward 6.x in 
the mid-to-long term.




Thanks,

S.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



  




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Support and development of versions

2008-02-28 Thread Stephen Nelson-Smith
On Thu, Feb 28, 2008 at 2:37 PM, David kerber [EMAIL PROTECTED] wrote:
  4.1.37 is probably your best short-term solution, and work toward 6.x in
  the mid-to-long term.

That was my gut feeling.  Could you explain why that is?  Is 5.5 a
wasteland?  I'll need to understand the rationale behind the
recommendation to make it stick with the development team.

S.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Support and development of versions

2008-02-28 Thread Caldarale, Charles R
 From: Stephen Nelson-Smith [mailto:[EMAIL PROTECTED] 
 Subject: Re: Support and development of versions
 
 Is 5.5 a wasteland?

It's not a wasteland, whereas 5.0 is.  However, the most attention goes
to the current level, while 4.1 and 5.5 activity is pretty much limited
to only serious bug fixes.  You definitely don't want to target for a
level that's already outdated.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Support and development of versions

2008-02-28 Thread David kerber

Stephen Nelson-Smith wrote:

On Thu, Feb 28, 2008 at 2:37 PM, David kerber [EMAIL PROTECTED] wrote:
  

 4.1.37 is probably your best short-term solution, and work toward 6.x in
 the mid-to-long term.



That was my gut feeling.  Could you explain why that is?  Is 5.5 a
wasteland?  I'll need to understand the rationale behind the
recommendation to make it stick with the development team.
  
Actually, 5.5.x is quite good and I use it in production, but it's in 
kind of a no-man's land development-wise.  Since 6.x has been around for 
a year or so, it's stable, and it's most likely getting the bulk of the 
development effort, and you know that 5.5.x development is going to be 
stopped before 6.x is, at some point in the future.  If you're porting 
an app from 4.x to something newer anyway, you might as well port to the 
one you know is going to have the longest lifetime, instead of using a 
mid-term version. 

If your app was already written for 5, I'd say stick with that line, but 
I wouldn't do new development or older-version porting to it.


D



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Support and development of versions

2008-02-28 Thread Mark Thomas

Stephen Nelson-Smith wrote:

On Thu, Feb 28, 2008 at 2:37 PM, David kerber [EMAIL PROTECTED] wrote:

 4.1.37 is probably your best short-term solution, and work toward 6.x in
 the mid-to-long term.


That was my gut feeling.  Could you explain why that is?  Is 5.5 a
wasteland?  I'll need to understand the rationale behind the
recommendation to make it stick with the development team.


Current status is available from:

http://wiki.apache.org/tomcat/TomcatVersions

Mark


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Support and development of versions

2008-02-28 Thread Stephen Nelson-Smith
On Thu, Feb 28, 2008 at 6:15 PM, Mark Thomas [EMAIL PROTECTED] wrote:

 Stephen Nelson-Smith wrote:
   On Thu, Feb 28, 2008 at 2:37 PM, David kerber [EMAIL PROTECTED] wrote:
4.1.37 is probably your best short-term solution, and work toward 6.x in
the mid-to-long term.
  
   That was my gut feeling.  Could you explain why that is?  Is 5.5 a
   wasteland?  I'll need to understand the rationale behind the
   recommendation to make it stick with the development team.

  Current status is available from:

  http://wiki.apache.org/tomcat/TomcatVersions

Thanks - that's a very handy summary.

Could someone help me  understand the differences between the servlet
and JSP versions?  Do the numbers imply no backward and/or forward
compatibility?  Given that the app I am administering was written some
years ago for 4.1, and I've been told it needs a specific Java version
(1.4.2_11) does this increase the likelihood of substantial rewrites
being needed to run on newer versions of Tomcat?

I'm puzzled - I don't know much about Java - how much changes?  And
why so quickly!?

S.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Support and development of versions

2008-02-28 Thread Jason Pyeron

 

 -Original Message-
 From: Mark Thomas [mailto:[EMAIL PROTECTED] 
 
 Current status is available from:
 
 http://wiki.apache.org/tomcat/TomcatVersions
 


What does RTC, for the process field stand for?


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-   -
- Jason Pyeron  PD Inc. http://www.pdinc.us -
- Principal Consultant  10 West 24th Street #100-
- +1 (443) 269-1555 x333Baltimore, Maryland 21218   -
-   -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you
have received it in error, purge the message from your system and
notify the sender immediately.  Any other use of the email by you
is prohibited. 


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Support and development of versions

2008-02-28 Thread Caldarale, Charles R
 From: Stephen Nelson-Smith [mailto:[EMAIL PROTECTED] 
 Subject: Re: Support and development of versions
 
 Could someone help me  understand the differences between the servlet
 and JSP versions?

The servlet and JSP specs are the place to look.  Each document includes
a section on what's changed from earlier versions.
http://jcp.org/aboutJava/communityprocess/mrel/jsr154/index2.html
http://jcp.org/aboutJava/communityprocess/final/jsr245/index.html

 Do the numbers imply no backward and/or forward
 compatibility?

Newer versions of Tomcat should run webapps based on older
specifications without any real difficulty.  Problems arise when webapps
do something container specific, such as depend on bugs fixed in later
versions.  Tomcat configuration has changed significantly, as might be
expected, so don't just blindly copy over your old server.xml and
Context elements when moving up.  Read the Tomcat docs, and modify the
various .xml files that come with the version of Tomcat you're moving
to.

 I've been told it needs a specific Java version (1.4.2_11)

The above is highly likely to be pure BS.  Again, other than webapps
absuing the system by being dependent on bugs or security holes fixed in
later levels, older programs run happily on the latest JVMs (which also
tend to be significantly faster than older ones).

The one significant incompatibility I remember is that classes being
imported must be part of a package.  It was never good practice to use
packageless classes, and at some point in the last few years it became
illegal.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Support and development of versions

2008-02-28 Thread Jason Pyeron

 

 -Original Message-
 From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, February 28, 2008 16:12
 To: Tomcat Users List
 Subject: RE: Support and development of versions
 
  From: Stephen Nelson-Smith [mailto:[EMAIL PROTECTED] 
  Subject: Re: Support and development of versions
  
  Could someone help me  understand the differences between 
 the servlet
  and JSP versions?
 
 The servlet and JSP specs are the place to look.  Each 
 document includes
 a section on what's changed from earlier versions.
 http://jcp.org/aboutJava/communityprocess/mrel/jsr154/index2.html
 http://jcp.org/aboutJava/communityprocess/final/jsr245/index.html
 
  Do the numbers imply no backward and/or forward
  compatibility?
 
 Newer versions of Tomcat should run webapps based on older
 specifications without any real difficulty.  Problems arise 
 when webapps
 do something container specific, such as depend on bugs fixed in later
 versions.  Tomcat configuration has changed significantly, as might be
 expected, so don't just blindly copy over your old server.xml and
 Context elements when moving up.  Read the Tomcat docs, and 
 modify the
 various .xml files that come with the version of Tomcat you're moving
 to.
 
  I've been told it needs a specific Java version (1.4.2_11)
 
 The above is highly likely to be pure BS.  

It might not be, but it should not be.

http://java.sun.com/j2se/1.5.0/compatibility.html
and
http://java.sun.com/javase/6/webnotes/compatibility.html




-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-   -
- Jason Pyeron  PD Inc. http://www.pdinc.us -
- Principal Consultant  10 West 24th Street #100-
- +1 (443) 269-1555 x333Baltimore, Maryland 21218   -
-   -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you
have received it in error, purge the message from your system and
notify the sender immediately.  Any other use of the email by you
is prohibited. 


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Support and development of versions

2008-02-28 Thread Mark Thomas

Jason Pyeron wrote:
 


-Original Message-
From: Mark Thomas [mailto:[EMAIL PROTECTED] 


Current status is available from:

http://wiki.apache.org/tomcat/TomcatVersions




What does RTC, for the process field stand for?


Review Then Commit. It means every patch must get at least 3 more +1 votes 
than -1 votes (from the committers) before it can be applied to that branch.


Mark


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




RE: Support and development of versions

2008-02-28 Thread Caldarale, Charles R
 From: Jason Pyeron [mailto:[EMAIL PROTECTED] 
 Subject: RE: Support and development of versions
 
 It might not be, but it should not be.
 http://java.sun.com/j2se/1.5.0/compatibility.html
 and
 http://java.sun.com/javase/6/webnotes/compatibility.html

Other than enum becoming a reserved word, did you see anything in there
that was significant?

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]