|
Quick Lists
|
|
Bug ID:
|
6655234
|
|
Votes
|
0
|
|
Synopsis
|
j.l.i.: setNativeMethodPrefix does not document that prefix string can be null
|
|
Category
|
java:serviceability
|
|
Reported Against
|
|
|
Release Fixed
|
7(b26)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
|
|
Submit Date
|
25-JAN-2008
|
|
Description
|
Filed By : JCK team
JDK : java full version "1.6.0-fcs"
switch/Mode : default
JCK test owner : http://javaweb.sfbay/jcce/tcks/jck/docs/others/owners.jto
Failed tests : None
Problem description
===================
The javadoc specification for the Instrumentation.setNativeMethodPrefix method at:
http://java.sun.com/javase/6/docs/api/java/lang/instrument/Instrumentation.html#setNativeMethodPrefix(java.lang.instrument.ClassFileTransformer
,%20java.lang.String)
states as follows:
---Excerpt-from-spec---
Parameters:
...
prefix - The prefix which has been applied to wrapped native methods.
---End-of-excerpt---
It would be fine to document that null value for prefix is acceptable but has no effect on the failure handling of native method resolution, i.e. equals to empty prefix.
Posted Date : 2008-01-25 13:11:15.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
The implementation tolerates passing either a NULL or an
empty string ("") as parameter prefix. I agree that the
spec is silent about the semantics of either of those
values.
Adapting the proposed rewrite from comment #1:
prefix - The prefix to apply to wrapped native methods when
retrying a failed native method resolution. If prefix
is either NULL or the empty string, then failed native
method resolutions are not retried for this transformer.
Posted Date : 2008-02-06 19:12:16.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
