users
[Top] [All Lists]

WebApps: how not to deploy?

To: <users@xxxxxxxxxx>
Subject: WebApps: how not to deploy?
From: "Herbers, Joe" <herbers@xxxxxxx>
Date: Wed, 1 Sep 2004 15:47:32 -0400
Delivered-to: mailing list users@cinjug.org
Mailing-list: contact users-help@cinjug.org; run by ezmlm
Thread-index: AcSQXIWYqcH9k6QxTQCehLb9MpkzOQ==
Thread-topic: WebApps: how not to deploy?

Let’s say you have a web application that requires Java 1.4.  Is there a good way to prevent it from deploying on an appserver if the appserver is only running 1.3?

 

What I’ve noticed by default on at least one appserver is that you won’t see an issue till a client hits a JSP page that references a class file, at which point the client gets a message like “The major.minor version '48.0' is too recent for this tool to understand.”

 

This isn’t very clear!  Rather than this appearing to the first user who hits the server, we’re thinking perhaps it would be better to print an error message on startup.  However, since the output may be buried in a log file somewhere (for example on Oracle 9i’s AppServer) it seems like the only way to get attention is to prevent deployment of the war as well.  What do you think?

 

<Prev in Thread] Current Thread [Next in Thread>
  • WebApps: how not to deploy?, Herbers, Joe <=