товарищи! кто-нибудь делал проекты в которых используется данная связка?
прошёл небольшой туториал http://www.ibm.com/developerworks/bpm/bpmjournal/1308_jackson/1308_jackson.html
там всё предельно просто, но когда пытаюсь прикрутить свои event rules ( ссылка раз , ссылка два ), ничего не работает, проект вообще не компилируется
проект event rules рабочий, при тестировании ошибок не выдавал, логика работает правильно
может у кого-нибудь есть пошаговая инструкция?
просьба, ссылки на инфоцентры не давать, сам их уже несколько дней мониторю :-)

вот такую портянку выдаёт
Begin running task [Deploying [Rsv1CheckFlow] to integration server [default]]

BIP2087E: Broker 'IB9NODE' was unable to process the internal configuration message.

The entire internal configuration message failed to be processed successfully.

Use the messages following this message to determine the reasons for the failure. If the problem cannot be resolved after reviewing these messages, contact your IBM Support center. Enabling service trace may help determine the cause of the failure.

BIP4041E: Execution group 'default' received an administration request that encountered an exception.

While attempting to process an administration request, an exception was encountered. No updates have been made to the configuration of the execution group.

Review related error messages to determine why the administration request failed.

BIP2241E: A Loadable Implementation Library (.lil, .jar, or .par) is not found for message flow node type 'DSEREventOutputNode' in message flow 'Rsv1Shema.Rsv1Flow'.

The broker received an instruction to create a message flow node of type 'DSEREventOutputNode', in message flow 'Rsv1Shema.Rsv1Flow'. The broker cannot create nodes of this type because an implementation library for this node type does not exist in the LIL path.

Ensure that the LIL path is correct, and that it contains all the required node implementation libraries, including those supplied by IBM. The node name is case sensitive, therefore check that the toolkit and runtime names match. If the broker is trying to create a node type that ends in 'NodeNode', ensure that when the node was registered with the toolkit the name registered did not end in 'Node'.
Also ensure that you have saved the message flow, and any nested message flows. Redeploy the new configuration to the broker, specifying a complete configuration. If the LIL file is correct, check that the message node type is correct.

The task was unsuccessful: The deployment was unsuccessful. Check error messages above for explanation.