Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 5243 invoked from network); 15 Apr 2005 12:54:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Apr 2005 12:54:06 -0000 Received: (qmail 99090 invoked by uid 500); 15 Apr 2005 12:53:57 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 99014 invoked by uid 500); 15 Apr 2005 12:53:56 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 98995 invoked by uid 99); 15 Apr 2005 12:53:56 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from smtp001.mail.ukl.yahoo.com (HELO smtp001.mail.ukl.yahoo.com) (217.12.11.32) by apache.org (qpsmtpd/0.28) with SMTP; Fri, 15 Apr 2005 05:53:55 -0700 Received: from unknown (HELO ?192.168.1.31?) (reinhard?poetz@62.178.239.20 with plain) by smtp001.mail.ukl.yahoo.com with SMTP; 15 Apr 2005 12:53:52 -0000 Message-ID: <425FB95D.3090108@apache.org> Date: Fri, 15 Apr 2005 14:53:49 +0200 From: Reinhard Poetz User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [CForms] conditional "required" attribute needed or a "better" solution References: <329A68716B57D54E8D39FD3F8A4A84DF01AAF52E@um-mail0136.unimaas.nl> In-Reply-To: <329A68716B57D54E8D39FD3F8A4A84DF01AAF52E@um-mail0136.unimaas.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Linden H van der (MI) wrote: > Guys, > > can someone with in-depth knowledge of the CForms widgets help me out > here? I want to build a form that can be used to enter an HL7v3 > TelecomAddress[1]. The final XML result looks like this: > > > > or > > > > I've managed to build the appropriate widget structure for it, but I > have a problem: either 'nullFlavor' or 'value' should be used. If > 'nullFlavor' is empty, then 'value' is required and consists of two > required parts: 'scheme' (= tel:, selection list) and the actual number. > So I defined 'value' as an aggregateField. > > Is it possible to define the two parts of 'value' to be required, while > the aggregateField itself is not? > > Or is there a different solution to solve this problem? > > > [1] HL7 = a US standards organisation in the field of Medical > Informatics. HL7v3 is their 3rd version of standards, primarily defined > for standardized communication of medical and personal information > between (medical) systems. What about a custom validator? -- Reinhard P�tz Independent Consultant, Trainer & (IT)-Coach {Software Engineering, Open Source, Web Applications, Apache Cocoon} web(log): http://www.poetz.cc --------------------------------------------------------------------