How to consume REST WebService using Axis2 in Adobe CQ5.5

Hi All,
    How to consume REST WebService using Axis2 in Adobe CQ5.5 ?
Please help me with this.Thanks very much for your help.
Thanks & Regards,
Kumar

We had enough trouble getting the "osgi compliant" Axis2 library to run in OSGI without spooky failures that we ended up re-writing everything utilizng JAX-WS. JAX-WS is present in the underlying JDK, you just need to create an OSGI fragment bundle that exposes these classes from the JDK. So basically a bundle that just exports:
com.sun.xml.ws,
                                com.sun.xml.ws.addressing,
                                com.sun.xml.ws.addressing.model,
                                com.sun.xml.ws.addressing.v200408,
                                com.sun.xml.ws.api,
                                com.sun.xml.ws.api.addressing,
                                com.sun.xml.ws.api.client,
                                com.sun.xml.ws.api.fastinfoset,
                                com.sun.xml.ws.api.handler,
                                com.sun.xml.ws.api.message,
                                com.sun.xml.ws.api.message.stream,
                                com.sun.xml.ws.api.model,
                                com.sun.xml.ws.api.model.soap,
                                com.sun.xml.ws.api.model.wsdl,
                                com.sun.xml.ws.api.pipe,
                                com.sun.xml.ws.api.pipe.helper,
                                com.sun.xml.ws.api.server,
                                com.sun.xml.ws.api.streaming,
                                com.sun.xml.ws.api.wsdl.parser,
                                com.sun.xml.ws.api.wsdl.writer,
                                com.sun.xml.ws.binding,
                                com.sun.xml.ws.client,
                                com.sun.xml.ws.client.dispatch,
                                com.sun.xml.ws.client.sei,
                                com.sun.xml.ws.developer,
                                com.sun.xml.ws.developer.servlet,
                                com.sun.xml.ws.encoding,
                                com.sun.xml.ws.encoding.fastinfoset,
                                com.sun.xml.ws.encoding.soap,
                                com.sun.xml.ws.encoding.soap.streaming,
                                com.sun.xml.ws.encoding.xml,
                                com.sun.xml.ws.fault,
                                com.sun.xml.ws.handler,
                                com.sun.xml.ws.message,
                                com.sun.xml.ws.message.jaxb,
                                com.sun.xml.ws.message.saaj,
                                com.sun.xml.ws.message.source,
                                com.sun.xml.ws.message.stream,
                                com.sun.xml.ws.model,
                                com.sun.xml.ws.model.soap,
                                com.sun.xml.ws.model.wsdl,
                                com.sun.xml.ws.org.objectweb.asm,
                                com.sun.xml.ws.protocol.soap,
                                com.sun.xml.ws.protocol.xml,
                                com.sun.xml.ws.resources,
                                com.sun.xml.ws.server,
                                com.sun.xml.ws.server.provider,
                                com.sun.xml.ws.server.sei,
                                com.sun.xml.ws.server.servlet,
                                com.sun.xml.ws.spi,
                                com.sun.xml.ws.streaming,
                                com.sun.xml.ws.transport,
                                com.sun.xml.ws.transport.http,
                                com.sun.xml.ws.transport.http.client,
                                com.sun.xml.ws.transport.http.server,
                                com.sun.xml.ws.transport.http.servlet,
                                com.sun.xml.ws.util,
                                com.sun.xml.ws.util.exception,
                                com.sun.xml.ws.util.localization,
                                com.sun.xml.ws.util.pipe,
                                com.sun.xml.ws.util.xml,
                                com.sun.xml.ws.wsdl.parser,
                                com.sun.xml.ws.wsdl.writer,
                                com.sun.xml.ws.wsdl.writer.document,
                                com.sun.xml.ws.wsdl.writer.document.http,
                                com.sun.xml.ws.wsdl.writer.document.soap,
                                com.sun.xml.ws.wsdl.writer.document.soap12,
                                com.sun.xml.ws.wsdl.writer.document.xsd,
                                com.sun.xml.internal.bind,
                                com.sun.xml.internal.bind.v2,
                                com.sun.xml.internal.ws,
                                com.sun.xml.internal.ws.addressing,
                                com.sun.xml.internal.ws.addressing.model,
                                com.sun.xml.internal.ws.addressing.v200408,
                                com.sun.xml.internal.ws.api,
                                com.sun.xml.internal.ws.api.addressing,
                                com.sun.xml.internal.ws.api.client,
                                com.sun.xml.internal.ws.api.fastinfoset,
                                com.sun.xml.internal.ws.api.handler,
                                com.sun.xml.internal.ws.api.message,
                                com.sun.xml.internal.ws.api.message.stream,
                                com.sun.xml.internal.ws.api.model,
                                com.sun.xml.internal.ws.api.model.soap,
                                com.sun.xml.internal.ws.api.model.wsdl,
                                com.sun.xml.internal.ws.api.pipe,
                                com.sun.xml.internal.ws.api.pipe.helper,
                                com.sun.xml.internal.ws.api.server,
                                com.sun.xml.internal.ws.api.streaming,
                                com.sun.xml.internal.ws.api.wsdl.parser,
                                com.sun.xml.internal.ws.api.wsdl.writer,
                                com.sun.xml.internal.ws.binding,
                                com.sun.xml.internal.ws.client,
                                com.sun.xml.internal.ws.client.dispatch,
                                com.sun.xml.internal.ws.client.sei,
                                com.sun.xml.internal.ws.developer,
                                com.sun.xml.internal.ws.encoding,
                                com.sun.xml.internal.ws.encoding.fastinfoset,
                                com.sun.xml.internal.ws.encoding.soap,
                                com.sun.xml.internal.ws.encoding.soap.streaming,
                                com.sun.xml.internal.ws.encoding.xml,
                                com.sun.xml.internal.ws.fault,
                                com.sun.xml.internal.ws.handler,
                                com.sun.xml.internal.ws.message,
                                com.sun.xml.internal.ws.message.jaxb,
                                com.sun.xml.internal.ws.message.saaj,
                                com.sun.xml.internal.ws.message.source,
                                com.sun.xml.internal.ws.message.stream,
                                com.sun.xml.internal.ws.model,
                                com.sun.xml.internal.ws.model.soap,
                                com.sun.xml.internal.ws.model.wsdl,
                                com.sun.xml.internal.ws.org.objectweb.asm,
                                com.sun.xml.internal.ws.protocol.soap,
                                com.sun.xml.internal.ws.protocol.xml,
                                com.sun.xml.internal.ws.resources,
                                com.sun.xml.internal.ws.server,
                                com.sun.xml.internal.ws.server.provider,
                                com.sun.xml.internal.ws.server.sei,
                                com.sun.xml.internal.ws.spi,
                                com.sun.xml.internal.ws.streaming,
                                com.sun.xml.internal.ws.transport,
                                com.sun.xml.internal.ws.transport.http,
                                com.sun.xml.internal.ws.transport.http.client,
                                com.sun.xml.internal.ws.transport.http.server,
                                com.sun.xml.internal.ws.util,
                                com.sun.xml.internal.ws.util.exception,
                                com.sun.xml.internal.ws.util.localization,
                                com.sun.xml.internal.ws.util.pipe,
                                com.sun.xml.internal.ws.util.xml,
                                com.sun.xml.internal.ws.wsdl.parser,
                                com.sun.xml.internal.ws.wsdl.writer,
                                com.sun.xml.internal.ws.wsdl.writer.document,
                                com.sun.xml.internal.ws.wsdl.writer.document.http,
                                com.sun.xml.internal.ws.wsdl.writer.document,
                                com.sun.xml.internal.ws.wsdl.writer.document.soap,
                                com.sun.xml.internal.ws.wsdl.writer.document.soap12,
                                com.sun.xml.internal.ws.wsdl.writer.document.xsd,
                                com.sun.xml.internal.messaging.saaj.soap

Similar Messages

  • Consume a restful webservice using plsql

    Hi
    We need to consume a restful webservice and this needs to be implemented using plsql.
    I know that we can use utl_dbws or utl_http to consume SOAP based web services but
    there is not much information on how to consume restful web services.
    kindly let me know if you have information.
    Cheers
    rigel

    851866 wrote:
    Im looking for the opposite scenario where i need to access a restful web service from plsql.Why would a RESTful call be any different from a normal URL call? HTTP is the transport mechanism - and UTL_HTTP is used in PL/SQL as the client side of a HTTP conversation.
    I posted sample code of a how to use PL/SQL as a brower client in {message:id=1925297} - using a pipeline table to demonstrate the contents returned by the web server in response using plain SQL.
    Depending on what the contents is, you can write it into a BLOB (dealing with binary data returned), a CLOB (for XML data for example), or using varchar2 you can for example parse a text/csv response (no need for a pipeline in such a case).
    The only real issue I can see with a RESTful service is URL construction - as the URL becomes "parameterised" and not just the query string itself, or the data contents (name values) in the POST structure.

  • PI Consume Restful Webservices

    Hi,
    I have scenario in which PI needs to consume Restful webservices.
    I am looking at HTTP receiver adapter in which I want to set appropreate action (POST, GET, PUT or DELETE) based on mapping.
    For example I want to DELETE purcahse order TXU-19282. The http request that sends to Restful webservice looks like as follows.
    DELETE /restfulwebservice-war/poservice/TXU-19282 HTTP/1.0
    Connection: close
    Content-Type: text/xml
    Content-Length: 0
    Pragma: no-cache
    Now my question is how do I set set above information on HTTP receiver adapater. I looked at dynamic configuration and could find it useful.
    Also I am interested in finding how do I set both heder and Payload via mapping?
    Please let me know.
    Thank you,
    Balaji

    I dont think, there is an option to mention (POST, GET, PUT or DELETE) in HTTP reciever adapter.
    usually , it is with JDBC adapter.
    Lets wait for someone to answer as well. am not much sure.
    Also I am interested in finding how do I set both heder and Payload via mapping?
    Usually, header can be filled with XSL mapping. payload can also be filled with XSL or else with simple graphical mapping.
    -santosh.

  • Consuming a WebService using OSR (uddi) endpoint

    Hey folks,
    I'm trying to consume a WebService declaratively in my ADF taskflow, using a WebService Proxy connection in my model project, as the guides/tutorials told me to. However, I don't have the final endpoint of the service as it is registered in the OSR (Oracle Service Registry) and all I have is its UDDI key.
    So, in fact, my application must connect to OSR to get the service endpoint based on the uddi key and then resolve the port binding based on that.
    Any ideas on how I can perform this?
    Thanks in advance!

    This article helped me out! So if you came here with the same problem, here's some light!
    http://biemond.blogspot.co.uk/2009_12_01_archive.html

  • How to consume SOAP webservice in to my java/j2ee application

    Hi,
          I am a java developer. how to i consume SAP soap webservice in to my java application.
    scenario : 1
    We are migrating 2 specific java modules in to SAP System.But master details are stored in to my java application database.Those details are require
    to SAP application. So that they provide me WSDL file,  How to i consume soap webservice in to my java application and also, How to i provide master data details to SAP system through SOAP webservice.
    Any body provide me a detail instruction how to integrate SAP Application in to my java application using SOAP webservice. or
    In this scenario i will go for any one open source ESB to consume the soap webservice in to my java application, and provide master data to
    SAP application, can any one guide to me.

    Hi,
    What IDE are you using?, for example with Eclipse i used WSDL2JAVA plugin in this way i converted the WSDL in java classes easily. Depending your development environment you can use different tools that makes easier the integration using the WSDL.
    Regards.

  • How to consume json webservice in abap?

    hello  every one please help me how to consume json format webservice in abap.
    i am new in abap please help me out .
    Thanks&Regards
    ~Ahmad

    hi check this,
    First create a web service in SAP. The blog by Uwe Kunath descibes this clearly. Then create an Xcode project and use the ASIHTTPRequest wrapper to connect to the web service. Parse the response with the KissXML parser. A more out of the box solution is NetWeaver Gateway. It also let you use SAP web services but it also generates iOs code for you. SAP just released a trial version in de download section.
    Example of ASIHTTPRequest
    - (void)getFlightData:(NSString *) selectedDate {
         NSURL *url = [NSURL URLWithString:@"http://abap.sapdev.nl:8000/sap/resources/flights/from/%/to/%/date/20110128?sap-client=001"];
         ASIHTTPRequest *request = [ASIHTTPRequest requestWithURL:url];
         [request setUsername:@"BCUSER"];
         [request setPassword:@"minisap"];
         [request startSynchronous];
         NSError *error = [request error];
         if (!error) {
              NSString *response = [request responseString];
              [self parseXML:response];
    Example of KissXML
    -(void)parseXML:(NSString*)source {
         NSError *error = nil;
         DDXMLDocument *theDocument = [[DDXMLDocument alloc] initWithXMLString:source options:0 error:&error];
         NSArray *results = [theDocument nodesForXPath:@"/asx:abap/asx:values/TAB/BAPISFLDAT" error:&error];
         for (DDXMLElement *flightdetail in results) {
              NSString *airlineid =   [[flightdetail elementForName:@"AIRLINEID"] stringValue];
              NSString *airline =     [[flightdetail elementForName:@"AIRLINE"] stringValue];

  • Consume ABAP Webservice using AJAX javascript

    Hi,
    We created webservice for  ABAP BAPI. And I want to consume this using AJAX javascript.
    But I am getting "Access Denied" javascript error.
    Please let me know how to pass the credentials while trying to consume this webservice
    I tried below code, but its NOT workng
    var URL ="http://hostname/sap/bc/srt/rfc/sap/servicename?sap-client=400&sap-user=testuser&sap-password=testpassword";
    xmlhttprequest.open("POST", URL, true);
    Please let me know your thoughts ...
    Thanks
    Edited by: sona p on Feb 27, 2010 12:18 AM

    Hi,
    Thanks for your response. I did the same as mentioned in the link provided by you. But it is not working . I am still getting "Access denied" javascript error in the second line ( xmlhttprequest.open) . Below is my code.
    var auth = make_base_auth('userid','password');
    xmlhttprequest.open("POST", URL, true);
    xmlhttprequest.setRequestHeader('Authorization', auth);
    xmlhttprequest.setRequestHeader ("Content-Type", "text/xml");
    xmlhttprequest.onreadystatechange = getDataList;
    xmlhttprequest.send(SOAPEnvelope);
    Please let me know your thoughts. Thanks again for your response.

  • Consuming peoplesoft webservices using JSF application gives error

    Hi,
    I am using Jdeveloper 11g to consume a peoplesoft webservice which does the basic datbase operations.
    I have been successful in creating a proxy using the wsdl file and using JAX-WS approach to achieve the same.
    I can connect to the webservice using the proxy client.
    But when i package the proxy( create a jar) and import in my web application (JSF application), i am running into following error.
    <ActionListenerImpl><processAction> com.sun.xml.ws.streaming.XMLStreamReaderException: unexpected XML tag. expected: {http://peoplesoft.com/KCM_WEB_CASE_CI}Get__CompIntfc__KCM_WEB_CASE_CIResponse but found: {http://schemas.xmlsoap.org/ws/2002/xx/secext}Get__CompIntfc__KCM_WEB_CASE_CIResponse
    javax.faces.el.EvaluationException: com.sun.xml.ws.streaming.XMLStreamReaderException: unexpected XML tag. expected: {http://peoplesoft.com/KCM_WEB_CASE_CI}Get__CompIntfc__KCM_WEB_CASE_CIResponse but found: {http://schemas.xmlsoap.org/ws/2002/xx/secext}Get__CompIntfc__KCM_WEB_CASE_CIResponse
         at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102)
         at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
         at javax.faces.component.UICommand.broadcast(UICommand.java:387)
         at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475)
         at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756)
         at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82)
         at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
         at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: com.sun.xml.ws.streaming.XMLStreamReaderException: unexpected XML tag. expected: {http://peoplesoft.com/KCM_WEB_CASE_CI}Get__CompIntfc__KCM_WEB_CASE_CIResponse but found: {http://schemas.xmlsoap.org/ws/2002/xx/secext}Get__CompIntfc__KCM_WEB_CASE_CIResponse
         at com.sun.xml.ws.streaming.XMLStreamReaderUtil.verifyTag(XMLStreamReaderUtil.java:214)
         at com.sun.xml.ws.streaming.XMLStreamReaderUtil.verifyTag(XMLStreamReaderUtil.java:222)
         at com.sun.xml.ws.client.sei.ResponseBuilder$DocLit.readResponse(ResponseBuilder.java:531)
         at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:127)
         at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
         at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:135)
         at $Proxy135.getCompIntfcKCMWEBCASECI(Unknown Source)
         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:597)
         at weblogic.wsee.jaxws.spi.ClientInstance$ClientInstanceInvocationHandler.invoke(ClientInstance.java:363)
         at $Proxy136.getCompIntfcKCMWEBCASECI(Unknown Source)
         at project1.proxy.KCM_WEB_CASE_CISoapClient.getKCMMethod_final(KCM_WEB_CASE_CISoapClient.java:618)
         at login.view.Handler.CRMSearchHandler.getSearchResults(CRMSearchHandler.java:18)
         at login.view.backing.Login.search(Login.java:54)
         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:597)
         at com.sun.el.parser.AstValue.invoke(AstValue.java:157)
         at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
         at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
    I am not sure what else i need to import or rather how to package the proxy classes to get it working.
    Any help will be highly appreciated.
    I even tried creating a webservice proxy in the JSF project instead of importing the jar, yet i am getting the same error, but the irony is that when i run just the proxy class(standalone with main method) i can get access to the webservice.
    Thanks
    Ash
    Edited by: [email protected] on Jun 8, 2010 2:38 PM

    Well,
    There is a issue with analyzer capturing SOAP traffic when using with secure proxies, so that is why you are not seeing any data there.
    And I think if you will try your jax-rpc code again, it might work as there was nothing incorrect in your code, so might be that the whole config was corrupt which was throwing out incorrect error(s).
    About a web service with credentials, you can quickly create one.
    Have a java class like the following:
    import javax.jws.WebService;
    import weblogic.jws.Policy;
    @WebService
    @Policy(uri = "policy:Wssp1.2-2007-Https-UsernameToken-Plain.xml")
    public class Class1 {
    public Class1() {
    super();
    public String sayHello() {
    return "Hi";
    The procy code for this will be something like:
    private static Class1Service class1Service;
    public static void main(String[] args) {
    try {
    class1Service = new Class1Service();
    Class1 class1 = class1Service.getClass1Port();
    Map<String, Object> requestContext = ((BindingProvider) class1).getRequestContext();
    setPortCredentialProviderList(requestContext);
    // Add your code to call the desired methods.
    System.out.println(class1.sayHello());
    } catch (Exception ex) {
    ex.printStackTrace();
    public static void setPortCredentialProviderList(Map<String, Object> requestContext) throws Exception {
    // TODO - Provide the required values
    String username = "weblogic";
    String password = "weblogic1";
    List<CredentialProvider> credList = new ArrayList<CredentialProvider>();
    // Add the necessary credential providers to the list
    credList.add(getUNTCredentialProvider(username, password));
    //credList.add(getBSTCredentialProvider(clientKeyStore, clientKeyStorePassword, clientKeyAlias, clientKeyPassword, serverKeyStore, serverKeyStorePassword, serverKeyAlias, requestContext));
    //credList.add(getSAMLTrustCredentialProvider());
    requestContext.put(WSSecurityContext.CREDENTIAL_PROVIDER_LIST, credList);
    Thanks,
    Vishal

  • Connection issue while accessing a jersey restful webservice using aysynch callback method.

    Hi,
    I am having one consumer and producer application. Producer is a Jersey restful webservice deployed in a tomcat server. Consumer side I am using executor service to create one scheduler which will keep on polling and creates a new Thread where I am making a asynch callback req to the service(Producer). But the problem is after my asynch executor thread will die still I can see one connection in deployed server.
    I used yourkit profiler, I can see one thread in runnable state even when the asynch executor dies.
    I think bec of scheduler still there is a connection between client and service. I wanted to create multiple consumer to process multiple thread but because of thread leakage I am not able to proceed.
    Could you please help me on this?

    Err, close the connection?

  • How to Consume a WebService in JSP DynPage

    Hi Friends,
    We have created a Web Service and We want to Consume that in my JSP Dyn Page.
    Please let me know how to consume the Web Services that are created.
    I am having a WSDL File and need to consume it in Enterprise Portal Applications.
    Thanks in Advance.
    Regards,
    Palani

    Hi Palani,
       Create a Portal Application and access the External Web Service (Say for example, http://api.google.com/GoogleSearch.wsdl ).  Create the Portal Application Object -> Portal Web Service -> Portal WebService from wsdl file -> Client Side -> Enter the Wsdl file as http://api.google.com/GoogleSearch.wsdl -> Select the methods to expose -> Enter the service name, Alias and package name should be a unique one. and finish.
    Create bean to set the values.
    In your JSPDynpage Component enter the following code:
    public void doInitialization(){
       YourServiceName obj=(YourServiceName) PortalRuntime.getRuntimeResources().getService(YourServiceName.KEY);
      MyBean beanObj = new MyBean();
      beanObj.setterMethod(obj.calltheMethodinWSDL());
    And in your JSP page, call the bean getter method.
      It's overview only, you can do it.
    Regards,
    Venkatesh. K

  • How to call the webservice using ADF Bindings

    Hi,
    I have created a Data control of the webservice using the WSDL Url. (Web Service is secured and so i have given the security configurations)
    Webservice works fine when i drag and drop that in to a jspx page.
    Now i want to call the service from a java class so that i can modify the data a bit. ( Tried with Webservice client and proxy and it is not working)
    Please provide me with some link or solution as how to achieve this.
    Thanks,
    Hari

    You need to have the method binding in the page that calls the Web service - otherwise you can't use the binding layer.
    If you don't want to use the binding layer you can have your managed bean just call out to the Web service directly - you can use JDeveloper's Web service proxy creation wizard to get the code for this.
    If you want to call the Web service through binding outside of the page you can also drag the method into a taskflow as a method call.

  • How to consume an webservice in XI

    Hi,
      I need to consume an webservice in XI, can any one please guide me in this.
    Regards,
    Lakshmi

    HI
      I  guess you want to consume webservice in webdynpro from XI ,  if that is the case
      may be you can ask your XI consultant to provide you a WSDL url , and expose that as
    webservice using adaptive webservice model and if you are using  EP 7.0 you have to create Destinations
    in the visual admin tool ->webservice security-> dynamic proxy
      and if you are using CE 7.1 then you can create the destination in
    NWA->SOA management -> Destination template 
      and for creating destination you can search SDN there are many thread available
    /people/katharina.seiz/blog/2008/12/11/web-service-150-pi-150-web-service-scenario--a-complete-walkthrough
    check the above link this may give you some idea
    Thanks.
    Edited by: murali krishna  reddy on May 4, 2009 9:36 AM

  • How to consume J2EE webservice in Oracle BPEL

    Dear All,
    Can any one please tell me that how to consume J2EE web service in Oracle BPEL. What is local registry. How am able to register my web service in to the local registry. Please suggest me.
    Thanks,
    Rajesh

    Hi,
    What IDE are you using?, for example with Eclipse i used WSDL2JAVA plugin in this way i converted the WSDL in java classes easily. Depending your development environment you can use different tools that makes easier the integration using the WSDL.
    Regards.

  • How to consume a webservice from sap crm

    Hi All,
    How to consume and access an external webservice from sap crm?
    Suggest me.
    Regards,
    Sanjani
    Edited by: Sanjani on Dec 6, 2010 3:09 PM
    Edited by: Sanjani on Dec 10, 2010 1:08 PM

    Please check the wiki link mentioned below. It will help you to an extent.
    http://wiki.sdn.sap.com/wiki/display/CRM/CreatingWebServiceinSAP+CRM
    Rg,
    Harshit

  • How to create a webservice using a WSDL document !!!

    I have tried to create webservice using WSDL but i dont need any document ... is there any document where i can see a thorough procedure to develope it

    Hi,
    go to tools in ID and click define webservices
    It will show a window where u have to give interface name and name space and u have to provide soap url their
    http://<port>/XISOAPAdapter/MessageServlet?channel=:service:channel
    then a webservice is created....
    thanq
    krishna
    Edited by: krishnachitanya siddavattam on Mar 6, 2008 10:51 AM

Maybe you are looking for