Yes, you can. You just need to remove the jbossweb-jetty.sar or jbossweb-tomcat.sar depending on your distribution from the deploy directory of the instance you are runing. e.g. if you are running the default instance, it would be located in server/default/deploy of your distribution. You'll probably want to remove the http-invoker.sar and also the jmx-console.war as they will be of little use without the servlet engine in place.
However, the integrated service is much faster for web applications that make use of the EJB layer. This is because the communication between the servlets/JSPs and the EJBs or other JBoss components do not have to occur over the wire so to speak as the communication is contained in the same JVM. So consider this when making your decision to have a distributed install.
Once those directories are removed and JBoss is started JBoss reports errors presumably looking for the jetty/tomcat service just removed. Are these errors anything to worry about? Can one get rid of these errors.
I wish that a standalone jboss download was available for those of us who don't care whether we run in the same JVM as servlet container. Some of us deploy jboss on separate machine from web container. Everytime I download jboss I have to go through this problem. Even if I did want to run in same JVM I would like to select which version of whatever servlet container that I want to run.
JBoss, please package a standalone version (you can include instructions on integrating servlet container in same JVM).
Since its a matter of deleting one directory from your deploy directory, seems hardly worth the effort.
Sorry to have to go over this again but I think my question above got missed. Once teh Jetty folder is removed and JBoss is started it spits out errors. Other components are obviously looking for Jetty. Are theses errors anything to worry about? Can one get rid of these errors? Thanks.
Probably the JMX console is complaining. Remove it, too... (jmx-console.war).
Instead of removing the embedded web service I would prefer to configure it with different ports, because the jmx-console is worth beeing deployed and running ;-)