Let me clarify.
What I'm trying to do is have a server with my EJB's/Seam Components deployed in a standalone jar, and then be able to access these EJB's/Seam Components from a war(s) deployed on other server(s).
Basically, the idea of having my Seam components as a web service that anyone could develop a web application for.
It is possible, but you need to deploy the Seam components that are to be called remotely in an EAR with a WAR and a full Seam config, even if you don't have any JSF pages on that box.
Woot! Thanks Gavin, I'll try that out right away.
I have been asked to do the same thing. Please let me know how you make out in this post .