Static methods not supported?

When I create a static function in netbeans 6.5 like:
class Conversions
    static function c2f (celcius: Number): Number
        9.0/5.0*celcius+32.0
}I get the warning that *'static is no longer supported, it will be removed soon, use script-level declarations'.*
Does anybody know what this means, how do I declare class level functions?
Besides that, where is a good, uptodate, complete language reference, I get all unknown pages?

Found it myself, but I think that there's an inconsistency with the javafx plugin and the javafx compiler, because the code in my first message gives a warning, but does run.
When you change the 'static' into 'public', it behaves as a class method, in the IDE. The following code, does not cause a warning in Netbeans:
class Conversions {
    public function c2f (celcius: Number): Number {
        9.0 / 5.0 * celcius + 32.0
print(Conversions.c2f(37.0));But, unfortunately, it doesn't run:
non-static method c2f(double) cannot be referenced from a static context
print(Conversions.c2f(37.0));
1 errorAny suggestions, is there an update (for Netbeans or my javafx) to fix this?

Similar Messages

  • "Function or method not supported" error at IviRFSigGen InitializeWithOptions.vi

    Error 1074135023 at "IviRFSigGen Initialize With Options.vi", Primary Error (Hex 0xBFFA0011) "Function or method not supported". Error occurs when using Agilent IVI driver for RF Signal Generator (E4437B) with LabView. Instrument also does not switch to remote mode in response to the IVI initialize command from LabView, but direct communication using NI-488.2 Communicator works.

    It looks like you are using the NI IVI Class Drivers, and have configured them to use the Agilent IVI-C driver under the hood. For some reason, it looks like the class drivers aren't happy with the Agilent driver, and that's the cause of the error.
    You should first confirm your IVI configuration in MAX. You should make sure IVI Logical Name is pointing to the right Agilent driver, correct instrument address, etc. That name is what you pass into Initialize with Options.
    If this doesn't pan out, it looks like you'll have to debug things.
    First of all, do you need to use IVI? If not, then I'd recommend you download our LabVIEW instrument driver for this instrument, so that you can get LabVIEW source code.
    It's available on http://ni.com/idnet/ at
    href="http://zone.ni.com/idnet97.nsf/9b2b33e1993d877786256436006ec498/539916348394adc7862568ab005fbb....
    If you do need IVI, then I'd suggest you try NI's IVI-C driver for this instrument, also on http://ni.com/idnet/ at this link. This includes LabVIEW Wrapper VIs for the driver.
    If you want to use Agilent's driver, did they provide LabVIEW support with their driver? That is, did they include LabVIEW wrapper VIs? If so, you might try just calling the "AGE4437B InitializeWithOptions.vi" directly and see if you get an error. If they did not provide wrapper functions, I'd call them up and ask if they can give them to you.
    I hope this helps. Let us know what you figure out.
    Brian

  • Error: "Function or method not supported." when using RF List Mode on NI 5673E

    Hi,
    I am trying to use the RF List Mode in NI RFSG 5673E. I tried running the sample code "RFSG Configuration List Frequency and Power Sweep.vi" but an error would show up:
    "Error: niRFSGCreateConfigurationList.VI <ERR> The LO reported the following error: Function or method not supported." with the error code: BFFA4239. 
    I also tried running other sample codes that contain the Configuration List VI's but the same error appeared. I am using NI RFSG 1.8.5.
    I would really appreciate any help on this. Thanks!

    Hello jdlabrador,
    I setup a 5673E here and tried to run the same example.  I did not encounter an error.
    Other reports I've found pertaining to this error usually involved a large number of steps - there was not enough space on the hardware to accommodate them.  The error text you're seeing is a little different in that it states that the Create Configuration List method isn't supported for the LO.
    Do each of the modules in your 5673E (5450, 5611, 5652) pass a self-test in MAX?  
    Have you associated the 5450 and 5652 with the 5611?
    Could you post a screenshot of the fully-expanded Devices and Interfaces tree from MAX?
    Since RFSG 1.9.5 is available, it may be a good first-step to upgrade to it.  
    Best regards,
    Matthew H.
    Applications Engineer
    National Instruments

  • Intel Mac 10.4.x "Connection Method not supported -9786"

    we have a customer with the new intel powerbook and tiger system.
    but if he want to print via tcp/ip he get this error on the screen:
    "Connection Method not supported -9786"
    i could nowhere found this error code.
    any ideas ????
    andy
    powerbook g4   Mac OS X (10.4.6)  

    Hi Andy,
    I just read your posting from two weeks ago and thought I would add some info.
    Yesterday I had a customer suffering the same problem. They had just purchased an iMac w Intel and were attempting to connect to a Canon iR4570. They had other PPC Mac's which were running varying versions of 10.4 and were all printing okay. But this iMac was getting the error -9786.
    I found that he was trying to connect via IPP, but entering the queue name as LP (which is what you do for LPR connections). By changing the queue to socket://ip address:9100 the error was resolved.
    The thing to note about this situation was that since this was the first printer he was adding to his Mac, the protocol was defaulted to IPP. With the previous driver installations he had performed on the other Mac's, the protocol was defaulted to LPR. This would have been due to this protocol being the last one used previously. But the customer had only been taught to add the IP address and the queue name and wasn't aware of the protocol menu...

  • POST method not supported by this URL

    Hello gentlemen,
              We are trying to migrate our servlets from another Web Application
              Server (IBM WebSphere 2.02) to Weblogic 4.5.1.
              A servlet that did work fine with WebSphere, now produces the "POST
              method not supported by this URL" error under Weblogic.
              Of course, we implement doPost method in our servlet.
              Any idea to fix this problem? thank you.
              emanuele
              

              Emanuele--
              In the ICSessionServlet file you are posting the data to ICIdentification servlet which is
              again a servlet
              So you need to register this servlet in weblogic.properties file before you post something to
              this servlet.
              Also the way you are calling the servlet is totally wrong from weblogic standpoint
              You don't need to specify the package name in weblogic(this is OK in java web server) for e.g.
              icdoor.myservlet.session.ICIdentificationServlet.
              Because we are registering the servlet with full package name in properties file so we don't
              need to mention the package
              name here..
              Call the servlet in the following way or whichever way is suitable for you.
              Here is how i'm calling ICIdentificationServlet
              http://localhost:7001/ICIdentificationServlet
              Here is the output i'm getting after entering user name/password
              "Welcome Startfighter"
              Requested URL
              http://localhost:7001/Stupida
              Hope this helps
              Kumar
              emanuele wrote:
              > Here's the source code for a servlet producing "HTTP method POST is not
              > supported by this URL".
              >
              > I have registered servlet Stupida in the file weblogic.properties. This
              > servlet subclass the ICSessionServlet.
              > The service() method of ICSessionServlet ask for a userid and a password
              > (user and password are not verified, anyway) and then calls the doPost()
              > method of ICIdentification servlet. This one displays a sort of "Welcome
              > page" and then the calling URL. (if it works fine...).
              >
              > On WebSphere, it works. On Weblogic, it doesn't.
              >
              > Any idea?
              >
              > emanuele
              >
              > "Kumaraswamy A." wrote:
              >
              > > can you post the stacktrace , also if possible send your java file
              > > too!..
              >
              >
              

  • JDBC 2.0 method not supported Error occuring in WL 6.1 sp1

    Hi ,
    When I connect to a mssqlserver 2000 using a session bean and execute the following
    statement
    "stmDataAccess=conDataAccess.createStatement(ResultSet.CONCUR_UPDATABLE,ResultSet.TYPE_SCROLL_INSENSITIVE);"
    i get the following error at the client and server side
    what can be wrong?.Support for Jdbc 2.0 is inherent in WL 6.1 isn't it?
    java.rmi.RemoteException: EJB Exception:; nested exception is:
    javax.ejb.EJBException
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented]
    Start server side stack trace:
    java.rmi.RemoteException: EJB Exception:; nested exception is:
    javax.ejb.EJBException
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented]
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
    at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    javax.ejb.EJBException
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented]
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    ; nested exception is:
    javax.ejb.EJBException:
    Start server side stack trace:
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
    at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    javax.ejb.EJBException
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented]
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
    Start server side stack trace:
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
            at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
            at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
            at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
            at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
            at java.lang.reflect.Method.invoke(Native Method)
            at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
            at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
            at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
            at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
            at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
            at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
            at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
            at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
            at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
            at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
            at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End  server side stack trace
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
    Start server side stack trace:
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
    at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    <<no stack trace available>>
    --------------- nested within: ------------------
    javax.ejb.EJBException:
    Start server side stack trace:
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
    at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    javax.ejb.EJBException
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented]
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
    Start server side stack trace:
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
            at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
            at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
            at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
            at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
            at java.lang.reflect.Method.invoke(Native Method)
            at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
            at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
            at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
            at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
            at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
            at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
            at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
            at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
            at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
            at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
            at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End  server side stack trace
    <<no stack trace available>>

    Hi
    As I know, not all mehtods are supported by WebLogic. For Example for Oracle only
    a SubSet of the JDBC methods are supported (see the link http://e-docs.bea.com/wls/docs61///////oracle/API_joci.html#1070961).
    I can imagine that for Microsoft Products this is even worse.
    Regards Patrick
    "Thomas" <[email protected]> wrote:
    >
    Hi,
    I'm using the driver that comes along with the application server ie
    weblogic.jdbc.mssqlserver4.Driver.If
    this driver doesn't support JDBC 2.0 where can i find a suitable driver
    as my
    app needs updatable recordsets with updateXXX methods and absolute moves?
    Thanks in advance
    "noone_home" <[email protected]> wrote:
    Hi,
    It looks like your JDBC driver does not support JDBC 2.0. I believethe
    the JDBC
    driver for SQL Server that came with WLS 6.x supports only JDBC 1.1.
    I'm making
    the assumption that that is the driver which you are using.
    hth.
    "Thomas" <[email protected]> wrote:
    Hi ,
    When I connect to a mssqlserver 2000 using a session bean and execute
    the following
    statement
    "stmDataAccess=conDataAccess.createStatement(ResultSet.CONCUR_UPDATABLE,ResultSet.TYPE_SCROLL_INSENSITIVE);"
    i get the following error at the client and server side
    what can be wrong?.Support for Jdbc 2.0 is inherent in WL 6.1 isn't
    it?
    java.rmi.RemoteException: EJB Exception:; nested exception is:
    javax.ejb.EJBException
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
    is>>>not implemented
    Start server side stack trace:
    java.rmi.RemoteException: EJB Exception:; nested exception is:
    javax.ejb.EJBException
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
    is>>>not implemented
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
    is
    not implemented
    at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    javax.ejb.EJBException
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
    is>>>not implemented
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    ; nested exception is:
    javax.ejb.EJBException:
    Start server side stack trace:
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 methodis
    not implemented
    at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    javax.ejb.EJBException
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
    is>>>not implemented
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
    is>>>not implemented>>> >>>Start server side stack trace:>>>java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method>is>>>not implemented>>>        at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)>>>        at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)>>>        at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)>>>        at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)>>>        at java.lang.reflect.Method.invoke(Native Method)>>>        at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)>>>        at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)>>>        at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)>>>        at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)>>>        at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown>>>Source)>>>        at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)>>>        at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)>>>        at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)>>>        at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)>>>        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)>>>        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)>>>End  server side stack trace>>>
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 methodis
    not implemented
    Start server side stack trace:
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 methodis
    not implemented
    at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    <<no stack trace available>>
    --------------- nested within: ------------------
    javax.ejb.EJBException:
    Start server side stack trace:
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 methodis
    not implemented
    at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    javax.ejb.EJBException
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
    is>>>not implemented
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
    is>>>not implemented>>> >>>Start server side stack trace:>>>java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method>is>>>not implemented>>>        at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)>>>        at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)>>>        at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)>>>        at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)>>>        at java.lang.reflect.Method.invoke(Native Method)>>>        at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)>>>        at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)>>>        at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)>>>        at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)>>>        at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown>>>Source)>>>        at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)>>>        at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)>>>        at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)>>>        at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)>>>        at weblogic.kernel.ExecuteThread.execute>>(ExecuteThread.java:139)>>>        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)>>>End  server side stack trace>>>
    <<no stack trace available>>

  • Web service Method not supported

    Hy, i have this serious problem.
    I have any web service method  that in , Visual Composer 7.1, have the suffix "Not supported".
    I don't understand this situation because i can test it on web service navigator with success.
    This is the SOAP request/response from Web service navigator test:
    SOAP request:
    <?xml version="1.0" encoding="utf-8"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <SOAP-ENV:Body>
        <pns:getMaterialDetail xmlns:pns="urn:WsMaterialGetDetailVi">
          <pns:matnr/>
          <pns:werks/>
        </pns:getMaterialDetail>
      </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    SOAP response:
    <?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <SOAP-ENV:Body>
        <rpl:getMaterialDetailResponse xmlns:rpl="urn:WsMaterialGetDetailVi">
          <rpl:Response xmlns:pns="urn:it.futura.lib.ws">
            <pns:returnCode>3</pns:returnCode>
            <pns:returnCodeDescription>Codice Materiale non fornito</pns:returnCodeDescription>
            <pns:returnCodes xmlns:tns="java:sap/standard" xsi:type="tns:Vector">
              <tns:Vector xsi:type="xs:string">0</tns:Vector>
              <tns:Vector xsi:type="xs:string">0</tns:Vector>
              <tns:Vector xsi:type="xs:string">3</tns:Vector>
            </pns:returnCodes>
            <pns:returnCodesDescription xmlns:tns="java:sap/standard" xsi:type="tns:Vector">
              <tns:Vector xsi:type="xs:string">Environment name found: NVP</tns:Vector>
              <tns:Vector xsi:type="xs:string">Dettagli ambiente trovato: NVP</tns:Vector>
              <tns:Vector xsi:type="xs:string">Codice Materiale non fornito</tns:Vector>
            </pns:returnCodesDescription>
          </rpl:Response>
        </rpl:getMaterialDetailResponse>
      </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    Sincerely yours
    Thank's
    Andrea Maraviglia

    Thank's Shay. I'm thinking that the problem is about NWDS for this reason: at the moment i am testing a standard web service present on WAS( http://serverWAS:53000/IciUserService/IciUserConf?wsdl)that with a method ( getAttributes) that return an array of classes on VC and this test is ok.
    So i'm creating an similar web service that return array of classes with my NWDS (vers. 7.0.7..) and wizard but on VC it's don't supported.
    The SOAP Response of standard web service and my web service, have different structure. I'm thinking that the problem is NWDS because the SOAP response is function of the WSDL generated by Wizard on NWDS.
    Thank's in advance.
    Andrea Maraviglia
    Edited by: Andrea Maraviglia on Nov 28, 2008 5:46 PM

  • "Import string" method not supported in LabVIEW 7.1

    We have made an application that support multi-language (English, French, etc.). In LabVIEW 6.1, we used the "import string" VI method to support this option. The method was executed just before to open front panel. The code was based on this example found in NI Developer Zone:
    Translation/Localization Tools in LabVIEW
    (http://sine.ni.com/apps/we/niepd_web_display.disp​lay_epd4?...
    But surprise in version 7.1, this method can't be loaded without the diagram block. So the built application doesn't support it! It works only in the development interface. Why this change?
    If someone has an idea to solve this, let me know.

    If you build that example into an EXE under LabVIEW 7.1, it should work fine as long as you add the non top-level VIs as Dynamic VIs and add the language files as Support Files when you create the executable, making sure to specify in "Custom Destinations" that you want the string files to end up in the same directory as the EXE.
    Your point about the method requiring the block diagram is correct, according to the help for the method. However, I think the diagrams will be available to the run-time engine as long as you haven't purposefully removed them prior to creating the EXE in the manner described above. Maybe someone else can chime in on this point, because I know the App Builder changes a lot with every new major LabVIEW version (and sometimes, with minor versions too!).
    In any case, I just did a test where I downloaded the example you referenced, created a .BLD file as I indicated above, and got a successful executable that was able to use the Import VI Strings method to load the desired language at run-time.
    Regards,
    John

  • Method Not Suypported- Statement.setQueryTimeout(int)

    I'm having a bout of confusion over error messages. We're using a product to monitor our IT resources and currently trying to monitor Informix DB response through JDBC.
    Our software package said we should use the Informix JDBC 1.40 but only 1.50 was available to us. From the language I think the help file was written when 1.4 was out because it makes no mention of earlier or later versions.
    The notes for 1.5 say JDK 1.1.6, 1.1.7, or 1.1.8 needs to be installed. (no mention of a JRE, though I assume JDK convers that as well.) We installed JDK 1.1.8
    Our monitor is erroring out, quickly, saying that
    connect error,
    Method not supported : Statement.setQueryTimeout(int).
    I'm having trouble identifing where this is unsupported. Would someone recognize, does this means ....
    Infromix JDBC 1.5 is making a request that JDK 1.1.8 doesn't support?
    Informix JDBC 1.5 is making a request that the java interface on the Informix DB server doesn't recognize?
    JDK 1.1.8 is lacking some requirement?
    Some other inbetween layer (which I am not recognizing) is the problem?
    A later version of JRE is running and causing the conflict (perhaps this method is obsolete in JRE 1.3.0)
    I confirmed that the JDK 1.1.8 is in the first in the path and gets executed by default. (instead of another version on the NT server). There is another version 1.3.0 installed.

    I have no expertise with informix, but I know that the Statement.setTimeOut(int) method is supported in 1.1.x, therefore this is most likely being generated by the driver or the database.

  • JNI static method call fails for the 6th time

    Hello,
    I have a JNI Method which calls the static method which gets reference to singleton class(getReference()), JVM crashes.
    what might be the problem?
    is it due to insufficient memory or any other reason?
    Here is my code.
    eScannerClass = gEnv->FindClass("com/elvista/jscaner/EScanner");
    eScannerContructId = gEnv->GetStaticMethodID(eScannerClass,"getReference","()Lcom/elvista/jscaner/EScanner;");
    eScannerUpdateMethodId = gEnv->GetMethodID(eScannerClass,"updateScanStatus","(Lcom/elvista/jscaner/EScanEvent;)V");
    eScannerObjectRef = gEnv->NewObject(eScannerClass,eScannerContructId);Thanx for any help on this.

    Hi,
    the eScannerContructId is refering a static method, not a constructor. Therefore you must not use gEnv->NewObject, which is only allowed for constructors. Instead you have to use gEnv->CallStaticObjectMethod to call getReference().
    Martin

  • Static methods in interfaces

    Java cognoscenti,
    Anyone know why I can't declare a method as static in an interface, but I can in an abstract class. Surely, semantically it's the same - defering the implementation of a static method, not an abstract class and an interface. By the way, I'm using JDK 1.2.2 if that makes a difference

    No, it's not the same. You are not "defering the
    implementation of a static method" because static
    methods are never polymorphic.
    Static methods cannot be abstract for this reason, and
    only abstract methods are allowed in interfaces.I didnt't know that. I thought that - because you can override static methods and you can call them onto an actual instance the method binding would be done at run-time, not at compile-time. So I was trying to prove you wrong, but you are correct !
    A short summary of what I've learnt so far:
    - interfaces cannot contain static methods
    - abstract classes cannot contain abstract static methods
    - static methods can be overriden, but they are not polymorphic; this means that the compiler decides which method to call at compile-time.
    /* output
    SuperClass.someMethod()
    SubClass.someMethod()
    SuperClass.someMethod()
    SuperClass.someMethod()
    SubClass.someMethod()
    SubClass.someMethod()
    SuperClass.someMethod()
    public class Test {
      public final static void main(String[] args) {
          // output: SuperClass.someMethod()
          new SuperClass().someMethod();
          // output: SubClass.someMethod()
          new SubClass().someMethod();
          // output: 2x SuperClass.someMethod()
          SuperClass someClass1 = new SubClass();
          someClass1.someMethod();
          showSuper(someClass1);
          // output: 2x SubClass.someMethod()
          SubClass someClass2 = new SubClass();
          someClass2.someMethod();
          showSub(someClass2);
          showSuper(someClass2); // SuperClass.someMethod()
      public final static void showSuper(SuperClass c) {
            c.someMethod();
      public final static void showSub(SubClass c) {
            c.someMethod();
    class SuperClass {
      public static void someMethod() {
        System.out.println("SuperClass.someMethod()");
    class SubClass extends SuperClass {
      public static void someMethod() {
        System.out.println("SubClass.someMethod()");

  • Why are these Webservices not supported in VC ?

    Hi all,
    I am using NW04s SP9, and I plan to make MDM-Application with VC.
    Therefore I introduced MDM-WebService into NW and defined it on VC.
    but "searchRecords" of "MDMSearchRecords" was displayed with "Not supported"
    in the right frame .
    Mmm...
    So I decided to think from a beginning.
    [http://www.27seconds.com/Holidays/US/USHolidayService.asmx?wsdl|http://www.27seconds.com/Holidays/US/USHolidayService.asmx?wsdl]
    I defined above it on VC and I used "Getholidaydate" .
    Good! .
    However,,, "Getholidaysforyear" was also "Not supported".
    Why are these methods "Not supported" ? .
    and how will come to be usable these methods in VC? .
    Thanx in advance.
    Regards,
    k.sugimoto.

    Hi
    Visual Composer supports Web services that are compliant with the Basic Profile 1 standard of the Web Services Interoperability (WS-I) Organization (http://help.sap.com/saphelp_nw70/helpdata/en/e0/92583ab4da4b9cb524f61ba4267d25/content.htm)
    Best regards
    Vincenzo

  • I am not able access static methods from startup class

    I have a simple java class which queries the Database and holds some data. I am trying to access a static method of this class from the StartupClass and I am not able to do so. But I am able to access a static variable of the same class.
    Can someone help me here.

    Well, welcome to the world of "hacked" phones. If your purchase was from the US, you obviously purchased an iPhone that is locked to a US carrier. The iPhone must have been jailbroken and unlocked via software to accommodate your foreign SIM card. Now that you have updated the phone, it is locked back to the US carrier. Only the carrier can authorize Apple to unlock the iPhone and none of the US carriers will unlock the iPhones. Best suggestion is to sell the phone and obtain a factory unlocked version directly from the Apple store.
    To answer your other question, there is not a supported method to downgrade iOS.

  • Strange IE ExternalInterface Bug: "Object does not support this property or method"

    We have an application on a relatively slow server (I mention
    the speed because it may be relevant).
    The app is flash 8 and uses ExternalInterface to call a
    javascript function in its parent page. It also used the
    ExternalInterface to receive a call from another function. These
    calls happens separately (the outbound one calls up a list view of
    items, clicking on an item calls up the details in the flash
    movie). In between the calls, the flash movie is hidden by moving
    it off screen using absolute positioning.
    On my local development box (Windows XPSP2) this works fine
    in both directions.
    On our production server (LAMP) this works fine in both
    directions in Firefox 1.5 and 2.0
    BUT while the outbound call from Flash to the page works fine
    in Internet Explorer 6 or 7, the call back from the page to the
    flash movie fails with the error messgage "Object does not support
    this method or property"
    We've tried not hiding the flash so it is always present on
    the page and still the browser > flash communication breaks in
    ie.
    We've tried using both the Adobe active content script and
    swfobject to embed the flash in the page with no difference in the
    resultset. In truth we've given up and gone to a two-page solution,
    reloading the flash from the start each time but I wondered if
    anyone had encountered a similar issue? Can't see why it would work
    perfectly in FF but not in IE.

    Not sure if this is your problem, but you do reference the
    Flash object
    differently, depending on the browser. In a video player we
    made, that uses
    JS to communicate back to Flash, I use a function like this
    to modify the
    variable depending on the browser:
    function changeVideo(xname){
    //ff
    if(window.vplayer){
    window.document["vplayer"].SetVariable("theXML", xname);
    window.document["vplayer"].GotoFrame(2);
    window.document["vplayer"].Play();
    //ie
    if(document.vplayer){
    document.vplayer.SetVariable("theXML", xname);
    document.vplayer.GotoFrame(2);
    document.vplayer.Play();
    The Flash is in a <div> named 'vplayer'
    Dave -
    Head Developer
    http://www.blurredistinction.com
    Adobe Community Expert
    http://www.adobe.com/communities/experts/

  • Java.lang.Error: JAX-RPC 1.1 method is not supported in WLS 8.1 clients.

    We have some web services that run under OC4J 10.1.3.4. We have various JEE 'client' apps (JSF, servlets etc.) that use these web services. These JEE apps also run under OC4J.
    We started a migration project from oc4j to weblogic 10.3.2. In phase 1 we want to move these JEE 'client' apps to weblogic. In phase 2 we want to move the web services themselves to weblogic with adjustments to the JEE 'client' apps as needed.
    However we ran into an issue during this phase 1. Deploying these JEE 'client' apps to weblogic results in an error like this:
    java.lang.Error: JAX-RPC 1.1 method is not supported in WLS 8.1 clients. If you are attempting to run an OC4J 10.1.3 JAX-RPC client in WLS, please see the Web Service Migration Guide for instructions.
    We are including Oracle web services client libraries (http://download.oracle.com/otn/java/oc4j/1013/wsclient_extended.zip) in these JEE 'client' apps's war files because weblogic does not have them.
    What part of Web Service Migration Guide is the above error message talking about? Do we have to re-generate the client side proxies for all these web services using weblogic's clientgen task in 'JAXRPC' mode? Many of these web services are doc/literal jax-rpc web services. Or does the migration guide recommend we migrate the web services first to weblogic? Any other specific information on working around this error message would be greatly appreciated.

    Hi,
    I had the same issue but I just managed to fix it. You must upgrade and/or regenerate you proxy. This creates new classes (possibily in a new package) that you must use in your code. I had this error because the classes directory was not clean after the rebuild and the old classes (in the old package) were still present, so the compilation was successful with the old classes. So clean your classes directories, regenerate your proxy and use the new classes in your code.
    Regards,
    Sylvain

Maybe you are looking for