I remember that newer versions of JBoss have some file system
abstraction (virtual fs or something like that). This caused similar
problems to other Wicket users. Check the mail archives.
Also try with another web container (e.g. Tomcat or Jetty) and see
whether the problem is still there.

On Thu, Aug 4, 2011 at 6:34 PM, rush66 <jrlangs...@gmail.com> wrote:
> My apologies for the confusion. Development is cumbersome in windows with
> this issue having to restart jboss to pickup changes made to JS and CSS
> files.
>
> We are using Wicket 1.5RC5.1.  Changes to JS and CSS files are not picked up
> using eclipse running jboss locally in windows 7. Something from the javaw
> process seems to be leaving file handles to the resources open and due to
> the warning that shows up in the log about failed to get last modified time
> it makes me think it is something in the modification watcher.  Something
> about the file handle or lock prevents eclipse from coping it to the output
> directory.
>
> Concerning ubuntu we setup a dev environment running the same eclipse and
> jboss with the project. When changes to JS and CSS files are made with the
> app server is running it doesn't log the same warning. So refreshing the
> browser in ubuntu changes to resource files are picked up.
>
> I hope that can clarify the situation a little more.
>
> Thanks
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/CSS-JS-resource-file-handle-issues-tp3701938p3719068.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to