[
https://issues.apache.org/jira/browse/WICKET-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13141657#comment-13141657
]
Todd Heaps commented on WICKET-3957:
------------------------------------
Unfortunately I haven't had time to do anything with JBoss 6/7 because of time
crunch to get a large web site developed and deployed in production.
We are still experiencing the locks, but have noticed that with newer versions
of the Wicket 1.5 branch the locking problem no longer happens all of the time
(but still often). JBoss 6 was released 12/28/2010 and 7 on 7/12/2011 so JBoss
5.1 to isn't that old - when it comes to production use.
Please do whatever you feel is necessary with this bug. Becoming familiar with
JBoss 6/7 enough to get a quick start working will take time we won't have for
probably another few months.
> PackageResource file locking problem
> ------------------------------------
>
> Key: WICKET-3957
> URL: https://issues.apache.org/jira/browse/WICKET-3957
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.5-RC5.1
> Environment: Windows 7, JBoss 5.1.0.GA, Eclipse Helios/Indigo
> Reporter: Todd Heaps
> Attachments: file-locking-1.4.zip, file-locking.zip,
> jboss-5.1-installation.txt
>
>
> After moving from 1.4.x to 1.5-RC5.1, updates to resources loaded via
> IHeaderContributor.renderHead() cause file and/or directory locking problems
> on individual files and/or at the base package directory level. The resulting
> locking problems disallow changes to resources without stopping the server,
> followed by a project refresh, rebuild, and server restart. This obviously
> slows down development time quite severely.
> Comparable quick starts generated from 1.4.17 and 1.5-SNAPSHOT demonstrate
> the problem in 1.5 but no problem in 1.4.17. Similar testing in Linux reveals
> no problems, nor does there appear to be a problem when using the generated
> quick starts with Jetty. This seems to be a JBoss and Windows with Wicket 1.5
> specific problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
