Closed GoogleCodeExporter closed 9 years ago
Attaching feed file where value of ows_metainfo field inline <meta
name="ows_MetaInfo" content="1;#"/> is a result of bad parsing
Original comment by shashank...@gmail.com
on 4 Mar 2009 at 12:28
Attachments:
please clarify your comment.
Thanks,
Val
Original comment by valorek...@gmail.com
on 4 Mar 2009 at 6:34
The connector discovers the metadata but fails while parsing the content. This
happens only for the content retrieved as under ows_metainfo field and not for
other
attributes. By The Way, for every custom metadata, SharePoint web service also
sends
a corresponding metadata attribute apart from the one it sends as in
ows_metainfo.
Any document specific custom metadata is also returned as part of ows_metainfo
field.
The format used to distinguish between various custom metadata included in
ows_metainfo field is not straightforward and hence connector fails while
parsing the
content of ows_metainfo
Original comment by rakesh.s...@gmail.com
on 4 Mar 2009 at 6:57
to rakesh.shete:
-- By The Way, for every custom metadata, SharePoint web service also sends
-- a corresponding metadata attribute apart from the one it sends as in
ows_metainfo.
This is not precisely the case. The Lists WS returns custom fields requested in
the
viewFields argument, or if not specified, fields belonging to a given view. The
Connector code does not specify viewFields nor the viewName when calling the
Lists WS
thus making the WS default to the fields available in the default view (see
here:
http://msdn.microsoft.com/en-us/library/lists.lists.getlistitems.aspx) If the
default
view is configured not to include a certain custom field X, it will not be
returned
by the WS as part of the ows_ prefixed fields and will only be returned as a
part of
the ows_MetaInfo statebag field.
-- The format used to distinguish between various custom metadata included in
-- ows_metainfo field is not straightforward and hence connector fails while
parsing
-- the content of ows_metainfo
The format of the ows_metainfo field is _always_ new-line delimited, as
returned by
SharePoint. I've confirmed this with packet capture analysis by examining data
returned by Lists WS. The inconsistency happens when data is parsed by Axis
before
the Connector code receives it. Please see the specifics in the original post
for the
proposed regex-based solution that allows you to parse the data regardless of
the bug.
Val
Original comment by valorek...@gmail.com
on 7 Mar 2009 at 3:47
Connector sends all the metadata discovered under property bag ows_MetaInfo as
separate distinguished attributes. As a result of this, users will no more see
any
attribute name with the name ows_MetaInfo.
Apart from this, connector also does some little changes in the original
metadata
names and their values as they are returned by the Web Service:
1. Leading ows_ is removed from the attribute names
2. Leading vti_ is removed from the attribute names
3. _x0020_ is replaced by <space> from the attribute names
4. Leading <ITEM_ID>;# is removed from the attribute values
The purpose of the above changes are to make the metadata names and values more
meaningful to end users.
Original comment by th.nitendra
on 24 Jun 2009 at 12:06
Verified in 2.0.0 and works fine.
Original comment by shashank...@gmail.com
on 25 Jun 2009 at 12:10
Original issue reported on code.google.com by
valorek...@gmail.com
on 2 Mar 2009 at 9:29