[jira] [Commented] (PIVOT-996) Unable to run with SAP JVM

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] [Commented] (PIVOT-996) Unable to run with SAP JVM

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/PIVOT-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984983#comment-15984983 ]

Roger Whitcomb commented on PIVOT-996:
--------------------------------------

Looking at the code, there are two possible ways to fix this that I see:
1. Just use "java.version" instead of "java.vm.version" in the ApplicationContext static initialization.  This is problematic since there is a public API that returns this value -- could break customer code.  But, I'm wondering if "java.version" isn't more helpful anyway, than the JVM version (or maybe this is what was intended all along, and it is essentially a typo?).
2. Figure out a bullet-proof way to parse weird version strings.  Also problematic, since we don't know what new schemes could come about in the future that might break the parsing.

My inclination is to try to figure out 2), but put it out for comment about 1).  Thoughts?


> Unable to run with SAP JVM
> --------------------------
>
>                 Key: PIVOT-996
>                 URL: https://issues.apache.org/jira/browse/PIVOT-996
>             Project: Pivot
>          Issue Type: Bug
>    Affects Versions: 2.0.4
>            Reporter: Sandro Martini
>            Assignee: Sandro Martini
>             Fix For: 2.0.5, 2.1.0
>
>
> As reported in our Dev mailing list, the check on JVM version that we do doesn't work with JVM different than Oracle Java.
> For example the SAP JVM with version "8.1.028 25.51-b14" generates the problem, which is blocking.
> The discussion thread is visible for example [here](http://apache-pivot-developers.417237.n3.nabble.com/Issue-in-Version-decode-with-SAPJVM-td4027425.html).
> We should check if log a warning and continue the execution, or parse anything after he major.minor.patch as a string ...



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
Loading...