[XSTR-269] Attribute capability to XStream

Details

Type: New Feature
Status: Closed
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 1.2
Component/s: None
Labels:
None

Description

This is pretty important for RESTful SoA and interop with .Net.

Paired, TDD with Ian Cartwright.

Options
- Sort By Name
- Sort By Date
- Ascending
- Descending
- Download All

Attachments

AttributeAliasingMapper.java

09/Feb/06 10:05 AM

1 kB

Paul Hammant
AttributeAliasTest.java

09/Feb/06 10:06 AM

2 kB

Paul Hammant
AttributeConverter.java

09/Feb/06 10:04 AM

1 kB

Paul Hammant
attributes.patch

09/Feb/06 10:03 AM

11 kB

Paul Hammant

Issue Links

is related to

XSTR-124 Advanced Aliases

relates to

XSTR-260 PropertiesConverter does not handle tabs and newlines

XSTR-62 Make an option to create primitive and String properties as attributes.

XSTR-613 CLONE -Make an option to create primitive and String properties as attributes.

Activity

Hide

Permalink

Mauro Talevi added a comment - 21/Feb/06 3:20 AM

Attribute support has been added - but not using the AttributeConverter interface, which would not have allowed
the reuse of all the converters already developed.

Rather, a new interface SingleValueConverter has been extracted (which most converters already implemented)
and promoted to top-level user API. Implementations of this interface can be serialised to a single String value
and hence be potentially used as attribute.

In addition, attribute aliases need to be registered just like other aliases,

xstream.aliasAttribute("date", Date.class)

where date is the attribute name.

Still todo is the ability to choose the field name.

xstream.aliasAttribute("date", "m_date", Date.class)

Show

Mauro Talevi added a comment - 21/Feb/06 3:20 AM Attribute support has been added - but not using the AttributeConverter interface, which would not have allowed the reuse of all the converters already developed. Rather, a new interface SingleValueConverter has been extracted (which most converters already implemented) and promoted to top-level user API. Implementations of this interface can be serialised to a single String value and hence be potentially used as attribute. In addition, attribute aliases need to be registered just like other aliases, xstream.aliasAttribute("date", Date.class) where date is the attribute name. Still todo is the ability to choose the field name. xstream.aliasAttribute("date", "m_date", Date.class)

Hide

Permalink

Jörg Schaible added a comment - 24/Feb/06 2:42 PM

Paul, please comment, if this is, what you needed.

Show

Jörg Schaible added a comment - 24/Feb/06 2:42 PM Paul, please comment, if this is, what you needed.

People

Assignee:

Unassigned

Reporter:

Paul Hammant

Votes:

0 Vote for this issue

Watchers:

0 Start watching this issue

Dates

Created:

09/Feb/06 10:03 AM

Updated:

23/Mar/10 1:00 PM

Resolved:

24/Feb/06 2:42 PM