Excellent, I'm glad I asked. I'll just let it be for now. . .
David
Don Brown wrote:
Talk to Bob Lee. He is in the middle of creating a new API that would
replace how Struts 2 apps currently interact with the framework. In
that work, he is creating new Struts interfaces, many of which simply
wrap xwork ones so that a Struts 2 application wouldn't be tied to or
even know about xwork. The interfaces you bring up are part of that
conversion, already in progess.
Don
On 10/23/06, David H. DeWolf <[EMAIL PROTECTED]> wrote:
Both the API and the Core modules have defined the Aware interfaces
(RequestAware, ResponseAware, and ParamaterAware). Only the versions in
the core module are actually used by the interceptor.
I would suggest that we do one of three things:
1) Remove the interfaces defined in org.apache.struts2.servlet (in the
api module) to avoid confusion
2) Refactor the ServletConfigInterceptor to use the
org.apache.struts2.servlet interfaces defined in the api module and
remove the org.apache.struts2.interpceptor interfaces (in the core
module).
3) Use reflection to determine whether or not to set the request. In
this case I would suggest removing the core interfaces and leaving the
api interfaces for convenience (just as we have an Action interface for
convenience).
Am I right that this duplication is simply oversight? Anyone have any
preference as to which option I use to rectify it?
David
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
