Win a copy of TensorFlow 2.0 in Action this week in the Artificial Intelligence and Machine Learning forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Paul Clapham
  • Bear Bibeault
  • Jeanne Boyarsky
Sheriffs:
  • Ron McLeod
  • Tim Cooke
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Jj Roberts
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • salvin francis
  • Scott Selikoff
  • fred rosenberger

Deployment of classes on Websphere

 
tumbleweed
Posts: 5089
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If classes are develped with Visualage for Java 3.5 can one deploy them on the new Websphere 4 application servers without having to redisign and/or recompile them ?
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It depends on what you mean by "classes". Since VisualAge for Java can't generate WAR files, you will have to use the tooling that comes with WebSphere 4.0 (the AAT -- Application Assembly Tool) to generate WAR files for your servlets and JSP's -- you simply export the Java class files into a directory structure and then use AAT to build the WAR files from there.
If you mean classes that make up EJB's, then you can use the EJB 1.1 deployment tools built into VisualAge for Java 4.0 to generate EJB 1.1 compatible jar files directly.
You will also want to use the AAT to assemble your WAR and EJB JAR files into Enterprise ARchive (EAR) files.
This is all described in the "migration" section of WebSphere 4.0's InfoCenter and the migration documents that come with VisualAge for Java 4.0.

------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
 
Kyle Brown
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
One more thing -- the Servlet spec and JSP spec supported by WebSphere 4.0 is the same as that supported by VisualAge 4.0 -- none of those classes will have to change. Likewise, the EJB spec supported by WebSphere 4.0 (EJB 1.1) is mostly a superset of the EJB spec supported directly by VisualAge 4.0 (EJB 1.0). Your classes will have to be repackaged as described in the previous message, but not redesigned or rewritten.

------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
[This message has been edited by Kyle Brown (edited September 21, 2001).]
 
Greenhorn
Posts: 28
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What if we spin the situation around: using VisualAge for Java 4.0 to develop for WebSphere 3.5.3. Could there be headaches when deploying the servlets and JSP's because the VisualAge for Java 4.0 WTE (WebSphere Test Environment) is no longer an accurate representation of WebSphere 3.5.3?
 
Kyle Brown
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No, the VAJ 4.0 WTE IS the WebSphere 3.5.3 WebSphere environment. We did not update the WebSphere inside of VAJ 4.0 to WAS 4.0 because WAS 4.0 required Java 1.3... There should be no problems developing on VAJ 4.0 for deployment on WebSphere 3.5.3.
Kyle
------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
See my homepage at http://members.aol.com/kgb1001001 for other WebSphere information.
 
Ted J Schrader
Greenhorn
Posts: 28
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks again, Kyle.
reply
    Bookmark Topic Watch Topic
  • New Topic