Web Services with Apache Axis plugin Weblogic

Hi,
I am a newbie to Web Services & Apache Axis. I have plugged in Apache Axis with
Weblogic 6.1. I wanted to know whether an architecture of the following is possible.
Web Services published on Apache Axis wrapped on SessionBeans on Weblogic 6.1.
Also can I get some docs, samples that can help me.
Any help is appreciated.
Meghna

Hi Meghna,
hmmm...if you are going to start off with webservices, why not go with
the very best available: WLS 8.1 has:
- much better schema coverage,
- rpc, doc-literal and doc-literal-wrapped style
- async client
- jms transport
- security and RM
- many new ant tasks
See the full list: http://edocs.bea.com/wls/docs81/webservices.html
All the features...plus outstanding performance and our award winning
support.
Bruce
Meghna Sinha wrote:
>
Hi,
I am a newbie to Web Services & Apache Axis. I have plugged in Apache Axis with
Weblogic 6.1. I wanted to know whether an architecture of the following is possible.
Web Services published on Apache Axis wrapped on SessionBeans on Weblogic 6.1.
Also can I get some docs, samples that can help me.
Any help is appreciated.
Meghna

Similar Messages

  • Making Asynchronous Web Services in apache axis

    Hi all,
    I am willing to make an asynchronous web service using apache axis.Can I use Tomcat 5.x or I have to use WebLogic only.Please help.
    With regards,
    ajse

    Hi all,
    I really need to know this,becouse I am running out of time.Can anyone pls
    let me know about this?
    With regards,
    ajse

  • Web services with Apache plugin

    Hi!
    I am setting up a weblogic 8.1 env. were I have Apache as HTTP server working as proxy for external (outside the company) calls. Is it going to work out-of-the-box for Web Services as well or is there anything I need to think about?
    Thx,
    Iggy

    Hi Meghna,
    hmmm...if you are going to start off with webservices, why not go with
    the very best available: WLS 8.1 has:
    - much better schema coverage,
    - rpc, doc-literal and doc-literal-wrapped style
    - async client
    - jms transport
    - security and RM
    - many new ant tasks
    See the full list: http://edocs.bea.com/wls/docs81/webservices.html
    All the features...plus outstanding performance and our award winning
    support.
    Bruce
    Meghna Sinha wrote:
    >
    Hi,
    I am a newbie to Web Services & Apache Axis. I have plugged in Apache Axis with
    Weblogic 6.1. I wanted to know whether an architecture of the following is possible.
    Web Services published on Apache Axis wrapped on SessionBeans on Weblogic 6.1.
    Also can I get some docs, samples that can help me.
    Any help is appreciated.
    Meghna

  • Web services with Apache CXF

    :confused; Has anyone worked with apache CXF as a backend web
    service. I loaded the wsdl in with the data import tool and it did
    grab the wsdl correctly. I ended up running a network sniffer to
    see if the actual values being passwd to the backend were being
    done correctly. However my apache CXF puked with null values. Is
    the data import tool ready for prime time ? Anyone ?
    Thanks
    Here is the dump of the network.
    0x0350: 6164 6420 786d 6c6e 733a 746e 733d 2268
    add.xmlns:tns="h
    0x0360: 7474 703a 2f2f 4465 6661 756c 744e 616d
    ttp://DefaultNam
    0x0370: 6573 7061 6365 223e 0a20 2020 2020 203c
    espace">.......<
    0x0380: 746e 733a 6164 643e 0a20 2020 2020 2020
    tns:add>........
    0x0390: 203c 746e 733a 6172 6730 3e35 3c2f 746e
    .<tns:arg0>5</tn
    0x03a0: 733a 6172 6730 3e0a 2020 2020 2020 2020
    s:arg0>.........
    0x03b0: 3c74 6e73 3a61 7267 313e 363c 2f74 6e73
    <tns:arg1>6</tns
    0x03c0: 3a61 7267 313e 0a20 2020 2020 203c 2f74
    :arg1>.......</t
    0x03d0: 6e73 3a61 6464 3e0a 2020 2020 3c2f 746e
    ns:add>.....</tn
    0x03e0: 733a 6164 643e 0a20 203c 2f53 4f41 502d
    s:add>...</SOAP-
    0x03f0: 454e 563a 426f 6479 3e0a 3c2f 534f 4150
    ENV:Body>.</SOAP
    0x0400: 2d45 4e56 3a45 6e76 656c 6f70 653e
    -ENV:Envelope>

    :confused; Has anyone worked with apache CXF as a backend web
    service. I loaded the wsdl in with the data import tool and it did
    grab the wsdl correctly. I ended up running a network sniffer to
    see if the actual values being passwd to the backend were being
    done correctly. However my apache CXF puked with null values. Is
    the data import tool ready for prime time ? Anyone ?
    Thanks
    Here is the dump of the network.
    0x0350: 6164 6420 786d 6c6e 733a 746e 733d 2268
    add.xmlns:tns="h
    0x0360: 7474 703a 2f2f 4465 6661 756c 744e 616d
    ttp://DefaultNam
    0x0370: 6573 7061 6365 223e 0a20 2020 2020 203c
    espace">.......<
    0x0380: 746e 733a 6164 643e 0a20 2020 2020 2020
    tns:add>........
    0x0390: 203c 746e 733a 6172 6730 3e35 3c2f 746e
    .<tns:arg0>5</tn
    0x03a0: 733a 6172 6730 3e0a 2020 2020 2020 2020
    s:arg0>.........
    0x03b0: 3c74 6e73 3a61 7267 313e 363c 2f74 6e73
    <tns:arg1>6</tns
    0x03c0: 3a61 7267 313e 0a20 2020 2020 203c 2f74
    :arg1>.......</t
    0x03d0: 6e73 3a61 6464 3e0a 2020 2020 3c2f 746e
    ns:add>.....</tn
    0x03e0: 733a 6164 643e 0a20 203c 2f53 4f41 502d
    s:add>...</SOAP-
    0x03f0: 454e 563a 426f 6479 3e0a 3c2f 534f 4150
    ENV:Body>.</SOAP
    0x0400: 2d45 4e56 3a45 6e76 656c 6f70 653e
    -ENV:Envelope>

  • Problem with a  web service with Jbuilder 2005 and Weblogic 8.1

    Hi,
    i�m trying to create a web-service using Jbuilder 2005 Enterprise and Weblogic 8.1. It is a very simple web-service, come kinda "Hello World".
    In the last step, after deploying my "ApplicatioModule1", i get this error:
    "Unable to connect to server t3://localhost:7001 as user weblogic.
    Reason: javax.naming.CommunicationException. Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
         java.net.ConnectException: Connection refused: connect; No available router to destination
         at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
         at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:291)
         at weblogic.jndi.Environment.getContext(Environment.java:164)
         at weblogic.jndi.Environment.getInitialContext(Environment.java:143)
         at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(MBeanHomeTool.java:157)
         at weblogic.Deployer.runBody(Deployer.java:555)
         at weblogic.utils.compiler.Tool.run(Tool.java:146)
         at weblogic.utils.compiler.Tool.run(Tool.java:103)
         at weblogic.Deployer.main(Deployer.java:399)
    Check option -adminurl, -username and -password. "
    I dont know why i get this error. I think the weblogic server is properly configured and running.
    Anybody can help me?? Thx.

    i have found the solution to the problem myself. I only had to execute this command file startWebLogic.cmd which is placed in this default installation directory C:\bea\user_projects\domains\mydomain in order to put the server listening to ports.
    i hope anybody with the same problem could fix it by reading this post.

  • JDeveloper 10.1.3.3.0:  Problem with Apache Axis 1.4 response handler

    I have written both a request handler and a response handler for calling a web service using Apache Axis 1.4.
    The request handler is working, but when the web service returns a soap fault, my response handler is not getting called (I have set breakpoints in both the "onFault" and "invoke" methods of the response handler, which extends "org.apache.axis.handlers.BasicHandler").
    Here is what my WSDD looks like:
    <deployment xmlns="http://xml.apache.org/axis/wsdd/" xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
       <transport name="http" pivot="java:org.apache.axis.transport.http.HTTPSender"/>
       <globalConfiguration>
          <requestFlow>
             <handler name="MyRequestHandler" type="java:com.mycompany.MyRequestHandler"/>
          </requestFlow>
          <responseFlow>
             <handler name="MyResponseHandler" type="java:com.mycompany.MyResponseHandler"/>
          </responseFlow>
       </globalConfiguration>
    </deployment>Thanks!
    Jonathan
    Edited by: user1993443 on Mar 6, 2009 9:03 AM

    The OC4J version with comes in jdeveloper has instaled ADF, is a version prepared to test your aplications and well ready for that.
    The OC4J standalone version is this [http://www.oracle.com/technology/tech/java/oc4j/index.html] and is downloaded separately here [http://www.oracle.com/technology/software/products/ias/htdocs/utilsoft.html] .
    The structured folder of the OC4J standAlone is never is contended inside Jdeveloper folder and when you try to install ADF with ADF runtime installer you only need to map to your OC4J folder base.
    Good Luck.

  • Web services with Jdeveloper using weblogic as server

    Hi,
    I try to test creating PL/SQL web services by using a connection hosted by weblogic server instead of OC4J. The problem is what I try to publish a package of the database in the second stage when it asks for the connection to use, in the list I don't found the connection I create to weblogic . It presents as choice only connections used the server OC4J.
    I do not Know if it is possible to publish a package as web service by using weblogic server connection, and how to do it.
    can anyone help me please .
    Nawal

    Web services can only be published to BEA if you install Apache SOAP on BEA and use the Apache SOAP option of JDeveloper. The J2EE Web Services implementation framework is specific to Oracle9iAS.
    The PL/SQL Web Services server implementation is based on the J2EE Web Services option and as a result is not really portable to BEA.
    To publish a PL/SQL Web service on BEA with JDeveloper you would have to write the Java wrapper code to invoke the stored procedure using standard JDBC and then publish that Java class as a Web service using Apache SOAP. Then if you had Apache SOAP installed on BEA you would be set.
    Portability of Web services implementations is a big feature coming with JAX-RPC - currently what most vendors have is interoperability between implementations because of things like SOAPBuilders and WS-I. When JAX-RPC becomes part of J2EE 1.4 roughly in June and vendors start putting out implementations on it you should get closer to portability.
    In the meantime, the easiest way to get portability is to use the same SOAP server on both servers - Apache SOAP is a good example.
    Hope this helps.
    Mike

  • Weblogic - a web service with java.lang.Object parameter

    hi all,
    i'm creating a web service with a java.lang.Object parameter.
    my question is as follows:
    when a client calls the web service, how to i get the soap message object and convert it to soap message string using the parameter?
    thanks,
    alex

    Here's some code from one of the Axis samples, this shows the basic process of making a call:
    package samples.message;
    import org.apache.axis.client.Service;
    import org.apache.axis.client.Call;
    import org.apache.axis.message.SOAPBodyElement;
    import org.apache.axis.utils.Options;
    import org.apache.axis.utils.XMLUtils;
    import org.w3c.dom.Element;
    import java.net.URL;
    import java.util.Vector;
    public class TestMsg {
    public String doit(String[] args) throws Exception {
    Options opts = new Options(args);
    opts.setDefaultURL("http://localhost:8080/axis/services/MessageService");
    Service service = new Service();
    Call call = (Call) service.createCall();
    call.setTargetEndpointAddress( new URL(opts.getURL()) );
    SOAPBodyElement[] input = new SOAPBodyElement[2];
    input[0] = new SOAPBodyElement(XMLUtils.StringToElement("urn:foo",
    "e1", "Hello"));
    input[1] = new SOAPBodyElement(XMLUtils.StringToElement("urn:foo",
    "e1", "World"));
    Vector elems = (Vector) call.invoke( input );
    SOAPBodyElement elem = null ;
    Element e = null ;
    elem = (SOAPBodyElement) elems.get(0);
    e = elem.getAsDOM();
    String str = "Res elem[0]=" + XMLUtils.ElementToString(e);
    elem = (SOAPBodyElement) elems.get(1);
    e = elem.getAsDOM();
    str = str + "Res elem[1]=" + XMLUtils.ElementToString(e);
    return( str );
    public static void main(String[] args) throws Exception {
    String res = (new TestMsg()).doit(args);
    System.out.println(res);

  • Web services with servicegen i Weblogic 7

    I am trying to create web services with Weblogic's tool servicegen and
    ANT. It works great until I have a web service method that return a PK
    class of an EJB. I get the error "Error: bean property and public
    field found with the same name: id" (full stacktrace below). After
    some investigating I found out that it was my PK class that was the
    bad guy. But my PK class MUST have the field "id" public, otherwise
    ejbc complains...
    Am I doing anything wrong or does anyone have a solution?
    /Weasel
    webservices:
    [servicegen] Generating service "HelloWorldEJB" ...
    [servicegen] Generating XML types and serializers from ejb-jar
    (E:\java\projects\CMP20CMR-xdoclet\build\ejb\weblogic-ejb\samples-ejb.jar)
    [servicegen] weblogic.xml.schema.binding.BindingException: Error: bean
    property and public field found with the same name: id
    [servicegen]      at weblogic.ant.taskdefs.webservices.autotype.AutoTypeTask.execute(AutoTypeTask.java:356)
    [servicegen]      at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.generateService(ServiceGenTask.java:248)
    [servicegen]      at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.execute(ServiceGenTask.java:141)
    [servicegen]      at org.apache.tools.ant.Task.perform(Task.java)
    [servicegen]      at org.apache.tools.ant.Target.execute(Target.java)
    [servicegen]      at org.apache.tools.ant.Target.performTasks(Target.java)
    [servicegen]      at org.apache.tools.ant.Project.executeTarget(Project.java)
    [servicegen]      at org.apache.tools.ant.Project.executeTargets(Project.java)
    [servicegen]      at org.apache.tools.ant.Main.runBuild(Main.java)
    [servicegen]      at org.apache.tools.ant.Main.start(Main.java)
    [servicegen]      at org.apache.tools.ant.Main.main(Main.java)
    [servicegen] --- Nested Exception ---
    [servicegen] weblogic.xml.schema.binding.BindingException: Error: bean
    property and public field found with the same name: id
    [servicegen]      at weblogic.ant.taskdefs.webservices.autotype.ComponentAutoTyper.mapComponent(ComponentAutoTyper.java:157)
    [servicegen]      at weblogic.ant.taskdefs.webservices.autotype.EJBAutoTyper.run(EJBAutoTyper.java:100)
    [servicegen]      at weblogic.ant.taskdefs.webservices.autotype.AutoTypeTask.execute(AutoTypeTask.java:350)
    [servicegen]      at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.generateService(ServiceGenTask.java:248)
    [servicegen]      at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.execute(ServiceGenTask.java:141)
    [servicegen]      at org.apache.tools.ant.Task.perform(Task.java)
    [servicegen]      at org.apache.tools.ant.Target.execute(Target.java)
    [servicegen]      at org.apache.tools.ant.Target.performTasks(Target.java)
    [servicegen]      at org.apache.tools.ant.Project.executeTarget(Project.java)
    [servicegen]      at org.apache.tools.ant.Project.executeTargets(Project.java)
    [servicegen]      at org.apache.tools.ant.Main.runBuild(Main.java)
    [servicegen]      at org.apache.tools.ant.Main.start(Main.java)
    [servicegen]      at org.apache.tools.ant.Main.main(Main.java)
    [servicegen] --- Nested Exception ---
    [servicegen] weblogic.xml.schema.binding.BindingException: Error: bean
    property and public field found with the same name: id
    [servicegen]      at weblogic.xml.schema.binding.internal.codegen.JavaInspector.checkForFieldConflict(JavaInspector.java:384)
    [servicegen]      at weblogic.xml.schema.binding.internal.codegen.JavaInspector.addPropertiesToScalar(JavaInspector.java:345)
    [servicegen]      at weblogic.xml.schema.binding.internal.codegen.JavaInspector.fillDescriptor(JavaInspector.java:152)
    [servicegen]      at weblogic.xml.schema.binding.internal.codegen.JavaInspector.getDescriptor(JavaInspector.java:115)
    [servicegen]      at weblogic.xml.schema.binding.internal.codegen.JavaInspector.createDescriptorForClass(JavaInspector.java:90)
    [servicegen]      at weblogic.xml.schema.binding.internal.codegen.Compiler.compile(Compiler.java:121)
    [servicegen]      at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.mapClass(XSDTypeMappingBuilder.java:88)
    [servicegen]      at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.mapClass(XSDTypeMappingBuilder.java:101)
    [servicegen]      at weblogic.xml.schema.binding.internal.TypeMappingBuilderBase.addMapping(TypeMappingBuilderBase.java:176)
    [servicegen]      at weblogic.ant.taskdefs.webservices.autotype.ComponentAutoTyper.addMapping(ComponentAutoTyper.java:85)
    [servicegen]      at weblogic.ant.taskdefs.webservices.autotype.ComponentAutoTyper.mapComponent(ComponentAutoTyper.java:113)
    [servicegen]      at weblogic.ant.taskdefs.webservices.autotype.EJBAutoTyper.run(EJBAutoTyper.java:100)
    [servicegen]      at weblogic.ant.taskdefs.webservices.autotype.AutoTypeTask.execute(AutoTypeTask.java:350)
    [servicegen]      at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.generateService(ServiceGenTask.java:248)
    [servicegen]      at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.execute(ServiceGenTask.java:141)
    [servicegen]      at org.apache.tools.ant.Task.perform(Task.java)
    [servicegen]      at org.apache.tools.ant.Target.execute(Target.java)
    [servicegen]      at org.apache.tools.ant.Target.performTasks(Target.java)
    [servicegen]      at org.apache.tools.ant.Project.executeTarget(Project.java)
    [servicegen]      at org.apache.tools.ant.Project.executeTargets(Project.java)
    [servicegen]      at org.apache.tools.ant.Main.runBuild(Main.java)
    [servicegen]      at org.apache.tools.ant.Main.start(Main.java)
    [servicegen]      at org.apache.tools.ant.Main.main(Main.java)
    BUILD FAILED
    E:\java\projects\CMP20CMR-xdoclet\script\build.xml:498:
    weblogic.xml.schema.binding.BindingException: Error: bean property and
    public field found with the same name: id

    Web services can only be published to BEA if you install Apache SOAP on BEA and use the Apache SOAP option of JDeveloper. The J2EE Web Services implementation framework is specific to Oracle9iAS.
    The PL/SQL Web Services server implementation is based on the J2EE Web Services option and as a result is not really portable to BEA.
    To publish a PL/SQL Web service on BEA with JDeveloper you would have to write the Java wrapper code to invoke the stored procedure using standard JDBC and then publish that Java class as a Web service using Apache SOAP. Then if you had Apache SOAP installed on BEA you would be set.
    Portability of Web services implementations is a big feature coming with JAX-RPC - currently what most vendors have is interoperability between implementations because of things like SOAPBuilders and WS-I. When JAX-RPC becomes part of J2EE 1.4 roughly in June and vendors start putting out implementations on it you should get closer to portability.
    In the meantime, the easiest way to get portability is to use the same SOAP server on both servers - Apache SOAP is a good example.
    Hope this helps.
    Mike

  • Invoking a AXIS Web Service with a Java object as input argument

    Hi
    I've been trying to execute a bpel process that invokes a web service deployed through axis.
    This web service takes a java object as input argument as opposed to data types that are directly mapped to java types through the SOAP engine.
    I deployed and tested the service outside of BPEL using a test client class. Everything works well.
    When I try to configure the "Assign" and "Invoke" activities so that service can be invoked, I cannot see the data structure through the variable picker and I see the following message:
    "The element {urn:ComplexTypeWebService}TimeSheetBean is not know to the schema container. Perhaps a schema file that uses it needs to include or import its definition.There mat also be an XML schema issue (non resolvable schema) which prevents {urn:ComplexTypeWebService}TimeSheetBean from being seen by the schema processor."
    Is there any example that demonstrates how to invoke an axis web service in such scenario? What am I doing wrong?
    Please, let me know.

    The passing of Java objects in and out of a web service is NOT supported. variables must be xml documents defined by a XML schema. In my opinion, missing Java object and WSDL is not a good idea. -Edwin

  • Consuming Synchronous RESTful Web Service with PI

    Dear experts,
    i have a scenario for consuming RESTful web service.
    i have followed all the steps showed in the following link for configuring my interface.
    http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/08/11/calling-synchronous-restful-web-service-with-pi--i
    but still i am facing issues at the communication channel level, the trace of the communication channel is as follows
    Error While Sending Message: Additional error text from response: com.sap.engine.interfaces.messaging.api.exception.MessagingException: org.apache.axis.ConfigurationException: adapter is null org.apache.axis.ConfigurationException: adapter is null at com.sap.aii.adapter.axis.modules.HandlerCore.process(HandlerCore.java:60) at com.sap.aii.adapter.axis.modules.HandlerBean.process(HandlerBean.java:86) at sun.reflect.GeneratedMethodAccessor602.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at com.sun.proxy.$Proxy3284.process(Unknown Source) at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:264) at sun.reflect.GeneratedMethodAccessor544.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at com.sun.proxy.$Proxy646.process(Unknown Source) at com.sap.aii.af.app.listener.AFWListenerBean.onMessage(AFWListenerBean.java:422) at sun.reflect.GeneratedMethodAccessor558.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at com.sun.proxy.$Proxy603.onMessage(Unknown Source) at com.sap.engine.messaging.impl.spi.ServicesImpl.deliver(ServicesImpl.java:362) at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1091) at com.sap.engine.messaging.impl.core.queue.consumer.RequestConsumer.onMessage(RequestConsumer.java:75) at com.sap.engine.messaging.impl.core.queue.Queue.run(Queue.java:1017) at com.sap.engine.messaging.runtime.MSWorkWrapper.run(MSWorkWrapper.java:58) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
    i have also attached screen shots of module tab of my SOAP(Axis) adapter
    regards,
    sushant

    Hi Sushant
    Check the question 11.I am getting org.apache.axis.ConfiguraitonException: adapter is null in this note 1039369 - FAQ XI Axis Adapter
    (you will find all the answers in the attachment section)
    Regards.

  • Consuming SAP web services with tables

    I'm doing kind of feasibility study on consuming SAP web
    services from CF.
    So far so good, but I'm stuck dealing with tables
    (import/export parameters in SAP world).
    I know how to receive a table object from SAP functions:
    * With Apache Axis v1.2: pass an empty CF structure as a
    parameter
    * With Apache Axis v1.4: pass an empty CF array as a
    parameter
    Then the parameter is filled with data (replaced with Java
    object) and we can just parse the object accordingly.
    My question here is whether or not we can pass a *table with
    actual records*.
    For example, I want to pass a table with multiple records to
    update DB records under SAP.
    I tried passing (1) CF array of structure and (2) Java
    ArrayList with no chance.
    The web service call itself completes without errors (no
    method signature error), but the SAP function seems to see the
    parameter as an empty table.
    Anyone has been successful with this case?
    Any suggestion would be much appreciated.

    Thanks Dan,
    Unfortunately CF query object didn't work either.
    Now I'm looking at the code generated by Flex Builder to see
    how the classes are like ;-)
    It's just an ArrayCollection of simple value objects
    (representing a row).
    So CF array of structure or Java ArrayList looks a reasonable
    approach though they don't at all.

  • Compile build.xml with Ant for web service with annotations

    Hi Friends,
    I have a web service with annotations, using javax.annotation.PostConstruct, and javax.annotation.PreDestroy.
    I have a build.xml to create a EAR for this web service.
    When I run the ant task, the build complete successfully but the .war file cannot be deployed on the WLS server. Taking a closer look, I see that the required files such as, webservices.xml, weblogic.xml, weblogic-webservices.xml, Provision.wsdl files are not generated.
    Following is the build.xml file:
    <?xml version="1.0" encoding="windows-1252" ?>
    <project default="jwsc">
    <property file="build.properties"/>
    <property name="weblogic.jar.classpath"
    value="C:/bea_jDev/wlserver_10.3/server/lib"/>
    <property name="oimclient.jar.classpath"
              value="C:/_data/Project_Dc/OIM_jars" />
         <property name="com.jar.classpath" value="C:/JDeveloper/mywork/Service_Test/lib" />
    <taskdef name="jwsc" classname="weblogic.wsee.tools.anttasks.JwscTask">
    <classpath>
    <path id="weblogic.classpath">
    <pathelement path="WEBLOGIC_HOME"/>
    <fileset dir="${weblogic.jar.classpath}">
    <include name="**/*.jar"/>
    </fileset>
    </path>
    </classpath>
    </taskdef>
    <target name="all" depends="clean,build-service,deploy"></target>
    <target name="build-service">
         <jwsc srcdir="${src.home}" destdir="ear_directory" >
    <classpath>
    <path id="oim.classpath">
    <pathelement path="OIM_HOME"/>
    <fileset dir="${oimclient.jar.classpath}">
    <include name="**/*.jar"/>
    </fileset>
    <fileset dir="${com.jar.classpath}">
    <include name="**/*.jar"/>
    </fileset>
    </path>
    </classpath>
    <jws file="${jws.home}" type="JAXWS" />
    </jwsc>
    </target>
    <target name="deploy">
    <!--add wldeploy task here -->
    </target>
    <target name="clean">
    <delete dir="output" />
    </target>
    </project>
    Can you please point out what else is to be done and where exactly am I going wrong in writing the build.xml file.
    Let me know if some else information is required.

    This is what I get when I run the ant task:
    Buildfile: C:\JDeveloper\mywork\ProvisioningService_Test2\Provision\resource\build.xml
    build-service:
    [jwsc] JWS: processing module /com/fox/provision/webservice/endpoint/impl/ProvisionEndPointImpl
    [jwsc] Parsing source files
    [jwsc] Parsing source files
    [jwsc] 1 JWS files being processed for module /com/.../provision/webservice/endpoint/impl/ProvisionEndPointImpl
    [jwsc] [JAM] Warning: failed to resolve class org.apache.xmlbeans.XmlObject
    [jwsc] [JAM] Warning: failed to resolve class com.bea.xml.XmlObject
    [jwsc] [JAM] Warning: failed to resolve class javax.xml.rpc.holders.Holder
    [jwsc] JWS: C:\..\...\..\...\code\ProvisioningService\src\com\...\provision\webservice\endpoint\impl\..EndPointImpl.java Validated.
    [jwsc] Processing 1 JAX-WS web services...
    [jwsc] warning: Specified AnnotationProcessorFactory, 'com.sun.istack.ws.AnnotationProcessorFactoryImpl', not found on search path.
    warning: No annotation processors found but annotations present.
    2 warnings
    [jwsc] Compiling 2 source files to C:\DOCUME~1\....\LOCALS~1\Temp\_lsgijm
    [jwsc] Building jar: C:\..\...\..\...\code\ProvisioningService\src\com\...\provision\webservice\deploy\ear_directory\com\fox\provision\webservice\endpoint\impl\...EndPointImpl.war
    [jwsc] Created JWS deployment outputFile: C:\..\...\..\...\code\ProvisioningService\src\com\...\provision\webservice\deploy\ear_directory\....\...\provision\webservice\endpoint\impl\..EndPointImpl.war
    [jwsc] [EarFile] Application File : C:\..\...\..\...\code\ProvisioningService\src\com\.....\provision\webservice\deploy\ear_directory\META-INF\application.xml
    [AntUtil.deleteDir] Deleting directory C:\DOCUME~1\....\LOCALS~1\Temp\_lsgijm
    BUILD SUCCESSFUL
    Total time: 7 seconds
    Due to some limitations, I edited the path in the build.xml files.
    Please let me know what can be done. Thanks.
    Edited by: user9112073 on Nov 22, 2011 9:52 PM

  • Web services - JAX-RPC/Axis/OC4J

    Hi,
    We are planning to expose some of J2EE applications as web service. It is based on JAX-RPC 1.0. I have checked it with Apache-Axis without changing any code and it worked. Will it work in OC4J without any code changes?
    1. Does OC4J or Oracle SOAP server supports(or implements) JAX-RPC?
    2. Do we need to change any code?
    rgds
    Bala Murali

    Right now we have a JAX-RPC 1.1 with JSR 109 support preview here on OTN at - this came out at OracleWorld:
    http://otn.oracle.com/tech/java/oc4j/1003/content_preview.html
    The target production date is summer 2004. There are also plans to do another drop of this preview with updated support later this year and possibly again before the production release.
    We have quite a lot of functionality that we are targetting to flesh out our Web services support in the areas of reliability, orchestration, transactions and security.
    Mike.

  • Running the Web Crawler with a new plugin (sample HTMLMetatagFilter)

    Hi,
    I tried the steps described from the guide: http://docs.oracle.com/cd/E40518_01/ias.310/ias_webcrawler/toc.htm#Running%20the%20Sample%20Web%20Crawler%20Plugin
    These are the steps that I perform:
    1. Open the sample plugin project with Eclipse
    2. Build the sample plugin from Eclipse
    https://dl.dropboxusercontent.com/u/21502321/Endeca/Captura.PNG
    3. Add the pluging to the IAS lib directory (directory called with the same name of the jar, filter-htmlmetatags, which contains the jar file generated and the plugin.xml file)
    4. Activate the plugin for the Web Crawler (copy the plugin.includes and plugin.excludes properties from default.xml to site.xml in both polite-crawl and non-polite-crawl directories)
    5. Run the Web Crawler with a new plugin (sample plugin from the guide called HTMLMetatagFilter)
    And when I run the web crawler I get the follow error:
    c:\Oracle\Endeca\IAS\3.1.0\bin>web-crawler.bat -c c:\Oracle\Endeca\IAS\workspace\conf\web-crawler\polite-crawl -d 0 -s c:\Oracle\Endeca\IAS\workspace\conf\web-crawler\default\endeca.lst
    INFO    2013-12-03 20:18:46,104 0       com.endeca.eidi.web.Main        [main]
    Reading seed URLs from: c:\Oracle\Endeca\IAS\workspace\conf\web-crawler\default\endeca.lst
    INFO    2013-12-03 20:18:46,104 0       com.endeca.eidi.web.Main        [main]
    Seed URLs: [http://www.oracle.com/]
    ERROR   2013-12-03 20:18:46,354 250     com.endeca.eidi.web.Main        [main]
    Crawler failed on crawler initialization. Shutting down.
    java.lang.UnsupportedClassVersionError: com/endeca/eidi/web/parse/HTMLMetatagFilter : Unsupported major.minor version 51.0
            at java.lang.ClassLoader.defineClass1(Native Method)
            at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
            at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
            at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
            at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
            at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
            at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
            at java.security.AccessController.doPrivileged(Native Method)
            at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
            at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
            at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
            at org.apache.nutch.plugin.Extension.getExtensionInstance(Extension.java:156)
            at org.apache.nutch.parse.ParseFilters.getExtensionList(ParseFilters.java:47)
            at com.endeca.eidi.web.process.ExtensionInstances.<init>(ExtensionInstances.java:52)
            at org.apache.nutch.parse.ParseFilters.<init>(ParseFilters.java:33)
            at com.endeca.eidi.web.UrlProcessor.<init>(UrlProcessor.java:82)
            at com.endeca.eidi.web.Crawler.<init>(Crawler.java:81)
            at com.endeca.eidi.web.Main.main(Main.java:140)
    Crawler failed on crawler initialization.
    java.lang.UnsupportedClassVersionError: com/endeca/eidi/web/parse/HTMLMetatagFilter : Unsupported major.minor version 51.0
            at java.lang.ClassLoader.defineClass1(Native Method)
            at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
            at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
            at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
            at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
            at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
            at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
            at java.security.AccessController.doPrivileged(Native Method)
            at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
            at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
            at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
            at org.apache.nutch.plugin.Extension.getExtensionInstance(Extension.java:156)
            at org.apache.nutch.parse.ParseFilters.getExtensionList(ParseFilters.java:47)
            at com.endeca.eidi.web.process.ExtensionInstances.<init>(ExtensionInstances.java:52)
            at org.apache.nutch.parse.ParseFilters.<init>(ParseFilters.java:33)
            at com.endeca.eidi.web.UrlProcessor.<init>(UrlProcessor.java:82)
            at com.endeca.eidi.web.Crawler.<init>(Crawler.java:81)
            at com.endeca.eidi.web.Main.main(Main.java:140)
    I do not understand why this error appears and why there is a problem with version?? How can I make this sample work?
    Note: this is my configuration system:
    * OEID 3.1
    * IAS installed with Jetty
    * Windows 7 x64
    * Any server running (endeca_server_domain, endeca_studio_domain, endeca_ps_domain)
    * Endeca IAS service running

    I'm using Java 6 update 43 for all Endeca 3.1 products, because is the recomended version to use. I did an installation with Java 7u45 in other machine and Endeca did not works well. (https://forums.oracle.com/thread/2607872)
    But I know when is installed the Integrator, it has integrated Java 7. And I think when I generate the .jar file from the Integrator, it has data with Java 7, so, when I run the Web Crawler with this plugin from the command prompt of Windows, the crawler Installation works with Java 6 (which I already installed).
    So, what should I do if all endeca 3.1 (except Integrator) has to work with java 6u43 and the Integrator generates files with java 7?

Maybe you are looking for