I never said that, I just gave you an alternate way of achieving the same thing :)
I'm not familiar nor did I ever use the SharedResources#putClassAlias() method, but given the API for SharedResources it seems to have been moved or removed. Wicket 1.4.x (has it at): http://wicket.apache.org/apidocs/1.4/org/apache/wicket/SharedResources.html# putClassAlias(java.lang.Class, java.lang.String) Wicket 1.5.x (does not list it, at least not in the same class name): http://wicket.apache.org/apidocs/1.5/org/apache/wicket/SharedResources.html If adding the resources to the root of the war works, why bother? Unless you're packaging a reusable component or you use dynamic resources, but having a static URL might indicate otherwise. Take a look at IResource and the many different implementations of it and see which one can help you most, or implement your own either from scratch or extending an existing one :) http://wicket.apache.org/apidocs/1.5/org/apache/wicket/request/resource/IRes ource.html ~ Thank you, Paul Bors -----Original Message----- From: Alec Swan [mailto:[email protected]] Sent: Tuesday, September 11, 2012 11:42 AM To: [email protected] Subject: Re: Wicket 1.5 migration questions > I take it by global you mean http://myServer:###/myWebApp/global? Yes. > If so, why don't you just add the folder to the root of your war? Good point, I could do that, but I'd rather keep my current folder structure. So, does it mean that putClassAlias functionality is gone in 1.5? Thanks, Alec --------------------------------------------------------------------- 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]
