[JBoss-user] [JBossWS] - Re: JNDI Lookup returns Reference - causes ClassCastExceptio
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 post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3904091#3904091 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3904091 --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: JNDI Lookup returns Reference - causes ClassCastExceptio
[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 talk to is via a property I set in the initial context? | env.setProperty(javax.naming.Context.PROVIDER_URL, jnp://myservername:1099); | I will persist with my JAR file vivisections, then. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3903762#3903762 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3903762 --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: JNDI Lookup returns Reference - causes ClassCastExceptio
[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 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 in this forum thread: http://www.jboss.com/index.html?module=bbop=viewtopict=70738 View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3903812#3903812 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3903812 --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: JNDI Lookup returns Reference - causes ClassCastExceptio
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 : http://www.jboss.com/index.html?module=bbop=viewtopicp=3903818#3903818 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3903818 --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: JNDI Lookup returns Reference - causes ClassCastExceptio
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 --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: JNDI Lookup returns Reference - causes ClassCastExceptio
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 just isn't able to provide web service artifacts to an app client running locally from a remote JNDI call? And that it can only provide these artifacts locally? You are very clear when you say: mka wrote : Hi Craig, | A stand-alone client cannot execute the code posted there without having JBOSS running locally (i.e. on the same machine). | And my thinking was thrown out when I mentioned previously: craigpugsley wrote : [coming] across an interesting thread: | | http://www.jboss.com/index.html?module=bbop=viewtopict=70738 | | ...where: | | [EMAIL PROTECTED] 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 | | | | Does this mean I'm banging my head against a brick wall here, as support for client/server separation of J2EE Application Clients in JBoss isn't going to be properly supported (i.e. with remote clients) until 4.0.4? | ...which I think sounds pretty unequivocal. I'm clearly asking there whether talking to a remote JBoss without a local JBoss is possible. To which the reply was: [EMAIL PROTECTED] wrote : | 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 | ..and I assumed at the time this meant that all I needed to do was make sure I had library version parity on both the local client and remote JBoss. Reading this last quote from Jason Greene back now, however (you should use the same jboss version for the container that you deploy your application-client), it looks like he's talking about the local JBoss I need to have running (the container). This is all very confusing for someone who is relatively new to J2EE development, and the fact that no one seems to want to say yes, you actually need a local JBoss running to talk to your remote JBoss in any of the wikis, or even explicitly on this thread, just adds to this confusion. So, can I ask where you are at with this now? Are you sorting your libraries into a sanitised JAR, then biting the bullet and deploying a local JBoss? We, too, deploy via JWS and this has been a very successful course when using WebSphere (the commercial app server we're porting to - see my previous comments to see why I'm even here), as WebSphere actually deploys an application client application container to the local client via JWS from the remote WebSphere first, then your application client is deployed in the normal JWS manner. I would assume this app client app container is equivalent to the 'minijboss' Jason Green talks about, and against which the JNDI calls are made. Once again, thanks very much for taking the time to recount your experiences. Your elucidation is much appreciated, and I'm sure this will help many countless others. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3902938#3902938 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3902938 --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: JNDI Lookup returns Reference - causes ClassCastExceptio
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 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3902941 --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: JNDI Lookup returns Reference - causes ClassCastExceptio
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 architecture to be ideal for your situation (definitely not ideal for me), go ahead and deploy the j2ee client jar just as the wiki suggests, but make sure your stand-alone client and jboss running the j2ee client jar are actually on the same computer. Your stand-alone client should then pull the WS artefacts off the local JNDI, and execute them locally. The work of connecting to your remote web service, running on a different computer with yet another instance of JBOSS, will be performed by the j2ee client jar on your local JBOSS instance. Sounds convoluted? I agree. Looks like an academic exercise? I agree. Not something you'd exactly present to a customer who wants to run your stand-alone client, right? To work around this I've spent sleepless nights trying all sorts of configurations to get a true stand-alone client without the need for a JBOSS install on a client machine. My stand-alone client is deployed via JWS, as a requirement. So obviously deploying JBOSS at each download of the client is out of the question. In this dark, obscure and lonely quest, I've experienced the classcastexception issues you've come across. The classcast exceptions are probably because you have jwsdp jars in your classpath, particularly the jaxrpc ones, as well as Jboss jars. The client runtime seems to get confused between sun and jboss based classes at so many different levels that it's easier to simply isolate the two types of jars. You might say lets cast the darn things, but trust me, if you intend to actually spend your developing your application, isolate the files one by one. Run your app with either JBOSS or Sun jars. There will be one or two sun classes that you cannot do without as your classloader complains, but pick them out of the jar and stick them in a new sanitized jar. I tried running just Sun based jars for my app, got some different type of problem, so now I'll try and run against just the JBOSS based jars, with a few selective Sun classes. I've read the responses that talk about the bane of using implementation specific solutions for the stand-alone client. Guess what folks, my customers do not really care whether or not the stand-alone client is J2EE compliant or not. The interoperability thing is cool, but if we have to include JBOSS on every single client computer to get the thing to work, how can this be a portable solution? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3902700#3902700 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3902700 --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: JNDI Lookup returns Reference - causes ClassCastExceptio
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 : http://www.jboss.com/index.html?module=bbop=viewtopicp=3902199#3902199 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3902199 --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: JNDI Lookup returns Reference - causes ClassCastExceptio
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 mention of serial version IDs, however, suggests to me something to do with differing versions of the serialisation/deserialisation classes? I'm confused and in need of someone to shine a torch over this. I think this is important information that, when we've resolved it, would be worth adding to your wiki pages to help other perilous travellers trying to implement client apps cross-appserver-platform. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3902225#3902225 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3902225 --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: JNDI Lookup returns Reference - causes ClassCastExceptio
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 you would see
when using jdk1.4.x with jboss are:
|/** @since 4.0.2, compatible with j2ee1.4 by default */
|final static long serialVersionUID;
|static
|{
| if (SerialVersion.version == SerialVersion.LEGACY)
| serialVersionUID = 8217399441836960859L;
| else
| serialVersionUID = -3852060120346905000L;
|}
|
You need to track down the source of the bogus -6756054858541526837 value.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3902273#3902273
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3902273
---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: JNDI Lookup returns Reference - causes ClassCastExceptio
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 | [EMAIL PROTECTED] client]$ for j in *.jar | do | echo $j | jar -tf $j | grep ServiceObjectFactory | done | activation.jar | avalon-framework.jar | axis-ws4ee.jar | commons-discovery.jar | commons-logging.jar | concurrent.jar | ejb3-persistence.jar | getopt.jar | hibernate-annotations.jar | hibernate-client.jar | jacorb.jar | javax.servlet.jar | jboss-annotations-ejb3.jar | jboss-aop-jdk50-client.jar | jboss-aspect-jdk50-client.jar | jboss-client.jar | jboss-common-client.jar | jboss-deployment.jar | jboss-ejb3-client.jar | jboss-ejb3x.jar | jboss-iiop-client.jar | jboss-j2ee.jar | jboss-jaxrpc.jar | jboss-jsr77-client.jar | jboss-remoting.jar | jboss-saaj.jar | jboss-system-client.jar | jboss-transaction-client.jar | jboss-ws4ee-client.jar | org/jboss/webservice/client/ServiceObjectFactory.class | jbossall-client.jar | jbosscx-client.jar | jbossha-client.jar | jbossjmx-ant.jar | jbossmq-client.jar | jbosssx-client.jar | jmx-client.jar | jmx-invoker-adaptor-client.jar | jnp-client.jar | juddisaaj.jar | log4j.jar | logkit.jar | mail.jar | namespace.jar | scout.jar | wsdl4j.jar | View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3901691#3901691 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3901691 --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: JNDI Lookup returns Reference - causes ClassCastExceptio
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, cause: java.io.InvalidClassException: javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID = 4418622981026545151, local class serialVersionUID = -6756054858541526837 | at org.jboss.webservice.client.ServiceObjectFactory.getObjectInstance(ServiceObjectFactory.java:114) | at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:301) | at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1110) | at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1127) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:690) | at org.jboss.naming.client.java.javaURLContextFactory$EncContextProxy.invoke(javaURLContextFactory.java:120) | at $Proxy0.lookup(Unknown Source) | at javax.naming.InitialContext.lookup(InitialContext.java:347) There doesn't seem to be any mention of this exception in this JBossWS forum, but I did come across an interesting thread: http://www.jboss.com/index.html?module=bbop=viewtopict=70738 ...where: [EMAIL PROTECTED] 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 | Does this mean I'm banging my head against a brick wall here, as support for client/server separation of J2EE Application Clients in JBoss isn't going to be properly supported (i.e. with remote clients) until 4.0.4? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3901701#3901701 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3901701 --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: JNDI Lookup returns Reference - causes ClassCastExceptio
[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 missing? AFAIK, this is just telling me the object factory that is doing the looking up, not what it is actually looking up. Looking up the JavaDocs for this package tells me this about the 'ServiceObjectFactory': anonymous wrote : This ServiceObjectFactory reconstructs a javax.xml.rpc.Service for a given WSDL when the webservice client does a JNDI lookup | | It uses the information provided by the service-ref element in application-client.xml | Looking back at my application-client.xml file, I see nothing wrong with the service-ref elements as far as I can see. The only difference is the 'service-interface' element. In the example application-client.xml file on your WSClientAppl wiki page, the 'service-ref' looks like this: | service-ref |service-ref-nameservice/OrganizationServiceEJB/service-ref-name |service-interfacejavax.xml.rpc.Service/service-interface |wsdl-fileMETA-INF/wsdl/server-ejb.wsdl/wsdl-file |jaxrpc-mapping-fileMETA-INF/jaxrpc-mapping.xml/jaxrpc-mapping-file | /service-ref | | service-ref |service-ref-nameservice/OrganizationServiceJSE/service-ref-name | service-interfacecom.underworld.crimeportal.OrganizationEndpointService/service-interface |wsdl-fileMETA-INF/wsdl/server-web.wsdl/wsdl-file |jaxrpc-mapping-fileMETA-INF/jaxrpc-mapping.xml/jaxrpc-mapping-file | /service-ref Whereas, mine looks like this (re-quoted from original post): service-ref | service-ref-nameservice/PolicyControlCenterService/service-ref-name | service-interfacejavax.xml.rpc.Service/service-interface | wsdl-fileMETA-INF/wsdl/PolicyControlCenter_jboss.wsdl/wsdl-file | jaxrpc-mapping-fileMETA-INF/PolicyControlCenter_mapping_jboss.xml/jaxrpc-mapping-file | service-qname xmlns:pfx=http://service.repository.policymatter.com;pfx:PolicyControlCenterService/service-qname | port-component-ref | service-endpoint-interfacecom.policymatter.repository.service.PolicyControlCenter/service-endpoint-interface | /port-component-ref | /service-ref | service-ref | service-ref-nameservice/PolicyFileMgrService/service-ref-name | service-interfacejavax.xml.rpc.Service/service-interface | wsdl-fileMETA-INF/wsdl/PolicyFileMgr_jboss.wsdl/wsdl-file | jaxrpc-mapping-fileMETA-INF/PolicyFileMgr_mapping_jboss.xml/jaxrpc-mapping-file | service-qname xmlns:pfx=http://service.policymatter.com;pfx:PolicyFileMgrService/service-qname | port-component-ref | service-endpoint-interfacecom.policymatter.service.PolicyFileMgr/service-endpoint-interface | /port-component-ref | /service-ref ...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. I'll investigate this next and see what happens. If this doesn't make a difference, do you think the classes I'm missing are my own classes on the server-side, or some JBossWS classes on the client side? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3901491#3901491 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3901491 --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: JNDI Lookup returns Reference - causes ClassCastExceptio
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. | | I'll investigate this next and see what happens. I changed my application-client.xml to point to our class, and I get the same behaviour. No change. Do you think the classes I'm missing are my own classes on the server-side, or some JBossWS classes on the client side? What am I doing that is so deviant from the standard way of doing J2EE app clients? Why doesn't this just work? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3901522#3901522 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3901522 --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: JNDI Lookup returns Reference - causes ClassCastExceptio
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 : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3901330 --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: JNDI Lookup returns Reference - causes ClassCastExceptio
[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 aren't binding
and my application isn't start at all.
I then tried simply swapping the ordering of the packages in the
jndi.properties file from:
|
java.naming.factory.url.pkgs=org.jboss.naming.client:org.jboss.naming:org.jnp.interface
|
to
|
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces:org.jboss.naming.client
|
and now, at least, my application launches again.
However, I'm still no closer than I was before. I can still see the JNDI name
bound in the JNDI (as described previously), and performing the lookup call
still returns a Reference object instead of my PolicyFileMgrService object.
I've tried adding the libraries described in JBossWSFAQ wiki page:
| ...build.xml from the samples.zip
| path id=client.classpath
| fileset dir=${jboss.home}/client
| include name=activation.jar/
| include name=axis-ws4ee.jar/
| include name=commons-discovery.jar/
| include name=commons-logging.jar/
| include name=jbossall-client.jar/
| include name=jboss-saaj.jar/
| include name=jboss-jaxrpc.jar/
| include name=jboss-ws4ee-client.jar/
| include name=log4j.jar/
| include name=namespace.jar/
| include name=wsdl4j.jar/
| /fileset
| /path
|
But this just seems to leave me with naming exception errors and class cast
exceptions, probably brought about due to class path clashes between the old
libs I had to get from a JBoss previous to the 403 I'm using now.
You mention that I could be 'missing classes needed by the jndi object
factory'. Is this on the client-side? Which libraries are these?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3901181#3901181
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3901181
---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: JNDI Lookup returns Reference - causes ClassCastExceptio
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 : http://www.jboss.com/index.html?module=bbop=viewtopicp=3900970#3900970 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3900970 --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
