struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 38050] - Remote Method Call Simplification
Date Tue, 03 Jan 2006 19:29:58 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38050>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38050





------- Additional Comments From dgeary@apache.org  2006-01-03 20:29 -------
(In reply to comment #1)
> It is not quite in time for Christmas :-), but grab nightly build 20060103 or
> later and have a look at the classes in the new "org.apache.shale.remoting"
> package.  The package overview Javadocs for this package contain some basic
> documentation, which will have to suffice until the website features
> documentation is updated, as well as the Use Cases example app.

This is very nice. Thanks Craig, for the quick response to the initial RFE.

A couple questions:

1. Perhaps I'm missing something, but the implementation of
MethodBindingProcessor seems broken to me. Here's why:

MethodBindingProcessor creates a method binding based on the incoming URL. The
name of the method is always the URL's extension, so for example,
http://shale_example/dynamic/bean.methodname results in this method binding:
#{bean.methodname}. But a URL like that will likely never be processed by the
phase listener because it's not mapped to the Faces servlet. So, to trigger the
method binding processor, you've got to have a URL like
http://shale_example/dynamic/bean.faces (where *.faces is mapped to the Faces
Servlet), but now the method binding is #{bean.faces}.

So it seems that you can only invoke either methods named faces (or whatever
you've chosen for extension mapping to the Faces servlet) or you have to add
additional mappings to the Faces servlet for each method name.

2. I would like to add a remote validation mechanism so we can use the Commons
Validator integration to do realtime validation, in addition to client- and
server-side. I would like to add a new mechanism, Mechanism.VALIDATOR_RESOURCE,
with a default mapping of '/validate/*'. Should I ultimately add another call to
configureMappings in RemotingPhaseListener.createMappings() and add a fourth
default mapping?

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Mime
View raw message