issue with defaultCommandChild

It appears that the defaultCommandChild attribute is ignored. Regardless of what the attribute is set to the default command always seems to default to the first child that is defined.Is this a known issue? Is there a fix/workaround?
[254 byte] By [canoepaddler] at [2007-11-25 8:23:27]
# 1
I will do a regression test, but can you give us more information about where you're specifying the attribute, and any error messages you are receiving?
tfast at 2007-7-1 14:45:18 > top of Java-index,Development Tools,Java Tools...
# 2

We're not receiving any type of error message. The problem is that the button that I set the defaultCommandChild to is just not being executed.

We're specifying the attribute in the jato form tag of the jsp as follows:

<jato:form name="Login" defaultCommandChild="/Submit">

The html that is rendered for this page appears as follows:

<html>

<head>

<title>Login</title>

</head>

<body>

<form name="Login" method="post" action="../module1/Login;jsessionid=525185F36523B4A3F02214C8B6622571">

<h1></h1>

<p>

Login:<input type="text" name="Login.login" value="" maxLength="20" size="20">

<p>

Password:<input type="password" name="Login.password" value="" maxLength="20" size="20">

<p>

<input type="submit" name="Login.reset" value="Reset">

<input type="submit" name="Login.submit" value="Submit">

<input type="hidden" name="jato.defaultCommand" value="/Submit">

<input type="hidden" name="jato.pageSession" value="">

</form>

<!-- Add content here -->

</body>

</html>

NOTE: This is using JATO 1.2.1 .

canoepaddler at 2007-7-1 14:45:18 > top of Java-index,Development Tools,Java Tools...
# 3
Based on the rendered page, the defaultCommandChild value should be "/submit", without the capital "S". Try that and let me know.Todd
tfast at 2007-7-1 14:45:18 > top of Java-index,Development Tools,Java Tools...
# 4
Changing the case of the Submit did not make a difference.Any other suggestions?
canoepaddler at 2007-7-1 14:45:18 > top of Java-index,Development Tools,Java Tools...
# 5

Well, I've verified that the defaultCommandChild attribute is working as expected in 2.0, and I don't know of any reasons it wouldn't be working the same in 1.2.1. Have you confirmed that your Button is registered via a call to registerChild()? Have you tried your test case in a different browser?

If all else fails, maybe you can send a simple test case based on your app in WAR format for us to test here. If nothing else, send your ViewBean and JSP sources. Send all to jatoteam@sun.com.

Todd

tfast at 2007-7-1 14:45:18 > top of Java-index,Development Tools,Java Tools...