For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 18 replies, 2 voices, and was last updated 18 years, 7 months ago by
.
-
Posts
-
It doesn’t. So, what is the difference ? How come when I choose custom deployment at some location it works but it doesn’t work within WAS 5 ?!
thanks
klaussThis is officially very strange… is your WAS install on a network partition? Was it installed as a different user? Could this possibly be a permission issue?
I wonder if at an even lower level, if there is a corrupt directory or file on the hard disk… Can you try and recreate the custom deployment one level up each time from the correct WAS directory until it *does* write correctly? I’m curious if there is something weird about the entire WAS install (meaning no directory UNDER it will work) or if it’s just the installedApps dir…
@support-rkalla wrote:
This is officially very strange… is your WAS install on a network partition? Was it installed as a different user? Could this possibly be a permission issue?
I wonder if at an even lower level, if there is a corrupt directory or file on the hard disk… Can you try and recreate the custom deployment one level up each time from the correct WAS directory until it *does* write correctly? I’m curious if there is something weird about the entire WAS install (meaning no directory UNDER it will work) or if it’s just the installedApps dir…
You think that is strange ?! Hear this !
I finally manage to make it work following the next steps:
1. you deploy the packaged ear file on the installableApps in the Manage Deployments section on the WAS 5 and then deploy, also using the Manage Deployments section, the same project using the <b>Custom Suffixed</b> configuration, in the installedApps dir of the WAS 5 as <b>exploded</b> project.
2. do the WAS 5 console deploy of the same application (it overwrites the exploded project on the installedApps with all the components including the generated RMIC code)
3. stop server and using the Manage Deployments you can remove now the packaged project.What you have now is the exploded project on the right directory on the WAS 5 app server but deployed using Custom Suffixed config of MyEclipse, hence all the changes you make now in the project are synchronized directly on the server. <b>Except for all the changes I’m making on the EJBs</b>. Could this be because the EJBs are deployed inside a jar file on the exploded project ?!
klauss
1. you deploy the packaged ear file on the installableApps in the Manage Deployments section on the WAS 5 and then deploy, also using the Manage Deployments section, the same project using the Custom Suffixed configuration, in the installedApps dir of the WAS 5 as exploded project.
2. do the WAS 5 console deploy of the same application (it overwrites the exploded project on the installedApps with all the components including the generated RMIC code)
3. stop server and using the Manage Deployments you can remove now the packaged project.I understand the need to overlay an exploded deployment ontop of the existing app, that is what is outlined in that doc, but I don’t understand why you had to use suffixed OR why it’s not been working this entire time… I really appreciate you following up with that information for other folks in the same situation though, that is important.
Except for all the changes I’m making on the EJBs. Could this be because the EJBs are deployed inside a jar file on the exploded project ?!
Yes that is correct. We do not re-create archived files for hot-syncing because we used to WAY back in the day, and there was quite an out-cry from folks that were maintaining huge enterprise projects, and every single time they saved some multi-megabyte archive would be re-created in the background and redeployed. It really bogged down the machine during development.
