Expose ejb3 as jaxws web service

Dear,
I want to expose my ejb3 stateless sessionbean as a jaxws web service (in order to have versioning for production redeployment high availability). I followed these docs a bit: http://e-docs.bea.com/wls/docs92/webserv/jws.html
excerpt of my class :
@Session(ejbName="myWSBean")
@MethodIsolationLevelPattern(pattern="*", isolationLevel=IsolationLevel.TRANSACTION_READ_COMMITTED)
@JndiName(remote="...")
@RoleMapping(principals="MYUSER", roleName="MYUSER")
@TransactionAttribute(value=TransactionAttributeType.REQUIRED)
@Stateless
@WebService(name="MyServicePort", serviceName="MyService",
targetNamespace="http://.../.../MyInterfaceService")
public class MyWSBean implements SessionBean{
When I try to build the web service with the jws ant task, I get following errors:
[jwsc] [ERROR] - The annotation weblogic.ejbgen.RoleMapping is not allowed on ...MyWSBean because it is a JAX-WS type web service.
[jwsc] [ERROR] - The annotation weblogic.ejbgen.Session is not allowed on ...MyWSBean because it is a JAX-WS type web service.
Seems its not allowed to mix jaxws and ejb3 annotations. What is the way to go to expose my ejb3 bean as a resource?
thx

Thx for your reply.
I did it differently: Creating a EJB3 bean (using the weblogic.ejbgen annotations) and afterwords creating a seperate file for the JAXWS webservice and there injecting the bean via the EJB annotation. Works smoothly.
Although I would rather use 1 file for both sessionbean and web service
Therefore, like I said, in the EJB3 sessionbean I now use following ejbgen annotations:
@Session(ejbName="...",
               runAs="...", runAsIdentityPrincipal="...",
               createAsPrincipalName="...", passivateAsPrincipalName="...",
               transTimeoutSeconds="7200", enableCallByReference=Bool.TRUE,
               useCallerIdentity=Bool.FALSE)
@MethodIsolationLevelPattern(pattern="*", isolationLevel=IsolationLevel.TRANSACTION_READ_COMMITTED)
@RoleMapping(principals="...", roleName="...")
Not sure why this is 'ejbgen' annotations, instead of just ejb or javaee general annotations... Arent there any more standard annotations or so in order to specify these configurations (rolemapping, MethodIsolationLevelPattern, Session, runas, createasprincipalname...) ?
thanks

Similar Messages

  • Oc4j and ejb3.0 as web services

    Hi,
    I have deployed a ejb3.0 jar with following files.
    Interface :
    package samples.webservice;
    import javax.jws.WebService;
    *@WebService*
    public interface HelloRemote
    public String echo(String input);
    Bean
    package samples.webservice;
    import javax.ejb.Remote;
    import javax.ejb.Stateless;
    import javax.jws.WebMethod;
    import javax.jws.WebService;
    import javax.jws.soap.SOAPBinding;
    *@WebService(name = "HelloRemote",serviceName = "HelloWorldService")*
    *@SOAPBinding(style = SOAPBinding.Style.RPC)*
    *@Remote(HelloRemote.class)*
    *@Stateless (name = "HelloRemote")*
    public class HelloWorld implements HelloRemote
    *@WebMethod*
    public String echo(String input)
    return input+"Hello";
    The ejb jar does not contain any deployment descriptor. I deployed it on OC4J 10.1.3.5. and Java-6.
    It got deployed without any error.
    But I am not able to see the WSDL using url.
    My ejb jar name is TestOc4j.jar
    At whct url I will be able to see the WSDL.
    I checked the admin console, under web services tab, there is no entry. I think it should show my Ws entry.
    Am I missing any step. The same WS (as ejb3) worked fine with the jboss6.
    Regards
    Ganesh

    Hi,
    you could use TopLink exposed by a EJB 3.0 session bean and use web services annotation of JSR-181 (available as a library) to expose it as a Web Service. In Business Components you expose methods to WebService by creating a remote configuration. I've done TopLink/EJB 3.0 and found it straight forward to use. In both cases the information to query from row 50 . 125 needs to be passed in by the Webservice.
    For PLSQL you may want to look at PLSQL WebServices (there are OBE availabe on the OTN website for JDeveloper -- look in the 10.1.2 or 9.0.5 section)
    Frank

  • Exposing RFC as a Web Service

    Hello All,
    I am working on a SOAP to SOAP (Backend as ECC where I am exposing an RFC as Web Service). Once the Web service is generated for RFC and the WSDL is imported in PI, I can see that all the fields in different nodes become mandatory.
    Is it how normally Web Service for BAPI works or can this behaviour (mandatory / optional) be controlled ?
    Also when I execute the end to end scenario via SOAP UI, I don't get any error back but also neither get the Return table nor the Sales Order NO. I am using the BAPI BAPI_SALESORDER_CREATEFROMDAT2.
    Can it be because of no COMMIT (The BAPI uses external commit although this reason seems less likely as executing a RFC wo any commit atleast gives me a Sales Order no) ?
    How can this call be analysed in backend ECC system ? (As I assume that messages will not be visible in SXMB_MONI as explained by the Harald's thread below. I am currently in process of getting authorization of SOAMANAGER logs but wondering how it'll help?
    Thanking you in advance.
    SOAP to SOAP scenario: XML messages not visible in SXMB_MONI
    Cheers
    KanesI

    Hi,
    Please see the SOAP ststud..
    http://<host>:5<sys#>00/mdt/amtServlet
    also you might check any error logs.
    The error is because of invalid xml document. So check the validity of the xml message ie. after first mapping i.e Req mapping.
    For this you can refer this -
    http://help.sap.com/saphelp_nw2004s/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm
    See the below links
    Also this blog may help you-/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
    Could not post a SOAP request  to the interface
    Message Servlet is in Status ERROR
    Error while posting messages to SOAP sender adapter SP 13
    http://localhost:50000/XISOAPAdapter/HelperServlet?action=FindChannel&channel=PartyA:SOAPService:soapchannel
    SOAP Adapter in PCK
    Regards
    Chilla..

  • Benefits of exposing function module as web services

    Hi All,
    We are developing a case study about exposing function modules as web services.
    Those web services would be later used for integration to SAP box with a Java application.
    Kindly help me with the pros and cons of exposing function modules as web services when compared to SAP PI. Also please do quote some examples, wherever possible.
    Thanks,
    Varun

    Hi Varun,
    Pros--->
    1)Exposing FM as Web Services is indeed a good choice when you want service consumer to be platform and language independent.
    i.e it can be consumed by .Net, java or any other language.
    2) You are moving towards SOA
    3) Composing Business Process by concatenating different functional modules is easy.
    4) Complexity is less while consuming services Java, CAF etc.
    Cons----> Performance for Web Services is comparatively less than JCo .
    If you are bringing PI in between landscape, you are increasing one more layer of middleware which would also hit performance.
    The benefit which PI can give is monitoring your company wide integrations at one central point when you have huge systems.
    Hope this helps.
    Piyush

  • Exposing Inbound Interfaces as Web Service

    Hi,
    when it comes to expose XI interfaces as web services, the XI documentation quotes:
    "Sie können sowohl von Outbound- als auch von Inbound-Message-Interfaces WSDL-Beschreibungen erzeugen."
    -> i.e. Inbound interfaces can be exposed as web services.
    But the web service definition wizard expects the quotation of an outbound interface. So am I right when I say that I always need an outbound interface? If yes, why is it possible to expose inbound interfaces???
    Cheers,
    Heiko

    Hi,
    no, inbound interfaces can only call web services
    that are exposed on some other web servers
    only outobund XI interfaces can be exposed as web services
    (in this case XI acts as a web server)
    and other applicaitons can call this outbound interface
    Regards,
    michal

  • Binding RESTful web service / being exposed to a RESTful web service

    Hi , I have two quick questions
    1. can ORACLE BPEL bind a RESTful web service?
    2. can a BPEL process be exposed to a RESTful web service?
    Thanks

    Bumping back to the top of the list.
    Has anyone got any experience with RESTful web services saving to an item vs. a collection? Any pointers are greatly appreciated.
    Earl

  • JWSC Ant task with JAXWS web services failed

    Hi,
    I do not manage to generate my JAXWS web services using jwsc ant task. It worked when my web services were JAX-RPC web services but now I have an error.
    In my build process, I generate first the web service artifacts from wsdl files using wsdlc :
    <path id="bea-ant-task.classpath">
      <pathelement location="${java.home}/../lib/tools.jar" />
      <fileset dir="${bea.home.dir}/wlserver_10.0/server/lib"/>
      <fileset dir="${bea.home.dir}/modules"/>
    </path>
    <taskdef name="wsdlc" classname="weblogic.wsee.tools.anttasks.WsdlcTask">
      <classpath refid="bea-ant-task.classpath" />
    </taskdef>
    <target name="generate-artifacts">
       <wsdlc type="JAXWS" srcWsdl="${build.wsdl.dir}/AlarmWS.wsdl" destJwsDir="${build.artifacts.jar.dir}" />
       <wsdlc type="JAXWS" srcWsdl="${build.wsdl.dir}/AlertWS.wsdl" destJwsDir="${build.artifacts.jar.dir}" />
    </target>Then I tried to generate my web services with jwsc :
    <taskdef name="jwsc" classname="weblogic.wsee.tools.anttasks.JwscTask">
      <classpath refid="bea-ant-task.classpath" />
    </taskdef>
    <target name="generate-webservices">
      <jwsc srcdir="src" destdir="${ear.dir}" keepGenerated="yes" classpathref="compile.classpath" >
           <module contextpath="myappli" name="webservices.jar" explode="true">
          <jws type="JAXWS" file="${myappli.path}/alarm/jwsendpoint/AlarmBean.java" compiledWsdl="${build.artifacts.jar.dir}/AlarmWS_wsdl.jar"/>
          <jws type="JAXWS" file="${myappli.path}/alert/jwsendpoint/AlertBean.java" compiledWsdl="${build.artifacts.jar.dir}/AlertWS_wsdl.jar"/>
        </module>
      </jwsc>
    </target>This task generate the following error :
    generate-webservices:
         [jwsc] JWS: processing module webservices.jar
         [jwsc] Parsing source files
         [jwsc] Parsing source files
         [jwsc] 2 JWS files being processed for module webservices.jar
         [jwsc] JWS: C:\projects\appli\main\src\net\aze\appli\services\alarm\jwsendpoint\AlarmBean.java Validated.
         [jwsc] JWS: C:\projects\appli\main\src\net\aze\appli\services\alert\jwsendpoint\AlertBean.java Validated.
         [jwsc] Processing 2 JAX-WS web services...
         [jwsc] warning: Annotation types without processors: [javax.ejb.Stateless, javax.annotation.Resource, javax.annotation.security.RolesAllowed]
         [jwsc] C:\DOCUME~1\wg\LOCALS~1\Temp\_jg4rtr3\net\aze\appli\jws\alert\PTAlert.java:33: The endpoint interface net.aze.appli.jws.alarm.PTAlarm does not match the interface net.aze.appli.jws.alert.PTAlert.
         [jwsc] public interface PTAlert {
         [jwsc]        ^
         [jwsc] 1 error
         [jwsc] 1 warning
         [jwsc] Command invoked: apt C:\apps\bea10\JROCKI~1\jre\bin\java.exe -classpath C:\projects\appli\lib\common\caplib.jar;C:\pr......[pre]
    C:\projects\aze\main\bea-build.xml:15: The following error occurred while executing this line:
    C:\projects\aze\main\ant\bea-generate-webservices.xml:46: The following error occurred while executing this line:
    C:\projects\aze\main\ant\bea-generate-webservices.xml:110: weblogic.wsee.tools.WsBuildException: Error processing JAX-WS web servicesHere is my bean implementation :
    @Stateless()
    @Resource(name = "jdbc/applids", mappedName = "applids", type = DataSource.class)
    @WebService(endpointInterface = "net.aze.appli.jws.alarm.PTAlarm")
    @HandlerChain(file = "../../../handler/alarmHandlerChain.xml")
    @RolesAllowed({"anonym", "systemUser"})
    public class AlarmBean implements PTAlarm {
        @Resource
        private SessionContext sessionContext;
        public AlarmCreateOut persist(AlarmCreateIn in) {
            return AlarmDelegate.getInstance(sessionContext).persist(in);
    @Stateless()
    @Resource(name = "jdbc/applids", mappedName = "applids", type = DataSource.class)
    @WebService(endpointInterface = "net.aze.appli.jws.alert.PTAlert")
    @RolesAllowed({"anonym", "systemUser"})
    public class AlertBean implements PTAlert {
        @Resource
        private SessionContext sessionContext;
        public AlertCreateOut persist(AlertCreateIn in) {
            return AlertDelegate.getInstance(sessionContext).persist(in);
    }Jwsc seems to mix the interfaces... If I try to generate only one bean in jwsc it works...
    Any ideas? I can't find the solution, could it be a bug?
    Thanks for your help.
    Edited by will_mad at 09/11/2007 1:56 AM

    Hi,
    I do not manage to generate my JAXWS web services
    using jwsc ant task. It worked when my web services
    were JAX-RPC web services but now I have an error.
    In my build process, I generate first the web service
    artifacts from wsdl files using wsdlc :
    <path id="bea-ant-task.classpath">
    <pathelement location="${java.home}/../lib/tools.jar" />
    <fileset dir="${bea.home.dir}/wlserver_10.0/server/lib"/>
    <fileset dir="${bea.home.dir}/modules"/>
    </path>
    <taskdef name="wsdlc" classname="weblogic.wsee.tools.anttasks.WsdlcTask">
    <classpath refid="bea-ant-task.classpath" />
    </taskdef>
    <target name="generate-artifacts">
    <wsdlc type="JAXWS" srcWsdl="${build.wsdl.dir}/AlarmWS.wsdl" destJwsDir="${build.artifacts.jar.dir}" />
    <wsdlc type="JAXWS" srcWsdl="${build.wsdl.dir}/AlertWS.wsdl" destJwsDir="${build.artifacts.jar.dir}" />
    </target>Then I tried to generate my web services with jwsc :
    <taskdef name="jwsc" classname="weblogic.wsee.tools.anttasks.JwscTask">
    <classpath refid="bea-ant-task.classpath" />
    </taskdef>
    <target name="generate-webservices">
    <jwsc srcdir="src" destdir="${ear.dir}" keepGenerated="yes" classpathref="compile.classpath" >
    <module contextpath="myappli" name="webservices.jar" explode="true">
    <jws type="JAXWS" file="${myappli.path}/alarm/jwsendpoint/AlarmBean.java" compiledWsdl="${build.artifacts.jar.dir}/AlarmWS_wsdl.jar"/>
    <jws type="JAXWS" file="${myappli.path}/alert/jwsendpoint/AlertBean.java" compiledWsdl="${build.artifacts.jar.dir}/AlertWS_wsdl.jar"/>
    </module>
    </jwsc>
    </target>This task generate the following error :
    generate-webservices:
    [jwsc] JWS: processing module webservices.jar
    [jwsc] Parsing source files
    [jwsc] Parsing source files
    [jwsc] 2 JWS files being processed for module
    odule webservices.jar
    [jwsc] JWS:
    JWS:
    C:\projects\appli\main\src\net\aze\appli\services\alar
    m\jwsendpoint\AlarmBean.java Validated.
    [jwsc] JWS:
    JWS:
    C:\projects\appli\main\src\net\aze\appli\services\aler
    t\jwsendpoint\AlertBean.java Validated.
    [jwsc] Processing 2 JAX-WS web services...
    [jwsc] warning: Annotation types without
    thout processors: [javax.ejb.Stateless,
    javax.annotation.Resource,
    javax.annotation.security.RolesAllowed]
    [jwsc]
    jwsc]
    C:\DOCUME~1\wg\LOCALS~1\Temp\_jg4rtr3\net\aze\appli\jw
    s\alert\PTAlert.java:33: The endpoint interface
    net.aze.appli.jws.alarm.PTAlarm does not match the
    interface net.aze.appli.jws.alert.PTAlert.
    [jwsc] public interface PTAlert {
    [jwsc]        ^
    [jwsc] 1 error
    [jwsc] 1 warning
    [jwsc] Command invoked: apt
    : apt C:\apps\bea10\JROCKI~1\jre\bin\java.exe
    -classpath
    C:\projects\appli\lib\common\caplib.jar;C:\pr......[pr
    e]
    C:\projects\aze\main\bea-build.xml:15: The following
    error occurred while executing this line:
    C:\projects\aze\main\ant\bea-generate-webservices.xml:
    46: The following error occurred while executing this
    line:
    C:\projects\aze\main\ant\bea-generate-webservices.xml:
    110: weblogic.wsee.tools.WsBuildException: Error
    processing JAX-WS web servicesHere is my bean implementation :
    @Stateless()
    @Resource(name = "jdbc/applids", mappedName =
    "applids", type = DataSource.class)
    @WebService(endpointInterface =
    "net.aze.appli.jws.alarm.PTAlarm")
    @HandlerChain(file =
    "../../../handler/alarmHandlerChain.xml")
    @RolesAllowed({"anonym", "systemUser"})
    public class AlarmBean implements PTAlarm {
    @Resource
    private SessionContext sessionContext;
    public AlarmCreateOut persist(AlarmCreateIn in)
    in) {
    return
    return
    n
    AlarmDelegate.getInstance(sessionContext).persist(in);
    @Stateless()
    @Resource(name = "jdbc/applids", mappedName =
    "applids", type = DataSource.class)
    @WebService(endpointInterface =
    "net.aze.appli.jws.alert.PTAlert")
    @RolesAllowed({"anonym", "systemUser"})
    public class AlertBean implements PTAlert {
    @Resource
    private SessionContext sessionContext;
    public AlertCreateOut persist(AlertCreateIn in)
    in) {
    return
    return
    n
    AlertDelegate.getInstance(sessionContext).persist(in);
    }Jwsc seems to mix the interfaces... If I try to
    generate only one bean in jwsc it works...
    Any ideas? I can't find the solution, could it be a
    bug?
    Thanks for your help.
    Edited by will_mad at 09/11/2007 1:56 AM
    Hi,
    I do not manage to generate my JAXWS web services
    using jwsc ant task. It worked when my web services
    were JAX-RPC web services but now I have an error.
    In my build process, I generate first the web service
    artifacts from wsdl files using wsdlc :
    <path id="bea-ant-task.classpath">
    <pathelement location="${java.home}/../lib/tools.jar" />
    <fileset dir="${bea.home.dir}/wlserver_10.0/server/lib"/>
    <fileset dir="${bea.home.dir}/modules"/>
    </path>
    <taskdef name="wsdlc" classname="weblogic.wsee.tools.anttasks.WsdlcTask">
    <classpath refid="bea-ant-task.classpath" />
    </taskdef>
    <target name="generate-artifacts">
    <wsdlc type="JAXWS" srcWsdl="${build.wsdl.dir}/AlarmWS.wsdl" destJwsDir="${build.artifacts.jar.dir}" />
    <wsdlc type="JAXWS" srcWsdl="${build.wsdl.dir}/AlertWS.wsdl" destJwsDir="${build.artifacts.jar.dir}" />
    </target>Then I tried to generate my web services with jwsc :
    <taskdef name="jwsc" classname="weblogic.wsee.tools.anttasks.JwscTask">
    <classpath refid="bea-ant-task.classpath" />
    </taskdef>
    <target name="generate-webservices">
    <jwsc srcdir="src" destdir="${ear.dir}" keepGenerated="yes" classpathref="compile.classpath" >
    <module contextpath="myappli" name="webservices.jar" explode="true">
    <jws type="JAXWS" file="${myappli.path}/alarm/jwsendpoint/AlarmBean.java" compiledWsdl="${build.artifacts.jar.dir}/AlarmWS_wsdl.jar"/>
    <jws type="JAXWS" file="${myappli.path}/alert/jwsendpoint/AlertBean.java" compiledWsdl="${build.artifacts.jar.dir}/AlertWS_wsdl.jar"/>
    </module>
    </jwsc>
    </target>This task generate the following error :
    generate-webservices:
    [jwsc] JWS: processing module webservices.jar
    [jwsc] Parsing source files
    [jwsc] Parsing source files
    [jwsc] 2 JWS files being processed for module
    odule webservices.jar
    [jwsc] JWS:
    JWS:
    C:\projects\appli\main\src\net\aze\appli\services\alar
    m\jwsendpoint\AlarmBean.java Validated.
    [jwsc] JWS:
    JWS:
    C:\projects\appli\main\src\net\aze\appli\services\aler
    t\jwsendpoint\AlertBean.java Validated.
    [jwsc] Processing 2 JAX-WS web services...
    [jwsc] warning: Annotation types without
    thout processors: [javax.ejb.Stateless,
    javax.annotation.Resource,
    javax.annotation.security.RolesAllowed]
    [jwsc]
    jwsc]
    C:\DOCUME~1\wg\LOCALS~1\Temp\_jg4rtr3\net\aze\appli\jw
    s\alert\PTAlert.java:33: The endpoint interface
    net.aze.appli.jws.alarm.PTAlarm does not match the
    interface net.aze.appli.jws.alert.PTAlert.
    [jwsc] public interface PTAlert {
    [jwsc]        ^
    [jwsc] 1 error
    [jwsc] 1 warning
    [jwsc] Command invoked: apt
    : apt C:\apps\bea10\JROCKI~1\jre\bin\java.exe
    -classpath
    C:\projects\appli\lib\common\caplib.jar;C:\pr......[pr
    e]
    C:\projects\aze\main\bea-build.xml:15: The following
    error occurred while executing this line:
    C:\projects\aze\main\ant\bea-generate-webservices.xml:
    46: The following error occurred while executing this
    line:
    C:\projects\aze\main\ant\bea-generate-webservices.xml:
    110: weblogic.wsee.tools.WsBuildException: Error
    processing JAX-WS web servicesHere is my bean implementation :
    @Stateless()
    @Resource(name = "jdbc/applids", mappedName =
    "applids", type = DataSource.class)
    @WebService(endpointInterface =
    "net.aze.appli.jws.alarm.PTAlarm")
    @HandlerChain(file =
    "../../../handler/alarmHandlerChain.xml")
    @RolesAllowed({"anonym", "systemUser"})
    public class AlarmBean implements PTAlarm {
    @Resource
    private SessionContext sessionContext;
    public AlarmCreateOut persist(AlarmCreateIn in)
    in) {
    return
    return
    n
    AlarmDelegate.getInstance(sessionContext).persist(in);
    @Stateless()
    @Resource(name = "jdbc/applids", mappedName =
    "applids", type = DataSource.class)
    @WebService(endpointInterface =
    "net.aze.appli.jws.alert.PTAlert")
    @RolesAllowed({"anonym", "systemUser"})
    public class AlertBean implements PTAlert {
    @Resource
    private SessionContext sessionContext;
    public AlertCreateOut persist(AlertCreateIn in)
    in) {
    return
    return
    n
    AlertDelegate.getInstance(sessionContext).persist(in);
    }Jwsc seems to mix the interfaces... If I try to
    generate only one bean in jwsc it works...
    Any ideas? I can't find the solution, could it be a
    bug?
    Thanks for your help.
    Edited by will_mad at 09/11/2007 1:56 AMI too am getting similar error. If you hit a solution, do let me know :)

  • Exposing backend data as Web Service

    I have an RFC which takes in employee name as input and supervisor name as output.
    I want to expose this functionality as Web Service using NWDS. What should I do? Any good tutorial?

    Hi,
    Check this weblog, which mentions how to convert RFCs as Webservices
    Using RFC as WebService in WebDynpro
    Regards,
    Ganesh N

  • Cannot find the WSDL as I expose a process to web service

    Hi,
    I have a simple process, and I try to expose it to a web service by using "Process Web Service", and I start the studio web server and test it with "http://localhost:8598/Lesson19-4WebService/webservices/ProcessService?WSDL" but no WSDL appear. Could you help me? Thanks in advance.
    Best Regards,
    Bill

    Please find the following forum.
    Process exposed as a web service does not work when deployed
    This should resolve the issue.
    Hope this helps.
    Sarat

  • Exposing a process as web service on Oracle BPM 11g

    Hi!
    Does somebody know how can I expose a process as a web service on Oracle BPM 11g? How does it works?
    In the version 10.3, when we exposed a process as web service it always had 3 default methods: startSession, getInstanceStatus and discardSession, is it the same in the 11g version?
    Where can I found some info about it? Any tutorial?
    Thanks a lot!
    Ana

    Typically you would use a Message Start event to start the process in conjunction with a Message End event. This will allow your process to be called as an asynchronous web service.
    In the "Implementation" section for the start event, you specify the input parameters. You can specify "Define Interface" to directly define the interface, or use an existing interface from the BPM Catalog (the From Catalog option).
    For further details on the different event types and their use cases, refer to the modeling and implementation guide:
    http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15176/toc.htm
    You can test the web service and examine the WSDL and endpoints by using FMW control (Enterprise Manager). In the menu on the left hand side: expand SOA -> SOA-Infra -> <Partition Name> -> Composite Name, then click the "Test" button at the top.

  • Error calling WS exposed by NETBEANS from Web Service Data Control

    Hi all,
    Can anyone help me? I'm calling a webservice via WebService DataControl, and the call generate this error:
    12-dic-2008 12.56.18 oracle.adf.model.connection.webservice.impl.WebServiceConnectionMessages debugGetSaajInteraction
    INFO: Creating a SaajInteraction for oracle.j2ee.ws.model.OperationImpl@b86609
    12-dic-2008 12.56.18 oracle.adf.model.connection.webservice.impl.WebServiceConnectionMessages debugGetSaajInteractionResult
    INFO: Created [email protected]a00b for oracle.j2ee.ws.model.OperationImpl@b86609
    12-dic-2008 12.56.18 oracle.j2ee.ws.rm.LogMessages logExceptionAsWarning
    AVVERTENZA: Internal error: oracle.wsm.policy.model.PolicyModelException: WSM-01647 : There are no policies that match the specified category wsrm and resource pattern {1}.
    12-dic-2008 12.56.18 oracle.fabric.common.AbstractSecurityInterceptor init
    INFO: AbstractSecurityInterceptor:init(), client.mode.jse==ture and isJEE==true, probably is a case of JEE client calling JSE client
    12-dic-2008 12.56.18 oracle.wsm.agent.WSMAgent init
    INFO: WSMAgent is initialized for category=management, function=agent.function.client, topologyNodePath=null, isJ2EE=true
    12-dic-2008 12.56.18 oracle.fabric.common.AbstractSecurityInterceptor init
    INFO: AbstractSecurityInterceptor:init(), client.mode.jse==ture and isJEE==true, probably is a case of JEE client calling JSE client
    12-dic-2008 12.56.18 oracle.wsm.agent.WSMAgent init
    INFO: WSMAgent is initialized for category=security, function=agent.function.client, topologyNodePath=null, isJ2EE=true
    12-dic-2008 12.56.23 oracle.wsm.common.logging.WsmMessageLogger logSevere
    GRAVE: errore nell''inizializzazione di Oracle WSM Policy Resolver. Passata configurazione errata: {0} {1}
    12-dic-2008 12.56.23 oracle.adf.model.connection.webservice.impl.WebServiceConnectionMessages debugExecuteFailure
    GRAVE: Failed to execute a SAAJ interaction.
    javax.xml.ws.soap.SOAPFaultException: javax.jbi.messaging.MessagingException: HTTPBC-E00798: Message normalization failed
         at oracle.j2ee.ws.client.jaxws.DispatchImpl.throwJAXWSSoapFaultException(DispatchImpl.java:827)
         at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:694)
         at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:226)
         at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:97)
         at oracle.adf.model.connection.webservice.impl.SaajInteractionImpl.execute(SaajInteractionImpl.java:84)
         at oracle.adfinternal.model.adapter.webservice.provider.soap.SOAPProvider.execute(SOAPProvider.java:310)
         at oracle.adfinternal.model.adapter.webservice.WSDataControl.invokeOperation(WSDataControl.java:244)
         at oracle.adf.model.bean.DCBeanDataControl.invokeMethod(DCBeanDataControl.java:377)
         at oracle.adf.model.binding.DCInvokeMethod.callMethod(DCInvokeMethod.java:258)
         at oracle.jbo.uicli.binding.JUCtrlActionBinding.doIt(JUCtrlActionBinding.java:1441)
         at oracle.adf.model.binding.DCDataControl.invokeOperation(DCDataControl.java:2126)
         at oracle.adf.model.bean.DCBeanDataControl.invokeOperation(DCBeanDataControl.java:403)
         at oracle.adf.model.adapter.AdapterDCService.invokeOperation(AdapterDCService.java:311)
         at oracle.jbo.uicli.binding.JUCtrlActionBinding.invoke(JUCtrlActionBinding.java:697)
         at oracle.jbo.uicli.binding.JUMethodIteratorDef$JUMethodIteratorBinding.invokeMethodAction(JUMethodIteratorDef.java:174)
         at oracle.jbo.uicli.binding.JUMethodIteratorDef$JUMethodIteratorBinding.initSourceRSI(JUMethodIteratorDef.java:631)
         at oracle.adf.model.binding.DCIteratorBinding.callInitSourceRSI(DCIteratorBinding.java:1625)
         at oracle.adf.model.binding.DCIteratorBinding.internalGetRowSetIterator(DCIteratorBinding.java:1601)
         at oracle.adf.model.binding.DCIteratorBinding.refresh(DCIteratorBinding.java:4202)
         at oracle.adf.model.binding.DCExecutableBinding.refreshIfNeeded(DCExecutableBinding.java:327)
         at oracle.adf.model.binding.DCIteratorBinding.getRowSetIterator(DCIteratorBinding.java:1563)
         at oracle.jbo.uicli.binding.MyIteratorBinding.initSourceRSI(JUAccessorIteratorDef.java:737)
         at oracle.adf.model.binding.DCIteratorBinding.callInitSourceRSI(DCIteratorBinding.java:1625)
         at oracle.adf.model.binding.DCIteratorBinding.internalGetRowSetIterator(DCIteratorBinding.java:1601)
         at oracle.adf.model.binding.DCIteratorBinding.refresh(DCIteratorBinding.java:4202)
         at oracle.adf.model.binding.DCExecutableBinding.refreshIfNeeded(DCExecutableBinding.java:327)
         at oracle.adf.model.binding.DCIteratorBinding.getRowSetIterator(DCIteratorBinding.java:1563)
         at oracle.jbo.uicli.binding.MyIteratorBinding.initSourceRSI(JUAccessorIteratorDef.java:737)
         at oracle.adf.model.binding.DCIteratorBinding.callInitSourceRSI(DCIteratorBinding.java:1625)
         at oracle.adf.model.binding.DCIteratorBinding.internalGetRowSetIterator(DCIteratorBinding.java:1601)
         at oracle.adf.model.binding.DCIteratorBinding.refresh(DCIteratorBinding.java:4202)
         at oracle.adf.model.binding.DCExecutableBinding.refreshIfNeeded(DCExecutableBinding.java:327)
         at oracle.jbo.uicli.binding.JUCtrlHierNodeBinding.getChildren(JUCtrlHierNodeBinding.java:567)
         at oracle.adfinternal.view.faces.model.binding.RowDataManager.getRowCount(RowDataManager.java:232)
         at oracle.adfinternal.view.faces.model.binding.FacesCtrlHierBinding$FacesModel.getRowCount(FacesCtrlHierBinding.java:486)
         at org.apache.myfaces.trinidad.component.UIXTable._processStamps(UIXTable.java:505)
         at org.apache.myfaces.trinidad.component.UIXTable.processFacetsAndChildren(UIXTable.java:373)
         at org.apache.myfaces.trinidad.component.UIXCollection.decodeChildrenImpl(UIXCollection.java:202)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.decodeChildren(UIXComponentBase.java:955)
         at org.apache.myfaces.trinidad.component.UIXCollection.processDecodes(UIXCollection.java:196)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.decodeChildrenImpl(UIXComponentBase.java:969)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.decodeChildren(UIXComponentBase.java:955)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.processDecodes(UIXComponentBase.java:811)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.decodeChildrenImpl(UIXComponentBase.java:969)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.decodeChildren(UIXComponentBase.java:955)
         at org.apache.myfaces.trinidad.component.UIXForm.processDecodes(UIXForm.java:75)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.decodeChildrenImpl(UIXComponentBase.java:969)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.decodeChildren(UIXComponentBase.java:955)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.processDecodes(UIXComponentBase.java:811)
         at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1015)
         at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:504)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl$ApplyRequestValuesCallback.invokeContextCallback(LifecycleImpl.java:1113)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:293)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:175)
         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:292)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:181)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:85)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:278)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:238)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:195)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:138)
         at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at oracle.security.jps.wls.JpsWlsFilter.doFilter(JpsWlsFilter.java:102)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:65)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3496)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    12-dic-2008 12.56.23 oracle.adf.model.connection.webservice.impl.WebServiceConnectionMessages debugGetSaajInteraction
    INFO: Creating a SaajInteraction for oracle.j2ee.ws.model.OperationImpl@b86609
    12-dic-2008 12.56.23 oracle.adf.model.connection.webservice.impl.WebServiceConnectionMessages debugGetSaajInteractionResult
    INFO: Created [email protected]9b49a5 for oracle.j2ee.ws.model.OperationImpl@b86609
    12-dic-2008 12.56.23 oracle.j2ee.ws.rm.LogMessages logExceptionAsWarning
    AVVERTENZA: Internal error: oracle.wsm.policy.model.PolicyModelException: WSM-01647 : There are no policies that match the specified category wsrm and resource pattern {1}.
    12-dic-2008 12.56.23 oracle.fabric.common.AbstractSecurityInterceptor init
    INFO: AbstractSecurityInterceptor:init(), client.mode.jse==ture and isJEE==true, probably is a case of JEE client calling JSE client
    12-dic-2008 12.56.23 oracle.wsm.agent.WSMAgent init
    INFO: WSMAgent is initialized for category=management, function=agent.function.client, topologyNodePath=null, isJ2EE=true
    12-dic-2008 12.56.23 oracle.fabric.common.AbstractSecurityInterceptor init
    INFO: AbstractSecurityInterceptor:init(), client.mode.jse==ture and isJEE==true, probably is a case of JEE client calling JSE client
    12-dic-2008 12.56.23 oracle.wsm.agent.WSMAgent init
    INFO: WSMAgent is initialized for category=security, function=agent.function.client, topologyNodePath=null, isJ2EE=true
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://j2ee.netbeans.org/wsdl/PBOv2UseCase/input"><env:Header/><env:Body><ns:inputOperation><id>1</id><dateFrom>2008-12-12</dateFrom><dateTo>2008-12-19</dateTo></ns:inputOperation></env:Body></env:Envelope>12-dic-2008 12.56.28 oracle.wsm.common.logging.WsmMessageLogger logSevere
    GRAVE: errore nell''inizializzazione di Oracle WSM Policy Resolver. Passata configurazione errata: {0} {1}
    12-dic-2008 12.56.28 oracle.adf.model.connection.webservice.impl.WebServiceConnectionMessages debugExecuteFailure
    GRAVE: Failed to execute a SAAJ interaction.
    javax.xml.ws.soap.SOAPFaultException: javax.jbi.messaging.MessagingException: HTTPBC-E00798: Message normalization failed
         at oracle.j2ee.ws.client.jaxws.DispatchImpl.throwJAXWSSoapFaultException(DispatchImpl.java:827)
         at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:694)
         at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:226)
         at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:97)
         at oracle.adf.model.connection.webservice.impl.SaajInteractionImpl.execute(SaajInteractionImpl.java:84)
         at oracle.adfinternal.model.adapter.webservice.provider.soap.SOAPProvider.execute(SOAPProvider.java:310)
         at oracle.adfinternal.model.adapter.webservice.WSDataControl.invokeOperation(WSDataControl.java:244)
         at oracle.adf.model.bean.DCBeanDataControl.invokeMethod(DCBeanDataControl.java:377)
         at oracle.adf.model.binding.DCInvokeMethod.callMethod(DCInvokeMethod.java:258)
         at oracle.jbo.uicli.binding.JUCtrlActionBinding.doIt(JUCtrlActionBinding.java:1441)
         at oracle.adf.model.binding.DCDataControl.invokeOperation(DCDataControl.java:2126)
         at oracle.adf.model.bean.DCBeanDataControl.invokeOperation(DCBeanDataControl.java:403)
         at oracle.adf.model.adapter.AdapterDCService.invokeOperation(AdapterDCService.java:311)
         at oracle.jbo.uicli.binding.JUCtrlActionBinding.invoke(JUCtrlActionBinding.java:697)
         at oracle.jbo.uicli.binding.JUMethodIteratorDef$JUMethodIteratorBinding.invokeMethodAction(JUMethodIteratorDef.java:174)
         at oracle.jbo.uicli.binding.JUMethodIteratorDef$JUMethodIteratorBinding.executeQuery(JUMethodIteratorDef.java:377)
         at oracle.jbo.uicli.binding.MyIteratorBinding.initSourceRSI(JUAccessorIteratorDef.java:746)
         at oracle.adf.model.binding.DCIteratorBinding.callInitSourceRSI(DCIteratorBinding.java:1625)
         at oracle.adf.model.binding.DCIteratorBinding.internalGetRowSetIterator(DCIteratorBinding.java:1601)
         at oracle.adf.model.binding.DCIteratorBinding.refresh(DCIteratorBinding.java:4202)
         at oracle.adf.model.binding.DCExecutableBinding.refreshIfNeeded(DCExecutableBinding.java:327)
         at oracle.adf.model.binding.DCIteratorBinding.getRowSetIterator(DCIteratorBinding.java:1563)
         at oracle.jbo.uicli.binding.MyIteratorBinding.initSourceRSI(JUAccessorIteratorDef.java:737)
         at oracle.adf.model.binding.DCIteratorBinding.callInitSourceRSI(DCIteratorBinding.java:1625)
         at oracle.adf.model.binding.DCIteratorBinding.internalGetRowSetIterator(DCIteratorBinding.java:1601)
         at oracle.adf.model.binding.DCIteratorBinding.refresh(DCIteratorBinding.java:4202)
         at oracle.adf.model.binding.DCExecutableBinding.refreshIfNeeded(DCExecutableBinding.java:327)
         at oracle.jbo.uicli.binding.JUCtrlHierNodeBinding.getChildren(JUCtrlHierNodeBinding.java:567)
         at oracle.adfinternal.view.faces.model.binding.RowDataManager.getRowCount(RowDataManager.java:232)
         at oracle.adfinternal.view.faces.model.binding.FacesCtrlHierBinding$FacesModel.getRowCount(FacesCtrlHierBinding.java:486)
         at org.apache.myfaces.trinidad.component.UIXTable._processStamps(UIXTable.java:505)
         at org.apache.myfaces.trinidad.component.UIXTable.processFacetsAndChildren(UIXTable.java:373)
         at org.apache.myfaces.trinidad.component.UIXCollection.decodeChildrenImpl(UIXCollection.java:202)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.decodeChildren(UIXComponentBase.java:955)
         at org.apache.myfaces.trinidad.component.UIXCollection.processDecodes(UIXCollection.java:196)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.decodeChildrenImpl(UIXComponentBase.java:969)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.decodeChildren(UIXComponentBase.java:955)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.processDecodes(UIXComponentBase.java:811)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.decodeChildrenImpl(UIXComponentBase.java:969)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.decodeChildren(UIXComponentBase.java:955)
         at org.apache.myfaces.trinidad.component.UIXForm.processDecodes(UIXForm.java:75)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.decodeChildrenImpl(UIXComponentBase.java:969)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.decodeChildren(UIXComponentBase.java:955)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.processDecodes(UIXComponentBase.java:811)
         at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1015)
         at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:504)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl$ApplyRequestValuesCallback.invokeContextCallback(LifecycleImpl.java:1113)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:293)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:175)
         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:292)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:181)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:85)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:278)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:238)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:195)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:138)
         at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at oracle.security.jps.wls.JpsWlsFilter.doFilter(JpsWlsFilter.java:102)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:65)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3496)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    12-dic-2008 12.56.28 oracle.adf.model.connection.webservice.impl.WebServiceConnectionMessages debugGetSaajInteraction
    INFO: Creating a SaajInteraction for oracle.j2ee.ws.model.OperationImpl@b86609
    12-dic-2008 12.56.28 oracle.adf.model.connection.webservice.impl.WebServiceConnectionMessages debugGetSaajInteractionResult
    INFO: Created [email protected]b5491 for oracle.j2ee.ws.model.OperationImpl@b86609
    12-dic-2008 12.56.28 oracle.j2ee.ws.rm.LogMessages logExceptionAsWarning
    AVVERTENZA: Internal error: oracle.wsm.policy.model.PolicyModelException: WSM-01647 : There are no policies that match the specified category wsrm and resource pattern {1}.
    12-dic-2008 12.56.28 oracle.fabric.common.AbstractSecurityInterceptor init
    INFO: AbstractSecurityInterceptor:init(), client.mode.jse==ture and isJEE==true, probably is a case of JEE client calling JSE client
    12-dic-2008 12.56.28 oracle.wsm.agent.WSMAgent init
    INFO: WSMAgent is initialized for category=management, function=agent.function.client, topologyNodePath=null, isJ2EE=true
    12-dic-2008 12.56.28 oracle.fabric.common.AbstractSecurityInterceptor init
    INFO: AbstractSecurityInterceptor:init(), client.mode.jse==ture and isJEE==true, probably is a case of JEE client calling JSE client
    12-dic-2008 12.56.28 oracle.wsm.agent.WSMAgent init
    INFO: WSMAgent is initialized for category=security, function=agent.function.client, topologyNodePath=null, isJ2EE=true
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://j2ee.netbeans.org/wsdl/PBOv2UseCase/input"><env:Header/><env:Body><ns:inputOperation><id>1</id><dateFrom>2008-12-12</dateFrom><dateTo>2008-12-19</dateTo></ns:inputOperation></env:Body></env:Envelope>
    The webservice called is exposed by NetBeans 6.1 and its wsdl is this:
    <?xml version="1.0" encoding="UTF-8" ?>
    - <definitions name="input" targetNamespace="http://j2ee.netbeans.org/wsdl/PBOv2UseCase/input" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype" xmlns:ns="http://j2ee.netbeans.org/xsd/tableSchema" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://j2ee.netbeans.org/wsdl/PBOv2UseCase/input" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
    - <types>
    - <xsd:schema targetNamespace="http://j2ee.netbeans.org/wsdl/PBOv2UseCase/input">
    <xsd:import namespace="http://j2ee.netbeans.org/xsd/tableSchema" schemaLocation="http://TRIALT004.mytria.tria.it:9084/PBOv2UserCaseApplication-sun-http-binding/PBOv2UseCase/STAKE_HEAD.xsd" />
    </xsd:schema>
    </types>
    - <message name="inputOperationRequest">
    <part name="id" type="xsd:string" />
    <part name="dateFrom" type="xsd:date" />
    <part name="dateTo" type="xsd:date" />
    </message>
    - <message name="inputOperationResponse">
    <part name="part1" type="ns:STAKE_HEAD" />
    </message>
    - <portType name="inputPortType">
    - <operation name="inputOperation">
    <input name="input1" message="tns:inputOperationRequest" />
    <output name="output1" message="tns:inputOperationResponse" />
    </operation>
    </portType>
    - <binding name="inputBinding" type="tns:inputPortType">
    <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
    - <operation name="inputOperation">
    <soap:operation />
    - <input name="input1">
    <soap:body use="literal" namespace="http://j2ee.netbeans.org/wsdl/PBOv2UseCase/input" />
    </input>
    - <output name="output1">
    <soap:body use="literal" namespace="http://j2ee.netbeans.org/wsdl/PBOv2UseCase/input" />
    </output>
    </operation>
    </binding>
    - <service name="inputService">
    - <port name="inputPort" binding="tns:inputBinding">
    <soap:address location="http://TRIALT004.mytria.tria.it:9084/inputService/inputPort" />
    </port>
    </service>
    - <plnk:partnerLinkType name="input">
    <plnk:role name="inputPortTypeRole" portType="tns:inputPortType" />
    </plnk:partnerLinkType>
    </definitions>
    Edited by: Matteo on Dec 12, 2008 7:49 AM

    Hi,
    I have the same issue using JDeveloper 11.1.1.0.1 to build a web service data control on a web service exposed with weblogic...
    Does anyone have a solution ?
    Thanks
    ( Note: this is a new issue, it might have appeared after upgrading from 11.1.1.0.0 to 11.1.1.0.1 )

  • Unable to expose a method in web service

    Hi,
    My scenario is to expose a method in service. This method will take date as input & should return all the rows.
    To Implement this, I took employeeVO of HR DB(Employees Table) & created a ViewCriteria "GetEmpbyHireDate" with Hiredate as input param.
    & in AMImpl the code is
    public BaseEmployeeVOImpl getEmployeesByHireDate(Date hiredate){
    BaseEmployeeVOImpl baseEmployeeVO = (BaseEmployeeVOImpl) findViewObject("BaseEmployee1");
    baseEmployeeVO.setApplyViewCriteriaName("GetEmpbyHireDate");
    baseEmployeeVO.setNamedWhereClauseParam("pHireDate", hiredate);
    baseEmployeeVO.executeQuery();
    return baseEmployeeVO;
    The issue is I'm not able to see this method in "Available" list of Web Service Wizard.
    Help me in understanding what is missing ?
    Thanks in advance.
    P.S. from Jdev Help I understood that "Only methods with simple attributes as parameters and return types that are either void or view rows will appear in the list." & my method is returning rows of a EmployeeVO.

    Hi,
    2 comments:
    1) View Criteria can be directly exposed as find methods. Its on the last wizard page (just click the View Criteria tab). So no need for an Impl method
    2) If you wanted to expose a method, then the documentation I think is crystal clear: "oracle.jbo.server.ViewRowImpl or any subtype" Your method returns BaseEmployeeVOImpl (see the difference ?)
    Frank

  • Follow up to web services question:  How do I expose java components as web services on iPlanet 6.0 app server?

    My task - my company has several legacy PowerBuilder applications that access a variety of Sybase and MS SQL databases. Rather than re-inventing the wheel by re-writing these applications in Java, we would like to enable these applications to call java components (EJBs) that will provide new functionality. I would need a piece of software called CSXtend (from www.cynergysystems.com) to allow PowerBuilder to call a web service. However, I am not sure how to expose my business functions (EJBs) as web services on the iPlanet 6.0 App server. Thanks for all previous responses! Any additional info would be greatly appreciated! Mike

    I have used Glue (http://www.themindelectric.com/products/glue/glue.html) to expose some of our stuff as Web Services. I recently found this on serverside. It's pretty good.
    http://www.theserverside.com/resources/article.jsp?l=Systinet-web-services-part-1
    I believe that the middleware they use can be plugged into IPlanet. There is also an article in the knowledge base on the IPlanet site.
    Jon

  • Help:  Exposing BAPI's as Web Services in WAS 6.20

    Hello,
    I'm very new to WAS and I don't have access to a development environment yet (network issues).  I was hoping someone might be able to shed some light on the following: 
    I'd like to expose certain BAPI's as Web Services in a way that my .NET client can talk SOAP directly to WAS 6.20 (without having to generate proxies). Is this possible? 
    Also, is there a Web Service Creation Wizard in 6.20 that makes the process of exposing BAPI's simple, similar to the wizard in 6.40?  To date I've been able to navigate the BOR and generate WSDL for the BAPI's that I'm interested in however, this doesn't get me all the way there.  I'm looking for documentation on how to make the Web Service interface for those BAPI's generally available through WAS.
    I'll take anything at this point.  Even a pointer to some documentation.
    Thanks,
    Jay

    Hi Jay,
    Yes, it is possible in Web AS 6.20 to expose BAPIs as Web services. You find the exact documentation of how to do this in the SAP Service Marketplace: http://service.sap.com/connectors. Then go to "SOAP Processor" --> "Media Library". However, the wizard that helps you create the Web service is not yet available in 6.20.
    Regards,
    Susanne

  • Exposing EJB interfaces as Web Service

    Hi all,
    I created a prototype using EJBs and Web Services and found out that JDeveloper only allows to expose as Web
    Services the Remote interfaces of EJBs and not the Local ones.
    Assuming I have included Local and Remote interfaces for each of my EJBs exposed, my questions is, after deploying the application on OC4J 10g are the Web Services accessing the EJBs through the Local interface (I assume it should) but then why I am only allowed to expose the Remote one as Web Service?
    TIA,
    Best Regards,
    Giovanni

    Hi,
    no, inbound interfaces can only call web services
    that are exposed on some other web servers
    only outobund XI interfaces can be exposed as web services
    (in this case XI acts as a web server)
    and other applicaitons can call this outbound interface
    Regards,
    michal

Maybe you are looking for