Hi Wolfgang,
This was my checkin from last night -- it ended up containing files I didn't mean to submit. Let me see if I can submit the rest of the files (e.g., the updated Jpf interface) quickly; if not, I'll just roll back my original change.
Thanks, and apologies for the inconvenience, Rich
At 09:40 AM 9/15/2004, you wrote:
Hi there,
I've got a checkin request for netui DRT.
Although the Jpf.ActionOutput interface doesn't have a variable named "required", the required attribute(parameter?) is
specified in PageInputController.jpf. Thus, the drt process fails.
The result of diff below removes the "required" attribute.
Thanks in advace.
wolfgang
Index: netui/test/webapps/drt/coreWeb/pageFlowCore/pfPageInput/PageInputController.jpf
===================================================================
--- netui/test/webapps/drt/coreWeb/pageFlowCore/pfPageInput/PageInputController.jpf (revision 46118)
+++ netui/test/webapps/drt/coreWeb/pageFlowCore/pfPageInput/PageInputController.jpf (working copy)
@@ -37,7 +37,7 @@
navigateTo = Jpf.NavigateTo.currentPage),
@Jpf.Forward(
name = "globalSuccessMissingButNullable",
- [EMAIL PROTECTED](name="missingButNullable", type=String.class, required=false)},
+ [EMAIL PROTECTED](name="missingButNullable", type=String.class)},
navigateTo = Jpf.NavigateTo.currentPage)
})
@Jpf.ViewProperties(
@@ -302,7 +302,7 @@
forwards = {
@Jpf.Forward(
name = "success",
- [EMAIL PROTECTED](name="missingButNullable", type=String.class, required=false)},
+ [EMAIL PROTECTED](name="missingButNullable", type=String.class)},
navigateTo = Jpf.NavigateTo.currentPage)
})
protected Forward missingButNullable1()
