Handling First_rows in Web Logic

Question

Dear ALL,
The First_rows hint in a query in oracle gives data in first come first server basis .
Is there any way to handle java result set to act in sync with first_rows so that first few are processed not needing to wait for query completion.
It seems resultset object waits for query completion (i.e) complete result set to be fetched.
Basically i am just a beginner to java and middleware.
Can this be done?
There is an option prefetch enable in weblogic console ....does this correspond to first_rows ?
Thanks in advance,
Vijay G

Answer 1

Hi,
>Could you tell how to move the targets section?
Weblogic Console-->Deployments-->Your Application-->Testing
>Any link for reading?
http://docs.oracle.com/cd/E14571_01/web.1111/b31974/deployment_topics.htm
https://blogs.oracle.com/shay/entry/common_pitfalls_when_deploying
After you deploy the application, you can test it from Oracle WebLogic Server. To test-run your ADF application, open a browser window and enter a URL:
  For non-Faces pages: http://<host>:port/<context root>/<page>
  For Faces pages: http://<host>:port/<context root>/faces/<view_id>  where <view_id> is the view ID of the ADF task flow view activity.
Tip:
The context root for an application is specified in the view-controller project settings by default as ApplicationName/ProjectName/context-root. You can shorten this name by specifying a name that is unique across the target application server. Right-click the view-controller project, and choose Project Properties. In the Project Properties dialog, select Java EE Application and enter a unique name for the context root.
Note:
/faces has to be in the URL for Faces pages. This is because JDeveloper configures your web.xml file to use the URL pattern of /faces in order to be associated with the Faces Servlet. The Faces Servlet does its per-request processing, strips out /faces part in the URL, then forwards the URL to the JSP. If you do not include the /faces in the URL, then the Faces Servlet is not engaged (since the URL pattern doesn't match). Your JSP is run without the necessary JSF per-request processing.
Regards,
Fabian