I saw a post before about someone having trouble redeploying with Weblogic. We’re having the same trouble with Tomcat on Windows.

 

We have a webapp that includes Flex, but we can’t do an ‘undeploy’ or a ‘reload’ without having to shutdown the server and explicity deleting the webapp directory because the locks on the jars in WEB-INF\flex\jars aren’t being released, even though the webapp has been stopped. An undeploy with remove all other webapp artifacts except for this directory, effectively preventing redeploying the webapp without a server restart.

 

Tomcat has a work around: you can set the antiResourceLocking="true" attribute in conf/context.xml before starting Tomcat, but for us, this is a bad solution because of the size of our webapp. Setting this attribute is known to drastically increase webapp startup time.

 

I’ve heard that there won’t be a solution for this until Flex 2.0, but I’d really like to know if that’s the case, or if anyone else has discovered a workaround for this issue.

 

Thanks!

 

Tony

 

 

tony pujals| senior engineer | Yahoo! small business publishing tools

p. 408.349.6284 | e. [EMAIL PROTECTED] | y!id tonypujals

 



--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




Reply via email to