[JIRA-Opensymphony] Created: (WF-173) WorkflowQuery.STEP used incorrectly in JDBCWorkflowStore queries

[email protected]
Newsgroups gmane.comp.java.open-symphony.devel
Message-ID <[email protected]>
Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://jira.opensymphony.com/secure/ViewIssue.jspa?key=WF-173


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: WF-173
    Summary: WorkflowQuery.STEP used incorrectly in JDBCWorkflowStore queries
       Type: Bug

     Status: Assigned
   Priority: Minor

    Project: OSWorkflow
 Components: 
             Persistence Layer
             Core
   Versions:
             2.5

   Assignee: Patrick Lightbody
   Reporter: Dave Hauver

    Created: Thu, 29 May 2003 8:00 PM
    Updated: Thu, 29 May 2003 8:00 PM

Description:
JDBCWorkflowStore uses the wrong field name in the query criteria when Workflow.STEP is used as a query parameter.  A query created as new WorkflowQuery(WorkflowQuery.STEP, WorkflowQuery.CURRENT, WorkflowQuery.EQUALS, 5) uses a criteria of the form "ID=5" instead of "STEP_ID=5".  There is a very easy fix for this.  In the queryComparison(WorkflowQuery) method, change the following line of code:

case WorkflowQuery.STEP: // stepId
     left = stepId;

to:


case WorkflowQuery.STEP: // stepId
     left = stepStepId;


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.opensymphony.com/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.