Thanks for the responses… and the winner is:
setDefaultRequestHandler( requestHandlerForKey( directActionRequestHandlerKey()
) );
(Thanks Hugi)
Larry Mills-Gahl
elem...@gmail.com
On Aug 12, 2014, at 4:22 PM, Larry Mills-Gahl wrote:
> I was using the Wonder pageWithName(Class) hoping to
I was using the Wonder pageWithName(Class) hoping to make the issues with
another Main on the classpath moot. That’s when I saw that “Main” was still
getting passed into the WOApplication.pageWithName and began wondering if the
String for the class name was getting set somewhere as a default bef
On Aug 12, 2014, at 12:56 PM, Theodore Petrosky wrote:
>
> @Override
> public WOActionResults defaultAction() {
> return pageWithName(CPEMain.class.getName());
> }
>
>
> what about adding getName()
>
I think pageWithName in Wonder takes ether class or the cl
I take that back.
I just tried it on one of my apps
@Override
public WOActionResults defaultAction() {
//return pageWithName(Main.class.getName());
return pageWithName(KickOffBriefInstructions.class);
}
worked fine to subst
@Override
public WOActionResults defaultAction() {
return pageWithName(CPEMain.class.getName());
}
what about adding getName()
On Aug 12, 2014, at 3:32 PM, Larry Mills-Gahl wrote:
> I am trying to use a different default component in the defaultAction
For this to work you’ll have to make the direct action request handler your
default request handler. Stashing this in your Application class’ constructor
should do the trick.
setDefaultRequestHandler( requestHandlerForKey( directActionRequestHandlerKey()
) );
Cheers,
- hugi
> On 12. ágú. 20
I am trying to use a different default component in the defaultAction.
The defaultAction is pretty straight forward:
@Override
public WOActionResults defaultAction() {
return pageWithName(CPEMain.class);
}
… but the Application still looks for “Main” when
