There is still one aspect to handle on this, the issue of co-located registry.

At present systinet only has an HTTP transport which means that the ESB cannot be located within the same server as the registry.  Tom is investigating solutions.

Link: Added: This issue related JBESB-2649

Attachment: Added: stacktrace.log

Len asked me to comment on this one - here's where I believe we are on this one.       We created a mock servlet implementation of a Systinet transport (JBESB-2649).     We would like to create a cleaner transport - one that implements Systinet's interfaces (JBESB-2783) for a future release.

The mock servlet implementation is in product/tools/systinet - I'm unsure of whether this is being built as part of SOA-P or whether it should be built as part of SOA-P, or whether the plan is to provide this JAR upon request.

Don't know about the stack trace - would need a lot more details like what transport is being used, etc.

I can reproduce what Jiri is seeing as well -  the error seems to be tied to their web framework.        I'm not sure if HP has qualified SOA Registry Foundation on jboss 5.X.

Also, can we move the stacktrace to a new issue??

Link: Added: This issue related SOA-1919

The stack trace issue is tracked here:  SOA-1190

See SOA-1919 for related issue.