"scott.stark@jboss.org" wrote:
This dicussion of needing a local jboss instance is completely false. You need the jboss jars only.
env.setProperty(javax.naming.Context.PROVIDER_URL, "jnp://myservername:1099");
"scott.stark@jboss.org" wrote:
This dicussion of needing a local jboss instance is completely false. You need the jboss jars only.
"jason.greene@jboss.com" wrote:
Currently the J2EE application client jar has to be deployed on the same system as the standalone client app. This means in the current release, you need to have a minijboss running on the client system. We are going to add support for remote client access in 4.0.4.
http://jira.jboss.org/jira/browse/JBWS-438
-Jason
mka,
I think our problem paths may have met again. I'm now experiencing a 'javax.naming.NamingException: Cannot load wsdl file' exception, which you describe experiencing here:
http://www.junlu.com/msg/196710.html
Did you resolve this as part of your JAR re-shuffling?
I think this is no different to any other serialVersionUID issue. The server that binds the QName into JNDI is using a different version than your client. From the class loaders you can find out from which jar QName is comming from.
This is not really web service related.