[jira] [Commented] (ROL-1436) JPA backend code triggers lots of warning messages at build time

["Glen Mazza (JIRA)" <ji...@apache.org>]

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

Glen Mazza commented on ROL-1436:
---------------------------------

I fixed all of the first type of comment, and couldn't see any of the second.  We still have about a dozen remaining of this type: https://issues.apache.org/jira/browse/OPENJPA-2389, which I left hoping that OPENJPA-2389 will get fixed first.
                
> JPA backend code triggers lots of warning messages at build time
> ----------------------------------------------------------------
>
>                 Key: ROL-1436
>                 URL: https://issues.apache.org/jira/browse/ROL-1436
>             Project: Roller
>          Issue Type: Task
>          Components: JPA Backend
>            Reporter: Allen Gilliland
>            Assignee: Roller Unassigned
>
> There are a ton of warning messages given when building the new jpa backend code and they should probably be addressed ...
> [openjpac] "org.apache.roller.pojos.TaskLockData" uses property access, but its field "timeAquired" is accessed directly in method "getLeaseExpires" defined in "org.apache.roller.pojos.TaskLockData".
> [openjpac] Bytecode analysis of the setter and getter methods for persistent property "org.apache.roller.pojos.TaskLockData.locked" indicates that the two methods might be acting on different backing fields.  The setter method assigns to field "locked", while the getter method returns field "null".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira