You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by Apache Wiki <wi...@apache.org> on 2005/10/02 12:05:24 UTC

[Jakarta-cactus Wiki] Update of "GeneralDiscussions/Maven2Migration" by KenneyWesterhof

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jakarta-cactus Wiki" for change notification.

The following page has been changed by KenneyWesterhof:
http://wiki.apache.org/jakarta-cactus/GeneralDiscussions/Maven2Migration

------------------------------------------------------------------------------
  
  = Proposals =
  
-  * To decouple the subprojects.
+  * To decouple the subprojects [Finished for framework main code; test code still needs decoupling]
-  * To re-organize the project structure in a maven-friendly way.
+  * To re-organize the project structure in a maven-friendly way [Partly done]
   * It will be great if Cactus was intellegent enough to detect automatically the servlet version. Take `HttpServletRequestWrapper` as an example. Maybe we don't need to provide one `HttpServletRequestWrapper` per servlet spec version. We may try to implement a generic `HttpServletRequestWrapper` that supports all versions. For methods which are not supported by the servlet spec (for example, `getRequestURL()` is not supported by version 2.2), just throw out an `UnsupportedOperationException`. Thus we may make a codebase that is cleaner and easier to maintain.
  
+ = Comments =
+  * Detecting the servlet version is a good idea; however it might require runtime access to the different servlet specifications. A general HttpServletRequestWrapper that works for all servlet specifications sound good. There's just one problem: it has to 'implements ...' a specific interface. The name of the interface is the same, but I'm not sure about the runtime checking - the jvm might detect that it's a different interface and throw IncompatibleClassChangeError or something similar. Since the differences between the code are minimal we can live with just one implementation that will be linked against the different servlet specifications. We can either re-link existing code multiple times or create empty subclasses in different projects.
+ 

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