tracker issue : CF-3149329

Duplicate ID:	CF-3138032

Problem Description:

Re-Submitting as the previous was closed as duplicate to other bugs, when in fact there was nothing that makes them related. If you don't understand the issue, you are welcome to send me a private email, and I will demonstrate it, or give you a better understanding of the issue. However I missed the notification of needing more information, and I can tell you it is not related to the tickets you asked if it was. The original ticket that was closed was marked user error, this is not user error in any way shape or form.

Again, please be aware that this is an issue and it is highly sort after when dealing with companies that are ISO9001 certified. Because they have a requirement that auditing take place on all and any changes to the database, the global events is the best place to try and do this. Unfortunetly, one is not able to create an entity and save it as the example demonstrates, the error message returned is that the session has closed.

Again this is a requirement for anyone who needs to do work with ISO9001 companies, without this working it is impossible to provide an easy way to write this. Sure one can manually make changes to each an every entity, but the problem there is that it is too easy to make mistakes and miss changes. The global events provide a way for it to never be missed.


I wanted to try this again and get you to understand how important this error is.

Currently I am trying to find a way to write audit logs for my entities, and have been trying to find a way for this using entities for now 4 years.

I will give you the basic code, but rest assured that this is also being checked to see if that entity has called the event if so then don't run the code. But for now I just want to give you a basic concept of the problem.

So lets say we have an event handler.

public void function postInsert(any entity) {
var domain = new domains.audit(auditDateTime: now(), template: #getMetaData( entity ).fullname#, detail: 'This is a test of strength', ipAddress: cgi.http_host);
entitySave(domain);
}

Now remember that this is an example, the actual code will check to see if the even being run is the audit so we don't end up in some serious loop.

As it stands now there is no way to be able to do this, and it will throw a session closed error. All the standard Java techniques don't seem to work because there is no way to open a new session for that entity to be created and saved.

This is also a major issue that as annoyed me for 4 years and I am at a loss, a big loss as how to implement something like this. When you code for anyone who has ISO certifications this is a must that audit logs take place on data that has changed.

So I am in need of a solution here, but I am not sure the client will even pay for an upgrade to ColdFusion 10. So I may just have to go and right this in Grails where I am able to achieve this with no issues.

Steps to Reproduce:

Actual Result:

Expected Result:

Any Workarounds:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3149329

External Customer Info:
External Company:  
External Customer Name: ascott67
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

Comments: