Thanks, Your mail comes just a second too late, i rebuilt turbine with some log statements and i saw that too. Now is there any way i can avoid to have to do that? My point is, since i'd like to package my classes by functionality and not by "type", i'd have to add many packages to the module.packages property; and since i've seen turbine simply attempts to load my action from every package specified in module.packages(i'm not saying there's a better way though), i guess that would be a dumb loss of performances to have many packages there. Can I do something about it? (or just forget about my favorite of organizing my packages?)
BTW, can someone tell me to what extend the action classes are cached after having been retrieved for the first time? Are they cached forever? Also, i noticed if i change my local-portlet.xreg file, live, then it seems to be reloaded. Are the corresponding actions and other classes reloaded as well? Thx & Cheers, greg -----Original Message----- From: Jeremy Ford [mailto:[EMAIL PROTECTED] Sent: mercredi 3 septembre 2003 20:02 To: [EMAIL PROTECTED] Subject: Re: Requested Action Not Found Try placing you action in the package package com.company.web.helloworld.actions. Jeremy Ford --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
