Ahh... are you try to set up an RESTful type of URI where the path is relevant to the request being executed?

I had to do something like that for an images resource recently... although it may be more at the mercy of Wicket than what you need.

Hmm... how about a IRequestTargetUrlCodingStrategy?
This is on the verge of guessing now, but i think it will allow you to mount it and then check if you want to process the request with it.

What I used it for was some Apple javascript (Dashcode stuff) that was being insistent on the paths it used for its resources and which didn't match those used for a Wicket resource. The coding strategy would essentially checked if the path began with some known value, and then used a PackageResourceStream to load the wicketized version of the content.

The code for the strategy is below in case it gives you the clues you need to resolve your issue.

- Brill

public class IPhoneImageRequestTargetUrlCodingStrategy implements
                IRequestTargetUrlCodingStrategy {

        @Override
        public IRequestTarget decode(RequestParameters requestParameters) {
                String path = requestParameters.getPath();
                ResourceStreamRequestTarget target = new 
ResourceStreamRequestTarget(
                                new PackageResourceStream(DashboardPage.class, 
path));
                return target;
        }

        @Override
        public CharSequence encode(IRequestTarget requestTarget) {
                return null;
        }

        @Override
        public String getMountPath() {
                return "Images";
        }

        @Override
        public boolean matches(IRequestTarget requestTarget) {
                return false;
        }

        public boolean matches(String path) {
                return path.startsWith("Images/") && path.endsWith(".png");
        }

        @Override
        public boolean matches(String path, boolean arg1) {
                return matches(path);
        }

}






On 23-Mar-09, at 1:12 AM, Jan Kriesten wrote:


Hi Brill,

what about setting up an "error page" using the standard servlet method
that points to a wicket page?

the point is: you will still get a 404 error code for the page (which the
user/search engine shouldn't, since it's not an error).

Best regards, --- Jan.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to