Re: Resource lookup/caching in OSGI environment
https://issues.apache.org/jira/browse/WICKET-2212 thanks, K On Mon, Apr 6, 2009 at 4:02 AM, Igor Vaynberg igor.vaynb...@gmail.comwrote: open a jira issue for this -igor On Sun, Apr 5, 2009 at 4:38 PM, Kristof Jozsa kristof.jo...@gmail.com wrote: Hi all, 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..) thanks, Kristof - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Resource lookup/caching in OSGI environment
Hi all, 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..) thanks, Kristof
Re: Static injection not working (wicket-guice)
Hi Edgar, can you share some details with me about what you're trying to accomplish? You can write me privately, this doesn't sound like a wicket issue so better not load the wicket-users list with the topic. Kristof On Wed, Oct 22, 2008 at 8:02 AM, Edgar Merino [EMAIL PROTECTED] wrote: Hello, I've been trying to inject a service to some classes that are not wicket components, I've asked here and was suggested to use static injection: InjectorHolder.getInjector().inject(this); however this is not working with guice, I always get an illegalstateexception, injectorholder has not been assigned an injector. I've tried ((GuiceInjectorHolder) (RequestCycle.get().getApplication().getMetaData(GuiceInjectorHolder.INJECTOR_KEY))).getInjector().injectMembers(this); however that gives me serialization problems, since wicket is not creating a proxy for my service. I'm on my way to give salve a try but I'm having some problems there too (waiting for a response from the Discussion group), what suggestions can you make? Thanks in advance, Edgar Merino - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Salve and Guice
Hi Edgar, did you use either static weaving or the runtime agent as described at http://code.google.com/p/salve/wiki/ConfiguringInstrumentation ? Kristof On Tue, Oct 21, 2008 at 11:42 AM, Edgar Merino [EMAIL PROTECTED] wrote: I've been searching for information on how to use guice to lookup dependencies with salve, the wiki only mentions how to add the guice locator but I believe that is not working (at least not by it self). I've got a class in a wicket application that is not a component, but I need a service injected, so I'm using salve for this, instead of using @Inject to inject the service I use @Dependency, but I'm getting nullpointerexceptions, any hint? Thank you, Edgar Merino - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wicket 1.4 release
totally out of topic and excuse me for my curiosity, but do you use subversion to the heavy lifting with such branching/merging there or use some distributed version control system behind the scenes? K On Thu, Oct 2, 2008 at 9:25 AM, Johan Compagner [EMAIL PROTECTED] wrote: yes we should make a 1.3.5 and a 1.4m4 asap, there are a lot of changes I think i will make some time this weekend to look over jira issues and also merge back a lot of changes i already did in 1.3.5 igor did also a lot of stuff already so for me within 1 or 2 weeks we could do both releases johan On Thu, Oct 2, 2008 at 8:15 AM, Stefan Lindner [EMAIL PROTECTED] wrote: It's clear that it's not possible to estimate the release of 1.4 final. But can anybody tell us whether a new snapshot (1.4M4) is in sight? Stefan -Ursprüngliche Nachricht- Von: Timo Rantalaiho [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 2. Oktober 2008 05:37 An: users@wicket.apache.org Betreff: Re: wicket 1.4 release On Wed, 01 Oct 2008, lesterburlap wrote: I've searched everywhere and can't find an answer. I know this is kind of a crappy question to ask the developers... Is there an estimate for a Wicket 1.4 GA release? Will it possibly be by January 2009? I think that it's impossible to estimate the releases of a volunteer-based open source projects in any meaningful way, unfortunately. If others know better, please pipe in. You can always follow the number of open issues https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truepid=12310561fixfor=12313295resolution=-1sorter/field=issuekeysorter/order=DESC ( http://tinurl.us/a2b895 ) but there might be some new ones coming in as well. Also work continues on 1.3.5 at the same time (fortunately, many of the issues can probably be fixed to both at the same time). Your good patches to the issues are bound to make the release happen earlier ;) I need to make a decision about whether or not to upgrade to 1.4-m3 from 1.3. while intending to upgrade to 1.4 GA prior to my product release in January. I need some stuff that's in 1.4, but I can't release our product with beta libraries included. Fortunately, there is not a lot of special testing for the releases, so a milestone is nearly good enough ;) What's more problematic with releasing with a milestone dependency are the possible API breaks. Best wishes, Timo -- Timo Rantalaiho Reaktor Innovations OyURL: http://www.ri.fi/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
setResponsePage(Page) and back button
Hi,
I'd love to use setResponsePage(Page) (so redirecting to a concrete
page instance instead of a page class) on handling standard (non-ajax)
links in my application. I found it very handy to use the actual model
objects in their current state, instantiate the new page object
passing the current models and set them as the response page, like
this:
public void onClick() {
setResponsePage(new MySubPage(anyCurrentModelObject));
}
Unfortunately, every time I use the back button and trying to click on
links again, I get a page expiration. Is there any way around this?
I don't claim this being a problem, there might be a rational reason
for this behaviour, but passing current model objects this way would
be much more handy than using page parameters and rebuilding models on
the new page from scratch. Can I somehow accomplish this?
thanks,
Kristof
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: setResponsePage(Page) and back button
Damn, you be starboard! Removin' t' only known unserializable booty
from me base page class immediately solved t' problem. I bow before
your mightyness, captain!
Kristof Threapwood
On Fri, Sep 19, 2008 at 11:41 AM, Martijn Dashorst
[EMAIL PROTECTED] wrote:
Avast! Did ye check furr t' nasty serialization errs? Them could sink
a mighty ship and cause them pesky expiration pages.
Capt'n McDasmans
(t'is Internation'l Talk Like a pirate day t'day matey!)
http://talklikeapirate.com
On Fri, Sep 19, 2008 at 11:36 AM, Kristof Jozsa [EMAIL PROTECTED] wrote:
Hi,
I'd love to use setResponsePage(Page) (so redirecting to a concrete
page instance instead of a page class) on handling standard (non-ajax)
links in my application. I found it very handy to use the actual model
objects in their current state, instantiate the new page object
passing the current models and set them as the response page, like
this:
public void onClick() {
setResponsePage(new MySubPage(anyCurrentModelObject));
}
Unfortunately, every time I use the back button and trying to click on
links again, I get a page expiration. Is there any way around this?
I don't claim this being a problem, there might be a rational reason
for this behaviour, but passing current model objects this way would
be much more handy than using page parameters and rebuilding models on
the new page from scratch. Can I somehow accomplish this?
thanks,
Kristof
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
