Sending bean to webservice

Hi
I'm developing a JAX-RPC web services. I have trouble understanding the Coffee Break Example in the bean part. I want to send bean to the service and also return bean from the service. Could anyone tell me how it can be done? or giving me some easy example code?

Hello,
Here are the steps you have to follow. Note that my example refers to dii clients:
1. Create the request & response beans. You can place them into the same package where the web service classes exist. For example:
The request bean
===============
package webservice;
public class RequestBean implements java.io.Serializable
private String name;
public RequestBean()
public void setName(String val)
name = val;
public String getName()
return name;
The response bean
================
package webservice;
public class ResponseBean implements java.io.Serializable
private String result;
public ResponseBean()
public void setResult(String val)
result = val;
public String getResult()
return result;
2. Create the web service interface and implementation classes. For example:
Interface
=======
package webservice;
import java.rmi.Remote;
import java.rmi.RemoteException;
import java.rmi.Remote;
import java.rmi.RemoteException;
public interface HelloIF extends Remote
public ResponseBean sayHello(RequestBean request) throws RemoteException;
The implementation class
=====================
package webservice;
import java.rmi.RemoteException;
public class HelloImpl implements HelloIF
public HelloImpl()
public ResponseBean sayHello(RequestBean request) throws RemoteException
ResponseBean response = new ResponseBean();
response.setResult("Hello, " + request.getName() + "!");
return response;
3. Compile, package and deploy the web service, using preferably a ant script. You may simply use the ones supplied by the jwsdp-1.3 tutorial samples, just with a little modification to comply with your web service. At this point, your work with the web service side is done.
4. Now, the dii client usually discovers the web service dynamically. For the purposes of this example though, we assume that this has already been done and we have the information needed. Just add the beans you created in step 1 in your client project's classpath. Here is the sample dii client class:
package dii;
import javax.xml.rpc.Call;
import javax.xml.rpc.Service;
import javax.xml.rpc.JAXRPCException;
import javax.xml.namespace.QName;
import javax.xml.rpc.ServiceFactory;
import javax.xml.rpc.ParameterMode;
import webservice.RequestBean;
import webservice.ResponseBean;
public class DIIClient
private static String endpointURL = "<put here the web service url>";
/* VALUES TAKEN FROM WEB SERVICE's WSDL DOCUMENT */
private static String serviceName = "<put here the service name>";
private static String portName = "<put here the port name>";
private static String operationName = "sayHello";
private static String inParameterName = "RequestBean_1";
private static String requestType = "RequestBean";
private static String responseType = "ResponseBean";
private static String BODY_NAMESPACE_VALUE = "<this one is also taken from wsdl>";
private static String TYPES_NAMESPACE_VALUE = "<this one is also taken from wsdl>";
private static String ENCODING_STYLE_PROPERTY = "javax.xml.rpc.encodingstyle.namespace.uri";
private static String NS_XSD = "http://www.w3.org/2001/XMLSchema";
private static String URI_ENCODING = "http://schemas.xmlsoap.org/soap/encoding/";
public DIIClient()
public static void main(String[] args)
DIIClient dIIClient = new DIIClient();
try
// create the Service object
System.out.println("Creating service...");
ServiceFactory serviceFactory = ServiceFactory.newInstance();
Service service = serviceFactory.createService(new QName(serviceName));
// create the Call object
System.out.println("Creating call...");
QName port = new QName(portName);
Call call = service.createCall(port);
call.setTargetEndpointAddress(endpointURL);
// set call properties
System.out.println("Setting call properties...");
call.setProperty(call.OPERATION_STYLE_PROPERTY, "rpc");
call.setProperty(call.SOAPACTION_USE_PROPERTY, new Boolean(false));
call.setProperty(call.ENCODINGSTYLE_URI_PROPERTY, "http://schemas.xmlsoap.org/soap/encoding/");
// set the request and response types
System.out.println("Setting request and response types...");
QName QNAME_REQUEST_TYPE = new QName(TYPES_NAMESPACE_VALUE, requestType);
QName QNAME_RESPONSE_TYPE = new QName(TYPES_NAMESPACE_VALUE, responseType);
call.setReturnType(QNAME_RESPONSE_TYPE, webservice.ResponseBean.class);
call.setOperationName(new QName(BODY_NAMESPACE_VALUE, operationName));
call.addParameter(inParameterName,QNAME_REQUEST_TYPE,webservice.RequestBean.class,ParameterMode.IN);
RequestBean request = new RequestBean();
request.setName("<your name>");
Object[] params = {request};
// invoke remote method
System.out.println("Invoking remote method...");
ResponseBean response = (ResponseBean)call.invoke(params);
// display response
System.out.println("Received response");
if (response == null)
System.out.println("Response is null");
else
System.out.println(response.getResult);
catch (Exception exception)
exception.printStackTrace();
Now, the static clients are more simple, since you have everything fixed for you by running the wscompile tool. The wscompile will also generate the web service beans classes along with the client stubs. You may also use the wscompile with the option -import instead of -gen:client, so that the tool will generate the bean classes only together with serializers and deserializers.
i hope i helped you
Regards

Similar Messages

  • Exposing spring's beans as Webservices

    Hello there! We need to expose our Spring based application beans as webservices. I know how to do this using Axis, as its well documented on the Spring documentation. But how can I specify specific ServletEndpoints for my webservices on Oracle AS 10.1.2?
    Regards

    Is it possible to expose a different endpoint on Oracle? I can't find anything in the (poor) Oracle's documentation

  • Error while sending request to Webservice from Client app on Weblogic

    Hi Everybody,
    As part of web service development and deployment, I created one simple webservice and tried to deploy it on Apache Tomcat 5.5 and then weblogic 9.2. It worked fine on Apache Tomcat but it didn't work on Weblogic. Here are the steps I followed.
    1) Created a webservice within one Dynamic Web project
    2) Created a Client application
    3) Deployed both (by exporting war files from eclipse3.2) on Tomcat Apache locally on the same machine (localhost)
    4) Invoked client in the browser which allows to send simple request (Hello!) to Webservice
    5) Invoked webservice method call from the Client browser window
    6) Received success response back from webservice.
    Then, I deployed same war files on Weblogic 9.2 (different machine on the network)
    - Both got deployed successfully and reached to ACTIVE state on Weblogic and became ready to accept requests.
    - When invoked Client application on the browser, it worked.
    - From that client application browser window, I tried to invoke webservice call, I got the exception as below:
    exception: java.net.ConnectException: Connection refused: connect
    I will greatly appreciate any advice on this. Let me know if more information is needed.
    Thanks in advance.
    Gaurang Prajapati

    Have you given the correct ip or machine name in the client?

  • Possible to create a JAX-WS, session-bean-based webservice for WebLogic 10?

    All,
    sorry - but I'm going a bit crazy here. I have been unable to figure out the secret hand-shakes for developing a session-bean-based web service that will run properly under Weblogic 10.0. There are examples out there on how to create webservices that exists within a war file - but none that I can find that reside within a session bean (an ear file).
    I can't even figure out how to do with this Bea Workshop for WebLogic Platform 10.0! Is this possible? I can't find any examples anywhere on how to do this. I must be missing something...
    Does WebLogic 10.0 support web services within session beans? I've figured out how to do this with JBoss, Sun App Server, and Glassfish - but no luck so far with WebLogic.
    If anyone can please point me in the proper direction it would be very appreciated. My company likes WebLogic, but we have to be able to do this in order to continue using it.
    Thanks,
    -john

    Yeah - I've tried that. Everything builds fine - but when I deploy to WebLogic 10, I get the stack below. It looks like it is looking for the class examples.webservices.jaxws.jaxws.SayHello - but there isn't such a class in the example...
    Any thoughts? I'm completely stuck!
    <Apr 16, 2007 4:15:45 PM PDT> <Error> <HTTP> <BEA-101216> <Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
    class: examples.webservices.jaxws.jaxws.SayHello could not be found
    at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
    at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
    at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
    at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
    at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
    Truncated. see log file for complete stacktrace
    >
    <Apr 16, 2007 4:15:45 PM PDT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1176765341457' for task '0'. Error is: 'weblogic.application.ModuleException: Exception activating module: EJBModule(WL6-ejb.jar)
    Unable to deploy EJB: SimpleEjbImpl from WL6-ejb.jar:
    Unable to deploy EJB: WL6-ejb.jar from WL6-ejb.jar:
    [HTTP:101216]Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
    class: examples.webservices.jaxws.jaxws.SayHello could not be found
    at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
    at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
    at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
    at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
    at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
    at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229)
    at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:315)
    at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:125)
    at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
    at javax.servlet.GenericServlet.init(GenericServlet.java:241)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
    at weblogic.wsee.deploy.WseeWebappModule.activate(WseeWebappModule.java:139)
    at weblogic.wsee.deploy.WSEEEjbModule.activate(WSEEEjbModule.java:371)
    at weblogic.wsee.deploy.WsEJBDeployListener.activate(WsEJBDeployListener.java:52)
    at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1414)
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423)
    at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    weblogic.application.ModuleException: Exception activating module: EJBModule(WL6-ejb.jar)
    Unable to deploy EJB: SimpleEjbImpl from WL6-ejb.jar:
    Unable to deploy EJB: WL6-ejb.jar from WL6-ejb.jar:
    [HTTP:101216]Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
    class: examples.webservices.jaxws.jaxws.SayHello could not be found
    at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
    at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
    at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
    at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
    at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
    at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229)
    at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:315)
    at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:125)
    at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
    at javax.servlet.GenericServlet.init(GenericServlet.java:241)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
    at weblogic.wsee.deploy.WseeWebappModule.activate(WseeWebappModule.java:139)
    at weblogic.wsee.deploy.WSEEEjbModule.activate(WSEEEjbModule.java:371)
    at weblogic.wsee.deploy.WsEJBDeployListener.activate(WsEJBDeployListener.java:52)
    at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1414)
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423)
    at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:440)
    at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
    Truncated. see log file for complete stacktrace
    class: examples.webservices.jaxws.jaxws.SayHello could not be found
    at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
    at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
    at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
    at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
    at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
    Truncated. see log file for complete stacktrace
    >
    <Apr 16, 2007 4:15:46 PM PDT> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application '_appsdir_WL6_ear'.>
    <Apr 16, 2007 4:15:46 PM PDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application '_appsdir_WL6_ear'.>
    <Apr 16, 2007 4:15:46 PM PDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: Exception activating module: EJBModule(WL6-ejb.jar)
    Unable to deploy EJB: SimpleEjbImpl from WL6-ejb.jar:
    Unable to deploy EJB: WL6-ejb.jar from WL6-ejb.jar:
    [HTTP:101216]Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
    class: examples.webservices.jaxws.jaxws.SayHello could not be found
    at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
    at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
    at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
    at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
    at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
    at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229)
    at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:315)
    at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:125)
    at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
    at javax.servlet.GenericServlet.init(GenericServlet.java:241)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
    at weblogic.wsee.deploy.WseeWebappModule.activate(WseeWebappModule.java:139)
    at weblogic.wsee.deploy.WSEEEjbModule.activate(WSEEEjbModule.java:371)
    at weblogic.wsee.deploy.WsEJBDeployListener.activate(WsEJBDeployListener.java:52)
    at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1414)
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423)
    at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:440)
    at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
    Truncated. see log file for complete stacktrace
    class: examples.webservices.jaxws.jaxws.SayHello could not be found
    at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
    at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
    at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
    at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
    at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
    Truncated. see log file for complete stacktrace
    >

  • Question about sending soap to webservice

    hi
    i am trying to find a sample to demonstrate how a client can send a soap request to a webservice. usually, there is sample to show how to use webservice client jar to create request object and call webservice with it. i was wondering if i can just pass a soap xml to the webservice. thanks

    FCE will look for the media files defined in the Source field of each clip in the browser and in the timeline. In your case it will mark the clips "offline" (red bar on the browser icons) and you'll have to reconnect them to files in the new location on the external hard drive.
    You'll have also to set the new location in the Scratch Disk parameters in System Settings to tell FCE where to store the newly captured footage.
    After that you should have no problem.
    Piero

  • Using EJB remote session beans llike webservice.

    My requirement is to fetch a big size ASCII stream file from a remote location. For this can I use Statless EJB Session beans?
    For this EJB application & Web application will be on my application server side & EJB client should reside on the remote end side from where I want to fetch the file. - Please confirm my this logic as I am new in Java & EJB, I am having a basic query like this. (I don't want to proceed with EJB web service like (@Stateless, @WebService), I want to purly use EJB Statless Remote session beans - Is this possible?
    If yes, can I have one sample example URL pls?
    Thanks in advance for your help.

    My requirement is to fetch a big size ASCII stream file from a remote location. For this can I use Statless EJB Session beans?
    For this EJB application & Web application will be on my application server side & EJB client should reside on the remote end side from where I want to fetch the file. - Please confirm my this logic as I am new in Java & EJB, I am having a basic query like this. (I don't want to proceed with EJB web service like (@Stateless, @WebService), I want to purly use EJB Statless Remote session beans - Is this possible?
    If yes, can I have one sample example URL pls?
    Thanks in advance for your help.

  • I' d like to send files through webservice not using XI

    i am trying p2p connection with Webservice.
    sending message success but files not.
    is any way to send files? someone tell that SOAP attach maybe help me.
    but i don't know how to do.
    please let me know how to use SOAP attach in SAP.
    all your comments make me solve my problem.
    thanks.

    InDesign CS4 can open .indd, .indt  and .inx files from earlier versions, but not from later. It should, however, be able to open .idml files saved or exported from newer versions, with the understanding that unsupported features will be lost, text will probably reflow due to differences in texts engines between versions, and that the greater the gap between versions the more likely there are to be noticeable differences from the original. You will need to be sure CS4 is at version 7.0.6 to read the .idml.

  • Stateless Bean imposing webservice in Weblogic 10

    Hi..
    Is it possible to implement Stateless bean webservice using jwsc task and deploying both services(ejb and webservice) as EAR???.
    If anybody knows please let me know what are the steps to follow.
    Thanks in advance and your help is appreciated........

    Hi,
    if you don't want to use @EJB to inject the EJB, then you'll need declare the EJB reference in deployment descriptor.
    Here is an example copied from EJB3 spec:
    <ejb-local-ref>
    <description>
    This is a reference to the local business interface
    of an EJB 3.0 session bean that provides a payroll
    service.
    </description>
    <ejb-ref-name>ejb/Payroll</ejb-ref-name>
    <local>com.aardvark.payroll.Payroll</local>
    </ejb-local-ref>
    then you can lookup the local ejb from "java:comp/env/ejb/Payroll".

  • How to send attachments thru webservice?

    Hi Friends,
    I am in a situation to send an image or pdf file thru webservice method as an attachment (i believe send attachment is the only possible way to send image or pdf).
    How can i do this ? If anyone has an idea pls let me know.
    Thanks,
    Raags

    http://msdn2.microsoft.com/en-us/library/ms996944.aspx
    http://www.ibm.com/developerworks/webservices/library/ws-attach.html

  • Example of using session bean with webservices

    Hello,
    I am working with netbeans 5.5 (with JAX-WS 2.0 library) and using Tomcat.
    I have created webservices and everything is working well so far. However, each webservice is making a connection to my database.
    I would like to use a session bean so that I make the connection only once (at the begining of the client session for example) and store it into my session bean.
    I am a newbie in those things, I search on the Web and on this forum some code examples. The only thing I have found is this article http://weblogs.java.net/blog/ramapulavarthi/archive/2006/06/maintaining_ses.html
    When I tried this, the session doesn't seem to work at all : I get the same result (counter=1) twice.
    Does anybody have a complete example of how to use a session with webservices please?
    Thanks a lot!

    Sorry, I was not very clear in my last message.
    I need all my webservices to share the same bean during one user session.
    Then, if a page calls 2 different web services, only 1 database connection is made instead of 2. And if the user opens other pages which call other webservices, they will use the connection kept into the session bean.
    Anyway, I tried to do like it is said in your website but I can not build my project. I have an error : java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/C:/.../build/web/WEB-INF/lib/jaxb-impl.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. I do not understand because I have downloaded the jax-ws 2.1.1 api and no other libraries are imported in my project. :-(
    I wonder if it is not related to netbeans...

  • Command bean or webservice for accessing EJB

    Hi Experts,
    I Want to access an Enterprise archieve DC created for EJB Module DC, through WebDynpro DC.
    Now I know that there are two ways to access EAR DC through webDynpro:
    1) Command bean
    2) Web Services
    Can anybody suggest the pros and cons of this two methods?
    Also please suggest which one to choose.
    Regards,
    Ashish Shah

    Hi,
    to access EJBs from WD, you can use the EJB3.0 model importer (a new feature introduced with NW CE). There's a good tutorial explaining that <a href="http://help.sap.com/saphelp_nwce10/helpdata/en/45/f7f744aea471fae10000000a1553f6/frameset.htm">here</a>.
    The Web services way should also work, but it means that you "wrap" the EJB, which is not needed in this case, I believe.
    Hope it helps!

  • Send message through Webservices

    In my web application using JSP, based on one event i would like to send a message to all the users who are accessing the application.
    The event will occur in javascript.
    The message should display by using javascript's alert() function.
    Is it possible, if it is then how to do?

    You can use the HOST or CLIENT_HOST command depending on your forms version and network setup.
    Try:
    HOST('cmd /c net send '||user||' '||<your message>);

  • Issue with Webservice Creation using Session Beans.

    Hi All,
    I want to expose my Session beans as webservice.
    I'm using Weblogic Application Server.
    When I do the modeling using JDeveloper, I'm unable to convert the Session bean to webservice.
    Any information on this is highly appreciable.
    Thanks & Regards,
    Kumar Madhavan.

    I can't give you much of a walk through, as I have just started it myself, but I'm using a universal unique identifier to represent each client. Whenever a client posts data from a jsp or applet the uuid is also sent. I use POST to pass all my parameters. If the server hasen't received data in say 5 minutes from the client then it is assumed the client went offline. Its working for me so far.
    COn

  • R3 (rfc-sender) - XI - Webservice ( soap-receiver)

    Hi,
    I am getting below error whenever webservice(target system) is unavailable.
    HTTP 404 Not Found
    Then RFC got failed in R3, due to this error in XI
    R3 (rfc-sender) <-> XI <-> Webservice ( soap-receiver) Synch
    User will enter the request data in R3 and waiting for the response, but webservice is down(i.e not available)
    Request is reached to XI box and XI is trying to send data when webservice is down( i,e not available), RFC is waiting for the response from XI box.
    how we will handle this kind of situation,how should i give response back to RFC( because RFC sent the request and waiting for the response, XI could not send any response back as Webservce is down, Please advice me how should XI inform to the end user r R3 abt webservice.
    I am getting this error to my mail box as i have configured ALERTS. i do not want to change existing RFC.
    is there any chance to send response to R3 even webservice is down, please can any one suggest.
    Thanks,
    SIva
    Edited by: Siva Grandhi on Jun 18, 2008 1:12 PM

    Hi siva,
    check this blog on HTTP errors.
    /people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
    May be the URL you have given in SOAP at receiver adapter is wrong.Check that once.
    Error: 404 Not Found
    Description: The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
    Possible Tips:- for HTTP_RESP_STATUS_CODE_NOT_OK 404
    u2022 404 is an HTTP response code that indicates that the resource in question couldn't be found. Usually this is due to an incorrect URL, so it is better to cross check all URLs. Check pipeline URL in the SLD in the business system of the Integration Server For this go to SLD->Business System-><yourIntegrtaion Server>->Pipeline URL: It should be like this http://<host>:<port>/sap/xi/engine?type=entry Where host is the host name of the Integration Server and port is the HTTP(8xxx) port. To verify this in Integration Server you can do like this. Go to SXMB_ADM->Integration Engine Configuration->Choose Edit from Menu -> Change Global Configuration Data to switch to change mode. Then select System Landscape - Load Configuration. (This is not required always)
    u2022 Check that the port really is the ICM HTTP Port and not the J2EE port i.e SMICM then menu GOTO --> SERVICES and check the port number for HTTP. It should be HTTP port
    u2022 If the error is Page cannot be displayed, cannot find server in https configurations Check and correct the SSL configuration for the ABAP and the J2EE side of the system
    u2022 If the error is because of integration server when using Proxy communications then check these. i.e SXMB_ADM->Integration Engine Configuration->Corresponding Integration Server enrty should be dest://<Http Integration server-Destination> Where < Http Integration server -Destination > is the RFC destination (SM59) of type HTTP connection (type H) to the Integration Server. In this case, host name, port, and path prefix are saved in the RFC destination.
    Thanks,
    Vijaya.

  • R3 (rfc-sender) - XI - Webservice ( soap-recever) Synch : error handlng

    R3 (rfc-sender) <-> XI <-> Webservice ( soap-receiver) Synch
    User will enter the request data in R3 and waiting for the response, but webservice is down(i.e not available)
    Request is reached to XI box and XI is trying to send data when webservice is down( i,e not available),  RFC is waiting for the response from XI box.
    how we will handle this kind of situation,how should i give response back to RFC( because RFC sent the request and waiting for the response,  XI could not send any response back as Webservce is down, Please advice me how should XI inform to the end user r R3 abt webservice down.
    Pleae help me out on this.
    Thanks,
    Dhanush.

    Hi,
    Normally, the Web service should provide a fault message back to XI and the RFC should also have an exception defined that will trigger a fault message mapping and that way the application error is sent back to R3.
    But if the web service does not provide u with a fault message then XI will trigger the System Error back to R3.
    The functionality of checking the DB status and propagating meaningful errors to XI as fault messages should lie with the web service.
    Thanks
    Vikranth

Maybe you are looking for

  • MSI GF4 Ti 4200 VIVO ???

    I'am f@#%ing tired this  now! I read from hexus.net that MSI GF4 Ti 4200 64Mb has Full VIVO function but no mention about it in the box ! But my Ti420065Mb has no VIVO !!! Why ??? Please EXPLAIN !!!    X(  When i install nvidia capture drivers the vi

  • Effects of R3 DS enhancement on remote cube

    Hi All, Is there a direct effect while running queries against a remote cube when its underlying R3 DS has been enhanced? An example is, I'm running queries on a remote cube copied from OL_PCA_1. Now I enhanced R3 DS 0EC_PCA_1_9 (which feeds IS 0EC_P

  • Can i use windows migration assistant to transfer files from my windows formatted external hard drive to my mac?

    I have a windows formatted external hard drive and a macbook pro. I was wondering if i could use the windows migration assistant to transfer files from my external hard drive to the mac

  • Employee information Upload in HR module

    Hello Experts,       I want to upload Employee Information in database using BDC so can any one send me step by step procedure for doing this.If possible send one example. Mail me on: "[email protected]" Thanx and Regards, Rahul Talele

  • Purchase Order Statistical Delivery Date changed automatically

    Hi, In the purchase order, when I go to change the delivery date, the statistical delivery date changed automatically. I do not want to change the statistical delivery date. Is there any User Exit or BADI to validate this? Please suggest the same. Re