| Code: |
|
<application-server application-directory="../applications" application-auto-deploy-directory="../application-autodeploy" deployment-directory="../application-deployments" > |
| Quote: |
|
With tomcat, I was simply able to hit the save button and all changes were automatilcly deployed and compiled. |
| Quote: |
|
With OC4j I Must stop the server, delete any insance of "EASE" in the application directory , redeploy and then re-start the server. |
| Quote: |
|
Auto-deploying file:/C:/dev/appservers/oc4j_rel2/j2ee/home/application-autodeploy/TestEAR/TestWeb/ (New server version detected)... Auto-unpacking C:\dev\appservers\oc4j_rel2\j2ee\home\application-autodeploy\TestEAR.ear... done. Auto-unpacking C:\dev\appservers\oc4j_rel2\j2ee\home\application-autodeploy\TestEAR\TestWeb.war... done. Auto-deploying TestEAR (Assembly had been updated)... Auto-deploying file:/C:/dev/appservers/oc4j_rel2/j2ee/home/application-autodeploy/TestEAR/TestWeb/ (Assembly had been updated)... |
| support-scott wrote: |
|
1) Create a web project and an EAR to contain it. |
| Quote: |
|
I've been through the tutorials and it is not readily apparent to me how to create an EAR after the fact. |
| Code: |
|
<application-server application-directory="../applications" application-auto-deploy-directory="../application-autodeploy" deployment-directory="../application-deployments" > |
| support-rkalla wrote: |
| Some J2EE app servers (like WebLogic) require that you fire up the adaministrative console and "deploy" the application into the app server before it is loaded... OC4J might be the same way. |
| Quote: |
|
I realized that I had to have Packaged Archive instead of Exploded Archive selected. |