cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 35800] New: - Want <ft:union case-path="...">
Date Tue, 19 Jul 2005 21:44:22 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35800>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35800

           Summary: Want <ft:union case-path="...">
           Product: Cocoon 2
           Version: 2.1.6
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: CocoonForms
        AssignedTo: dev@cocoon.apache.org
        ReportedBy: mlundquist2@comcast.net


Use case: the union (or its containing widget) is bound to an object of a polymorphic type.
 The form 
lets users edit some properties of the object, but not change its concrete type.

Currently, to support this use case I have to include the discriminator widget in the form
template with 
<fi:styling type="hidden">.  It seems screwy to have to have this go clear out to the
browser.  For a 
read-only discriminator, we should just be able to say

     <union case-path="type" ...>

in lieu of a discriminator widget that must be declared in the definition, binding and template,
and then 
be rendered as an <input type="hidden">.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Mime
View raw message