Ok, so I want to make sure I understand all this JBI stuff. Can someone confirm that this explanation is correct?
A Service Engine is a component that gets installed into the ESB. A Service Engine can be deployed by itself without a Service Unit and Service Assembly. When a Service Engine is installed a client can take advantage of it's functionality. A Service Unit is a package that contains resources that a Service Engine might need to operate, such as XML files, XSL files, or something else. A Service Assembly packages whatever Service Units that are needed together into a bundle and indicates what Service Component it should be deployed to. Now provided these are correct, I'm not sure I understand why the resources wouldn't be bundled with the Service Unit. I'm also not sure why if the Service Unit bundles only resources, why the Loan example contains only Service Units and those Service Units contain Web Services which I thought would have been placed in a Service Engine? Because of this, I can't find an example of a Service Engine and client so I can figure out how to use the example Service Engine built by Maven2. I'm also a little confused why when I deploy the build Service Engine that Maven2 created I don't see any of the end points or anything else show up in jconsole. I only see that the component is there. The jbi.xml in the Service Engine built by Maven2 doesn't seem to mention any of these endpoints or other classes. The way the examples are created, lead me to believe that Service Engines are useless because I can just put my business logic into a Service Unit using a Web Service. Can anyone clear this up for me? I want to make sure I'm developing my services correctly. The JBI spec seems to be contradictory to how the Service Mix examples are packaged. Thanks.
