Okay, a small misunderstanding here ;-) I know what's a DSL, my problem was how to apply it here. But if I read it right between the lines, you mean to have a XML-based "DSL" to configure the scenarios. I wouldn't have called it DSL in this approach, but I think you can. But the name DSL maybe strengthen the idea to make the scenario description a bit more general, no tied to jPDL or even jBPM, but "only" for simulation scenarios of business processes. Basically, I like this idea, but I think I prefer a two way approach then: Embedding in the process definition (namespaces or not) for fast and easy use, and an own scenario description XML file (some kind of DSL if you wish) for more complex scenarios (information there override the "inline" configuration). I think, this would be a good solution, easy but also powerful. One additonal thought: The external scenario description is a good idea for an addtional reason: When porting simulation to jbpm 4 with different languages, it is maybe not so easy to embedd stuff in BPEL or XPDL process descriptions like it is now in jPDL. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092255#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...