Problem Deploying Oracle PDK Portlet to Oracle Application Server 9.0.4.0

Question

I have a big issue trying to deploy a pdk portlet I have created in JDeveloper (10.1.2). The application is very simple, it consists of 2 JSP's (call them Select.jsp and Display.jsp) and 1 Java Class (Call it DoEverything.java).
The architecture of the system is VERY simple. The Select.jsp is a simple drop down list that is embedded in an html form, with the options in the drop down populated by a method call from DoEverything.java. Once the user selects an option and hits submit, he is sent to the Display.jsp, which is a simple html table that is populated by another method call from DoEverything.java. (Basically the whole system is a simple "view" of a given table in a DB based on the option selected in Select.jsp).
The system works perfect in JDeveloper, where I created it using the Oracle PDK Java Portlet wizard. However I'm running into a problem when I try and take it over to the Application Server. The main documentation I have been following is the: Oracle® Application Server Portal Developer's Guide and in particular the section 6.6.2.4.1 Creating a Connection to Oracle Application Server Containers for J2EE where it explains how to connect to the App. Server. The line "The steps that follow describe the procedure for deploying to a standalone instance of Oracle Application Server Containers for J2EE. For information about deploying to a full Oracle Application Server instance, please refer to the Oracle JDeveloper online Help system." is the one that is bothering me the most as I am trying to deploy to a full instance of the Oracle Application Server, but I cannot find anywhere that walks me through this in the online JDeveloper help.
Anyway, currently we ftp the appropriate JSP's, Java Class, provider.xml and provider properties files to their respective directories on the Application Server, register the provider and reboot the Http Server. (This has worked before except for the fact that when the user selected an option from the Select.jsp and the request was then sent over to the Display.jsp based on the form action the Display.jsp wasn't recognized. We figured the provider.xml file needed to be edited in this case in order to know where Display.jsp was being kept). In any event nothing seems to be working at the moment and my main concern is that it maybe we should be deploying as EAR/WAR (both of which I'm not super familiar and my second main concern is that it seems most people use JavaBeans and Struts and all sorts of different API's whereas here I just have a fairly simple Java Class back end that connects to the database and creates an object based on the attributes contained in the database (1 object for 1 unique row in the DB) and I want to be sure that the way I have developed this should still work with the Oracle AS. I'm hoping its just a matter of getting the directory structure straightened out and editing the provider.xml file to include all the JSP's.
Sorry for the long post, but if you could address my two main concerns and possible give me or point me towards a good thorough walk through of deploying a simple system (oracle pdk java portlet) like I have developed to the App. Server it would be greatly appreciated !
Thanks a lot.

Answer 1

Basically I started to develop this system inside Oracle AS and then when it came time to passing a request to a new page, it crapped out on me on the App. Server. So instead of trying to fix the problem there and then I continued to develop outside Portal and inside Jdeveloper. After a week or two once all my stuff worked perfectly I try and take it back into Portal but only the first JSP of all my Portlets would show up, because as soon as I would submit a form and the action directed me to a new page and Portal would be lost/confused. Obviously I shouldn't have done it that way but none the less...
So now I'm reading through the documentation you pointed me towards and it seems I have to qualify my parameters and then "attach" them to the url which the form will pass to the actioned page. I'm importing numerous classes (...urlUtils, etc) in order to qualify the parameters and then build this url without affecting any parameters currently present that my portlet does not own.
What I'm rambling towards here is all this separation of logic and presentation and the whole nine, implies different people can develop different parts of a 'system' mostly independant of one another...so in my situation I shouldn't in huge trouble yet, since underlying everything is a working system. My issue is with oracle and the App Server. If I take my code which works great outside of the App. Server and I fully qualify parameters and make sure my form actions are constructed using the UrlUtils in order to fully qualify them as well, and then I make sure page parameters are mapped to the proper portlet parameter values....should my system work on the App Server (assuming everything is done properly)....or am I still missing something.