On 12/22/05, Garner, Shawn <[EMAIL PROTECTED]> wrote:
>
> Can you elaborate on the first two bullets (*)?
> I'm not familiar with either.
The current remoting implementation in Shale allows you to register commands
or chains (in the Commons Chain sense) to context-relative URL patterns. It
uses a filter to intercept such requests ahead of the standard JSF
processing servlet. The "use cases" example webapp that comes with Shale
illustrates this with a couple examples, such as this one in the
chain-config.xml file:
<catalog name="remote">
<chain name="/list/stateNames.remote">
<command className="org.apache.shale.remote.EvaluateExpression"
expression="${domains.stateNames}"
attributeKey="strings"/>
<command className="org.apache.shale.remote.BasicListCompletions
"/>
</chain>
...
</catalog>
So, when a context relative URL of "/list/stateNames.remote" is recognized
on an incoming request, the specified chain is executed to prepare the
response (in this case, it creates a list of US state abbreviations and
names in an XML format), instead of the usual JSF processing.
It would be straightforward to make the matching a bit more flexible, so you
could match a pattern like "/list/*.remote" instead, going to a chain that
would then be able to parse out which list you wanted. But, even without
that, you could create a chain for all the interesting URLs with the
existing technology.
I'm not inclined to be for the idea of mixing architectures by including
> action based struts in JSF/Shale so I'm not big on the third bullet (*).
>
> Shawn
Craig
