[jboss-user] [jBPM] - Re: Invalid JPA definition for ProcessInstanceLog v5.4.0, leads to Hibernate exception

Maciej Swiderski do-not-reply at jboss.com
Thu Feb 7 09:55:37 EST 2013


Maciej Swiderski [https://community.jboss.org/people/swiderski.maciej] created the discussion

"Re: Invalid JPA definition for ProcessInstanceLog v5.4.0, leads to Hibernate exception"

To view the discussion, visit: https://community.jboss.org/message/796541#796541

--------------------------------------------------------------
in general, since they are primitives they will never be null as they get the default value for it's type. Nevertheless the idea behind it was to support null so please file a jira issue for it to make them as objects instead of primitives. I think the case where you would encounter it is when you have existing db will data and you upgrade that table and these values are null then by default. In that case it fails, is that what you ran into?

HTH
--------------------------------------------------------------

Reply to this message by going to Community
[https://community.jboss.org/message/796541#796541]

Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2034]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20130207/972455dd/attachment.html 


More information about the jboss-user mailing list