[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

[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=15985506#comment-15985506 ]

Roger Whitcomb commented on PIVOT-996:

PIVOT-996:  Yet more safety measures:  Parse the version strings inside a new
"safelyDecodeVersion()" method that traps all exceptions and provides an
"empty" version (that is, "0.0.0_00") in case of any errors.  This is what
the Pivot version already did, so use the same technique for the JVM and Java

Change the Javadoc for the three accessor methods to note this change of
behavior in case of errors.

Note: This should make application startup possible no matter what might
happen to version strings in the future.  We don't want these types of
urgent issues to come up ever again, to where the user application won't
start just because of a JVM update/change.

Sending        wtk\src\org\apache\pivot\wtk\ApplicationContext.java
Transmitting file data .done
Committing transaction...
Committed revision 1792807.

Reworked and merged to "branches/2.0.x":
Sending        .
Sending        wtk\src\org\apache\pivot\wtk\ApplicationContext.java
Transmitting file data .done
Committing transaction...
Committed revision 1792808.

> 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