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
Riyad Kalla.
-
AuthorPosts
-
klaussMemberI’m currently working with MyEclipse Enterprise Workbench Version: 5.1.0 GA Build id: 20061111-5.1.0-GA over the WAS 5.1.
Having created an enterprise application, following the tutorial at
http://myeclipseide.com/enterpriseworkbench/help/index.jsp?topic=/com.genuitec.myeclipse.doc/html/quickstarts/websphere6/index.html
I’ve managed to deploy my application and I was looking forward to use the Sync-on-demand feature. Which unfortunatelly doesn’t work.
I believe WAS 5.1 behaves the same way as WAS 6 described in the tutorial.
Then I discovered a warning message : “Deployment is out of date due to changes in the underlying project contents. You’ll need
to manually ‘Redeploy’ the project to update the deployed archive.” So I created an ant task which refreshes the exploded install and it works.Can anyone tell me what to set or change in order to have the sync-on-demand working within the MyEclipse IDE ?
Thanks
klaussDecember 22, 2006 at 9:43 am #263816
Riyad KallaMemberKlauss,
Running out-of-process tasks like Ant or other scripts that change the contents of the project will cause MyEclipse to loose perspective of exactly the files on your disk drive. YOu need to either refresh your project manually or go to Window > Prefs > General > Workspace, and check “Automatically refresh” in order to keep contents synchronized.December 29, 2006 at 8:36 am #263960
klaussMember@support-rkalla wrote:
Klauss,
Running out-of-process tasks like Ant or other scripts that change the contents of the project will cause MyEclipse to loose perspective of exactly the files on your disk drive. YOu need to either refresh your project manually or go to Window > Prefs > General > Workspace, and check “Automatically refresh” in order to keep contents synchronized.Ok, done that, still nothing … I mean, I am expecting that everytime I modify a class (EJB or a servlet) or a jsp to see sync-on-demand at work …and by that I mean the console giving me the messages that the project was modified and my new changes already in place (synchronized). but … nothing. I hardly use Ant to change the content … NO. I use ANT to simply copy from my workspace to the Exploded project on the AppServer. Basically, I’m refreshing manually. I was hoping to make it work automatically, thats all.
thanks,
klaussDecember 31, 2006 at 11:54 am #263976
Riyad KallaMemberKlauss,
Thanks for the clarification about the Ant script… out of curiosity are you using an exploded deployment for your ear? That is the only way to get the sync-on-demand support.January 2, 2007 at 9:50 am #264000
klaussMember@support-rkalla wrote:
Klauss,
Thanks for the clarification about the Ant script… out of curiosity are you using an exploded deployment for your ear? That is the only way to get the sync-on-demand support.Yes,I am. I’m doing everything by the book … so to speak. As I haven’t found a tutorial on WAS 5 I used the one on WAS 6 (presuming it all goes the same), the one which link I provided in my first post. All in all, it works if I refresh manually the content on the Exploded project on the AppServer. I only wish it could work automatically.
thanks
KlaussJanuary 2, 2007 at 10:15 am #264009
Riyad KallaMemberThe auto-deploy feature is hooked into the build cycle. That means you need to have, under Window > Prefs > General > Workspace, the Automatically build setting turned on (it’s default is ON). The thing is, if it requires you to refresh your project to get the deployment to work, that means either that setting is off OR you are changing files outside of the Eclipse process, so it’s not seeing them. In which case that first setting I mentioned should fix that.
January 4, 2007 at 10:32 am #264130
klaussMember@support-rkalla wrote:
The auto-deploy feature is hooked into the build cycle. That means you need to have, under Window > Prefs > General > Workspace, the Automatically build setting turned on (it’s default is ON). The thing is, if it requires you to refresh your project to get the deployment to work, that means either that setting is off OR you are changing files outside of the Eclipse process, so it’s not seeing them. In which case that first setting I mentioned should fix that.
So, what you’re saying is that whether:
1. I don’t have the “Build automatically” setting turned on, along with “Refresh automatically” on, so by doing that it would all work just fine.
2. OR, I’m changing files outside MyEclipse, hence the auto-deploy feature it’s not working because it is not able to detect the changes.Well, I turned on “Refresh automatically” which was unchecked having had “Build automatically” turned on all the time. And I only work inside the MyEclipse environment. And, it still doesn’t work. I need to refresh manually (deploy manually).Not only that, but not even the fact that I redeploy the project doesn’t seem to refresh my Exploded project on the AppServer.
So, where is the problem ?!
Plus, today I just found out my debug feature doesn’t work.The only thing I can think of is the fact that I’m using a trial version.
thanks
klaussJanuary 4, 2007 at 11:16 am #264131
Riyad KallaMemberKlauss,
Did the trial expire?Also, how are you determining that the changes are not being updated? Are you just hitting refresh in your browser, or are you actually using Windows Explorer to go out to the deployed location and check the time stamps o the actual files themselves to see if the timestamps are change? Also have you tried checking the contents, using say Notepad, of the deployed files to see if they are being updated?
Yes you got the facts above right, that is what I am saying. It sounds like all your settings and everything is just fine… so the only two things I can think of now is:
1) The files *are* getting deployed by MyEclipse, but they are not getting reloaded by your app server. So the actual files are updated, but your app server is still hosting you the old copies so you aren’t seeing the changes.
2) You are trying to redeploy to a running app server which is failing due to read-locks… (but you didn’t mention any problems, so maybe not?)
3) There is some miscommunication between functionality and what is actually happening and we are misunderstanding eachother…
January 5, 2007 at 2:14 am #264190
klaussMember@support-rkalla wrote:
Klauss,
Did the trial expire?Also, how are you determining that the changes are not being updated? Are you just hitting refresh in your browser, or are you actually using Windows Explorer to go out to the deployed location and check the time stamps o the actual files themselves to see if the timestamps are change? Also have you tried checking the contents, using say Notepad, of the deployed files to see if they are being updated?
Yes you got the facts above right, that is what I am saying. It sounds like all your settings and everything is just fine… so the only two things I can think of now is:
1) The files *are* getting deployed by MyEclipse, but they are not getting reloaded by your app server. So the actual files are updated, but your app server is still hosting you the old copies so you aren’t seeing the changes.
2) You are trying to redeploy to a running app server which is failing due to read-locks… (but you didn’t mention any problems, so maybe not?)
3) There is some miscommunication between functionality and what is actually happening and we are misunderstanding eachother…
My trial is due to expire at the end of the month, so I rather understand that’s not part of the problem.
Of the three things you have described, the one that fully applies is the first: the modified files are getting deployed by MyEclipse but are not actually deployed on the AppServer (updated – that’s why I use the ant script to manually update the files on the server). So, my app server still holds the old files – why needs to be done ?!
One more thing: when do you get read-locks ?! My WAS 5 AppServer was stopped when I removed the packaged project and added the exploded project in the manage deployments section.
thanks
klaussJanuary 5, 2007 at 8:05 am #264200
Riyad KallaMemberOf the three things you have described, the one that fully applies is the first: the modified files are getting deployed by MyEclipse but are not actually deployed on the AppServer (updated – that’s why I use the ant script to manually update the files on the server). So, my app server still holds the old files – why needs to be done ?!
Thank you for clarifying.
If this is the case, then you need to modify your Websphere 5 settings to reload changes to your web application. I’m not terribly familiar with Websphere, but I believe if you login to the administration console and go to the settings for your deployed webapp, the setting is on that page.
One more thing: when do you get read-locks ?! My WAS 5 AppServer was stopped when I removed the packaged project and added the exploded project in the manage deployments section.
Read locks are only an issue on Windows because of how the Windows filesystem works. Linux and Mac don’t have the same issue.
More specifically, when the app server has loaded resources from your web application and is running it (e.g. JAR files) it has a read-lock, which means when you try and remove the file, the remove operation will fail (undeployment in this case, will fail) so it’s always a good idea to switch the deployments when the app server is off.
January 5, 2007 at 8:37 am #264211
klaussMember@support-rkalla wrote:
Of the three things you have described, the one that fully applies is the first: the modified files are getting deployed by MyEclipse but are not actually deployed on the AppServer (updated – that’s why I use the ant script to manually update the files on the server). So, my app server still holds the old files – why needs to be done ?!
Thank you for clarifying.
If this is the case, then you need to modify your Websphere 5 settings to reload changes to your web application. I’m not terribly familiar with Websphere, but I believe if you login to the administration console and go to the settings for your deployed webapp, the setting is on that page.
One more thing: when do you get read-locks ?! My WAS 5 AppServer was stopped when I removed the packaged project and added the exploded project in the manage deployments section.
Read locks are only an issue on Windows because of how the Windows filesystem works. Linux and Mac don’t have the same issue.
More specifically, when the app server has loaded resources from your web application and is running it (e.g. JAR files) it has a read-lock, which means when you try and remove the file, the remove operation will fail (undeployment in this case, will fail) so it’s always a good idea to switch the deployments when the app server is off.
I see your point but I was under the impression it was MyEclipse’s job to copy (synchronize) the content from my workspace (which resides on disk C) to the exploded project under my Websphere server (which resides on disk G).Am I missing something ?! Cause if I do it manually it works just fine, so my AppServer responds to the new files, so it can’t be the dynamic class loading on behalf of Websphere. Anyway, I checked the settings on Websphere and it all appears to be fine as far as dynamic reloading is concerned.
It doesn’t concern the readlocks either from what I’ve seen.
thanks
klaussFeel free to PM me on the matter.
January 5, 2007 at 9:13 am #264212
Riyad KallaMemberI see your point but I was under the impression it was MyEclipse’s job to copy (synchronize) the content from my workspace (which resides on disk C) to the exploded project under my Websphere server (which resides on disk G).Am I missing something ?!
Klauss, this is exactly right. However from your comment above “the modified files are getting deployed by MyEclipse but are not actually deployed on the AppServer…” I took that to mean that MyEclipse *is* deploying the files… can you clarify what you mean? Is MyEclipse deploying the files, but just to the wrong directory maybe?
Cause if I do it manually it works just fine, so my AppServer responds to the new files, so it can’t be the dynamic class loading on behalf of Websphere. Anyway, I checked the settings on Websphere and it all appears to be fine as far as dynamic reloading is concerned.
Ok that is good news, in that case all we need to do is get MyEclipse putting the files in the right place and Websphere will pick them up.
January 5, 2007 at 9:44 am #264215
klaussMember@support-rkalla wrote:
I see your point but I was under the impression it was MyEclipse’s job to copy (synchronize) the content from my workspace (which resides on disk C) to the exploded project under my Websphere server (which resides on disk G).Am I missing something ?!
Klauss, this is exactly right. However from your comment above “the modified files are getting deployed by MyEclipse but are not actually deployed on the AppServer…” I took that to mean that MyEclipse *is* deploying the files… can you clarify what you mean? Is MyEclipse deploying the files, but just to the wrong directory maybe?
Cause if I do it manually it works just fine, so my AppServer responds to the new files, so it can’t be the dynamic class loading on behalf of Websphere. Anyway, I checked the settings on Websphere and it all appears to be fine as far as dynamic reloading is concerned.
Ok that is good news, in that case all we need to do is get MyEclipse putting the files in the right place and Websphere will pick them up.
I’m sorry, I must have mislead you … now that I think about it, MyEclipse doesnt deploy anything. When I said it did, I meant I was going to “Manage Deployments” section and deployed there, but there’s no actual deployment whatsoever cause MyEclipse doesn’t copy anything to Websphere. So, YES, MyEclipse should copy the modified content but it doesn’t. Now, all we need is to figure out why and what has to be done !
thanks
klaussJanuary 5, 2007 at 1:20 pm #264223
Riyad KallaMemberOk, it’s super sanity-check time… we’ll take this back to the basics and work our way up, figuring out what is going wrong here one piece of the puzzle at a time.
Step 1) Take a deep breath.
Step 2) Create a brand new Web Project, call it “TestWebProject”. Add a single JSP to the WebRoot dir, doesn’t matter what it’s called or it’s contents, just use the Default JSP template.
Step 3) Setup a custom deployment, with an Exploded type, for this project to some location that doesn’t exist, like C:\TestWebProject
Step 4) Open the JSP file in MYEclipse. Make a single change, like add the word “Stupendous” to the JSP file, and save it.
Step 5) Open Windows Explorer, go to C:\TestWebProject, open the JSP file with Notepad, do you see Stupendous in it?
If at Step 5 you DO NOT, see the word Stupendous, continue to the next steps:
Step 6) Go to File > Switch Workspace > C:\tempworkspace, hit OK to restart (should be a brand new workspace).
Step 7) Immediately start with Step 1 again, creating the test project, and testing the deployment. PLEASE NOTE that you need to use a different project name, like “SecondTestWebProject”, so when you deploy it to C:\SecondTestWebProject, there isn’t any conflict or confusion with the last web project.
Step 8) Now in the new workspace, with the new project, are you seeing the “Stupendous” word in your JSP?
January 5, 2007 at 4:20 pm #264236
klaussMember@support-rkalla wrote:
Ok, it’s super sanity-check time… we’ll take this back to the basics and work our way up, figuring out what is going wrong here one piece of the puzzle at a time.
Step 1) Take a deep breath.
Step 2) Create a brand new Web Project, call it “TestWebProject”. Add a single JSP to the WebRoot dir, doesn’t matter what it’s called or it’s contents, just use the Default JSP template.
Step 3) Setup a custom deployment, with an Exploded type, for this project to some location that doesn’t exist, like C:\TestWebProject
Step 4) Open the JSP file in MYEclipse. Make a single change, like add the word “Stupendous” to the JSP file, and save it.
Step 5) Open Windows Explorer, go to C:\TestWebProject, open the JSP file with Notepad, do you see Stupendous in it?
If at Step 5 you DO NOT, see the word Stupendous, continue to the next steps:
Step 6) Go to File > Switch Workspace > C:\tempworkspace, hit OK to restart (should be a brand new workspace).
Step 7) Immediately start with Step 1 again, creating the test project, and testing the deployment. PLEASE NOTE that you need to use a different project name, like “SecondTestWebProject”, so when you deploy it to C:\SecondTestWebProject, there isn’t any conflict or confusion with the last web project.
Step 8) Now in the new workspace, with the new project, are you seeing the “Stupendous” word in your JSP?
OK, you got my attention: with the custom deployment at some location it does synchronize the content. So, why not in the installedApps on the Websphere 5 AppServer ?!
I’ll try working with Custom Location instead of Websphere 5 choosing obviously the installedApps dir in the server and see if it works. -
AuthorPosts