Issues

Ikasan Dashboard Console
IKASAN-700
Add an ability to wiretap Payload meta-data information to Wiretap Service
IKASAN-699
Change build and uber pom's to include sources
IKASAN-698
Add default monitor and email notifier for flow status reporting at runtime
IKASAN-697
Configuration instances are not being re-initialised on deletion of a configuration at runtime
IKASAN-696
Console trying to render a wiretap RelatedIdentifier attribute which does not exist
IKASAN-695
Failure of a critical managedResource currently fails the deployment when flows are set to AUTOMATIC startup
IKASAN-694
Component support for Mongo
IKASAN-693
Change minimum JDK/JRE to 1.7
IKASAN-692
Provide backward compatibility library for using i9 against i8 messaging
IKASAN-691
Allow the broker implementation to support FlowEvent or flowEvent.payload at runtime
IKASAN-690
Allow test harness event capture to be disabled at the Subject listener level
IKASAN-689
Allow simple addition/removal of flowEventListener registered jobs
IKASAN-688
Simple java standalone appln to programmtically create the required persistence
IKASAN-687
Add utility class for programmatic setup of console permissions
IKASAN-686
Remove spring message conversion dependencies from jms producer
IKASAN-685
Allow JMS Consumer to access destinations via remote JNDI configurations
IKASAN-684
Move EndpointListener interface out of the consumer implementation and into spec
IKASAN-683
Deep-cloning of events by the replicationFactory can cause JVM failure for very complex events
IKASAN-682
Improve failure reporting on test harness fail reporting
IKASAN-681
JMS Consumer should close() connection rather than just stop() connection on shutdown
IKASAN-680
Add support for some off-the-shelf data converters
IKASAN-679
Disable automated event search result when getting to the Events Search in User Console
IKASAN-678
Initial development of a GUI for building modules,. flows, components, etc
IKASAN-677
User guide for Ikasan User Console
IKASAN-676
1-25 of 693