aspose file tools*
The moose likes Developer Certification (SCJD/OCMJD) and the fly likes Deprecation question on generated rmi code Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Certification » Developer Certification (SCJD/OCMJD)
Bookmark "Deprecation question on generated rmi code" Watch "Deprecation question on generated rmi code" New topic
Author

Deprecation question on generated rmi code

Paul Smiley
Ranch Hand

Joined: Jun 02, 2000
Posts: 244
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

Joined: Jun 02, 2000
Posts: 244
Answered my own question. I used the command line option for rmic as "rmic -v1.2" which took care of the deprecated methods.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Deprecation question on generated rmi code
 
Similar Threads
compiles with warning?
System variables
Suppressing Deprecation Warnings
compile time Error in java file generated by WSDL2Java
Need to label a tick stop on snap to JSlider