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

Similar Messages

Regarding Spring an hibernate as WebService

Dear All
I need to develop a Webservice with Spring and Hibernate and need to import
as Java Bean Model in NWDS!
Does any body have small application Source code to develop spring and Hibernate as Webservice?
or let me know how to proceed ?
Thanks
Shravan

Hi Shravan,
first of all I am wondering about the usage scenario. Why do you want to develop with Hibernate and Spring and then convert it to EJB? How about directly starting with EJBs. Developing Web Services based on EJB is pretty straightforward in NWDS. Even simpler if you are using Enterprise Service Builder to generate the wsdls.
If you want to stick with your choice I would recommend you to have a look on the official spring website. There are a lot of tutorials and samples for all components of spring, including web services: [http://static.springsource.org/spring-ws/sites/1.5/reference/html/tutorial.html|http://static.springsource.org/spring-ws/sites/1.5/reference/html/tutorial.html].
Kind Regards,
Carl Heckmann

Getting error when trying to expose the java class as webservice

I am new to webservices and ESB.
I have two custom schemas. LegacyCustomer.xsd and CommonCustomer.xsd. I am compiling these schemas using JAXP. I am trying to map one custom data to another data using java class. I am trying to expose this java class into webservice.
public class Test implements Serializable {
private static final long serialVersionUID = 1L;
public Test() {
public CustomerType transform (CustomerDataType custDataType) {
CustomerType custType = new CustomerType();
custType.setCustomerId(custDataType.getCustomerId());
return custType;
Schemas used are:
Input Schema:
<schema targetNamespace="http://xmlns.oracle.com/Esb/CustomerData" xmlns:cust="http://xmlns.oracle.com/Esb/CustomerData" xmlns="http://www.w3.org/2001/XMLSchema">
     <element name="CustomerData" type="cust:CustomerDataType"/>
     <complexType name="CustomerDataType">
          <sequence>
               <element name="CustomerId" type="string"/>
</sequence>
     </complexType>
</schema>
Output Schema:
<schema targetNamespace="http://xmlns.oracle.com/Esb/CustomerProvision" xmlns:CU="http://xmlns.oracle.com/Esb/CustomerProvision" xmlns="http://www.w3.org/2001/XMLSchema">
     <element name="Customer" type="CU:CustomerType"/>
     <complexType name="CustomerType">
          <sequence>
               <element name="CustomerId" type="string"/>
          </sequence>
     </complexType>
</schema>
When I try to do this I am getting following error
CustomerType of method transform cannot be serialized into xml, and no custom serializer has been defined for it.
Why do we need custom serializer here? And if this is mandatory how can we define this custom serializer?

Thanks for your reply...
I tried second option that you specified first. I did the transformation of objects using xslt. It is working fine.
But I couldn't able to do this using first method...,
When I tried to compile the schema using jaxp it is actually creating classes without the private variables. and hence it is not able to recognize those variables to generate the wsdl.
But I am not sure how to generate the classes with those private variables and getter and setters (to generate wsdl specification it seems to be mandatory one).
Can you please tell me how can we do the schema compilation (other than xml beans and jaxp.... I tried both)?

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

Can I expose existing java applications as webservices

I have some java based applications doing functions such as datamining, visualization ... Can I expose these as webservices? How to do that? Can I directly expose it as webservices? What tools should I use? Please explain.
Thanks

basically, if you have a java application doing stuff, you can create a webservice by writing JSP pages and beans and/or servlets. very simple example:
- write a jsp page for data input that access your bean
- write a bean that routes the request/response to/from your application classes
all you need for doing this is a webserver and a servlet container (e.g. tomcat).
however, if youre application is doing some graphical output, you could split your application in two: a client application for the visualization, which is communication with a servlet or a full blown J2EE server (http://java.sun.com/j2ee/tutorial/1_3-fcs/doc/WCC.html).

Exposing complete data structure in webservice

Hello Experts,
I have a scenario where a Bapi functionality(server proxy) is exposed as a webservice .
So scenario will be SOAP -> XI -> Proxy (calls a BAPI)
In our BAPI (proxy, target structure) we are having 100+ fields. Currently the WS consumer - application making SOAP call to our webservice will send only 20 (minimum required) fields. But in near future it will be updated to send all 100 fields.
Is it OK to include all 100 fields in source data type even though we will receive only 20 fields. (If i mark all of them as optional i.e. occurance 0..1) Or will it result in error?
Thanks in Advance,
XI Queries.

Hi,
>>Is it OK to include all 100 fields in source data type even though we will receive only 20 fields. (If i mark all of them as optional i.e. occurance 0..1) Or will it result in error?
yes it is ok to have all 100 fields in source even if you use only 20 fields. But later when you make them as mandatory or anything, you need to regenerate the wsdl
Regards
Suraj

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
>

How to expose a bapi as Rest webservice to consume in web applications

Hello experts , i now seriously need your suggestion here. Is there a way to expose a BAPI as a rest webservice which can be consumed by a web application in the end.
What is ICF ( Internet Communication Framework) ? Does this help in generating web service from BAPI ?
Netweaver Gateway might help to generate services but may not be recommended here in our scenario.

Please refer Real Web Services with REST and ICF for creation of rest services in sap. The BAPI will have to be called in your handler class.
I think your best bet would be to transfer the data in the body of the http request and use simple transformation(with multiple roots) to convert the xml data to sap formats. GZIP can also be used to compress the data that is being sent. We have done this successfully in one of our projects.
However this approach(RESTful Service) would involve more work when compared to the approach suggested by Vikram. If SOAP based services are ok, then you should go ahead with Vikram's approach.

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.

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".

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...

Exposing OPSS Api's as Webservice

Hi Folks,
In our application, we require to manage Portal Security via different application . I understand that OWC outsources its security needs to OPSS, thus my question is that can we create webservices on top of OPSS api's and manage portal security that way? Is it supported by Oracle ?
Thanks
Edited by: Chandan Thour on Jul 17, 2012 7:27 AM

some samples at below link
http://docs.oracle.com/cd/E14571_01/doc.1111/e14309/spmlapi.htm

Exposing proxy service as a webservice using sb protocol

Hi everybody.
My team and I were working on an integration project between several applications. So we created all the OSB Projects needed to connect those applications and now I'm working on a web application that reads several logs that these integrations leave in the database in order to watch what happen when they are executed. Right now I need my web application to be able to reprocess or retry the messages that show some issue or are in an error state.
For this purpose we developed a proxy with an sb protocol which let us communicate with all the other proxy services dynamically just passing to it the proxy name, his operation and the body message. And finally here's my question for you guys.
How can I expose that last proxy (with the sb protocol) as a web service so I can consume it for the reprocess/retry action?
Thanks.

Dont think you need a Proxy service with SB protocol at all. From what I understand, your process will be like this:
1. Web app reads DB logs to see which records need to be resubmitted
2. Web App needs to invoke OSB to resubmit the message from log to correct proxy.
What you can do is create a WSDL based HTTP proxy in OSB for resubmission, Web application should call this HTTP proxy and pass the body, target service name (full path), target service type (Proxy or Business) and target Operation name(optional as messaging or Any XML type services wont have an operation associated). You can add a dynamic routing node in the HTTP proxy which will invoke the target proxy based on the request information received from Web App.
SB protocol only needs to be used in a Proxy service if you want to invoke a Proxy deployed on one OSB domain from another OSB domain or from Oracle SOA composites. Here the consumer will be the Web App, so it needs to be an HTTP proxy and not SB.
P.S.: You should also consider sending transport/custom headers as well and not just the body for your resubmission to be more reusable.

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!

Exposing local entity beans to web tier?

Hello all,
I have a question concerning basic design issues with EJB and the JSP presentation
layer. Currently, I have designed a system using all local component interfaces
of EJB 2.0. I currently have the following architecture in place:
EJB --> Servlets (WebWork Actions) --> JSP
I'm utilizing the session facade design pattern where the business logic in encapsulated
in session beans, which internally access the entity beans, etc. However, I am
doing something of the following:
sessionBean.getUserAccounts() which returns a Collection of actual UserAcountLocal's.
I then am passing this collection off to the JSP just to cycle through each entity
bean and display the data via its getXXX() methods. No modifications to the entity
beans are being done directly in the Actions/JSPs, rather they are modified through
methods of the session beans. Now I know that there is the concept of DTO (Data
transfer objects), which send the data from the particular entity bean to a regular
java bean for presentation. I know that DTO's increase performance if one is using
remote interfaces, because there is less network traffic that occurs via that
transport method. However, I know that WebLogic performs excellent caching of
entity beans, so that multiple invocations of get() methods on entity beans will
not make a trip to the database each and every time the get() method is called.
So, my question is: Is it "safe" to continue with the current way I am designing/coding
the system? I just find it a bit tedious to create value objects for each and
every entity bean, if I know that I will not be calling setXXX() methods from
within the presentation layer. Also, with EJB 2.0 and the introduction of local
component interfaces, it seems that issues regarding limiting the amount of network
traffic don't seem to be so relevant. Any suggestions/tips are appreciated. :-)
Best regards,
Ryan LeCompte
[email protected]
http://www.louisiana.edu/~rml7669

use dtos
the main reason is that if you call a getXXX() method on a local or remote
interface from your servlet then that bean is retrieved again (as the
servlet is outside the transaction involved in the initial retrieval)
For example if you retrieve 100 users and want to display them in a html
table with the user id, first name and lastname then there end up being more
than 300 SQL statements executed (this is unless your ejbs are readonly)
If you have a tool (like sql server profiler) that traces sql statements i
recommend you use it to see the staggering amount of sql statements that are
being executed by your current code - then DTOs will look much more
appealing (it worked for me) :).
I would also recommend using dtos when performing updates. Basically work
towards your servlets never directly accessing anything entity bean related.
Some people extend this further and have the DTO as the single argument in
the create method of an entity bean - I havent done this yet myself but it
looks like a good idea to me.
"Ryan LeCompte" <[email protected]> wrote in message
news:[email protected]...
>
Hello all,
I have a question concerning basic design issues with EJB and the JSPpresentation
layer. Currently, I have designed a system using all local componentinterfaces
of EJB 2.0. I currently have the following architecture in place:
EJB --> Servlets (WebWork Actions) --> JSP
I'm utilizing the session facade design pattern where the business logicin encapsulated
in session beans, which internally access the entity beans, etc. However,I am
doing something of the following:
sessionBean.getUserAccounts() which returns a Collection of actualUserAcountLocal's.
I then am passing this collection off to the JSP just to cycle througheach entity
bean and display the data via its getXXX() methods. No modifications tothe entity
beans are being done directly in the Actions/JSPs, rather they aremodified through
methods of the session beans. Now I know that there is the concept of DTO(Data
transfer objects), which send the data from the particular entity bean toa regular
java bean for presentation. I know that DTO's increase performance if oneis using
remote interfaces, because there is less network traffic that occurs viathat
transport method. However, I know that WebLogic performs excellent cachingof
entity beans, so that multiple invocations of get() methods on entitybeans will
not make a trip to the database each and every time the get() method iscalled.
So, my question is: Is it "safe" to continue with the current way I amdesigning/coding
the system? I just find it a bit tedious to create value objects for eachand
every entity bean, if I know that I will not be calling setXXX() methodsfrom
within the presentation layer. Also, with EJB 2.0 and the introduction oflocal
component interfaces, it seems that issues regarding limiting the amountof network
traffic don't seem to be so relevant. Any suggestions/tips areappreciated. :-)
>
Best regards,
Ryan LeCompte
[email protected]
http://www.louisiana.edu/~rml7669

Exposing spring's beans as Webservices

Similar Messages

Maybe you are looking for