Janine,

You can define your own events in both HotLink and HotEvent, with or without dots.

The actual issue, as you mentioned in a separate post, is not with the dots in the event name, but with the "com.audium" prefix. While you can throw any event in HotLink, including "com.audium.NAME" ones, you cannot catch "com.audium.NAME" in your custom HotEvent.

The "com.audium" class is a reserved class and cannot be caught by custom HotEvents. Note that Audium uses those events to deal with server related activities and overwriting those events might cause Call Services to not be stable and behave incorrect.

With that said, I have created an issue in our internal bug tracking system to add a check for "com.audium" name in a custom HotEvent.

Hence, while you custom event "com.myname.myevent" will work fine in HotEvent, the event "com.audium.myevent" you previously defined ill not work.

Hope this helps,
Michael