Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript 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 ...
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Deprecation question on generated rmi code

Ranch Hand
Posts: 245
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
From the Application Submission html file: "In all packages, you should correct any use of deprecated methods" I am concerned about the "all" and "any" here.
While compiling a simple rmi example, I got a bunch of deprecation warnings on the generated stub and skeleton. Are we to concern ourselves with the generated code, or only the java files that we write/modify? For instance, one of the warnings from the generated skeleton says "Method releaseInputStream() in interface java.rmi.server.RemoteCall has been deprecated..."
This is using JDK 1.3 using the rmic compiler within JBuilder 3.5 environment. Thanks!
Paul Smiley
Ranch Hand
Posts: 245
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Answered my own question. I used the command line option for rmic as "rmic -v1.2" which took care of the deprecated methods.
Create symphonies in seed and soil. For this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic