As Craig pointed out, we decided some time ago not to support the idea of page-relative paths. Why? Because the "pages" are often in one place and the actions are "in" another. The action "path" is not really a file path or an URL it is simply a URI. People tend to dress up like it was an URL, but it really just an logical identifier. They don't represent a true directory structure and really don't have anything to be relative to.
Of course, people could try and align their action URIs with the locations of their pages, but that tends to go against the grain in a Model 2 application. The pages are simply the conclusion of an action, where the pages come from are just an implementation detail. If you need a tag to perform differently for your architechture, our best suggestion will be to create your own subclass. I do not get the feeling that anyone else here needs to support your architecture, and it might be best to move past the handwaving and start writing code to solve your particular problem. If you'd then like to share that code with the community, we often post links to such things on the resource page, so others can review your work and benefit from it. Many of the framework's current features started out this way. -Ted. -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
