For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 9 replies, 4 voices, and was last updated 18 years, 10 months ago by
.
-
Posts
-
Am I correct in assuming that MyEclipse has absolutely no ability to incrementally revise WARs when doing an application server deployment? Why is this feature, ubiquitous in other respectable IDE’s (NetBeans, JBuilder, etc.) present but completely missing MyEclipse? Is there anything the user community could do to help bring incremental WAR support into MyEclipse?
I apologize if there is previous discussion or notes on this matter. I gave a good effort to check. Also, if there is anything I can do to help add the functionality (the OS mentality), please let me know.
canadacow,
I don’t know what you mean by “incremental WAR”, but a feature that MyEclipse has had much longer than any other IDE that allows for immediate synchronization of changes is the use of Exploded Deployments. Your project is deployed, as-is, out to your app server then run. As you make changes to the files they are immediately synchronized with your app server for you as soon as the file is saved. No need to redeploy.You need to be using an exploded deployment for this functionality to work.
You need to be using an exploded deployment for this functionality to work.
I am aware that MyEclipse supports exploded deployments for some application servers and that incremental deployments are possible in such situations. However, it doesn’t seem as though MyEclipse supports exploded deployments for about half of the AS’s it supports. In particular, the AS in question, SJAS 9, does not support exploded deployments (at least not with MyEclipse at the helm).
In the MyEclipse documentation, it reads, “packaged deployment is less efficient than exploded deployment. This is because to update a packaged deployment with incremental changes requires rebuilding of the entire archive.” However, with other IDE’s they typically replace only the files that have changed in the WAR and have that revised WAR processed for deployment. The turn around with AS’s like SJAS is seconds rather than minutes.
Thank-you for your assistance in this matter.
I am aware that MyEclipse supports exploded deployments for some application servers and that incremental deployments are possible in such situations. However, it doesn’t seem as though MyEclipse supports exploded deployments for about half of the AS’s it supports. In particular, the AS in question, SJAS 9, does not support exploded deployments (at least not with MyEclipse at the helm).
I have used Sun Application Server 9 quite extensively with an exploded deployment for development. I have also used Glassfish, both have worked.
I appreciate your response, yet you have me confused. Both the MyEclipse documentation and MyEclipse itself claim that exploded deployments to Sun Java Application Server 9 are not possible. The following image is what I see regarding the disabled ability to do exploded deployments to SJSAS 9. I should point out that for a handful of other applications I use Tomcat and the exploded deployment is both enabled and workable there.
If I’m doing something wrong, please let me know. Also, following the image is my MyEclipse installation information.
*** Date: Thu Oct 19 11:22:16 EDT 2006
*** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_07*** MyEclipse details:
MyEclipse Enterprise WorkbenchVersion: 5.0 GA
Build id: 20060805-5.0-GA*** Eclipse details:
Eclipse SDKVersion: 3.2.1
Build id: M20060921-0945Eclipse Platform
Version: 3.2.1.r321_v20060921-b_XVA-INSQSyMtx
Build id: M20060629-1905Eclipse Java Development Tools
Version: 3.2.1.r321_v20060905-R4CM1Znkvre9wC-
Build id: M20060921-0945Eclipse Project SDK
Version: 3.2.1.r321_v20060801-tQ1w49KnTArT0FZ
Build id: M20060921-0945Eclipse RCP
Version: 3.2.1.r321_v20060801-2ekW2BxmcpPUOoq
Build id: M20060629-1905Eclipse Plug-in Development Environment
Version: 3.2.1.r321_v20060823-6vYLLdQ3Nk8DrFG
Build id: M20060921-0945Eclipse Graphical Editing Framework
Version: 3.2.0.v20060626
Build id: 20060627-0816Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\eclipse\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
1458_74
-vm
C:\WINNT\system32\javaw.exeThe documentation I am sourcing is here: http://myeclipseide.com/enterpriseworkbench/help/index.jsp?topic=/com.genuitec.myeclipse.doc/html/concepts/deployment.htm
I second the need for help regarding exploded deployments with SJAS/Glassfish. I have experienced similar problems and our migration to SJAS is now crippling us from a development perspective. The docs say it can’t be done, and the SJAS docs also say that you can’t do exploded autodeployments, so I don’t quite now how to deal with this.
Guys,
This looks like a bug. While we look into this on our end, you can always work around any hard-set connector limitations like this by creating a “Custom Location” deployment and telling it to deploy to a specific location.*Note: I closed the thread as a signal to myself that I had filed an associated bug with it in our internal tracking system. It doesn’t mean we are done talking about he issue.
