History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: IDEABKL-5300
Type: Usability Problem Usability Problem
Status: Open Open
Priority: Normal Normal
Assignee: Unassigned
Reporter: t800t8
Votes: 0
Watchers: 0
Available Workflow Actions

Mark as Stalled
Operations

If you were logged in you would be able to see more operations.
IDEA: Backlog

Updating "Generate Externalization" to use XmlSerializer

Created: 08 Oct 07 09:36   Updated: 08 Oct 07 14:40
Component/s: Plugin Support. DevKit
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown

Build: 7,330


 All   Comments   Work Log   Change History      Sort Order:
Dmitry Jemerov - 08 Oct 07 13:51
It's unclear what exactly should be generated. PersistentStateComponent gives you more flexibility regarding how your settings are structured, and at the same time reduces the need for boilerplate code.

t800t8 - 08 Oct 07 14:38
In prior versions of IDEA before Selena, when I generate externalization for a component (press Alt + Insert, then select "Generate Externalization"), IDEA will generate code which uses JDOMExternalizable and DefaultJDOMExternalizer. But they're deprecated in Selena so I ask you to update the "Generate Externalization" action to use PersistentStateComponent and/or XmlSerializer

Dmitry Jemerov - 08 Oct 07 14:40
I understand. For JDOMExternalizable, there was a single default implementation for the serialization code, which could be generated automatically. There is no such default implementation for PersistentStateComponent.