- This topic has 16 replies, 6 voices, and was last updated 20 years, 2 months ago by
.
-
Posts
-
I tested the Sun App Server 8 successfully with their hello.war
My test web app worked fine as well when I deployed the packaged archive with MyEclipse, but not with the exploded archive.
Do I need to configure something else somewhere?
I am using 3.8.1. + QF20040825 …
Regards,
Frank
Frank,
The Sun application server doesn’t support automatic deployment of exploded applications. It’s just a limitation in their implementation. We left the capability to produce an exploded deployment in the product in case Sun addresssed this limitation in a patch or in case some “Sun 8 wizard” knows a workaround to manually reconfigure the server’s config files to support it. Unfortunately, we have not found such a configuration internally.
Just for the record, you can of course get your web application to run by using the admin interface to the web-server. So, the myeclipse deployment works great, the only minor thing is that your application isn’t automatically installed. However, installing through the admin console only takes a few clicks plus a few clicks more if you wish to run from the web-site’s root.
Arjan,
Thanks for the followup. I’d forgotten about the admin console completely. So now I can add to what I said earlier by saying “do it like Arjan says and it works fine.” 🙂
Scott,
thanks for your prompt feedback.
I just re-read the Sync-on-Demand deployment description. It states that it works with exploded and packaged archives. Is the deployment of packaged archives just slower or are there then other limitations as well?
Regards,
Frank
Frank,
Sync-on-Demand won’t automatically synchronize changes to packaged archives due to the large overhead in repackaging the entire applications. For packaged archives, you’ll have to redeploy manually when you test your changes.
If we stated somewhere that Sync automatically updates packaged archives can you send me the reference so we can be sure to fix the description to be more clear?
Scott,
To my understanding there still seems to be something wrong with my setup and the Sun App Server deployment from within MyEclipse.
The test application did not get deployed to directory ‘autodeploy’ with the ‘.war’ extension!
When I define a new deployment and choose exploded archives for server: JBoss
Then the Deploy Location ‘…/deploy/webapp.war’ is shown with the .war extension at the end.When I change over to server: Sun in the same dialog …
Then the Deploy Location ‘…/autodeploy/webapp’ is shown WITHOUT the .war extension at the end?!Regards,
Frank
Scott,
“Sync-on-Demand works with either packaged deployment or exploded archive models, the later being the most advantageous to developers. ”
Maybe you can add the limitations for the packaged deployment here .. .
Regards,
Frank
The test application did not get deployed to directory ‘autodeploy’ with the ‘.war’ extension!
That’s because the Sun server doesn’t require it and JBoss does. There’s no standard on how to deploy exploded archives and each server just “supports what it wants” in this regard. It should still work fine when deployed through Sun’s admin tool, however.
Scott,
I asume you refer to the ‘Deploy …’ option under ‘Applications > Web Applications’ in the Sun AS console. According to my tests it works only with packaged archives.
The Deployment Page states:
Use this page to specify the location of an application to deploy. Applications can be in packaged files, such as .war and .ear files, or in the standard application directory format.Here I select upload file : NO … ‘The packaged file or directory path must be accessible from the server’
Then I define the packaged .war file and it works fine, but not with the Directory i.e. exploded archive. It does not even allow me to select a folder when I browse through the directories…
Regards,
Frank
Your did something else wrong then, I use Sun App server 8 too, and it just works fine with exploded archives.
You don’t have to browse for the directory, but you have to enter the path manually. E.g.
C:\Sun\AppServer\domains\domain1\autodeploy\my_app
Where my_app is your projects name.
For the context root, type anything you’d like (it doesn’t have to be the root you specified when creating the web application with the myeclipse wizard)
If you’d like you application to run on the site’s root, use / for the context root field and go to HTTP Service->Virtual Servers->server. On the Edit Virtual Server page, select my_app from the default web module dropdown box.
Sun Java System Application Server 8 (SJSAS 8) supports deploying both archives and directory deployment (what you called exploded archive.) To deploy a directory with an exploded WAR in the Admin GUI, select <Web Applications> and choose <Deploy…>. On the first page, for upload file choose <No> and put the local directory of the archive in the Directory field. I noticed there is a bug in that the browse dialog does not allow selection of a directory. I will report this. However, you can type or paste the absolute directory path directly into the field to get past this. Then click the <Next> field in the upper right, enter the name, context root, and some other optional choices, click <Finish> and you’re done.
As for tool support, the NetBeans Plugin we wrote for SJSAS 8 uses directory deployment with no problems. I do not know what troubles the MyEclipse team encountered implementing this feature in the MyEclipse plugin, but it is supported by the server.
Minor update – regarding selecting a directory in the Admin GUI. This is not a bug. Web Browsers do not allow the Browse Dialog to be configured to allow directory selection. Because of this, in the 8.1 administration console, the UI has been changed to reflect this limitation and avoid confusion. For 8.0, just key in the directory manually.
Some more information and clarification of Automatic Deployment and Directory Deployment. Each SJSAS8 domain has an Auto Deploy directory that is monitored and the server will auto deploy any archive file placed in this directory. See http://docs.sun.com/source/817-6088/depapp.html#wp1024720 for more details on this. In addition, to aid developer productivity, the server also supports the concept of deploying exploded archives. The directory in question must be initially deployed manually (see comments above and also the previous link). However, once this step is done, the server will monitor this deployed directory for changes to the application (e.g. changed JSP’s, etc.) and reflect those in the running application. (Presumably in any new sessions, what happens in any existing sessions, I’m not sure, but that probably depends on the scope of the change.)
So with respect to comments on “Automatic Directory Deployment”, what did you mean? Do the above features satisfy your needs?
