On Sun, May 25, 2008 at 9:05 AM, David Nedrow <[EMAIL PROTECTED]> wrote:
>
> What problems do packaged resources address?
they address encapsulation. suppose you want to use a 3rd party
component in your webapp...
in most other frameworks you would have to put the jar on the
classpath, than copy js/css/html resources the component needs to some
place where it expects it; if you dont want to copy it to the place
where it expects it you have to recode some stuff. this gets pretty
unmanageable when working with a lot of components, they may have
collisions in the resources they want, etc.
in wicket the only step is to put the jar on the classpath. since
everything the component needs is packaged in the jar it can
immediately start working.
none of the designers i worked with had any problem going into source
tree and working with resources there.
-igor
> I'm unsure as to why I would
> encapsulate resources in the package, rather than using them as I normally
> would via the WEB-INF tree.
>
> It seems as though encapsulating them would present a problem with
> separation of concerns, in which one team might be focusing just on
> presentation (eg. CSS, etc.) while another handles just the Java code.
>
> Using packaged resources would seem to require that the presentation people
> have access not only to the sources, but also to the dev platform to rebuild
> the package just to test CSS changes.
>
> -David
>
> -
> 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]
