Jahia Dev Forum > Change .war file...

1 (1 Good)
0 (0 Bad)

Change .war file than old componants also visible

by  bhadreshshiroya »  2014/02/03 10:28

i have to change the .war file than clean all cache and server restarts  than old componants also visible

Any solution cache releted in jahia  

 

  • Change .war file than old componants also visible
    2014/03/04 06:21

    bhadreshshiroya <p> i have to change the .war file than clean all cache and server restarts &nbsp;than old componants also visible</p> <p> Any solution cache releted in jahia &nbsp;</p> <p> &nbsp;</p>

  • Number of messages  18
    Registration date Feb 3, 2014
    1 (1 Good)
    0 (0 Bad)

    Re: Change .war file than old componants also visible

    by  shyrkov »  2014/02/21 09:23

    Hello,

     

    I am not sure to understand what you are trying to do.

    Could you be more precise on what are you doing, which Jahia version and build number you are using?

    I can only guess, that you are trying to deploy a new version of your custom module, where you have removed some components, right?

    The "old" components are not automatically removed when you deploy a new version. From the safety and consistency point of view, Jahia 6.6 does not delete any already deployed components when y a new version of a moduler is deployed. We are changing this behaviour in the upcoming Jahia 7, where we are basing module deployment on the OSGi framework and a lot more things are possible with it.

     

    Kind regards

    Sergiy

  • Re: Change .war file than old componants also visible
    2014/03/04 06:21

    shyrkov <p> Hello,</p> <p> &nbsp;</p> <p> I am not sure to understand what you are trying to do.</p> <p> Could you be more precise on what are you doing, which Jahia version and build number you are using?</p> <p> I can only guess, that you are trying to deploy a new version of your custom module, where you have removed some components, right?</p> <p> The &quot;old&quot; components are not automatically removed when you deploy a new version. From the safety and consistency point of view, Jahia 6.6 does not delete any already deployed components when y a new version of a moduler is deployed. We are changing this behaviour in the upcoming Jahia 7, where we are basing module deployment on the OSGi framework and a lot more things are possible with it.</p> <p> &nbsp;</p> <p> Kind regards</p> <p> Sergiy</p>

  • Number of messages  407
    Registration date Feb 21, 2014
    Contact
    Share
    Feedback

    Get in touch

    Whether you are a current user or if you are just evaluating Jahia, we are here to help.

    Contact us

    Share this page