// Copyright 2010 The Apache Software Foundation
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
to the user agent (i.e., the client web browser). Starting in Tapestry 5.2, asset paths are more structured, consisting of four parts:
/assets/-- the root path for all assets
So, an example path might be
/assets/1.0.1/corelib/components/select.png. The handler id would be
corelib, and the extra path would be
) or an error response (via
). It is the handler's responsibility to allow for client-side caching (possibly sending an
The handler should return true if it provided a response. If the handler returns false, this indicates that the
extra path did not identify a known asset (virtual or otherwise) and the AssetDispatcher service should send a
requestincoming asset request
responseused to send a response to client
extraPathadditional path to identify the specific asset
boolean handleAssetRequest(Request request, Response response, String extraPath) throws IOException;