Null connection context using java wrapped wwsec_api

How can I specify my OID connection information when using the PL/SQL wwsec_api with java wrappers?
I am getting a null connection context, and I assume that it is looking for the directory connection information (OID host,port,user,password).
Is this somehow specified in the .properties file?
The java was created with Jpublisher per the Jdeveloper help instructions. Following is a code snippet using the java classes created.
String userName = "username";
WwsecApi anWwsecApi = new WwsecApi();
WwsecApiRowtypeSql3 userInfo = (WwsecApiRowtypeSql3)anWwsecApi.personInfo(userName);
if (userInfo.getEmpno() != null)
out.print("Employee Number" + userInfo.getEmpno());
else
out.print("null");

-- Set the session context for a lightweight user as follows in your java code before executing the API call.
-- portal.wwctx_api.set_context(p_user_name => 'portal',p_password => 'password1',p_company => 'simplerewards');
portal.wwctx_api_private.set_context (p_user_name => 'portal');

Similar Messages

  • Null connection context with java wrapped wwsec_api

    How can I specify my OID connection information when using the PL/SQL wwsec_api with java wrappers?
    I am getting a null connection context, and I assume that it is looking for the directory connection information (OID host,port,user,password).
    Is this somehow specified in the .properties file?
    The java was created with Jpublisher per the Jdeveloper help instructions. Following is a code snippet using the java classes created.
    String userName = "username";
    WwsecApi anWwsecApi = new WwsecApi();
    WwsecApiRowtypeSql3 userInfo = (WwsecApiRowtypeSql3)anWwsecApi.personInfo(userName);
    if (userInfo.getEmpno() != null)
    out.print("Employee Number" + userInfo.getEmpno());
    else
    out.print("null");

    -- Set the session context for a lightweight user as follows in your java code before executing the API call.
    -- portal.wwctx_api.set_context(p_user_name => 'portal',p_password => 'password1',p_company => 'simplerewards');
    portal.wwctx_api_private.set_context (p_user_name => 'portal');

  • SQLException: found null connection context

    Using JDeveloper, I set up a connection with success. However, running the program generates the following error:
    java.sql.SQLException: found null connection context
    The error persists even when I use [contextNameFromtheConnection] with #sql{...};
    Thanks for your time.
    null

    You need to set your connection at runtime in your program. For example, to set the default connection:
    oracle.sqlj.runtime.Oracle.connect("jdbc:oracle:thin:@localhost:1521:orcl","scott","tiger");
    Or, if you have created a JDBC connection conn you could reuse that as follows.
    oracle.sqlj.runtime.Oracle.connect(conn);
    Hope this helps. -- Ekkehard

  • Connecting Pooling using Java Servlets

    Hello Friends I am in search of a programme to make a connection pooling using Java Servlets.
    Please let me know where i will get it or do post it.

    If you mean JDBC connection pools, one solution can be found here - http://www.javaexchange.com
    Chuck

  • How to connect obiee using java?

    please any one help to my request.
    -GB

    please review my java code....
    String s_userName = "Administrator";
              String s_password = "Administrator";
              String s_olapSvrName = "10.112.176.53";
              String s_provider = "http://10.112.176.53:13080/aps/JAPI";      //what purpose this line and what type of service provider required here     
              try
              IEssbase ess = IEssbase.Home.create(IEssbase.JAPI_VERSION);
    System.out.println("STEP1..........");
              //IEssDomain dom = ess.signOn(s_userName, s_password, false, null, s_provider);
    IEssDomain dom = ess.signOn(s_userName, s_password, false, null, s_provider);
              System.out.println("STEP2..........");
              IEssOlapServer olapSvr = (IEssOlapServer)dom.getOlapServer(s_olapSvrName);
              System.out.println("STEP3..........");
              olapSvr.connect();
              System.out.println("STEP4..........");
    catch(Exception e) {
    e.getMessage();
    i am getting error
    ERROR: Cannot connect to Provider Server.Make sure the signon parameters are correct and the Provider Server is running.
    1. where we can find the provider service in obiee?
    2. how to configure this service?
    3. which port this service is running?
    thanks in advance
    -GB

  • How to set portal context using Java/JPDK api.

    Hi,
    I am in the process of converting pl/sql based database provider contect portlets to Java based JPDK. I ran into issue where the database provider portlet users were getting context auto matically. Now with Java/JPDK portlets , I am receiving no data found error, since the context is not set. The pl/sql is setting wwctx_private_api.set_context ('portal') to set the context. From Java if we call this api, it is taking a toll on the performance and the portlet times out.
    Can any help how to set the context for a web provider using JPDK or any other better solution. Any immediate help is highly appreciated.
    Thanks,
    Rav.

    Hi
    We are trying to access content views for e.g portal.wwsbr_all_items s, portal.wwsbr_all_content_areas c,portal.wwsbr_all_folders f, from aweb provider portlet. When we do a select on those objects , we are getting java sql exception saying "ORA-06510: PL/SQL: unhandled user-defined exception
    ORA-06512: at "PORTAL.WWCTX_SSO", line 1745
    ORA-06510: PL/SQL: unhandled user-defined exception
    ORA-06512: at "PORTAL.WWCTX_SSO", line 1579
    ORA-06502: PL/SQL: numeric or value error
    ORA-06512: at "PORTAL.WWCTX_SSO", line 1834
    ORA-06512: at "PORTAL.WWCTX_API", line 199
    We need to know how to accesss the above views from a jsp based portlet.
    A

  • Internet Connection Sharing using java

    Dear all,
    I am currently trying to figure out a solution for making an application which would help me accomplish ICS.
    I have googled for ideas on this, without too much help.
    My ideas so far :
    1) Detect input(wait a min. how can I detect if this is the "live" wire ?) from a network interface and then try to share/redirect the traffic to the other n/w interfaces.
    2) Actually listing all the n/w interfaces and asking the user to select the master interface.
    the problem is, this may also have a few wireless connections hence I would need to know the signal strengths and then post WAP/WEP info too.
    I am thinking of using jpcap for this.
    This is the first time I am doing such a thing. Please let me know how do I proceed with this. I dont even know if the lines that I am thinkin on (1 & 2) are even correct.
    I would be grateful for any pointers on this.
    rgds,

    If you are talking about NAT? like the real internet connection sharing that many routers, firewalls, etc use to virtualize an IP then it cannot be done in PURE JAVA. Of course you can do something with JNI and possiably even get it to work. But then you will probably just be using features of the platform that your computer is installed upon as in order to do NAT, you have to be able to inject your code into the IP stack code.
    Linux you could do it easily as long as the kernel supported it, as you would just have to run ipchains/ipfw commands.
    in windows, I have no idea.
    However, if you are talking about a proxy, then there are many implementations already done. Proxies are almost trivial to implement these days.

  • Error: Found Null Connection

    Using JDeveloper, I set up a connection with success. However, running the program generates the following error:
    java.sql.SQLException: found null connection context
    The error persists even when I use [contextNameFromtheConnection] with #sql{...};
    Fortunately, when I switched back to SQLJ code only, setting up the connection using Oracle.connect(...), it works in JDK 1.18, but not in 1.2.2. Furthermore, by doing so, I had to leave the JDeveloper Connection standing there useless. I even can not delete it from the upper-left Navigator pane!
    I really appreciate your help. Have fun and sleepless night with ORACLE.
    Thanks for your time.
    Xiang
    null

    The 8.1.5 tools (SQLJ, and EJB CLient for example) must be run in JDK 1.1.x. The 8.1.6 versions of these should work with JDK 1.2.x

  • Crystal Reports data connection using Java beans

    Hi
    My name is Bach Ong, i'm currently perform re-configuring Crystal reports 2008 to connect via
    Java bean to Jboss server, this uses look up service on JBoss server. The connection is using Connect
    look up using the properties:
    java.naming.provider.url=jnp://emgsydapp121:10499
    java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
    java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
    for file CRConfig.xml i put as follows:
    <JDBCURL></JDBCURL>
    <JDBCClassName></JDBCClassName>
    <JDBCUserName></JDBCUserName>
    <JNDIURL>jnp://emgsydapp121:10499</JNDIURL>
    <JNDIConnectionFactory>org.jnp.interfaces.NamingContextFactor
    y</JNDIConnectionFactory>
    <JNDIInitContext>/</JNDIInitContext>
    <JNDIUserName></JNDIUserName>
    Can you advise us if this step is correct, and is there any
    documentation that can guide us to right direction.
    for Java testing in Eclipse using remote call class it is working suing the following code:
            Properties p = new Properties();
            p.put(Context.INITIAL_CONTEXT_FACTORY,
            "org.jnp.interfaces.NamingContextFactory");
            p.put(Context.URL_PKG_PREFIXES, "jboss.naming:org.jnp.interfaces");
            p.put(Context.PROVIDER_URL, "jnp://emgsydapp121:10499");
             InitialContext ctx = new InitialContext(p);
      Date asAtDate = CrystalUtils.convertToDate("2014-01-01", CrystalUtils.relativeToToday(0), false);
         String asxCode = "BHP";
         ClosingPricesReportRequest criteria = new ClosingPricesReportRequest(asAtDate, asxCode);
         InitialContext context = new InitialContext(p);
         ClosingPricesReportService ejb = (ClosingPricesReportService) context.lookup(ClosingPricesReportService.REMOTE_JNDI);
         ClosingPricesReport report = ejb.createMTMClosingPriceReport(criteria);
         System.out.println(report.getClosingPrices()[0].getClosingPrice());
         testval = report.getClosingPrices()[0].getClosingPrice().toString();
         System.out.println(testval);
    when i run the tes code the results as follow:
    10:49:45,244 DEBUG [SecurityAssociation ] Using ThreadLocal: false
    10:49:45,338 DEBUG [MicroSocketClientInvoker ] SocketClientInvoker[709446e4, socket://emgsydapp121:10473] constructed
    10:49:45,338 DEBUG [MicroRemoteClientInvoker ] SocketClientInvoker[709446e4, socket://emgsydapp121:10473] connecting
    10:49:45,338 DEBUG [MicroSocketClientInvoker ] Creating semaphore with size 50
    10:49:45,338 DEBUG [MicroRemoteClientInvoker ] SocketClientInvoker[709446e4, socket://emgsydapp121:10473] connected
    10:49:45,369 DEBUG [ClientSocketWrapper ] reset timeout: 0
    10:49:45,650 DEBUG [InvokerRegistry ] removed SocketClientInvoker[709446e4, socket://emgsydapp121:10473] from registry
    10:49:45,650 DEBUG [MicroSocketClientInvoker ] SocketClientInvoker[709446e4, socket://emgsydapp121:10473] disconnecting ...
    10:49:45,650 DEBUG [SocketWrapper ] ClientSocketWrapper[Socket[addr=/10.137.2.40,port=10473,localport=64150].2cba5bdb] closing
    37.99000000000000198951966012828052043914794921875
    37.99000000000000198951966012828052043914794921875
    Can anyone assist me in convert the above settings to get access by Crystal reports.
    My attemp current are below:
    public class CFDClosingPricesRpt extends CrystalReport {    
        //Constructor
        public CFDClosingPricesRpt(){
            super(ClosingPriceBean.INSTANCE);
         * Returns the ResultSet for this report to Crystal.
         * @param asxCode
         * @param asAtDateString
         * @return
    public ResultSet getNewReport(String asxCode, String asAtDateString) {                     
         try {
             Properties p = new Properties();
             p.put(Context.INITIAL_CONTEXT_FACTORY,
             "org.jnp.interfaces.NamingContextFactory");
             p.put(Context.URL_PKG_PREFIXES, "jboss.naming:org.jnp.interfaces");
             p.put(Context.PROVIDER_URL, "jnp://emgsydapp121:10499");
             //InitialContext ctx = new InitialContext(p);
             clearCachedReportBeans();     
       Date asAtDate = CrystalUtils.convertToDate("2013-01-01", CrystalUtils.relativeToToday(0), false);
          asxCode = "BHP";
          ClosingPricesReportRequest criteria = new ClosingPricesReportRequest(asAtDate, asxCode);
          //ClosingPricesReportService ejb = (ClosingPricesReportService) ctx.lookup(ClosingPricesReportService.REMOTE_JNDI);
          ClosingPricesReportService ejb = (ClosingPricesReportService) ServiceLocator.getInstance().getService(ClosingPricesReportService.REMOTE_JNDI);           
          ClosingPricesReport report = ejb.createClosingPriceReport(criteria);
          // assemble Crystal-friendly DTO
          Collection closingPrices = Arrays.asList(report.getClosingPrices());
          for (Iterator iter = closingPrices.iterator(); iter.hasNext();) {
                    MBLXClosingPrice cp = (MBLXClosingPrice) iter.next();               
                    if (cp==null) continue;               
                    addReportBean(new ClosingPriceBean( report.getSuppliedDate(),
                                cp.getClosingPrice(),
                                cp.getAsxCode()));
      } catch (Throwable x) {     
          saveErrorMessage(x);
      return getAsResultSet();             
    Thanks
    Bach Ong

    Hi Don Thanks for the reply.
    I've was able to connect via Java beans and JNDI. But this one is going the JNDI of JBoss sever, which the JNDI already configure and working for Crystal reports v10.
    Bach

  • How to create database connection and how to call it using Java

    Hi,
    Good day! I'd like to know how I can create a db connection in JDev, then use this connection to retrieve data using a Java Class? I've seen using New Gallery > Database Connection. But I'm not sure how I can access this connection using Java and display some output from the retrieved records.
    Any steps/tutorial link is appreciated.
    Thanks in advance,
    Rian

    Hi,
    If you need to access the connection in the entity object then refer http://download.oracle.com/docs/cd/E15523_01/web.1111/b31974/bcadvgen.htm#BABEIFAI i.e in MODEL.
    But if you want to access connection in ViewController part of application then you need to do it manually.For this i am giving you my code for reference.------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    import java.sql.Connection;
    import java.sql.ResultSet;
    import java.sql.SQLException;
    import java.sql.Statement;
    import javax.faces.context.FacesContext;
    import oracle.jdbc.pool.OracleDataSource;
    public class DataHandler {
    String jdbcUrl = null;
    String userid = null;
    String password = null;
    Connection conn;
    public static final String CONNECTION_STRING =
    FacesContext.getCurrentInstance().getExternalContext().getInitParameter("connectionString");
    public static final String USER_NAME =
    FacesContext.getCurrentInstance().getExternalContext().getInitParameter("userName");
    public static final String PASSWORD =
    FacesContext.getCurrentInstance().getExternalContext().getInitParameter("password");
    public DataHandler(String jdbcUrl, String userid, String password,
    boolean shouldConnect) throws SQLException {
    this.jdbcUrl = jdbcUrl;
    this.userid = userid;
    this.password = password;
    if (shouldConnect) {
    connect();
    public void connect() throws SQLException {
    OracleDataSource ds;
    ds = new OracleDataSource();
    ds.setURL(jdbcUrl);
    conn = ds.getConnection(userid, password);
    public Connection getConnection() {
    return conn;
    public ResultSet executeQuery(String sql) throws SQLException {
    Statement s = conn.createStatement();
    return s.executeQuery(sql);
    public void closeConnection() throws SQLException {
    if (!conn.isClosed()) {
    conn.close();
    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  • Open connections between AS Java and AS ABAP when using JRA

    Hi, we have a problem with open connections and hope that someone here could give me hint where to find a solution.
    The situation is that we open a connection from a Java application to an AS ABAP. In detail, the application first connects to a statefull session bean on the AS Java by RMI. The bean communicates with the associated AS ABAP by the Java Resource Adapter (JRA).
    All interactions between all components work correctly. But even after we close the application, manually close of the connections (on side of the AS Java) , remove all created and used session beans there are still open connections between the AS ABAP and the AS Java.
    The transaction smgw (Gateway Monitor) shows open connections from jlaunch to our local SAP gateway using the internal communication protocol. Obviously, the established connections are not closed, even when they are open for a week or longer.
    After opening 100 connections, the AS ABAP denies additional connection attempts.
    We have been able to close all open connections by restarting the AS Java or by restarting the Connector over the Visual Administrator (path: Cluster – Server – Services – Connector Container – “select the right connector” – stop / start).
    We have developed our application similar to the tutorial from [https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ad09cd07-0a01-0010-93a9-933e247d3ba4]
    Can someone explain to us why the connections stay open for so long? Is there no timeout mechanism? Or is there some way to close the connections from our Java application?

    Hello,
    maybe someone can help us with our problem.
    We have developed our application similar to the tutorial from https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ad09cd07-0a01-0010-93a9-933e247d3ba4 and it was running without problem with the SP12, now we change our system to SP16 and we are having the problem described in note 1083348, but as you can see, for us it was working with SP12 and now it doesn't work with SP16....
    Here is part of our code....
        public List getAll() {
            String functionName = "bla";
            try {
                openConnection();
                MappedRecord response = (MappedRecord) interaction.execute(null, request);
                MappedRecord record = (MappedRecord) response.get("E_S_RETURN_CODE");
                if (((String) record.get("RETURN_CODE")).equalsIgnoreCase("E")) {
                    throw new SQLException((String) record.get("RETURN_TXT"));
            catch (ResourceException exc) {
                throw new EJBException(".");
            catch (SQLException exc) {
                throw new EJBException(".");
            finally {
                closeConnection();
        protected void openConnection() {
            try {
                connection = connectionFactory.getConnection();
                interaction = connection.createInteraction();
            catch (ResourceException exc) {
                interaction = null;
                connection = null;
                throw new EJBException(getExceptionText(exc));
      protected void closeConnection() {
           try {
                if (interaction != null) {
                    interaction.close();
                if (connection != null) {
                    connection.close();
            catch (ResourceException exc) {
                throw new EJBException(".");
    With that code we are getting this error: "Connection handle is already closed and no longer associated with a managed connection" everytime we try to close the connection in the method closeConnection().
    We were thinking that maybe we should not close the connections, because the were already close, and tried not to close the connection (connection.close()), but then after a few time we are getting the following error, because we are not closing the connections:
    Connection to ABAP System could not be opened, because the Connection Factory returns "Cannot get connection for 120 seconds. Possible reasons: 1) Connections are cached within SystemThread(can be any server service or any code invoked within SystemThread in the SAP J2EE Engine), 2) The pool size of adapter "eis/..." is not enough according to the current load of the system or 3) The specified time to wait for connection is not enough according to the pool size and current load of the system. In case 1) the solution is to check for cached connections using the Connector Service list-conns command, in case 2) to increase the size of the pool and in case 3) to increase the time to wait for connection property. In case of application thread, there is an automatic mechanism which detects unclosed connections and unfinished transactions.". Please check the connection defined for the Connection Factory of the Java Resource Adapter with JNDI name...
    Any help?

  • Error Null Databinding context encountered -WSDL to Java webservice convert

    HI,
    I have been trying to generate service and client from WSDL using Jdeveloper11 and im unable to progress on this particular WSDL, i was succesfull in creating the client and service for a sample Apache WSDL using the Jdeveloper. If anyone can point out the issue in this WSDL or is there a bug in Jdeveloper when handling complex type? i attach the WSDL that i used, now note that the WSDL calls for another WSDL import witin it, if i comment out the import and its bindings im able to proceed,
    WSDL-1
    <!-- Tigerstripe : Operations relating to Alarm -->
    <wsdl:operation name="getAlarmsByKeys">
    <wsdl:input name="getAlarmsByKeysRequest" message="fmWS-v1-0:getAlarmsByKeysRequest" />
    <wsdl:output name="getAlarmsByKeysResponse" message="fmWS-v1-0:getAlarmsByKeysResponse" />
    <wsdl:fault name="getAlarmsByKeysException" message="fmWS-v1-0:getAlarmsByKeysException" />
    </wsdl:operation>
    <wsdl:operation name="getAlarmsByTemplate">
    <wsdl:input name="getAlarmsByTemplateRequest" message="fmWS-v1-0:getAlarmsByTemplateRequest" />
    <wsdl:output name="getAlarmsByTemplateResponse" message="fmWS-v1-0:getAlarmsByTemplateResponse" />
    <wsdl:fault name="getAlarmsByTemplateException" message="fmWS-v1-0:getAlarmsByTemplateException" />
    </wsdl:operation>
    <wsdl:operation name="queryAlarms">
    <wsdl:input name="queryAlarmsRequest" message="fmWS-v1-0:queryAlarmsRequest" />
    <wsdl:output name="queryAlarmsResponse" message="fmWS-v1-0:queryAlarmsResponse" />
    <wsdl:fault name="queryAlarmsException" message="fmWS-v1-0:queryAlarmsException" />
    </wsdl:operation>
    <!-- Tigerstripe : Operations for Interface artifact methods ( JVTAlarmCreationSession ) -->
    <wsdl:operation name="getAlarmSpecificInfoTypes">
    <wsdl:input
    name="getAlarmSpecificInfoTypesRequest"
    message="fmWS-v1-0:getAlarmSpecificInfoTypesRequest" />
    <wsdl:output
    name="getAlarmSpecificInfoTypesResponse"
    message="fmWS-v1-0:getAlarmSpecificInfoTypesResponse" />
    <wsdl:fault
    name="getAlarmSpecificInfoTypesException"
    message="fmWS-v1-0:getAlarmSpecificInfoTypesException" />
    </wsdl:operation>
    <wsdl:operation name="getVersion">
    <wsdl:input
    name="getVersionRequest"
    message="fmWS-v1-0:getVersionRequest" />
    <wsdl:output
    name="getVersionResponse"
    message="fmWS-v1-0:getVersionResponse" />
    <wsdl:fault
    name="getVersionException"
    message="fmWS-v1-0:getVersionException" />
    </wsdl:operation>
    <wsdl:operation name="createAlarms">
    <wsdl:input
    name="createAlarmsRequest"
    message="fmWS-v1-0:createAlarmsRequest" />
    <wsdl:output
    name="createAlarmsResponse"
    message="fmWS-v1-0:createAlarmsResponse" />
    <wsdl:fault
    name="createAlarmsException"
    message="fmWS-v1-0:createAlarmsException" />
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="JVTAlarmCreationSessionSoapBinding"
    type="fmWS-v1-0:JVTAlarmCreationSessionWSPort">
    <soap:binding style="document"
    transport="http://schemas.xmlsoap.org/soap/http" />
    <!-- Tigerstripe : Bindings relating to Alarm -->
    <wsdl:operation name="getAlarmsByKeys">
    <soap:operation soapAction="getAlarmsByKeys" style="document" />
    <wsdl:input>
    <soap:body parts="parameters" use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body parts="parameters" use="literal" />
    </wsdl:output>
    <wsdl:fault name="getAlarmsByKeysException">
    <soap:fault name="getAlarmsByKeysException" use="literal" />
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="getAlarmsByTemplate">
    <soap:operation soapAction="getAlarmsByTemplate" style="document" />
    <wsdl:input>
    <soap:body parts="parameters" use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body parts="parameters" use="literal" />
    </wsdl:output>
    <wsdl:fault name="getAlarmsByTemplateException">
    <soap:fault name="getAlarmsByTemplateException" use="literal" />
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="queryAlarms">
    <soap:operation soapAction="queryAlarms" style="document" />
    <wsdl:input>
    <soap:body parts="parameters" use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body parts="parameters" use="literal" />
    </wsdl:output>
    <wsdl:fault name="queryAlarmsException">
    <soap:fault name="queryAlarmsException" use="literal" />
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="getAlarmSpecificInfoTypes">
    <soap:operation soapAction="getAlarmSpecificInfoTypes" style="document" />
    <wsdl:input>
    <soap:body parts="parameters" use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body parts="parameters" use="literal" />
    </wsdl:output>
    <wsdl:fault name ="getAlarmSpecificInfoTypesException">
    <soap:fault name ="getAlarmSpecificInfoTypesException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="getVersion">
    <soap:operation soapAction="getVersion" style="document" />
    <wsdl:input>
    <soap:body parts="parameters" use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body parts="parameters" use="literal" />
    </wsdl:output>
    <wsdl:fault name ="getVersionException">
    <soap:fault name ="getVersionException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="createAlarms">
    <soap:operation soapAction="createAlarms" style="document" />
    <wsdl:input>
    <soap:body parts="parameters" use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body parts="parameters" use="literal" />
    </wsdl:output>
    <wsdl:fault name ="createAlarmsException">
    <soap:fault name ="createAlarmsException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    </wsdl:binding>
    <!-- Binding for the Notification Producer -->
    <!-- <wsdl:binding name="NotificationProducerSoapBinding" type="wsnt:NotificationProducer">
    <soap:binding style="document"
    transport="http://schemas.xmlsoap.org/soap/http" />-->
    <!-- =========== NotificationProducer Specific ============== -->
    <!-- <wsdl:operation name="Subscribe">
    <soap:operation soapAction="Subscribe" style="document"/>
    <wsdl:input>
    <soap:body use="literal"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal"/>
    </wsdl:output>
    <wsdl:fault name="ResourceUnknownFault">
    <soap:fault name="ResourceUnknownFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="SubscribeCreationFailedFault">
    <soap:fault name="SubscribeCreationFailedFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="TopicExpressionDialectUnknownFault">
    <soap:fault name="TopicExpressionDialectUnknownFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="InvalidFilterFault">
    <soap:fault name="InvalidFilterFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="InvalidTopicExpressionFault">
    <soap:fault name="InvalidTopicExpressionFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="TopicNotSupportedFault">
    <soap:fault name="TopicNotSupportedFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="InvalidProducerPropertiesExpressionFault">
    <soap:fault name="InvalidProducerPropertiesExpressionFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="InvalidMessageContentExpressionFault">
    <soap:fault name="InvalidMessageContentExpressionFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="UnacceptableInitialTerminationTimeFault">
    <soap:fault name="UnacceptableInitialTerminationTimeFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="UnrecognizedPolicyRequestFault">
    <soap:fault name="UnrecognizedPolicyRequestFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="UnsupportedPolicyRequestFault">
    <soap:fault name="UnsupportedPolicyRequestFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="NotifyMessageNotSupportedFault">
    <soap:fault name="NotifyMessageNotSupportedFault" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="GetCurrentMessage">
    <soap:operation soapAction="GetCurrentMessage" style="document" />
    <wsdl:input>
    <soap:body use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" />
    </wsdl:output>
    <wsdl:fault name="ResourceUnknownFault">
    <soap:fault name="ResourceUnknownFault" use="literal" />
    </wsdl:fault>
    <wsdl:fault name="TopicExpressionDialectUnknownFault">
    <soap:fault name="TopicExpressionDialectUnknownFault" use="literal" />
    </wsdl:fault>
    <wsdl:fault name="InvalidTopicExpressionFault">
    <soap:fault name="InvalidTopicExpressionFault" use="literal" />
    </wsdl:fault>
    <wsdl:fault name="TopicNotSupportedFault">
    <soap:fault name="TopicNotSupportedFault" use="literal" />
    </wsdl:fault>
    <wsdl:fault name="NoCurrentMessageOnTopicFault">
    <soap:fault name="NoCurrentMessageOnTopicFault" use="literal" />
    </wsdl:fault>
    <wsdl:fault name="MultipleTopicsSpecifiedFault">
    <soap:fault name="MultipleTopicsSpecifiedFault" use="literal" />
    </wsdl:fault>
    </wsdl:operation>
    </wsdl:binding>-->
    <!-- Binding for the SubscriptionManager -->
    <!-- <wsdl:binding name="SubscriptionManagerSoapBinding" type="wsnt:PausableSubscriptionManager">
    <soap:binding style="document"
    transport="http://schemas.xmlsoap.org/soap/http" />-->
    <!-- ========= SubscriptionManager specific operations ====== -->
    <!-- <wsdl:operation name="PauseSubscription">
    <soap:operation soapAction="PauseSubscription" style="document" />
    <wsdl:input>
    <soap:body use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" />
    </wsdl:output>
    <wsdl:fault name="ResourceUnknownFault">
    <soap:fault name="ResourceUnknownFault" use="literal" />
    </wsdl:fault>
    <wsdl:fault name="PauseFailedFault">
    <soap:fault name="PauseFailedFault" use="literal" />
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="Renew">
    <soap:operation soapAction="Renew" style="document" />
    <wsdl:input>
    <soap:body use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" />
    </wsdl:output>
    <wsdl:fault name="ResourceUnknownFault">
    <soap:fault name="ResourceUnknownFault" use="literal" />
    </wsdl:fault>
    <wsdl:fault name="UnacceptableTerminationTimeFault">
    <soap:fault name="UnacceptableTerminationTimeFault" use="literal" />
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="Unsubscribe">
    <soap:operation soapAction="Unsubscribe" style="document" />
    <wsdl:input>
    <soap:body use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" />
    </wsdl:output>
    <wsdl:fault name="ResourceUnknownFault">
    <soap:fault name="ResourceUnknownFault" use="literal" />
    </wsdl:fault>
    <wsdl:fault name="UnableToDestroySubscriptionFault">
    <soap:fault name="UnableToDestrySubscriptionFault" use="literal" />
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="ResumeSubscription">
    <soap:operation soapAction="ResumeSubscription" style="document" />
    <wsdl:input>
    <soap:body use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" />
    </wsdl:output>
    <wsdl:fault name="ResourceUnknownFault">
    <soap:fault name="ResourceUnknownFault" use="literal" />
    </wsdl:fault>
    <wsdl:fault name="ResumeFailedFault">
    <soap:fault name="ResumeFailedFault" use="literal" />
    </wsdl:fault>
    </wsdl:operation>
    </wsdl:binding>-->
    <wsdl:service name="JVTAlarmCreationSessionWebService">
    <wsdl:port name="JVTAlarmCreationSessionWSPort"
    binding="fmWS-v1-0:JVTAlarmCreationSessionSoapBinding">
    <soap:address location="http://localhost/JVTAlarmCreationSessionWebService/JVTAlarmCreationSession" />
    </wsdl:port>
    <!--wsdl:port name="NotificationProducerPort" binding="wsnt:NotificationProducerSoapBinding">
    <soap:address location="http://localhost/JVTAlarmCreationSessionWebService/NotificationProducer"/>
    </wsdl:port>
    <wsdl:port name="SubscriptionManagerPort" binding="wsnt:SubscriptionManagerSoapBinding">
    <soap:address location="http://localhost/JVTAlarmCreationSessionWebService/SubscriptionManager"/>
    </wsdl:port-->
    </wsdl:service>
    </wsdl:definitions>
    WSDL-2 imported in the above WSDL
    <?xml version="1.0" encoding="utf-8"?>
    <!--
    OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS's procedures with respect to rights in OASIS specifications can be found at the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification, can be obtained from the OASIS Executive Director.
    OASIS invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to implement this specification. Please address the information to the OASIS Executive Director.
    Copyright (C) OASIS Open (2004-2006). All Rights Reserved.
    This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document must be followed, or as required to translate it into languages other than English.
    The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.
    This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
    -->
    <wsdl:definitions name="WS-BaseNotification"
    targetNamespace="http://docs.oasis-open.org/wsn/bw-2"
    xmlns:wsntw="http://docs.oasis-open.org/wsn/bw-2"
    xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2"
    xmlns:wsa="http://www.w3.org/2005/08/addressing"
    xmlns:wsrf-rw="http://docs.oasis-open.org/wsrf/rw-2"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <!-- ========================== Imports =========================== -->
    <wsdl:import
    namespace="http://docs.oasis-open.org/wsrf/rw-2"
    location="rw-2.wsdl"/>
    <!-- ===================== Types Definitions ====================== -->
    <wsdl:types>
    <xsd:schema elementFormDefault="qualified">
    <xsd:import
    namespace="http://docs.oasis-open.org/wsn/b-2"
    schemaLocation="b-2.xsd"/>
    </xsd:schema>
    </wsdl:types>
    <!-- ================ NotificationConsumer::Notify ================
    Notify(
    NotificationMessage
    (SubscriptionReference, TopicExpression, ProducerReference,
    Message)*
    returns: n/a (one way)
    -->
    <wsdl:message name="Notify">
    <wsdl:part name="Notify" element="wsnt:Notify"/>
    </wsdl:message>
    <!-- ============== NotificationProducer::Subscribe ===============
    Subscribe(
    (ConsumerEndpointReference, [Filter], [SubscriptionPolicy],
    [InitialTerminationTime])
    returns: WS-Resource qualified EPR to a Subscription
    -->
    <wsdl:message name="SubscribeRequest" >
    <wsdl:part name="SubscribeRequest"
    element="wsnt:Subscribe"/>
    </wsdl:message>
    <wsdl:message name="SubscribeResponse">
    <wsdl:part name="SubscribeResponse"
    element="wsnt:SubscribeResponse"/>
    </wsdl:message>
    <wsdl:message name="SubscribeCreationFailedFault">
    <wsdl:part name="SubscribeCreationFailedFault"
    element="wsnt:SubscribeCreationFailedFault" />
    </wsdl:message>
    <wsdl:message name="TopicExpressionDialectUnknownFault">
    <wsdl:part name="TopicExpressionDialectUnknownFault"
    element="wsnt:TopicExpressionDialectUnknownFault" />
    </wsdl:message>
    <wsdl:message name="InvalidFilterFault">
    <wsdl:part name="InvalidFilterFault"
    element="wsnt:InvalidFilterFault" />
    </wsdl:message>
    <wsdl:message name="InvalidProducerPropertiesExpressionFault">
    <wsdl:part name="InvalidProducerPropertiesExpressionFault"
    element="wsnt:InvalidProducerPropertiesExpressionFault" />
    </wsdl:message>
    <wsdl:message name="InvalidMessageContentExpressionFault">
    <wsdl:part name="InvalidMessageContentExpressionFault"
    element="wsnt:InvalidMessageContentExpressionFault" />
    </wsdl:message>
    <wsdl:message name="UnrecognizedPolicyRequestFault">
    <wsdl:part name="UnrecognizedPolicyRequestFault"
    element="wsnt:UnrecognizedPolicyRequestFault" />
    </wsdl:message>
    <wsdl:message name="UnsupportedPolicyRequestFault">
    <wsdl:part name="UnsupportedPolicyRequestFault"
    element="wsnt:UnsupportedPolicyRequestFault" />
    </wsdl:message>
    <wsdl:message name="NotifyMessageNotSupportedFault">
    <wsdl:part name="NotifyMessageNotSupportedFault"
    element="wsnt:NotifyMessageNotSupportedFault" />
    </wsdl:message>
    <wsdl:message name="UnacceptableInitialTerminationTimeFault">
    <wsdl:part name="UnacceptableInitialTerminationTimeFault"
    element="wsnt:UnacceptableInitialTerminationTimeFault"/>
    </wsdl:message>
    <!-- ========== NotificationProducer::GetCurrentMessage ===========
    GetCurrentMessage(topicExpression)
    returns: a NotificationMessage (xsd:any)
    -->
    <wsdl:message name="GetCurrentMessageRequest">
    <wsdl:part name="GetCurrentMessageRequest"
    element="wsnt:GetCurrentMessage"/>
    </wsdl:message>
    <wsdl:message name="GetCurrentMessageResponse">
    <wsdl:part name="GetCurrentMessageResponse"
    element="wsnt:GetCurrentMessageResponse"/>
    </wsdl:message>
    <wsdl:message name="InvalidTopicExpressionFault">
    <wsdl:part name="InvalidTopicExpressionFault"
    element="wsnt:InvalidTopicExpressionFault" />
    </wsdl:message>
    <wsdl:message name="TopicNotSupportedFault">
    <wsdl:part name="TopicNotSupportedFault"
    element="wsnt:TopicNotSupportedFault" />
    </wsdl:message>
    <wsdl:message name="MultipleTopicsSpecifiedFault">
    <wsdl:part name="MultipleTopicsSpecifiedFault"
    element="wsnt:MultipleTopicsSpecifiedFault" />
    </wsdl:message>
    <wsdl:message name="NoCurrentMessageOnTopicFault">
    <wsdl:part name="NoCurrentMessageOnTopicFault"
    element="wsnt:NoCurrentMessageOnTopicFault" />
    </wsdl:message>
    <!-- ========== PullPoint::GetMessages ===========
    GetMessages(MaximumNumber)
    returns: NotificationMessage list
    -->
    <wsdl:message name="GetMessagesRequest">
    <wsdl:part name="GetMessagesRequest"
    element="wsnt:GetMessages"/>
    </wsdl:message>
    <wsdl:message name="GetMessagesResponse">
    <wsdl:part name="GetMessagesResponse"
    element="wsnt:GetMessagesResponse"/>
    </wsdl:message>
    <wsdl:message name="UnableToGetMessagesFault">
    <wsdl:part name="UnableToGetMessagesFault"
    element="wsnt:UnableToGetMessagesFault"/>
    </wsdl:message>
    <!-- ========== PullPoint::DestroyPullPoint ===========
    DestroyPullPoint()
    returns: void
    -->
    <wsdl:message name="DestroyPullPointRequest">
    <wsdl:part name="DestroyPullPointRequest"
    element="wsnt:DestroyPullPoint"/>
    </wsdl:message>
    <wsdl:message name="DestroyPullPointResponse">
    <wsdl:part name="DestroyPullPointResponse"
    element="wsnt:DestroyPullPointResponse"/>
    </wsdl:message>
    <wsdl:message name="UnableToDestroyPullPointFault">
    <wsdl:part name="UnableToDestroyPullPointFault"
    element="wsnt:UnableToDestroyPullPointFault"/>
    </wsdl:message>
    <!-- ========== PullPoint::CreatePullPoint ===========
    CreatePullPoint()
    returns: PullPoint (wsa:EndpointReference)
    -->
    <wsdl:message name="CreatePullPointRequest">
    <wsdl:part name="CreatePullPointRequest"
    element="wsnt:CreatePullPoint"/>
    </wsdl:message>
    <wsdl:message name="CreatePullPointResponse">
    <wsdl:part name="CreatePullPointResponse"
    element="wsnt:CreatePullPointResponse"/>
    </wsdl:message>
    <wsdl:message name="UnableToCreatePullPointFault">
    <wsdl:part name="UnableToCreatePullPointFault"
    element="wsnt:UnableToCreatePullPointFault"/>
    </wsdl:message>
    <!-- ================ SubscriptionManager::Renew ==================
    Renew( Duration | AbsoluteTime)
    returns: (New Termination Time [CurrentTime])
    -->
    <wsdl:message name="RenewRequest">
    <wsdl:part name="RenewRequest"
    element="wsnt:Renew"/>
    </wsdl:message>
    <wsdl:message name="RenewResponse">
    <wsdl:part name="RenewResponse"
    element="wsnt:RenewResponse"/>
    </wsdl:message>
    <wsdl:message name="UnacceptableTerminationTimeFault">
    <wsdl:part name="UnacceptableTerminationTimeFault"
    element="wsnt:UnacceptableTerminationTimeFault" />
    </wsdl:message>
    <!-- ============== SubscriptionManager::Unsubscribe ===============
    Unsubscribe()
    returns: empty
    -->
    <wsdl:message name="UnsubscribeRequest">
    <wsdl:part name="UnsubscribeRequest"
    element="wsnt:Unsubscribe"/>
    </wsdl:message>
    <wsdl:message name="UnsubscribeResponse">
    <wsdl:part name="UnsubscribeResponse"
    element="wsnt:UnsubscribeResponse"/>
    </wsdl:message>
    <wsdl:message name="UnableToDestroySubscriptionFault">
    <wsdl:part name="UnableToDestroySubscriptionFault"
    element="wsnt:UnableToDestroySubscriptionFault" />
    </wsdl:message>
    <!-- ========== SubscriptionManager::PauseSubscription ============
    PauseSubscription()
    returns: empty
    -->
    <wsdl:message name="PauseSubscriptionRequest">
    <wsdl:part name="PauseSubscriptionRequest"
    element="wsnt:PauseSubscription"/>
    </wsdl:message>
    <wsdl:message name="PauseSubscriptionResponse">
    <wsdl:part name="PauseSubscriptionResponse"
    element="wsnt:PauseSubscriptionResponse"/>
    </wsdl:message>
    <wsdl:message name="PauseFailedFault">
    <wsdl:part name="PauseFailedFault"
    element="wsnt:PauseFailedFault" />
    </wsdl:message>
    <!-- ========= SubscriptionManager::ResumeSubscription ============
    ResumeSubscription()
    returns: empty
    -->
    <wsdl:message name="ResumeSubscriptionRequest">
    <wsdl:part name="ResumeSubscriptionRequest"
    element="wsnt:ResumeSubscription"/>
    </wsdl:message>
    <wsdl:message name="ResumeSubscriptionResponse">
    <wsdl:part name="ResumeSubscriptionResponse"
    element="wsnt:ResumeSubscriptionResponse"/>
    </wsdl:message>
    <wsdl:message name="ResumeFailedFault">
    <wsdl:part name="ResumeFailedFault"
    element="wsnt:ResumeFailedFault" />
    </wsdl:message>
    <!-- =================== PortType Definitions ===================== -->
    <!-- ========= NotificationConsumer PortType Definition =========== -->
    <wsdl:portType name="NotificationConsumer">
    <wsdl:operation name="Notify">
    <wsdl:input message="wsntw:Notify" />
    </wsdl:operation>
    </wsdl:portType>
    <!-- ========= NotificationProducer PortType Definition =========== -->
    <wsdl:portType name="NotificationProducer">
    <wsdl:operation name="Subscribe">
    <wsdl:input message="wsntw:SubscribeRequest" />
    <wsdl:output message="wsntw:SubscribeResponse" />
    <wsdl:fault name="ResourceUnknownFault"
    message="wsrf-rw:ResourceUnknownFault" />
    <wsdl:fault name="InvalidFilterFault"
    message="wsntw:InvalidFilterFault"/>
    <wsdl:fault name="TopicExpressionDialectUnknownFault"
    message="wsntw:TopicExpressionDialectUnknownFault"/>
    <wsdl:fault name="InvalidTopicExpressionFault"
    message="wsntw:InvalidTopicExpressionFault" />
    <wsdl:fault name="TopicNotSupportedFault"
    message="wsntw:TopicNotSupportedFault" />
    <wsdl:fault name="InvalidProducerPropertiesExpressionFault"
    message="wsntw:InvalidProducerPropertiesExpressionFault"/>
    <wsdl:fault name="InvalidMessageContentExpressionFault"
    message="wsntw:InvalidMessageContentExpressionFault"/>
    <wsdl:fault name="UnacceptableInitialTerminationTimeFault"
    message="wsntw:UnacceptableInitialTerminationTimeFault"/>
    <wsdl:fault name="UnrecognizedPolicyRequestFault"
    message="wsntw:UnrecognizedPolicyRequestFault"/>
    <wsdl:fault name="UnsupportedPolicyRequestFault"
    message="wsntw:UnsupportedPolicyRequestFault"/>
    <wsdl:fault name="NotifyMessageNotSupportedFault"
    message="wsntw:NotifyMessageNotSupportedFault"/>
    <wsdl:fault name="SubscribeCreationFailedFault"
    message="wsntw:SubscribeCreationFailedFault"/>
    </wsdl:operation>
    <wsdl:operation name="GetCurrentMessage">
    <wsdl:input message="wsntw:GetCurrentMessageRequest"/>
    <wsdl:output message="wsntw:GetCurrentMessageResponse"/>
    <wsdl:fault name="ResourceUnknownFault"
    message="wsrf-rw:ResourceUnknownFault" />
    <wsdl:fault name="TopicExpressionDialectUnknownFault"
    message="wsntw:TopicExpressionDialectUnknownFault"/>
    <wsdl:fault name="InvalidTopicExpressionFault"
    message="wsntw:InvalidTopicExpressionFault" />
    <wsdl:fault name="TopicNotSupportedFault"
    message="wsntw:TopicNotSupportedFault" />
    <wsdl:fault name="NoCurrentMessageOnTopicFault"
    message="wsntw:NoCurrentMessageOnTopicFault" />
    <wsdl:fault name="MultipleTopicsSpecifiedFault"
    message="wsntw:MultipleTopicsSpecifiedFault" />
    </wsdl:operation>
    </wsdl:portType>
    <!-- ========== PullPoint PortType Definition ===================== -->
    <wsdl:portType name="PullPoint">
    <wsdl:operation name="GetMessages">
    <wsdl:input name="GetMessagesRequest"
    message="wsntw:GetMessagesRequest" />
    <wsdl:output name="GetMessagesResponse"
    message="wsntw:GetMessagesResponse" />
    <wsdl:fault name="ResourceUnknownFault"
    message="wsrf-rw:ResourceUnknownFault" />
    <wsdl:fault name="UnableToGetMessagesFault"
    message="wsntw:UnableToGetMessagesFault" />
    </wsdl:operation>
    <wsdl:operation name="DestroyPullPoint">
    <wsdl:input name="DestroyPullPointRequest"
    message="wsntw:DestroyPullPointRequest" />
    <wsdl:output name="DestroyPullPointResponse"
    message="wsntw:DestroyPullPointResponse" />
    <wsdl:fault name="ResourceUnknownFault"
    message="wsrf-rw:ResourceUnknownFault"/>
    <wsdl:fault name="UnableToDestroyPullPointFault"
    message="wsntw:UnableToDestroyPullPointFault" />
    </wsdl:operation>
    <wsdl:operation name="Notify">
    <wsdl:input message="wsntw:Notify"/>
    </wsdl:operation>
    </wsdl:portType>
    <!-- ========== CreatePullPoint PortType Definition =============== -->
    <wsdl:portType name="CreatePullPoint">
    <wsdl:operation name="CreatePullPoint">
    <wsdl:input name="CreatePullPointRequest"
    message="wsntw:CreatePullPointRequest" />
    <wsdl:output name="CreatePullPointResponse"
    message="wsntw:CreatePullPointResponse" />
    <wsdl:fault name="UnableToCreatePullPointFault"
    message="wsntw:UnableToCreatePullPointFault" />
    </wsdl:operation>
    </wsdl:portType>
    <!-- ========== SubscriptionManager PortType Definition =========== -->
    <wsdl:portType name="SubscriptionManager">
    <wsdl:operation name="Renew">
    <wsdl:input name="RenewRequest"
    message="wsntw:RenewRequest" />
    <wsdl:output name="RenewResponse"
    message="wsntw:RenewResponse" />
    <wsdl:fault name="ResourceUnknownFault"
    message="wsrf-rw:ResourceUnknownFault" />
    <wsdl:fault name="UnacceptableTerminationTimeFault"
    message=
    "wsntw:UnacceptableTerminationTimeFault" />
    </wsdl:operation>
    <wsdl:operation name="Unsubscribe">
    <wsdl:input name="UnsubscribeRequest"
    message="wsntw:UnsubscribeRequest" />
    <wsdl:output name="UnsubscribeResponse"
    message="wsntw:UnsubscribeResponse" />
    <wsdl:fault name="ResourceUnknownFault"
    message="wsrf-rw:ResourceUnknownFault" />
    <wsdl:fault name="UnableToDestroySubscriptionFault"
    message=
    "wsntw:UnableToDestroySubscriptionFault" />
    </wsdl:operation>
    </wsdl:portType>
    <!-- ====== PausableSubscriptionManager PortType Definition ======= -->
    <wsdl:portType name="PausableSubscriptionManager">
    <!-- ============== Extends: SubscriptionManager ============ -->
    <wsdl:operation name="Renew">
    <wsdl:input name="RenewRequest"
    message="wsntw:RenewRequest" />
    <wsdl:output name="RenewResponse"
    message="wsntw:RenewResponse" />
    <wsdl:fault name="ResourceUnknownFault"
    message="wsrf-rw:ResourceUnknownFault" />
    <wsdl:fault name="UnacceptableTerminationTimeFault"
    message=
    "wsntw:UnacceptableTerminationTimeFault" />
    </wsdl:operation>
    <wsdl:operation name="Unsubscribe">
    <wsdl:input name="UnsubscribeRequest"
    message="wsntw:UnsubscribeRequest" />
    <wsdl:output name="UnsubscribeResponse"
    message="wsntw:UnsubscribeResponse" />
    <wsdl:fault name="ResourceUnknownFault"
    message="wsrf-rw:ResourceUnknownFault" />
    <wsdl:fault name="UnableToDestroySubscriptionFault"
    message=
    "wsntw:UnableToDestroySubscriptionFault" />
    </wsdl:operation>
    <!-- === PausableSubscriptionManager specific operations === -->
    <wsdl:operation name="PauseSubscription">
    <wsdl:input message="wsntw:PauseSubscriptionRequest"/>
    <wsdl:output message="wsntw:PauseSubscriptionResponse"/>
    <wsdl:fault name="ResourceUnknownFault"
    message="wsrf-rw:ResourceUnknownFault" />
    <wsdl:fault name="PauseFailedFault"
    message="wsntw:PauseFailedFault" />
    </wsdl:operation>
    <wsdl:operation name="ResumeSubscription">
    <wsdl:input message="wsntw:ResumeSubscriptionRequest"/>
    <wsdl:output message="wsntw:ResumeSubscriptionResponse"/>
    <wsdl:fault name="ResourceUnknownFault"
    message="wsrf-rw:ResourceUnknownFault" />
    <wsdl:fault name="ResumeFailedFault"
    message="wsntw:ResumeFailedFault" />
    </wsdl:operation>
    </wsdl:portType>
    </wsdl:definitions>
    And the error i get is [fatal error] null databinding context encountered when creating service.
    Steps i followed:
    1. Created a new project in Jdev
    2. Right clicked on project to expand Business Tier - Web Services nodes. Selected the Java web Service from WSDL.
    3. Selected WSDL to convert
    ---Says it is Fetching WSDL
    ---then says building model
    --and pops error : [fatal error] null databinding context encountered.
    Any suggestions? I'm unable to get this issue fixed for a long time.

    Hey guys,
    I couldnt get this fixed in jdeveloper, i finally gave up on using Jdeveloper for Web service creation.
    I went back to my eclipse3.2.2 and used the Eclipse WTP 1.5.4 and guess what, it had no issues generating the service and client for my WSDL.
    I am not sure Jdeveloper can compete with Eclipse functionality and ease.

  • Java stored procedures connection context

    In my Oracle database there are two java stored procedures:
    A java stored procedure P1 having
    Connection conn1 = DriverManager.getConnection("jdbc:default:connection")
    and
    a java stored procedure P2 having
    Connection conn2 = DriverManager.getConnection("jdbc:default:connection")
    P1 calls P2 using conn1.CallableStatement.
    Here is the question: does P2 inherit the connection
    context conn1 (so that actualy conn2 = conn1) or P2's transactional
    scope is separate from P1's one?
    Thanks,
    -Eugene

    AFAIK, when you run Java in the database, for local SQL data access, there is only one default connection per session, P1 and P2 should share the same transaction context.
    Kuassi

  • Error in connection to oracle using java

    hi ,
    i am tring to make a connection to oracle database using java with this code
    public class DataBase {
    public DataBase(){
    Connection connection = null;
    try {
    // Load the JDBC driver
    String driverName = "oracle.jdbc.dirver.OracleDriver";
    Class.forName(driverName);
    // Create a connection to the database
    String serverName = "http://localhost:7777";
    String portNumber = "1521";
    String sid = "ora9i";
    String url = "jdbc:oracle:thin:@" + serverName + ":" + portNumber + ":" + sid;
    String username = "scott";
    String password = "tiger";
    connection = DriverManager.getConnection(url, username, password);
    } catch (ClassNotFoundException e) {
    JOptionPane.showMessageDialog(null,"Coud not find the database driver ");
    // Could not find the database driver
    } catch (SQLException e) {
    JOptionPane.showMessageDialog(null,"Coud not connect to the database ");
    // Could not connect to the database
    public static void main(String[] args) {
    new DataBase();
    i always got the compilation error Coud not find the database driver
    i am using oracle9i and jdk1.5.0_04 and my classpath is C:\oracle\ora92\jdbc\lib\ojdbc14.zip;C:\oracle\ora92\jdbc\lib\orai18n.zip
    i am realy stuck with this so any one can help me with this probelm
    thanks alot,

    thanks for your reply,
    yes i changed the server name and i verified the location of the JDBC driver file(s) on my computer. any way i solved my problem.
    you know there was a misunderstanding in what you mean by classpath, i thought that i have to change the classpath from control panel>system>advance>enviroment variable
    and then select classpaht and edit it. i was doing this but this is didn't work.
    then i don't know why i did that
    i went to java program and select my project,right click on it and then select properties>java build path and then select "add external Jars" button and then i simply choose them and add them to my project. and finaly it worked.
    thanks alot

  • [JCoAPI] The context with the session id scope type [null] is currently used in thread HTTP Worker

    Hello to all SAP-experts.
    I have an error in SAP CE, and i can see in troubleshooting following information:
    [JCoAPI] The context with the session id [JCo_mMnig6B1YRWfNCWhW0pY0CgFOhzFTAHqyFEA_SAP:P3fshVcB4PLh3CzLBVbpf5lVRxzFTAHqyFEA_SAPyxuggqvaUEsNVbxNQybjvxH0] scope type [null] is currently used in thread HTTP Worker [@1902361406] [0x91].Current thread is HTTP Worker [@1590998042] [0x97].
    invoked at com.sap.conn.jco.rt.Context.checkBusy(Context.java:633)
    invoked at com.sap.conn.jco.rt.Context.getConnection(Context.java:153)
    invoked at com.sap.conn.jco.rt.RfcDestination.execute(RfcDestination.java:1466)
    invoked at com.sap.conn.jco.rt.RfcDestination.execute(RfcDestination.java:1437)
    invoked at com.sap.conn.jco.rt.AbapFunction.execute(AbapFunction.java:300)
    invoked at com.sap.conn.jco.rt.DefaultRequest.execute(DefaultRequest.java:68)
    invoked at com.sap.tc.cm.arfc2.model.ARFC2GenericModelClassExecutable.executeInternal(ARFC2GenericModelClassExecutable.java:107)
    invoked at com.sap.tc.cm.arfc2.model.ARFC2GenericModelClassExecutable.execute(ARFC2GenericModelClassExecutable.java:68)
    invoked at com.sap.tc.cm.arfc2.gci.ARFC2TypedModelClassExecutable.execute(ARFC2TypedModelClassExecutable.java:54)
    invoked at ru.sng.terminal.utt.terminals.wd.comp.utt_term.Utt_term.loadReasonsToStop(Utt_term.java:1542)
    invoked at ru.sng.terminal.utt.terminals.wd.comp.utt_term.Utt_term.wdDoInit(Utt_term.java:186)
    invoked at ru.sng.terminal.utt.terminals.wd.comp.utt_term.wdp.InternalUtt_term.wdDoInit(InternalUtt_term.java:1054)
    invoked at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:161)
    invoked at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:227)
    invoked at com.sap.tc.webdynpro.progmodel.components.Component.initController(Component.java:258)
    invoked at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:206)
    invoked at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:590)
    invoked at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1457)
    invoked at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:660)
    invoked at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:349)
    invoked at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:326)
    invoked at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
    invoked at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
    invoked at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:55)
    invoked at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
    invoked at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    invoked at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
    invoked at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
    invoked at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
    invoked at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
    invoked at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
    invoked at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
    invoked at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
    invoked at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    invoked at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
    invoked at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    invoked at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
    invoked at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    invoked at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
    invoked at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    invoked at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    invoked at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    invoked at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    invoked at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    invoked at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    invoked at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    invoked at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    invoked at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    invoked at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    invoked at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    invoked at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
    invoked at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    invoked at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    invoked at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
    invoked at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    invoked at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    invoked at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
    invoked at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    invoked at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    invoked at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
    invoked at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
    invoked at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
    invoked at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    invoked at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    invoked at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Please, tell how can i solve this problem ?

    Hi Konstantin,
    it has nothing to do with the number of system threads. You are obviously executing several function modules statefully in multiple threads within the same session context. Stateful requests can only be executed in an ordered manner in case they should belong together. You are using ARFC2, which is part of the WebDynpro runtime. In case you are sure that the calls are independent from each other, it might be a good idea to adjust the scope type of some of your bindings. Then the requests will be executed with different scopes depending on your configuration and you can execute them concurrently
    Best regards,
    Markus

Maybe you are looking for

  • Report for interest payable

    Hi  I am in new abap programming .below is the specification I am unable to write a code for this . I have written a bit code. Can any one help in this.its very urgent. Please help me. Interest calculation Report Table : BSIS Variable we have to take

  • Can I use the nano sim card from my HTC One (M8) for an iPhone 6?

    I am getting a Mac and with Yosemite, it's geared towards iPhones. So, I have decided I want to get an iPhone 6. However, I don't want to spend the extra money to upgrade through AT&T. If I order the iPhone 6 off the internet, can I put the nano sim

  • RSS Feed Of New Movie Rentals (UK)?

    Hi, Does anyone know of an RSS feed that tracks new Movie Rentals added to the UK iTunes Store? It would be really to automatically be notified when any movies are added, instead of having to manually browse the store, looking out for changes.

  • Question about Aperture behavior on cropped photos

    Hello everyone, If I crop a photo in Aperture 3, and then click on the "Auto level" button, will the "auto level" stuff be applied relatively to the whole photo or only to the cropped photo (just like in Photoshop) ?...

  • Anyone know how to set file associations for QT in Inno Setup?

    I am working on an app that requires QT to play .smi files and can't seem to get it to work. I was using this code in the Inno Setup file: Root: HKCR; Subkey: ".smi"; ValueType: string; ValueName: ""; ValueData: "QuickTime.smi"; Flags: uninsdeleteval