dependencies on their framework. This is a good thing. This often translates
to people wanting to write objects that don't know they will be used in a
framework. This seems impossible if you actually want your objects to work with the features of the framework.
For instance it is likely that any reference you have to something supplied
by the framework should be marked transient. Your code has to declare that - it can't be managed by the framework.
Based on what you've described, I don't agree with you. Personally, I think of frameworks such as xwork/webwork can be thought of a sophisticated adapter. They adapt my business logic to the web, swing, jms, what have you. When I'm working on presentation or other layer integration issues, I'm dealing directly with the framework. However, when I'm working on business logic, I want the framework to get out of my way.
Can you provide a more detailed example of framework features you want to get access to directly from your business logic?
M
------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
