ArchgenXML with ArgoUML - text fields not working, and an ATBackRef question

akameswaran akameswaran at gmail.com
Thu Jul 12 20:54:45 UTC 2007


I will have to try the accessor tag.  Thanks again for the follow-up.

Still with the flakiness I see in ArgoUML - I'm tempted to stick with
the working code, via subclassing document.  The ramifications of this
are acceptable, and it works now.  But for the next version it would
be nice to know this can work.

On Jul 12, 12:05 pm, chris <c... at protaform.com> wrote:
> On Thu, 2007-07-12 at 14:29 +0000, akameswaran wrote:
> > 3)  My text field was called Description - that was the problem.
> > Other names work.  I was able to get the desired behavior by
> > explicitly subclassing ATDocument (bringing in the description field
> > from the schema)
>
> Ah-ha!  Yep - I did have this problem, and it was a Description field.
> And I know what the solution is.
>
> A standard Plone Description field does not use the usual
> 'getDescription()' function as an accessor, instead it (and the title
> field) use description() and title() respectively.  To fix your problem
> in the UML, set an 'accessor' tagged value on your Description field,
> with a value of 'description' (you can do this for title too).
>
> You don't need to code the accessor function - it'll Just Work (tm).
>
> No need to go subclassing stuff, and you don't need to rely on secondary
> products being installed.
>
> Hope this helps,
>
> Chris.
>
> > Thanks,
> > AK
>
> > _______________________________________________
> > Product-Developers mailing list
> > Product-Develop... at lists.plone.org
> >http://lists.plone.org/mailman/listinfo/product-developers
>
> _______________________________________________
> Product-Developers mailing list
> Product-Develop... at lists.plone.orghttp://lists.plone.org/mailman/listinfo/product-developers





More information about the Product-Developers mailing list