Diagramm title not saved

[GoogleCodeExporter]

The name field of a BPMN-diagram should be saved.

Possible would be a readonly-attribute that has the name-value given during
diagram creation.

Original issue reported on code.google.com by lutz.ger...@googlemail.com on 30 Apr 2008 at 8:43

[GoogleCodeExporter]

There is a general issue with saving properties. It seems that some are saved 
and
some are not. For example a task's name is stored, but if you enter something in
InputSets, it is not saved. 

First tests have shown that the problem has to be located in the DataManager. 
If you
call the serialize method for a shape, all properties are in the result.

Original comment by NicoPete...@gmail.com on 30 Apr 2008 at 4:20

• Added labels: Priority-Critical
• Removed labels: Priority-High

[GoogleCodeExporter]

Further tests show that saving of input sets works fine. Loading does not work.
However, this is not due to an error in the code, but in the stencil set:

When saving, all data is stored in eRDF. eRDF is case insensitive on it's 
QNames, as
far as I am aware of it. Property name storage, by convention, then happens in 
lower
case. When loading, the property "inputSets" is asked for. That one does not 
exist,
and a null value is gracefully loaded instead. There should be at least a 
warning in
such a case, I'll have a look on that.

Make sure all property ids in the stencil sets are lower-case, or write an 
issue to
make both load and save case-insensitive, latter, however, would have a negative
impact on third party code that works on the RDF generated from eRDF.

Does that also solve the problem with the name field of a BPMN-diagram?

Original comment by martin.c...@googlemail.com on 30 Apr 2008 at 9:09

[GoogleCodeExporter]

With the existing Java code to parse and pretty-print stencilsets, I could 
implement
a build-time validation of stencilsets. This way, such properties could be 
found in
the build process. Also, errors in the JSON structure could be found this way,
accurate to the line where a bracket is missing.

Original comment by martin.c...@googlemail.com on 2 May 2008 at 12:31

[GoogleCodeExporter]

the diagram's properties are currently not stored in the database. Some time 
ago,
those properties were part of the page's head and were also stored in the old 
backend.

A solution would be to store these properties the same way as the properties 
for the
other stencils.

Original comment by NicoPete...@gmail.com on 6 May 2008 at 2:06

[GoogleCodeExporter]

r527

Original comment by NicoPete...@gmail.com on 19 Jun 2008 at 8:01

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by NicoPete...@gmail.com on 12 Jul 2008 at 12:55

• Changed state: Verified