XStream

JRockit JVM Vendor change

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.3.1
  • Fix Version/s: 1.4
  • Component/s: Core
  • Labels:
    None
  • JDK version and platform:
    Oracle JRockit build R28.0.0

Description

As from version 4.0.0, Oracle changed the Vendor name of it's JVM, Oracle JRockit. Until this point the Vendor name was "BEA" - this is for what the current 1.3.1 XStream implementation looks for while checking JVM vendors. Oracle changed this in this release to "Oracle" which now causes to fail the vendor check in XStream.

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. XSTR-651 XStream doesn't use Sun14ReflectionProvider for Oracle (Sun) JDK 7

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. XSTR-653 Xstream Is not running in Enhance Mode on Bea -JRockit -r28

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jörg Schaible added a comment -

Again, thanks for heads-up. For the time being you can initialize XStream with a Sun14ReflectionProvider to make full advantage of XStream's enhanced mode unless XStream itself detects JRockit again.

Show
Jörg Schaible added a comment - Again, thanks for heads-up. For the time being you can initialize XStream with a Sun14ReflectionProvider to make full advantage of XStream's enhanced mode unless XStream itself detects JRockit again.
Hide
Permalink
Sandor Nemeth added a comment -

Thank you for the information but I think XStream itself detects the JVM Vendor information and for this reason Hudson gives me an error message that it's not compatible with my JVM.

I think the fastest and most error-proof solution will be to revert back the Oracle JVM to 3.x where the Vendor information was set to "BEA".

Also I'll give feedback to the guys developing and supporting Hudson to be aware of this issue.

Best regards,
Sandor Nemeth

Show
Sandor Nemeth added a comment - Thank you for the information but I think XStream itself detects the JVM Vendor information and for this reason Hudson gives me an error message that it's not compatible with my JVM. I think the fastest and most error-proof solution will be to revert back the Oracle JVM to 3.x where the Vendor information was set to "BEA". Also I'll give feedback to the guys developing and supporting Hudson to be aware of this issue. Best regards, Sandor Nemeth
Hide
Permalink
Markus Helbig added a comment -

patch to also accept Oracle as former BEA

Show
Markus Helbig added a comment - patch to also accept Oracle as former BEA
Hide
Permalink
Jörg Schaible added a comment -

I guess any JVM with Oracle as vendor is now appropriate for Sun14ReflectionProvider

Show
Jörg Schaible added a comment - I guess any JVM with Oracle as vendor is now appropriate for Sun14ReflectionProvider

People

  • Assignee:
    Jörg Schaible
    Reporter:
    Sandor Nemeth
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: