Status hbm references non existent status column from SysLog

[alcarraz]

status column does not exist in SysLog entity. So accessing the events property creates an invalid SQL sentence. Maybe it should point to source?

jPOS-EE/modules/status/src/main/resources/org/jpos/ee/status/Status.hbm.xml

Lines 41 to 45 in 0756f3a

	<set name="events" lazy="true" cascade="all-delete-orphan"
	order-by="id asc">
	<key column="status"/>
	<one-to-many class="org.jpos.ee.SysLog" />
	</set>

[ar]

This is on purpose. Originally, SysLog would have a column associated with the Revision History, and Status, and, and, and, but that doesn't scale well, so we've removed that relationship. Status could have an info-only SysLog id, suitable for most situations (without database integrity, though).

[alcarraz]

Sorry I don't know if I follow, problem is this generates a runtime error when accessing the events properties since it tries to execute an invalid SQL (status column does not exists) my proposal is either remove that relationship from the hbm or modify it by source without data integrity

[alcarraz]

With the modification proposed in #221 it works ok, it will create a SysLog for each event with source being the same as the status id

[alcarraz]

the line that fails is StatusManager.java#L11 when max events is not 0