Results 1 to 7 of 7

Thread: Behaviour of Zimlets with Zimbra 5.0

Hybrid View

  1. #1
    Join Date
    Nov 2007
    Posts
    17
    Rep Power
    7

    Default Behaviour of Zimlets with Zimbra 5.0

    Hello,

    I am trying to develop Zimlets using Zimbra 5.0 . I have noticed the following behaviour that makes for me the development quite difficult:

    When you deploy a Zimlet via the administration console (usually on port 7071), everything goes fine. Ok, I notice I have some bug in my Zimlet, then I undeploy it via the console. Ok, this also goes fine. But yet, wait, when I start Firebug against the running Zimbra client, I see in script Zimlet-nodev_all.js.zgz still the code of the Javascript code of the undeployed Zimlet.

    Is this behaviour normal? You undeploy a Zimlet and you still see have the "dead" code on the client? Is this a feature?

    What is the best strategy to develop Zimlets under Zimbra 5.0 . Is there some configuration options I should turn on? Which is the strategy you can use to develop Zimlets in a confortable way under Zimbra 5.0? Any idea ...?

    Kind regards,

    Gil Fernandes

  2. #2
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    21

    Default

    Welcome to the forums,

    First I would suggest using a test box where you can restart jetty.
    You can append &dev=1 which forces the zimlet source files to load separately. But while this eliminates the modular loading, caching, and also the minimization, it does change the overall behavior.
    I believe you can also increment the version in the xml file but I personally don't.
    Note: There is a known issue with the _dev folder not working ZimletWritingTip - Zimbra :: Wiki
    (Bug 19944 - Dev deployment of zimlets doesn't work is one of them)
    Last edited by mmorse; 11-27-2007 at 12:39 PM.

  3. #3
    Join Date
    Nov 2007
    Posts
    17
    Rep Power
    7

    Default

    Great !

    When I try dev=1, then I see in Firebug each one of the scripts. This is a big help already.
    Concerning restart of jetty, I already am running a test box on which I can restart it at any time. Yet I do not know how to restart it. I must confess I am a newbie to Jetty. How do you do it?

    Thanks for the valuable suggestion, Mike,

    Gil

  4. #4
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    21

    Default

    su zimbra
    zmmailboxdctl restart

  5. #5
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    21

    Default

    File a bug. &dev=1 isn't meant to be run all the time, and makes Zimbra much slower.

    This is likely related to lazy loading.

  6. #6
    Join Date
    Nov 2005
    Posts
    477
    Rep Power
    9

    Default

    Quote Originally Posted by jholder View Post
    File a bug. &dev=1 isn't meant to be run all the time, and makes Zimbra much slower.

    This is likely related to lazy loading.
    I am going to try and duplicate this behavior.

  7. #7
    Join Date
    Apr 2007
    Location
    Paris, France
    Posts
    367
    Rep Power
    8

    Default

    Comment for Gil: I have this behavior too. When I undeploy a zimlet, the zimlet is not activated anymore but files are not removed. Is this normal?

    PS : It is not only in 5.0, me I had it on 4.5

Similar Threads

  1. Replies: 26
    Last Post: 04-19-2011, 09:24 AM
  2. [SOLVED] Clamav problem ? What's happening ?
    By aNt1X in forum Installation
    Replies: 23
    Last Post: 02-14-2008, 04:43 AM
  3. Zimbra shutdowns every n hours.
    By Andrewb in forum Administrators
    Replies: 13
    Last Post: 08-14-2007, 08:55 AM
  4. upgrade woes -made into new thread
    By JustinHarlow in forum Installation
    Replies: 18
    Last Post: 06-08-2007, 12:11 PM
  5. Monitoring : Data not yet avalaible
    By s3nz3x in forum Installation
    Replies: 7
    Last Post: 11-30-2005, 06:18 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •