I'm fine without the utils class, however, I'll propose that we need some
static methods for default property access to write a tree walker consistent
with the serializer default property setter. The issue is that it is quite
possible, some day in the future :-) that the sequence list in a
My thinking was that if a client defined a list or a map using standard java
collection classes. If the recommendation is to always use pivot collection
classes in pivot code and sequence supports both map and list, that sounds
fine.
-Original Message-
From: Greg Brown (JIRA)
[
https://issues.apache.org/jira/browse/PIVOT-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12877799#action_12877799
]
Appddevvv commented on PIVOT-513:
-
I actually do not use it for my spring-based extension to
[
https://issues.apache.org/jira/browse/PIVOT-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12877805#action_12877805
]
Greg Brown commented on PIVOT-500:
--
I'd prefer to wait until update 21 is available before
This is what I was getting at when I was asking you about why you wanted this
feature. If I knew that your Spring integration did not actually depend on
this, I may not have committed the change.
In Pivot, we generally try to avoid creating features based on hypothetical use
cases. We like
Meant list and set not map.
-Original Message-
From: aappddeevv [mailto:aappdde...@verizon.net]
Sent: Friday, June 11, 2010 7:58 AM
To: dev@pivot.apache.org
Subject: RE: [jira] Updated: (PIVOT-514) create an annotation to specify the
default child property of a component used by the
