[Design of JBoss Web Services] - Caused by: org.jboss.ws.WSException: Cannot obtain java type
by patel_123
well i resolvec that error..
i am getting another error please help me in resolving this,
Caused by: org.jboss.ws.WSException: Cannot obtain java type mapping for: {http://wb1-329:8080}validateUser
at org.jboss.ws.deployment.JSR109MetaDataBuilder.buildParameterMetaDataDoc(JSR109MetaDataBuilder.java:451)
at org.jboss.ws.deployment.JSR109MetaDataBuilder.setupOperationsFromWSDL(JSR109MetaDataBuilder.java:200)
at org.jboss.ws.deployment.JSR109ClientMetaDataBuilder.buildMetaDataInternal(JSR109ClientMetaDataBuilder.java:208)
at org.jboss.ws.deployment.JSR109ClientMetaDataBuilder.buildMetaData(JSR109ClientMetaDataBuilder.java:126)
at org.jboss.ws.deployment.JSR109ClientMetaDataBuilder.buildMetaData(JSR109ClientMetaDataBuilder.java:82)
at org.jboss.ws.jaxrpc.ServiceImpl.(ServiceImpl.java:96)
at org.jboss.ws.jaxrpc.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:157)
at org.jboss.ws.jaxrpc.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:128)
at client.UserBean.loginUser(UserBean.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:126)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056878#4056878
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056878
18 years, 9 months
[Design of JBoss Web Services] - Caused by: java.lang.IllegalArgumentException: Cannot obtain
by patel_123
hi
i exposed my ejb components as webservices.It generated WSDl doc correctly.I checked my webmethods workd properly using service explorer utility provided by myeclipse5.5.It works fine.
But when client try to call a web sevice,it throws a exception,
this is my client app code,
try {
String namespace="http://wb1-329:8080";
String service="CustomerRegistration";
String wsdl="http://localhost:8080/CustomerRegistrationEJB?wsdl";
//ctx=new InitialContext();
//customerSessionRemote remote=(customerSessionRemote)ctx.lookup("customer/remote");
//String user=remote.validateUser(getUserName(), getPassword());
try {
URL defurl = new URL(wsdl);
System.out.println(defurl);
ServiceFactory serviceFactory=ServiceFactory.newInstance();
System.out.println("service fact");
Service remoteService=serviceFactory.createService(defurl, new QName(namespace,service));
System.out.println(remoteService);
customerSessionRemote invoker=(customerSessionRemote)remoteService.getPort(customerSessionRemote.class);
System.out.println(invoker);
String user=invoker.validateUser(getUserName(), getPassword());
this is error i am getting,
Caused by: java.lang.IllegalArgumentException: Cannot obtain wsdl service: {http://wb1-329:8080}CustomerRegistration
at org.jboss.ws.deployment.JSR109ClientMetaDataBuilder.buildMetaDataInternal(JSR109ClientMetaDataBuilder.java:164)
at org.jboss.ws.deployment.JSR109ClientMetaDataBuilder.buildMetaData(JSR109ClientMetaDataBuilder.java:126)
at org.jboss.ws.deployment.JSR109ClientMetaDataBuilder.buildMetaData(JSR109ClientMetaDataBuilder.java:82)
at org.jboss.ws.jaxrpc.ServiceImpl.(ServiceImpl.java:96)
at org.jboss.ws.jaxrpc.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:157)
at org.jboss.ws.jaxrpc.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:128)
at client.UserBean.loginUser(UserBean.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:126)
please anybody help me in resolving this...
thanks in advance
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056868#4056868
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056868
18 years, 9 months
[Design of JBossCache] - Re: Gravitation and POJO Cache
by jason.greene@jboss.com
"bstansberry(a)jboss.com" wrote : Is it possible to check if the forceDataGravitation option is set when the initial call to the PojoCache API is made, and then preserve that value through all the internal cache calls needed to construct the pojo?
|
Yes although since references are resolved lazily (and per traversal since they could change), I would have to tag the object to always use the flag. I would limit the calls to just get calls on an internal node, but there would still be one such call per pojo operation.
I could also build an API that would allow you to control the the lifespan of the gravitation force.
anonymous wrote :
| I guess that's what you meant by adding an option API. :)
Yes, and alternatively there could be some kind of block form, to allow you to specify how long to do this for:
| PojoCacheSession session = pojoCache.startSession();
| session.setForceGravitation(true);
| pojo.getBlah().getFoo();
| session.stop();
| pojo.setSimple();
|
-Jason
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056728#4056728
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056728
18 years, 9 months
[Design of JBossCache] - Re: Gravitation and POJO Cache
by bstansberry@jboss.com
"jason.greene(a)jboss.com" wrote : They could retrieve an object, wait for some period time (during which the data has been gravitated to another node), then trigger an update which would fail.
You describe a somewhat broken usage. Let me preface this by saying buddy replication is an advanced feature, not for the faint of heart, because it requires a lot of engineering effort on the part the writer of the app to ensure that the data is truly owned by one and only one node in the cluster. It would be great if that weren't the case, but the cost of not having it be the case is terrible performance due to constant gravitation calls.
So, getting an object from the cache, holding a ref to it, allowing a concurrent request to go to another node that gravitates the cache tree, and then using the original object without re-fetching it from the cache -- that means the app is not properly ensuring ownership of the data.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056720#4056720
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056720
18 years, 9 months
[Design of JBossCache] - Re: Gravitation and POJO Cache
by jason.greene@jboss.com
"jason.greene(a)jboss.com" wrote : I would need to handle puts as well, since I can't predict how someone is using POJO Cache. They could retrieve an object, wait for some period time (during which the data has been gravitated to another node), then trigger an update which would fail.
|
Although, in order to solve another problem, I have to do a read before almost every put to validate that the pojo hasn't been detached by a remote node (see JBCACHE-1057). So just forcing gravitation on reads will work, although the behavior and performance will match autoDataGravitation=true.
I guess a strong reason against requiring autoDataGravitation is that like in your case, you might want to mix cache and pojocache calls in the same cache instance.
-Jason
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056719#4056719
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056719
18 years, 9 months