facebook

Hot deployment problem for web.xml with WebSphere 6.1

  1. MyEclipse Archived
  2.  > 
  3. Bugs
Viewing 15 posts - 1 through 15 (of 17 total)
  • Author
    Posts
  • #279084 Reply

    Paul_P
    Member

    This message has not been recovered.

    #279142 Reply

    Loyal Water
    Member

    This message has not been recovered.

    #279673 Reply

    Paul_P
    Member

    Nipun,

    thanks for your message. As we heard, the first release of MyEclipse Blue Edition is scheduled for Mid March. We bought a number of MyEclipse 6.0.1 licenses and are using it in our everyday development. After MyEclipse Blue will come out, we will try it and probably upgrade our subscriptions.

    It would though be important for us that this bug be fixed as soon as possible. I suppose, that will take place in the next release of MyEclipse, so before the Blue Edition. Is that right? When will the next MyEclipse Version come out?

    Thanks & Regards,

    Paul P.

    #279684 Reply

    Riyad Kalla
    Member

    Paul,
    We are working to get this WAS-specific behavior into Blue Edition, but the good news is that we are targeting a mid-Jan release for Blue. Our 6.1 release we are shooting for March/April.

    I believe should have a milestone for Blue out before the final release, so any feedback you could give us during testing would be appreciated if possible when that happens.

    #280407 Reply

    rkathler
    Member

    Adding to issue above that Paul has listed, I have a problem that is related.

    App Server that I have – Websphere 61 on Windows XP Professional and Intel hardware.

    I followed the directions on the below url http://www.myeclipseide.com/documentation/quickstarts/websphere6/ to configure my Websphere 61 (not 60) server

    I wanted to do the Enterprise Sync-on-Demand Development as explained in the above URL. For some reason the MyEclipse 61 connector links to 2 different directories for Package and Exploded views.
    For Packaged View it points to – C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv02\installableApps
    For Exploded View it points to – C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv02\installedApps
    One is “installableApps” and one is “installedApps”.
    So with this I am not able to do the following instruction as documented in the MyEclipse documentation listed on the above URL.
    “So, in order to be able to install to WebSphere (and other application servers that require installation of EARs) and still gain the benefit of Exploded deployment, we need to do a little trick to “overlay” an exploded deployment ontop of an existing installed application. ”

    My question is – How do i configure MyEclipse to change the “Exploded” and the “Packaged” to the same directory to “overlay” or is there another way to do this?
    Any help is greatly appreciated.
    Thanks
    Raj

    #280452 Reply

    Riyad Kalla
    Member

    Raj,
    You don’t need to worry about changing the directory. What you do is first deploy the packaged deployment, it will be put in “installableApps”, you then login to WAS Admin Console and *install* the app. Now you remove the packaged deployment and redeploy an exploded deployment, it will automatically overlay ontop of where WAS installed the packaged app: “installedApps”

    #280461 Reply

    rkathler
    Member

    Awesome.
    Thanks Riyad.
    That did the trick. I was thinking too much and got ahead of me.
    Thanks
    Raj

    #280466 Reply

    Riyad Kalla
    Member

    No problem, glad it helped.

    #289530 Reply

    Paul_P
    Member

    Hi,

    we upgraded to MyEclipse Blue Edition. We are using MyEclipse 6.5.1 Blue-GA-20080715. Now some of my colleagues are working with IBM WebSphere Portal, Version 6.0.1.3. They have the same problem with WebSphere Portal:

    Some configuration files, particularly web.xml, portlet.xml und struts-config.xml, are saved upon installation in the following backup directory:
    <WebSpherePortalRoot>\profiles\<profileName>\config\cells\<cellname>\applications\<AppName>\deployments\<AppEAR>\

    As described in my previous messages, MyEclipse Blue use these files in the deployment process from the above directory, instead of the exploded deployment directory. This leads to the fact that when we change these configuration files, the old files are still used and the new ones are ignored.

    To solve this problem, the HotDeployment Plugin of MyEclipse Blue should IMHO copy the configuration files to the backup directory as well, not only to the Exploded Deployment Directory.

    Can you please deliver a patch that solves this problem?

    Many thanks in advance,

    Paul P

    #289753 Reply

    Riyad Kalla
    Member

    Paul,

    I believe a solution to this issue is on our roadmap, I’ll ping the Blue dev team to double check however.

    #289786 Reply

    Paul_P
    Member

    Hi rkhalla,

    I’m sorry, but this is not what I expected. For one year, you have been writing that you plan to fix this problem in the next release. Unfortunately, this didn’t happen, neither for WAS nor for the WebSphere Portal, neither in MyEclipse nor in the Blue Edition. This problem is costing our company every day time, nerves and money. We need to know when this problem will be solved, in order to be able to calculate reliably the work efficiency on our projects.

    Please provide us with an exact release date for this bugfix.

    Thanks in advance,

    Paul P

    #289809 Reply

    Riyad Kalla
    Member

    Paul,

    I’m discussing/evaluating this with management right now. Will need to wait on them for full evaluation.

    #290146 Reply

    Paul_P
    Member

    Hi Riyad,

    we have been waiting for two weeks now. How long do your management need for the “full evaluation” you are mentioning?

    Please give us a quick answer.

    Thank you,

    Paul

    #290161 Reply

    Riyad Kalla
    Member

    Paul,

    Management did assess it and will try and address it in November for the 7.0GA release. So I do have a pending commitment out of them now.

    #291320 Reply

    Paul_P
    Member

    Hi Riyad,

    has the bug been fixed in 7.0GA? When exactly will 7.0GA be (or has been) released?

    Thanks,

    Paul

Viewing 15 posts - 1 through 15 (of 17 total)
Reply To: Hot deployment problem for web.xml with WebSphere 6.1

You must be logged in to post in the forum log in