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.
View the original
[EMAIL PROTECTED] wrote : This dicussion of needing a local jboss instance is
completely false. You need the jboss jars only.
Thank you, Mr. Stark, for your reply. Could you clear one thing up for me then,
please:
If I'm talking to a remote JBoss, the way my app knows where the JBoss is to
[EMAIL PROTECTED] wrote : This dicussion of needing a local jboss instance is
completely false. You need the jboss jars only.
If this is really the case, why's one of your colleges saying this?:
[EMAIL PROTECTED] wrote : Currently the J2EE application client jar has to be
deployed on the same
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?
View the original post
This dicussion of needing a local jboss instance is completely false. You need
the jboss jars only.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3903543#3903543
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3903543
mka, I cannot even begin to thank you for what is probably the first (or at
least most) straight answer I've had in these two pages of thread.
Do you have an idea of what point the remote calls fail, and must be done
against a local JBoss (talking to the remote JBoss)? Is it that a remote JBoss
Here's another question for anyone:
if I'm calling the local JNDI on the local JBoss, how does the local JBoss know
where to look for the remote JBoss with the actual EJBs and services running?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3902941#3902941
Hi Craig,
I'm experiencing the same problem that you are, and have been for a while now.
Here is what the examples on the wiki neglect to mention:
A stand-alone client cannot execute the code posted there without having JBOSS
running locally (i.e. on the same machine). Once you assume this
No, it just means that you should use the same jboss version for the container
that you deploy your application-client and your client code.
e.g. you cannot deploy your application-client to 4.0.3 if the apllication that
does the jndi lookup runs on 4.0.2 jars
View the original post :
OK, I am using 4.0.3 JARs on the client side with 4.0.3 JBoss. Good.
However, I'm still no further forward with this. I don't even understand this
error message (posted on 18th Oct), let alone how to resolve it. There doesn't
seem to be anything in the forums or wikis mentioning this exception.
The serialverion of the QName class makes no sense. The value bundled in jdk5
is:
[EMAIL PROTECTED] bin]$ serialver javax.xml.namespace.QName
javax.xml.namespace.QName:static final long serialVersionUID =
4418622981026545151L;
The -6756054858541526837 matches no version I know of. Values
The client in missing the classes starting with the
org.jboss.webservice.client.ServiceObjectFactory which is not in the
jbossall-client.jar for some reason. Its in the jboss-ws4ee-client.jar:
| [EMAIL PROTECTED] client]$ jar -tf jbossall-client.jar | grep ServiceObjectF
| actory
|
Great. So now I have 'jbossall-client.jar' and 'jboss-ws4ee-client.jar' on my
classpath along with all the other JARs I've listed in earlier post.
I now get a different exception when I try to lookup the JNDI reference:
javax.naming.NamingException: Cannot unmarshall service ref meta data,
[EMAIL PROTECTED] wrote : Display the Reference.getFactoryClassName() to find
out what object factory is the starting point for the missing classes.
The object factory is 'org.jboss.webservice.client.ServiceObjectFactory'. I'm
sorry, but how does this help me determine what libraries are
craigpugsley wrote :
| ...the difference being the 'service-interface' elements are
'javax.xml.rpc.Service' for the 'OrganizationServiceEJB' and
'com.underworld.crimeportal.OrganizationEndpointService' for the
'OrganizationServiceJSE' - whereas mine are 'javax.xml.rpc.Service' for both.
|
Display the Reference.getFactoryClassName() to find out what object factory is
the starting point for the missing classes.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3901330#3901330
Reply to the post :
[EMAIL PROTECTED] wrote : ... The jndi.properties/env may need to contain a
java.naming.factory.url.pkgs=org.jboss.naming.client:org.jboss.naming:org.jnp.interfaces
setting.
After finding and changing the 'jndi.properties' file in
JBoss/server/default/conf/, I find that now, certain jndi names
You are either missing the correct object factory setting in jndi.properties,
or missing classes needed by the jndi object factory. The jndi.properties/env
may need to contain a
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces setting.
View the original post :
18 matches
Mail list logo
