why is Main being called again?
why is Main being called again?
- Subject: why is Main being called again?
- From: Baiss Eric Magnusson <email@hidden>
- Date: Fri, 27 Jan 2006 14:52:26 -0800
In cleaning out all the cobwebs with the new server move I re-visited
this issue I've had forever.
Track-Your-Finances has a <Main> page which is your basic <Login> page.
The user gets to it from clicking on a button on a static page which
does a:
<FORM method="post" name="startPage" action="http://track-your-
finances.com/cgi-bin/WebObjects/trackyourfinances">
which brings up the Main page (but not by going through
DirectAction.defaultAction())? I've done a stackTrace:
java.lang.Exception
at Main.<init>(Main.java:40)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance
(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance
(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at com.webobjects.foundation._NSUtilities.instantiateObject
(_NSUtilities.java:575)
at
com.webobjects.appserver._private.WOComponentDefinition._componentInstan
ceInContext(WOComponentDefinition.java:463)
at
com.webobjects.appserver._private.WOComponentDefinition.componentInstanc
eInContext(WOComponentDefinition.java:573)
at com.webobjects.appserver.WOApplication.pageWithName
(WOApplication.java:1954)
at
com.webobjects.appserver._private.WOComponentRequestHandler._dispatchWit
hPreparedSession(WOComponentRequestHandler.java:273)
at
com.webobjects.appserver._private.WOComponentRequestHandler._dispatchWit
hPreparedApplication(WOComponentRequestHandler.java:322)
at
com.webobjects.appserver._private.WOComponentRequestHandler._handleReque
st(WOComponentRequestHandler.java:358)
at
com.webobjects.appserver._private.WOComponentRequestHandler.handleReques
t(WOComponentRequestHandler.java:432)
at com.webobjects.appserver.WOApplication.dispatchRequest
(WOApplication.java:1306)
at com.webobjects.appserver._private.WOWorkerThread.runOnce
(WOWorkerThread.java:173)
at com.webobjects.appserver._private.WOWorkerThread.run
(WOWorkerThread.java:254)
at java.lang.Thread.run(Thread.java:552)
After the User logs in the page is dismissed and the User goes to
other pages in the meta-bank application.
If the User chooses either of 2 specific pages, suddenly the <Main>
class constructor gets called, the page doesn't come up but I can't
figure out what it is in the inner WO frameworks that needs something
from that Main class, here's its stackTrace:
java.lang.Exception
at Main.<init>(Main.java:40)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance
(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance
(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at com.webobjects.foundation._NSUtilities.instantiateObject
(_NSUtilities.java:575)
at
com.webobjects.appserver._private.WOComponentDefinition._componentInstan
ceInContext(WOComponentDefinition.java:488)
at
com.webobjects.appserver._private.WOComponentDefinition.componentInstanc
eInContext(WOComponentDefinition.java:594)
( same as 1st StackTrace, only the call points are different in the
above 2 methods for the 2nd and subsequent calls Main receives )
Is it ok that this is happening?
----
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@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden