Why must the workflow ENGINE generate an ear? I can imagine some designer delivering/creating an ear file but not the engine.
jBPM does not generate or specifically use an ear file. It uses a processdefinition which is parsed and put in a database. You can bundle all jBPM stuff in an ear and put a custom processdefinitionloader in there that deploy time reads that file and puts it in the DB. Bundeling it this way is something you have to do yourself and for the deployer, search the forum and/or wiki. there is some info on this subject.
I need an example of an application carried out with JBPM under Jboss IDE, so that I can understand how to work with this workflow, because the documentation on JBPM is rare and work with this workflow is a little delicate
thank you for the assistance you can send the project to me at my address email@example.com
If you read the documentation of the GPD, you will see exactely the things you need to know. The documentation on jBPM is (imo) not 'rare' but it is a little developer oriented and not fully meant to be just used by business users.