Not many people realize that jboss is sufficiently light weight that it can be used as a container for client apps. As your client evolves it may have needs for a nameing service (JNDI), management (JMX), plugable service architecture, messageing (JMS) etc ...
A minimal jboss installation has indeed a tiny footprint. You could experiment with the minimal configuration and add the JBossWS service. It maybe the the case that JBossWS client is not sufficiently decoupled from JBossWS server (which requires a servlet container), then we need to fix that. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3858481#3858481 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3858481 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
