- This topic has 5 replies, 2 voices, and was last updated 12 years, 5 months ago by
support-swapna.
-
AuthorPosts
-
striebhzMemberHi,
we have another annoying problem here:
If we redeploy our application with changes in XHTML (JSF), WebSphere won’t load the changes so we still see the old version in the browser.
If we change java code too everything works fine.We use “Packaged mode” for deployment and WebSphere 8.0.0.2.
The EAR in “installableApps” doesn’t get updates. I think it even is the version of the first deployment, but i’m not sure.
But: In “installedApps” the files are up-to-date, so I’m not sure if it is a MyEclipse or a WebSphere problem.
Nevertheless a hint or fix would be great.
Thanks.
support-swapnaModeratorstriebhz ,
It looks like an issue with Websphere 8.0.
1. Do you see this issue only with changes made to XHTML files? Do the jsps work fine?
2. Can you please try removing the project and deploy it again and see if it reflects the new changes?
3. Can you please also check if restarting of the server shows the correct version of the files ?Let us know how it works for you.
striebhzMemberCurrently, we don’t have any jsps.
But yes, removing and deploying or restarting the server fixes the problem.
We can also work around the problem by simply deploying twice. On the second deploy, MyEclipse states that there are no changes and performs a full redeploy.That way it works but it’s a very time consuming approach. Are there probably some cache files which should be deleted?
support-swapnaModeratorstriebhz,
If it is working fine when you restart the server, then its a WAS issue and I suggest you check on WAS related support forums for the fix.
Hope it helps.
striebhzMemberI will ask there for help, but shouldn’t MyEclipse support the users developping their applications and provide a workaround for that problem?
How does RAD handle that?
support-swapnaModeratorstriebhz,
We do support applications for Websphere and provide workarounds if the problem is with MyEclipse.
In this case, its the WAS issue and I am afraid I cannot provide a workaround. You will get better support in WAS forums for this issue.
Sorry for inconvenience caused.
-
AuthorPosts