[
https://issues.apache.org/jira/browse/WICKET-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696446#action_12696446
]
Kristof Jozsa commented on WICKET-2212:
---------------------------------------
Thanks Juergen for your quick work. The patch looks okay for me (by looking at
it), but after I fetched wicket from trunk, applied the patch and tried to
check in Modulefusion, other (completely unrelated) problems appeared.. I'll
either wait for a new modulefusion release or try to fix them myself, but it'll
take some time.
> Resource lookup/caching in OSGI environment spams errors for gone resources
> ---------------------------------------------------------------------------
>
> Key: WICKET-2212
> URL: https://issues.apache.org/jira/browse/WICKET-2212
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.4-RC2
> Environment: Wicket 1.4RC2 running in Modulefusion (on Apache Felix)
> Reporter: Kristof Jozsa
> Attachments: wiclet-2212.patch
>
>
> I'd put together a simple dynamic menu example running on Modulefusion where
> the contributed menu items and pages come from another OSGI bundles. It works
> exactly as expected, eg. submenus appear/disappear automatically without
> restarts on submenu modules' deploys and undeploys, but after undeploying an
> already visited page's module, my server logs starts repeating messages like
> this:
> 352322 [ModificationWatcher Task] ERROR
> org.apache.wicket.util.resource.UrlResourceStream - getLastModified for
> bundle://38.0:1/com/ftldev/wicket1/Boo.html failed: No bundle associated with
> resource: bundle://38.0:1/com/ftldev/wicket1/Boo.html
> I guess this has to do with resource caching. Is it possible to get this
> behaviour turn into a warning and/or get it stop after the first message? I
> guess once a resource has gone, it makes no good to keep looking for it
> forever anyway.. or is it another approach getting around this message?
> (again, appearently all my app keeps working fine meanwhile..)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
