No "clean" way of doing this. Are you working with a released version of Teaming (eg. Teaming 2.1), or would that meet your requirement if I made this easier in an upcoming release, that is, Teaming 3.0?

I am working with 2.1 now but a 3.0 solution would be acceptable.

Thanks

I just noticed the module listener example and wondered if that might be a better way to go.  Any thoughts and what are the advantages/disadvantages of the different approaches?

Gary

The module listener can certainly help you achieve your goal without going up to Teaming 3.0. However, I don't think you can do what you intend to do just by using module listener alone. You would still need to extend the controller.

The module listener provides a general mechanism where any entry point (i.e., public method) defined in the module interface (eg. addEntry, modifyEntry, etc.) can be intercepted by a plugin module. In your specific use case, you could write a module listener around the addEntry method which would then store the ID of the newly created entry in a thread-local variable. Then, when the execution control backs out to your controller level, you can grab the stored ID value and use it in whatever way you want. The reason why you still need to extend the controller is because the module listener itself has no access to the HTTP response object. The sample program in the source repository should give you the details.

Regards,

/Jong

I re-structured AddEntryController to contain the following protected method:

protected FolderEntry addReply(ActionRequest request, ActionResponse response,
Long folderId, Long parentId, String definitionId,
InputDataAccessor inputData, Map fileItems, Map options)

You can override this method in your subclass, and grab the ID from the resulting FolderEntry, and put it in the response object.

This change is available from the Teaming 3.0 trunk.

Sounds good. Thanks