Sounds good.
If you decide you really must use a ref cursor, the PL/SQL would look like this example hitting the emp table of the SCOTT schema:
CREATE OR REPLACE PROCEDURE SHOW_EMPLOYEES_CURSOR(a_results OUT SYS_REFCURSOR) IS
v_empno number;
v_ename varchar2(10);
v_job varchar2(9);
v_mgr number;
v_hiredate date;
v_sal number;
v_comm number;
v_deptno number;
BEGIN
OPEN a_results FOR SELECT empno, ename, job, mgr, hiredate, sal, comm, deptno
INTO v_empno, v_ename, v_job, v_mgr, v_hiredate, v_sal, v_comm, v_deptno
FROM emp;
RETURN;
END SHOW_EMPLOYEES_CURSOR;
On the webMethods side, you set up a storedProcedureWithSignature adapter service. On the call tab, enter the stored procedure name. The args should be populated for you. On the resultset tab, in the lower table, add a row for every column in the result set. Select the name of your ref cursor out arg in the result set name dropdown for each row. I set the type for all rows to VARCHAR.
The retch results will be pulled into an IS document which will contain a document list containing the rows fetched from the cursor.
Regards
#Integration-Server-and-ESB#Flow-and-Java-services#webMethods