The whole of the ESB configuration will be changing in the 5.0 architecture, independently of the SOA modeler. The modeler needs to remain ESB/SOI agnostic, but the general concept of services and links (seen in SCA as well) obviously remains. We'll need to figure out how to push the abstract graphical representations of such things down into specific deployment requirements.
Are you interested in getting involved with the modeler :-)?
BTW, when you're talking about the service modeler are you referring to Thomas Erl's donation? I assumed so here, but ...
I would definitely like to be involved in design discussions, as it could be very relevant to the conversation based ESB action work. Whether I will have time to help with implementation is unknown at this point - but would be interested.
I was not specifically referring to Thomas Erl's modeler - but just expressing a requirement to support the conversation work.
OK, so I think we should discuss a general architecture before diving into specifics such as ESB actions. Does that make sense to you?
That sounds like a good idea.
Are there any requirements/design docs, other than Thomas Erl's doc, to outline the requirements from the tool(s)?
There are some general requirements that we've been discussing internally for a while. I'll try to pull them together and post them here.