Sculptor 2.0.0: Why are collections of enums not supported in non-persistent domain objects?

8 views
Skip to first unread message

Torsten Juergeleit

unread,
Oct 6, 2011, 11:41:44 AM10/6/11
to fornax-...@googlegroups.com
We're using Sculptor without JPA ("jpa.provider=none").

Now we would like to generate (non-persistent) domain objects with collections of enums, e.g.

        enum Foo {
            FOO
        }

        ValueObject Bar {
            not persistent
            - List<@Foo> foos
        }

But this is prohibited by a constraint check.

This validation complain can be worked around by replacing the model reference by a plain-vanilla Java type reference, e.g.

        ValueObject Bar {
            List<com.acme.Foo> foos
        }


Now we're wondering why this constraint check is applied to non-persistent domain objects as well.

/Torsten

Patrik Nordwall

unread,
Oct 9, 2011, 10:40:17 AM10/9/11
to fornax-...@googlegroups.com
Good suggestion. Fixed CSC-662
Will be available next time I feel the need to deploy new eclipse plugin.
/Patrik
Reply all
Reply to author
Forward
0 new messages