Depending on what your "SecureComponent" actually does, you might
want to consider
- just having it as a flagging interface and test for it for example
in session.appendToResponse if context().page() implements it
- move general functionality to static methods of some
SecureUtilities class
- create a "SecureWrapper" dynamic element and wrap your normal
components with it. (not a component, because you may have problems
with stateful/stateless children)
And frankly, I couldn't imagine why you would make a long response
"secure"... the whole point of it is that it just does continual
reloads? And you might want to factor this out like in the
ERXLongResponsePage/ERXLongResponseTask because it's a pain to create
the html all over again for each type of task.
Cheers, Anjo
Am 06.07.2006 um 20:18 schrieb Baiss Eric Magnusson:
I have a class
public class SecureComponent extends WOComponent {
I have
public class ReviewTrans extends SecureComponent {
I want it to be
public class ReviewTrans extends SecureComponent {
where <SecureComponent> is a sub-class of WOLongResponsePage, not
WOComponent, but only for this one class.
NOTE: WOLongResponsePage is a sub-class of WOComponent.
All I can see to do is duplicate the code in SecureComponent and
create another class <SecureComponentLong>.
----
Baiss Eric Magnusson
<http://www.Track-Your-Finances.com>
<http://www.CascadeWebDesign.com>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/krank%
40logicunited.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
