Johan, when the J2EE client looks up the JAXRPC service from JNDI, it provides the properties for the JNDI initial context. Like this
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory | java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces | java.naming.provider.url=jnp://localhost:1099 | The java.naming.provider.url points to the JNDI tree where you deployed your WS4EE client too. So yes, you can have a remote client on a minimal jboss instance with its own JNDI tree. Deploying both WS server/client on the same jboss instance simplifies matters, but may not apply to your overall application design. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3858634#3858634 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3858634 ------------------------------------------------------- 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
