[
https://issues.apache.org/jira/browse/ODE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689393#action_12689393
]
Ciaran Jessup commented on ODE-422:
-----------------------------------
We've not seen any failures since that fix :) My only comment is that the
constructor for that object (Job) allows you to construct an instance that
would cause runtime exceptions within the equals/hashcode methods, this isn't
causing us a problem currently, but its something to be aware of!
> NPE in Job.equals of scheduler
> ------------------------------
>
> Key: ODE-422
> URL: https://issues.apache.org/jira/browse/ODE-422
> Project: ODE
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Windows Server 2003 SP2, Java 1.6.0-b105, Tomcat 5.5,
> ODE branch 1.2 revision 711434
> Reporter: John Rossall
> Priority: Minor
> Fix For: 1.3
>
> Attachments: Job.patch
>
>
> I get a null pointer exception in the equals method of
> org.apache.ode.scheduler.simple.Job.
> This is because the job id is null. Why the job id is null i do not know, but
> the constructor allows a null job id.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
