Could not transform class

Status: Beta

Brought to you by: asrgomes

#12 Could not transform class

Status: open

Owner: nobody

Labels: None

Priority: 5

Updated: 2008-09-01

Created: 2008-09-01

Creator: gvasquez

Private: No

One of my classes doesn't seem to like being instrumented.

It seems that the profiler is interpreting a ResourceBundle (a properties file) as an instrumentable Class (I'm just guessing as the error points out a "messages" class name, with a lowercase initial m, which is actually the messages.properties filename I'm using).

Please see atached console output and the problematic class.

NOTE: Some environment as the last bug I posted.

Discussion

gvasquez - 2008-09-01

Console Output

console-output.txt

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

gvasquez - 2008-09-01

Logged In: YES
user_id=1897973
Originator: YES

File Added: Messages.java

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

gvasquez - 2008-09-01

Non-instrumentable Class

Messages.java

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Could not transform class

Group

Searches

Help

#12 Could not transform class

Discussion