Call doGet from init

Hello
Please could you show through the code. I think there is something wrong with the init. If I run the servlet, it don't show a thing. It only displays: Site can't not be shown.
The doGet and also the dopost is not executed. Must I call in the doPost in the init(). And when yes how?
Thanks a lot!
Sandra Frei
import java.sql.*;
import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;
import java.util.Properties;
public class update42 extends HttpServlet {
Connection con = null;
public void init() {//throws ServletException {
String url = "jdbc:DBF:/sys:copal/copal_data/data/gesch/data/stamm";
try {
//Register the JDBC driver
Class.forName("zyh.sql.dbf.DBFDriver");//.newInstance();
con = DriverManager.getConnection(url, "fre","sandy66");
catch( Exception e ) {
e.printStackTrace();
}//end catch
}//end init()
public void doGet(HttpServletRequest req, HttpServletResponse res)
throws ServletException, IOException {
res.setContentType("text/html");
PrintWriter out = res.getWriter();
out.print("in do get");
//connecting to the Database
Statement stmt = null;
ResultSet rs = null;
PreparedStatement ps = null;
try
stmt = con.createStatement();
catch (SQLException e) {e.getNextException();}
// displaying records
try
rs = stmt.executeQuery("SELECT Random, Nsa, Bzng, Bzn2, Tart, Meeh, Fstat, Nzn FROM part");
catch (SQLException e) {e.getNextException();}
try
while(rs.next()) {
out.print("<form action=\"");
out.print( req.getRequestURI() );
out.print("\" method=\"post\">");
out.print("<input type=\"text\""); //hidden
out.print(" name=\"Random\" size=\"15\" value=\"");//without 15
out.print( rs.getObject(1).toString() );
out.print("\">");
out.print("<input type=\"text\"");
out.print(" name=\"Nsa\" size=\"15\" value=\"");
out.print( rs.getObject(2).toString() );
out.print("\">");
out.print("<input type=\"text\"");
out.print(" name=\"Bzng\" size=\"25\" value=\"");
out.print( rs.getObject(3).toString() );
out.print("\">");
out.print("<input type=\"text\"");
out.print(" name=\"Bzn2\" size=\"25\" value=\"");
out.print( rs.getObject(4).toString() );
out.print("\">");
out.print("<input type=\"text\"");
out.print(" name=\"Tart\" size=\"6\" value=\"");
out.print( rs.getObject(5).toString() );
out.print("\">");
out.print("<input type=\"text\"");
out.print(" name=\"Meeh\" size=\"6\" value=\"");
out.print( rs.getObject(6).toString() );
out.print("\">");
out.print("<input type=\"text\"");
out.print(" name=\"Fstat\" size=\"6\" value=\"");
out.print( rs.getObject(7).toString() );
out.print("\">");
out.print("<input type=\"text\"");
out.print(" name=\"Nzn\" size=\"15\" value=\"");
out.print( rs.getObject(8).toString() );
out.print("\">");
out.print(" <input type=\"submit\"");
out.print(" value=\" \">");
out.print(" Update<br>");
out.print("</form>");
catch (SQLException e) {e.getNextException();}
try
if(rs != null)
rs.close();
if(stmt != null)
stmt.close();
catch (SQLException e) {
e.printStackTrace();
out.print("</pre></code>");
out.print("<p\"><a href=\"");
out.print( req.getRequestURI() );
out.print("\">Back</a></p>");
out.print("</body></html>");
out.close();
public void doPost(HttpServletRequest req, HttpServletResponse res)
throws ServletException, IOException {
res.setContentType("text/html");
PrintWriter out = res.getWriter();
out.print("<html><body>");
out.print("<code><pre>");
out.print("<table border=1>");
out.print("<tr>");
out.print("<td><font color=green>Artikelnr</font></td>");
out.print("<td><font color=green>Bezeichnung</font></td>");
out.print("<td><font color=green>Zusatzbezeichnung</font></td>");
out.print("<td><font color=green>Art</font></td>");
out.print("<td><font color=green>ME</font></td>");
out.print("<td><font color=green>Stat</font></td>");
out.print("<td><font color=green>Spezifikation</font></td>");
out.print("</tr>");
// receiving parameters
String Bzn2 = req.getParameter("Bzn2").trim();
String Meeh= req.getParameter("Meeh").trim();
String Pk = req.getParameter("Random").trim();
boolean proceed = false;
Statement stmt = null;
Statement stmt1 = null;
ResultSet rs = null;
try {
String sql;
sql = "UPDATE part SET Bzn2 = " + "'" + Bzn2 + "'" + " WHERE Random LIKE " + "'" + Pk + "'";
stmt1 = con.createStatement();
out.print(sql);
out.print(Bzn2 + Meeh + Pk);
stmt1.executeUpdate(sql);
// displaying records
stmt = con.createStatement();
rs = stmt.executeQuery("SELECT * FROM part");
while(rs.next())
out.print("<tr>");
out.print("<td>"+ rs.getObject(1).toString()+ "</td>");
out.print("<td>"+ rs.getObject(2).toString()+ "</td>");
out.print("<td>"+ rs.getObject(3).toString()+ "</td>");
out.print("<td>"+ rs.getObject(4).toString()+ "</td>");
out.print("<td>"+ rs.getObject(5).toString()+ "</td>");
out.print("<td>"+ rs.getObject(6).toString()+ "</td>");
out.print("<td>"+ rs.getObject(7).toString()+ "</td>");
out.print("</tr>");
out.print("</table>");
catch (Exception e)
out.print(e.getMessage());
e.printStackTrace();
try
if(rs != null)
rs.close();
if(stmt != null)
stmt.close();
if(stmt1 != null)
stmt1.close();
catch (SQLException e) {e.getNextException();}
out.print("</pre></code>");
out.print("<p\"><a href=\"");
out.print( req.getRequestURI() );
out.print("\">Back</a></p>");
out.print("</body></html>");
out.close();
public void destroy() {
try {
//Close the connection to the database
con.close();
} catch( Exception e ) {
e.printStackTrace();
}

No, do NOT call doGet() or doPost() from the init() method. Your problem is something else, but you have not provided enough information to figure out what, and there are several possibilites. "Site can't not be shown"... I doubt that is the exact message you are getting.

Similar Messages

  • Calling doGet() from in the doPost() method.

    What is the conditions we have to cheak to call doGet() method from doPost().

    doGet() using for request.getParameter(). the exact story is u want to get some data form html (or) data bases. it is usefu

  • Call doGet in the Init of a servlet?

    Hello
    Please could you show through the code. I think there is something wrong with the init. If I run the servlet, it don't show a thing. It only displays: Site can't not be shown.
    The doGet and also the dopost is not executed. Must I call in the doPost in the init(). And when yes how?
    Thanks a lot!
    Sandra Frei
    import java.sql.*;
    import java.io.*;
    import javax.servlet.*;
    import javax.servlet.http.*;
    import java.util.Properties;
    public class update42 extends HttpServlet {
         Connection con = null;
         public void init() {//throws ServletException {
              String url = "jdbc:DBF:/sys:copal/copal_data/data/gesch/data/stamm";      
              try {
                   //Register the JDBC driver
                   Class.forName("zyh.sql.dbf.DBFDriver");//.newInstance();
                   con = DriverManager.getConnection(url, "fre","sandy66");                    
              catch( Exception e ) {
                   e.printStackTrace();
              }//end catch
         }//end init()
         public void doGet(HttpServletRequest req, HttpServletResponse res)
              throws ServletException, IOException {
              res.setContentType("text/html");
              PrintWriter out = res.getWriter();
              out.print("in do get");
              //connecting to the Database
              Statement stmt = null;
              ResultSet rs = null;
              PreparedStatement ps = null;
                   try
                   stmt = con.createStatement();
                   catch (SQLException e) {e.getNextException();}                              
                   // displaying records
                   try
                   rs = stmt.executeQuery("SELECT Random, Nsa, Bzng, Bzn2, Tart, Meeh, Fstat, Nzn FROM part");
                   catch (SQLException e) {e.getNextException();}                              
                   try
                   while(rs.next()) {
                        out.print("<form action=\"");
                        out.print( req.getRequestURI() );
                        out.print("\" method=\"post\">");
                        out.print("<input type=\"text\""); //hidden
                        out.print(" name=\"Random\" size=\"15\" value=\"");//without 15
                        out.print( rs.getObject(1).toString() );
                        out.print("\">");
                        out.print("<input type=\"text\"");
                        out.print(" name=\"Nsa\" size=\"15\" value=\"");
                        out.print( rs.getObject(2).toString() );
                        out.print("\">");
                        out.print("<input type=\"text\"");
                        out.print(" name=\"Bzng\" size=\"25\" value=\"");
                        out.print( rs.getObject(3).toString() );
                        out.print("\">");
                        out.print("<input type=\"text\"");
                        out.print(" name=\"Bzn2\" size=\"25\" value=\"");
                        out.print( rs.getObject(4).toString() );
                        out.print("\">");
                        out.print("<input type=\"text\"");
                        out.print(" name=\"Tart\" size=\"6\" value=\"");
                        out.print( rs.getObject(5).toString() );
                        out.print("\">");
                        out.print("<input type=\"text\"");
                        out.print(" name=\"Meeh\" size=\"6\" value=\"");
                        out.print( rs.getObject(6).toString() );
                        out.print("\">");
                        out.print("<input type=\"text\"");
                        out.print(" name=\"Fstat\" size=\"6\" value=\"");
                        out.print( rs.getObject(7).toString() );
                        out.print("\">");
                        out.print("<input type=\"text\"");
                        out.print(" name=\"Nzn\" size=\"15\" value=\"");
                        out.print( rs.getObject(8).toString() );
                        out.print("\">");
                        out.print(" <input type=\"submit\"");
                        out.print(" value=\" \">");
                        out.print(" Update<br>");
                        out.print("</form>");
                   catch (SQLException e) {e.getNextException();}                              
                   try
                        if(rs != null)
                             rs.close();
                        if(stmt != null)
                             stmt.close();
                   catch (SQLException e) {
                        e.printStackTrace();
         out.print("</pre></code>");
         out.print("<p\"><a href=\"");
         out.print( req.getRequestURI() );
         out.print("\">Back</a></p>");
         out.print("</body></html>");
         out.close();
         public void doPost(HttpServletRequest req, HttpServletResponse res)
              throws ServletException, IOException {
              res.setContentType("text/html");
              PrintWriter out = res.getWriter();
              out.print("<html><body>");
              out.print("<code><pre>");
              out.print("<table border=1>");
         out.print("<tr>");
              out.print("<td><font color=green>Artikelnr</font></td>");
              out.print("<td><font color=green>Bezeichnung</font></td>");
              out.print("<td><font color=green>Zusatzbezeichnung</font></td>");
              out.print("<td><font color=green>Art</font></td>");
              out.print("<td><font color=green>ME</font></td>");
              out.print("<td><font color=green>Stat</font></td>");
              out.print("<td><font color=green>Spezifikation</font></td>");
         out.print("</tr>");
              // receiving parameters
              String Bzn2 = req.getParameter("Bzn2").trim();
              String Meeh= req.getParameter("Meeh").trim();
              String Pk = req.getParameter("Random").trim();
              boolean proceed = false;
              Statement stmt = null;
              Statement stmt1 = null;
              ResultSet rs = null;
              try {
                   String sql;
              sql = "UPDATE part SET Bzn2 = " + "'" + Bzn2 + "'" + " WHERE Random LIKE " + "'" + Pk + "'";
                   stmt1 = con.createStatement();               
                   out.print(sql);
                   out.print(Bzn2 + Meeh + Pk);
                   stmt1.executeUpdate(sql);
              // displaying records
                   stmt = con.createStatement();               
                   rs = stmt.executeQuery("SELECT * FROM part");
                   while(rs.next())
                        out.print("<tr>");
                        out.print("<td>"+ rs.getObject(1).toString()+ "</td>");
                        out.print("<td>"+ rs.getObject(2).toString()+ "</td>");
                        out.print("<td>"+ rs.getObject(3).toString()+ "</td>");
                        out.print("<td>"+ rs.getObject(4).toString()+ "</td>");
                        out.print("<td>"+ rs.getObject(5).toString()+ "</td>");
                        out.print("<td>"+ rs.getObject(6).toString()+ "</td>");
                        out.print("<td>"+ rs.getObject(7).toString()+ "</td>");
                        out.print("</tr>");
                   out.print("</table>");
              catch (Exception e)     
                   out.print(e.getMessage());
                   e.printStackTrace();
                   try
                        if(rs != null)
                             rs.close();
                        if(stmt != null)
                             stmt.close();
                        if(stmt1 != null)
                             stmt1.close();
                   catch (SQLException e) {e.getNextException();}
              out.print("</pre></code>");
              out.print("<p\"><a href=\"");
              out.print( req.getRequestURI() );
              out.print("\">Back</a></p>");
              out.print("</body></html>");
              out.close();
         public void destroy() {
              try {
                   //Close the connection to the database
                   con.close();
              } catch( Exception e ) {
                   e.printStackTrace();
    }

    It won't get shown unless you make a call to the servlet from (e.g.) a web browser referencing it. And no - don't call doPost() or doGet() from the init() method. You might be lucky, and it might work, but it's inherently unsafe. Servlet engines will not normally call these methods until the servlet is properly initialised.
    And BTW, there is no guarantee that init() will be called until the first call to the servlet, unless you specify load on startup to the servlet engine.
    Your best bet is simply to type the URL of your servlet into your web browser. That will call doGet(). To call doPost(), you'll have to write a little HTML page with a form with method="post" and action=the name of your servlet.
    Robin

  • How to call servlet from jsp

    i m trying to call it from jsp using
    <a href="../purchaseP?orderno=<%=pno%>"><%=pno%></a>
    but its giving error..
    type Status report
    message HTTP method GET is not supported by this URL
    description The specified HTTP method is not allowed for the requested resource (HTTP method GET is not supported by this URL).

    i m trying to call it from jsp using
    <a href="../purchaseP?orderno=<%=pno%>"><%=pno%></a>
    but its giving error..
    type Status report
    message HTTP method GET is not supported by this URL
    description The specified HTTP method is not allowed
    for the requested resource (HTTP method GET is not
    supported by this URL).Are you implementing the doGet or doPost method in your servlet? If you are calling from a hyperlink then it needs to be implementing the GET method. To access the POST method use a html form.

  • Call ejb from browsers

    Hello Developers!
    I deployed my ejb to OAS4081. I call that
    from JDeveloper so it good. But when I try
    to call from applet in IExpl5 I can't
    instantiate the ORB. I've got a com.ms.security.SecurityException : oracle.oas.orb.CORBA.ORB.init
    I coded the CLASSPATH(oasoorb(yoj),client,
    ejbapi...) perfectly, I think.
    If anybody could help, please...
    Thanx!

    Hi there,
              I saw someone on this group had a problem to locate proper classpath
              to call EJB from JSP. I thought if you call EJB from classpath, you are
              calling the bean. But you loss all the EJB functions. To be able to utilize
              EJB features like object pooling. You need to call it from Weblogic server
              using url/jndi, not from the jar directly.
              Any comment? Am I right?
              BTW, my question about calling EJB from JSP means calling through URL,
              not a local path.
              Thank you
              >-------------------------------------------------------------------->
              Jim wrote in message <[email protected]>...
              >Hi there,
              > Can I call EJB from JSP? Is there a particular security setting or
              >concern for Weblogic? Is there an coding example?
              >
              >Thank you
              >
              >
              

  • Call webservice from PJC over https protocol

    Hello!
    I have problem calling webservice from PJC.
    The webservice is on https server so I must declare the keystore and truststore...
    I have generated java classes from wsdl file with SOPAUI and axis 1.0...
    Then I have made a code which integrate axis library, jsee ...
    On the client side all works fine (with jdk 1.3 compiler)
    When I deploy it on oracle forms server and call it from oracle form I get the error:
    java.net.MalformedURLException: unknown protocol: https
    in this way I register the certificate..
    private void registrirajCertifikat(String direktorij, String password,
            String keyStore, String trustStore) {
           System.out.println("keystore: " + direktorij + keyStore);
            System.out.println("trust: " + direktorij + trustStore);
            System.out.println("========================================");
            System.setProperty("javax.net.ssl.keyStore", direktorij + keyStore);
            System.setProperty("javax.net.ssl.keyStorePassword", password);
            System.setProperty("javax.net.ssl.keyStoreType", "pkcs12");
            System.setProperty("javax.net.ssl.trustStore", direktorij + trustStore);
            System.setProperty("javax.net.ssl.trustStorePassword",   password);
            System.setProperty("javax.net.ssl.trustStoreType", "jks");
            System.out.println("========================================");
            System.setProperty("java.protocol.handler.pkgs", "com.sun.net.ssl.internal.www.protocol");
            Security.addProvider( new com.sun.net.ssl.internal.ssl.Provider() );     
        }I have my kestore and truststore located on http server..
    Every time the bean is initializzed I download the keystore and truststore to my java.tmp.dir
    The same code in Jdeveloper works fine.. also in cmd prompt.. but in oracle forms I can't get it to run..
    anybody can help me?
    this is my console output when running a form:
    Oracle JInitiator: Version 1.3.1.22
    Using JRE version 1.3.1.22-internal Java HotSpot(TM) Client VM
    User home directory = C:\Documents and Settings\peterv.IN2SLO
    Proxy Configuration: no proxy
    JAR cache enabled
         Location: C:\Documents and Settings\peterv.IN2SLO\Oracle Jar Cache
         Maximum size: 50 MB
         Compression level: 0
    c:   clear console window
    f:   finalize objects on finalization queue
    g:   garbage collect
    h:   display this help message
    l:   dump classloader list
    m:   print memory usage
    q:   hide console
    s:   dump system properties
    t:   dump thread list
    x:   clear classloader cache
    0-5: set trace level to <n>
    Loading http://dekani:7777/forms/java/frmall_jinit.jar from JAR cache
    Loading http://dekani:7777/forms/java/images.jar from JAR cache
    Cached copy of http://dekani:7777/forms/java/in2kartica.jar
    ** DOKUMENTNI SISTEM   **
    ** PJC bean                     **
    zacetek
    http://10.1.2.235/in2/asarh.pfx
    Copying resource (type: application/octet-stream, modified on: Dec 18, 2009 12:39:35 PM)... to: C:\DOCUME~1\PETERV~1.IN2\LOCALS~1\Temp\asarh.pfx
    3794 byte(s) copied
    http://10.1.2.235/in2/arhaskeystore.jks
    Copying resource (type: application/octet-stream, modified on: Dec 18, 2009 12:39:35 PM)... to: C:\DOCUME~1\PETERV~1.IN2\LOCALS~1\Temp\arhaskeystore.jks
    3800 byte(s) copied
    Registriramo nastavitve za SSL
    keystore: C:\DOCUME~1\PETERV~1.IN2\LOCALS~1\Temp\asarh.pfx
    trust: C:\DOCUME~1\PETERV~1.IN2\LOCALS~1\Temp\arhaskeystore.jks
    ========================================
    po registraciji nastavitev za SSL
    ========================================
    https://hosting.arhiviraj.si/webservice2/InDocArchiveWS.asmx
    --> napaka: *java.net.MalformedURLException: unknown protocol: https*
    java.net.MalformedURLException: unknown protocol: https
         at java.net.URL.<init>(Unknown Source)
         at java.net.URL.<init>(Unknown Source)
         at java.net.URL.<init>(Unknown Source)
         at in2.mikrocop.Test.dokumenti(Test.java:94)
         at in2.mikrocop.Test.testiranje(Test.java:66)
         at in2.mikrocop.Test.<init>(Test.java:49)
         at java.lang.Class.newInstance0(Native Method)
         at java.lang.Class.newInstance(Unknown Source)
         at oracle.forms.ui.VBean.instantiateBean(Unknown Source)
         at oracle.forms.ui.VBean.setProperty(Unknown Source)
         at oracle.forms.handler.UICommon.instantiate(Unknown Source)
         at oracle.forms.handler.UICommon.onCreate(Unknown Source)
         at oracle.forms.handler.JavaContainer.onCreate(Unknown Source)
         at oracle.forms.engine.Runform.onCreateHandler(Unknown Source)
         at oracle.forms.engine.Runform.processMessage(Unknown Source)
         at oracle.forms.engine.Runform.processSet(Unknown Source)
         at oracle.forms.engine.Runform.onMessageReal(Unknown Source)
         at oracle.forms.engine.Runform.onMessage(Unknown Source)
         at oracle.forms.engine.Runform.sendInitialMessage(Unknown Source)
         at oracle.forms.engine.Runform.startRunform(Unknown Source)
         at oracle.forms.engine.Main.createRunform(Unknown Source)
         at oracle.forms.engine.Main.start(Unknown Source)
         at sun.applet.AppletPanel.run(Unknown Source)
         at java.lang.Thread.run(Unknown Source)

    I have tryed tu run my example with Jinitiator "java" like
    c:\java -jar c:\in2kartica.jar
    and all works fine..
    I don't know why the same example won't run inside oracle form as javabean?!?
    this is my cmd console
    C:\jdk\bin>java -jar c:\in2kartica.jar
    ** DOKUMENTNI SISTEM   **
    ** PJC bean            **
    keystore: C:\DOCUME~1\PETERV~1.IN2\LOCALS~1\Temp\asarh.pfx
    trust: C:\DOCUME~1\PETERV~1.IN2\LOCALS~1\Temp\arhaskeystore.jks
    ========================================
    po registraciji nastavitev za SSL
    ========================================
    https://hosting.arhiviraj.si/webservice2/InDocArchiveWS.asmx
    unknown attr1.3.6.1.4.1.311.17.1
    Dolzina: 91  <------------ this is the result from webservice located on address above

  • Calling Servlet from a java prog?

    Hi all,
    I am calling servlet from a java prog (Java Agent in Lotus Notes) by using URL and URLConnection object. how can i trigger the Servlet By using doPost method .I have to send some parameter also.
    Thanx
    Muthu

    you need to open a connection to the servlet. Then you must call getInputStream() and getOutputStream() and use them in any way you see fit. I was trying this before and could not get POST to work unless I openned the input stream from the servlet. Strange... but doGet worked without openning the input stream???
    // open a connection....
    // write to the servlet
    servletConnection.getOutputStream().write("whatever");
    servletConnection.getOutputStream().flush();
    servletConnection.getOutputStream().close();
    // grab what the servlet sends back, required to do a post.
    byte [] in = new byte[100];
    servletConnection.getInputStream().read(in);
    servletConnection.getInputStream().close();

  • Exception while calling BPEL from Java Class

    Hi All,
    I am trying to call BPEL from my Java Code. but i am getting following exception.
    java.lang.Exception: Failed to create "ejb/collaxa/system/DomainManagerBean" bean; exception reported is: "javax.naming.NameNotFoundException: ejb/collaxa/system/DomainManagerBean not found
         at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:52)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at com.oracle.bpel.client.util.BeanRegistry.lookupDomainManagerBean(BeanRegistry.java:218)
         at com.oracle.bpel.client.Locator.getDomainAuth(Locator.java:975)
         at com.oracle.bpel.client.Locator.<init>(Locator.java:73)
         at callbpel.CallBPEL.main(CallBPEL.java:40)
         at com.oracle.bpel.client.util.BeanRegistry.lookupDomainManagerBean(BeanRegistry.java:232)
         at com.oracle.bpel.client.Locator.getDomainAuth(Locator.java:975)
         at com.oracle.bpel.client.Locator.<init>(Locator.java:73)
         at callbpel.CallBPEL.main(CallBPEL.java:40)
    Process exited with exit code 0.
    Following is my java code.
    package callbpel;
    import com.collaxa.cube.util.GUIDGenerator;
    import com.collaxa.xml.XMLHelper;
    import com.oracle.bpel.client.Locator;
    import com.oracle.bpel.client.NormalizedMessage;
    import com.oracle.bpel.client.delivery.IDeliveryService;
    import java.util.Hashtable;
    import java.util.Map;
    import com.oracle.bpel.client.ServerException;
    import java.rmi.RemoteException;
    import java.util.Properties;
    import javax.naming.Context;
    import javax.naming.InitialContext;
    import javax.naming.NamingException;
    import org.w3c.dom.Element;
    public class CallBPEL {
    public CallBPEL() {
    public static void main(String[] args) {
    CallBPEL callBPEL = new CallBPEL();
    Hashtable env;
    try {
    env = callBPEL.getInitialContext();
    String xml = "<ssn xmlns=\"http://services.otn.com\">" + "1234" + "</ssn>";
    Locator locator = new Locator("default",env);
    IDeliveryService deliveryService = (IDeliveryService)locator.lookupService
    (IDeliveryService.SERVICE_NAME );
    NormalizedMessage nm = new NormalizedMessage();
    nm.addPart("payload", xml);
    try {
    deliveryService.post("JavaCallingBPEL", "initiate", nm);
    System.out.println("BPELProcess HelloWorld executed!<br>");
    } catch (ServerException e) {
    e.printStackTrace();
    } catch (RemoteException e) {
    e.printStackTrace();
    } catch (NamingException e) {
    e.printStackTrace();
    } catch (ServerException e) {
    e.printStackTrace();
    private static Hashtable getInitialContext() throws NamingException {
    Hashtable env = new Hashtable();
    env.put("orabpel.platform","ias_10g");
    env.put("java.naming.factory.initial","com.evermind.server.rmi.RMIInitialContextFactory");
    env.put("java.naming.provider.url","opmn:ormi://localhost:6004:oc4j_soa/orabpel");
    env.put("java.naming.security.principal","oc4jadmin");
    env.put("java.naming.security.credentials","welcome1");
    return env;
    I am breaking my head since last two days. i dont know whats the problem. i have included almost all the jars in class path.
    Can anybody help me in this.
    any help is appreciated.
    Thanks,
    Nimisha

    Hi all,
    I have solved above problem but run into some other exception below
    Dec 22, 2008 12:51:34 PM oracle.j2ee.rmi.RMIMessages EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER
    WARNING: Exception returned by remote server: {0}
    com.evermind.server.rmi.RMIConnectionException: Disconnected: com.oracle.bpel.client.AbstractIdentifier; local class incompatible: stream classdesc serialVersionUID = 3174123903773674079, local class serialVersionUID = -4389351842028223514
         at com.evermind.server.rmi.RmiCallQueue.notifyQueuedThreads(RmiCallQueue.java:70)
         at com.evermind.server.rmi.RMIClientConnection.notifyQueuedThreads(RMIClientConnection.java:154)
         at com.evermind.server.rmi.RMIClientConnection.resetState(RMIClientConnection.java:128)
         at com.evermind.server.rmi.RMIConnection.receiveDisconnect(RMIConnection.java:233)
         at com.evermind.server.rmi.RMIClientConnection.receiveDisconnect(RMIClientConnection.java:140)
         at com.evermind.server.rmi.RMIConnection.handleOrmiCommand(RMIConnection.java:208)
         at com.evermind.server.rmi.RMIClientConnection.processReceivedCommand(RMIClientConnection.java:222)
         at com.evermind.server.rmi.RMIConnection.handleCommand(RMIConnection.java:152)
         at com.evermind.server.rmi.RMIConnection.listenForOrmiCommands(RMIConnection.java:127)
         at com.evermind.server.rmi.RMIConnection.run(RMIConnection.java:107)
         at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:819)
         at java.lang.Thread.run(Thread.java:595)
    Any Idea?
    Thanks,
    Nimisha
    Edited by: user649974 on Jan 6, 2009 10:50 AM

  • Calling PopUpManager from a class in a library

    I have a class for logins that I have put in a Flex Library
    Project.
    Part of the login is a popup form(mxml) I have created and is
    in the library.
    The problem I have is this line:
    loginPopUp =
    LoginForm(PopUpManager.createPopUp(this,LoginForm,true));
    The error I get is:
    1067: Implicit coercion of a value of type
    dataManagers:LoginManager to an unrelated type
    flash.display:DisplayObject.
    The parent “this” is no good since its parent
    should be the application that called the logon.
    Can I reference the caller from the LoginManager class I
    created to feed to popupmanager as the parent for the popup?
    The code in the app using the llibray that relates to this
    (to save space) is:
    import dataManagers.LoginManager
    public var lm:LoginManager = new LoginManager();
    lm.initServices();
    //LoginManager.as
    package theLoginManager {
    import flash.events.Event;
    import mx.managers.PopUpManager;
    public class LoginManager {
    import LibraryViews.Login.LoginForm;
    public var loginPopUp:LoginForm;
    public function initServices() : void
    Alert.show("Login start");
    appCFC = new RemoteObject("ColdFusion");
    appCFC.source = "CFC.Users.usersGateway";
    appCFC.addEventListener(FaultEvent.FAULT, server_fault);
    appCFC.init.addEventListener(ResultEvent.RESULT,init_result);
    appCFC.getById.addEventListener(ResultEvent.RESULT,getById_result);
    displayLogin()
    private function displayLogin():void{
    loginPopUp =
    LoginForm(PopUpManager.createPopUp(this,LoginForm,true));//THIS IS
    THE PROBLEM LINE
    loginPopUp.addEventListener("loginSuccessful",
    removeLoginPopup);
    //Removes login form
    private function removeLoginPopup(event:Event):void{
    PopUpManager.removePopUp(loginPopUp);
    }//End Class
    }//End Package
    //LoginForm.mxml
    <?xml version="1.0" encoding="utf-8"?>
    <mx:TitleWindow xmlns:mx="
    http://www.adobe.com/2006/mxml"
    layout="absolute">
    <mx:Form width="100%" height="100%"
    defaultButton="{loginBTN}">
    <mx:FormItem width="100%" label="Username"
    required="true">
    <mx:TextInput id="email"
    width="175" text="mltv"/>
    </mx:FormItem>
    <mx:FormItem width="100%" label="Password"
    required="true">
    <mx:TextInput id="password"
    displayAsPassword="true"
    width="175" text="nuffer"/>
    </mx:FormItem>
    <mx:VBox width="100%" horizontalAlign="center">
    <mx:Button id="loginBTN" label="Login"
    click="authenticateUser();" fillColors="[#80ff00, #80ff00]"/>
    </mx:VBox>
    </mx:Form>
    </mx:TitleWindow>

    I solved it by passing the parent when I called it from the
    parent project:
    lm.initServices(this);
    and then created a var in the .as file:
    private var theCallingParent:DisplayObject;
    theCallingParent = theParent;
    Then used that variable when I called the popup:
    loginPopUp =
    LoginForm(PopUpManager.createPopUp(theCallingParent,LoginForm,true));
    Sorry to clog up the board.

  • Calling getAppletContext() from a working thread.

    Hi guys,
    I'm new to Java so all apologies if I'm asking a stupied question.
    I have a simple applet that creates a working thread and I'm tring to call getAppletContext() from that thread.
    Obviously my working thread has no instance of the Applet class so it fails.
    I've try to create an instance of Applet, but I'm getting an error saying that the applet is not initialised.
    This is my code:
    class MyThread extends Thread
        String ThreadName;
        public MyThread(String threadName)
            ThreadName = threadName;
        @Override public void run()
            // ??? How to make the following line work ???
            getAppletContext().showDocument(new URL("javascript:alert(\"Calling from myThread\")"));
    public class MyApplet extends Applet {
         public void init()
            // The following line works!
            getAppletContext().showDocument(new URL("javascript:alert(\"Calling from MyApplet)"));
            Thread WorkingThread = new MyThread("Thread1");                                                                
            WorkingThread.start();
    }{code}
    Please help,
    Many thanks!
    Salvador                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

    Got it.
    I needed to pass the keyword this to the thread constructor and then use that....
    Many thanks!

  • Call ABAP from Java

    Can any one help me in calling an ABAP program from Java.
    The version of SAP with me is 4.7.
    Thanks in advance.
    Regards ,
    Nagaraju Donikena

    To call ABAP from Java when I tried doing it from sample code given in help I was getting the following error. Can any one help in this regard.
    Exception in thread "main" java.lang.ExceptionInInitializerError: JCO.classIniti
    alize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
    JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [no sapjco
    rfc in java.library.path]. java.library.path
            at com.sap.mw.jco.JCO.<clinit>(JCO.java:735)
            at TestConnect.<init>(TestConnect.java:8)
            at TestConnect.main(TestConnect.java:25)

  • Calling ant from java

    public static void main(String[] args) {
              String arr[] = null;
              arr = new String[2];
              arr[0] = "-buildfile";
              arr[1] = "C:\\workspace\\my projects\\ANTTASKS\\bin\\build.xml";
              try {
                   Launcher launcher = new Launcher();
                   launcher.main(arr);     
              } catch (Exception e) {
                   System.out.println(e.getMessage());
                   // TODO: handle exception
    I tried calling ant from java. But the problem is that, i am not sure how to get the handle of error & input stream from this.
    I also need to know how do I kill the ant executable if there is some kind of exception like ConnectionTimeOut or is there any some kind of timeout mechanism.
    Earlier i was calling ant as an external process like Process P = new Process(), where p.execute("ant.bat xxxxx"). I used to get the error & input stream from the process itself.
    Please help!!!
    thanks

    A better approach would be to use the classes provided in Ant. The API documentation for Ant has all the necessary information.
    The sample code would look like:
    Project ant = new Project();
    ProjectHelper helper = new ProjectHelperImpl();
    ant.init();
    helper.parse(ant, new File("build.xml"));
    ant.executeTarget("clean");

  • How do I run a JCA adapter when I am calling it from an EJB?

    How do I run a JCA adapter when I am calling it from an EJB? Do I need to create an EJB client and place it in a Client container? If my EJB and JCA adapter are deployed is there a way to call my EJB from the command line?
    Mike

    Hi. When you look at the code I provided for you in other thread you will see that connecting to adapter is done through JNDI lookup. The creation of the adapter is done in your J2EE server. Here is some code for you where you can find mapping from code to ejb-jar and orion-ejb-jar.
    ejb-jar.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"
    version="2.1">
    <!--
    This file declares the interface (needs/promises) of the message-driven bean.
    The MDB requires:
    - a JMS queue (to receive messages from the client),
    - a JMS exception queue (to send undeliverable messages back to the source), and
    - a connection factory (to communicate with a JMS resource provider).
    Note that communication with the resource provider may be (and for this
    application is) via a JMS Connector rather than direct.
    -->
    <display-name>JMS Consume MDB - opp-ifs</display-name>
    <enterprise-beans>
    <entity>
    <description>Entity Bean ( BMP )</description>
    <display-name>EBEjbMecomsIFS</display-name>
    <ejb-name>EBEjbMecomsIFS</ejb-name>
    <local-home>EBEjbMecomsIFSLocalHome</local-home>
    <local>EBEjbMecomsIFSLocal</local>
    <ejb-class>EBEjbMecomsIFSBean</ejb-class>
    <persistence-type>Bean</persistence-type>
    <prim-key-class>java.lang.Long</prim-key-class>
    <reentrant>false</reentrant>
    <service-ref>
    <service-ref-name>service/interceptor</service-ref-name>
    <service-interface>javax.xml.rpc.Service</service-interface>
    <wsdl-file>META-INF/wsdl/MHS5_Jms_In_RS.wsdl</wsdl-file>
    <service-qname xmlns:ns="http://oracle.com/esb/namespaces/PilotOWSM_MustHavesScenario5">ns:ESB_MHS5_Jms_In_RS_Service</service-qname>
    </service-ref>
    </entity>
    <message-driven>
    <display-name>JMS Consume MDB - MDB</display-name>
    <ejb-name>MDBEjbMecomsIFS</ejb-name>
    <!-- name of bean in deployment descriptor (including orion-ejb-jar.xml file) -->
    <ejb-class>MDBEjbMecomsIFSBean</ejb-class>
    <!-- bean's fully qualified Java class name -->
    <messaging-type>javax.jms.MessageListener</messaging-type>
    <transaction-type>Container</transaction-type>
    <!-- allow incoming messages to be included in transactions -->
    <!-- The ejb requires a connection factory to access an external resource (JMS). -->
    <ejb-local-ref>
    <ejb-ref-name>ejb/local/EBEjbopp_ifs</ejb-ref-name>
    <ejb-ref-type>Entity</ejb-ref-type>
    <local-home>EBEjbMecomsIFSLocalHome</local-home>
    <local>EBEjbMecomsIFSLocal</local>
    <ejb-link>EBEjbMecomsIFS</ejb-link>
    </ejb-local-ref>
    <resource-ref>
    <!-- The resource's connection factory must be accessible at jndi location "java:comp/env/jms/QueueConnectionFactory". -->
    <res-ref-name>jms/QueueConnectionFactory</res-ref-name>
    <!-- The resource's connection factory must implement the "javax.jms.ConnectionFactory" interface. -->
    <res-type>javax.jms.ConnectionFactory</res-type>
    <!-- container managed authorization -->
    <res-auth>Container</res-auth>
    </resource-ref>
    </message-driven>
    </enterprise-beans>
    <assembly-descriptor>
    <!--
    Declare that a global transaction is required when the onMessage method of the ejb named
    "MDBEjbName" is called. This will cause the app server to automatically initiate a
    global (XA) transaction before calling onMessage (actually, before even receiving the JMS
    message that triggers onMessage) and end the transaction after onMessage returns. The
    JMS Connector will automatically rollback the transaction if onMessage throws an
    exception. onMessage may also set the transaction to be "rollback only".
    Participating in global transactions requires that the connection factory provided in the
    activation spec (see the ConnectionFactoryJndiName property earlier in this file) must be
    XA-capable (it must implement the javax.jms.XAConnectionFactory interface).
    If this declaration is ommitted, then onMethod will not be part of any global
    transaction. In that case the connection factory provided in the activation spec must
    implement the javax.jms.ConnectionFactory interface.
    -->
    <container-transaction>
    <method>
    <ejb-name>MDBEjbMecomsIFS</ejb-name>
    <method-name>onMessage</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>EBEjbMecomsIFS</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Supports</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    </ejb-jar>
    orion-ejb-jar.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <orion-ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:noNameSpaceSchemaLocation="http://www.oracle.com/technology/oracleas/schema/orion-ejb-jar-10_0.xsd">
    <enterprise-beans>
    <entity-deployment name="EBEjbMecomsIFS">
    <service-ref-mapping name="service/interceptor">
    <wsdl-location>http://on-poc62.ontw.alfa.local:7777/event/PilotOWSM/MustHavesScenario5/MHS5_Jms_In_RS?wsdl</wsdl-location>
    <service-qname localpart="ESB_MHS5_Jms_In_RS_Service" namespaceURI="http://oracle.com/esb/namespaces/PilotOWSM_MustHavesScenario5"/>
    <port-info>
    <wsdl-port namespaceURI="http://oracle.com/esb/namespaces/PilotOWSM_MustHavesScenario5"
    localpart="__soap_MHS5_Jms_In_RS_execute_ppt"/>
    <service-endpoint-interface>javax.xml.rpc.Service</service-endpoint-interface>
    <call-property>
    <name>javax.xml.rpc.service.endpoint.address</name>
    <value>http://on-poc62.ontw.alfa.local:7777/event/PilotOWSM/MustHavesScenario5/MHS5_Jms_In_RS</value>
    </call-property>
    <call-property>
    <name>javax.xml.rpc.soap.http.soapaction.uri</name>
    <value>execute</value>
    </call-property>
    <call-property>
    <name>javax.xml.rpc.soap.http.soapaction.use</name>
    <value>true</value>
    </call-property>
    <call-property>
    <name>javax.xml.rpc.soap.operation.style</name>
    <value>document</value>
    </call-property>
    <runtime enabled="owsm">
    <owsm init-home="/oracle/product/SoaAs/10.1.3/owsm/config/interceptors/C0003002"
    init-file="confluent.properties"/>
    </runtime>
    </port-info>
    </service-ref-mapping>
    </entity-deployment>
    <message-driven-deployment name="MDBEjbMecomsIFS"
    resource-adapter="OEMSJMSDRAopp-ifs"
    enabled="true" max-instances="10">
    <!--
    The ejb requires a connection factory implementing the "javax.jms.XAConnectionFactory"
    interface to be accessible at jndi location "java:comp/env/jms/QueueConnectionFactory". (see ejb-jar.xml and ....)
    A suitable connection factory is already accessible at jndi location "OEMSJMSDRASubcontext/MyXACF" (see oc4j-ra.xml)
    -->
    <resource-ref-mapping location="OEMSJMSDRASubopp-ifs/MyXACF"
    name="jms/QueueConnectionFactory"/>
    <!-- don't misspell this or you'll get an RP CF which doesn't work -->
    <!-- Required activation-spec properties. -->
    <!--
    ConnectionFactoryJndiName (string, no default)
    This should be the JNDI location of an RA connection factory.
    The JMS Connector will use this connection factory to create the JMS
    connection it uses to receive messages for this MDB's onMessage. If the
    exception queue is enabled (see UseExceptionQueue), the JMS Connector will
    also use a connection created from this connection factory for the production
    of messages to the exception queue.
    This connection factory must be compatible with the message domain(s). (For
    example, if the MDB is receiving messages from a queue, the connection
    factory should implement javax.jms.[XA]QueueConnectionFactory or
    javx.jms.[XA]ConnectionFactory.)
    For XA/non-XA considerations, see the <container-transaction> comments later
    in this file.
    -->
    <config-property>
    <config-property-name>ConnectionFactoryJndiName</config-property-name>
    <config-property-value>OEMSJMSDRASubopp-ifs/MyXAQCF</config-property-value>
    </config-property>
    <!--
    DestinationName (string, no default)
    This is JNDI location of the queue or topic from which messages to be
    delivered to the MDB's onMessage method should be received.
    The JNDI locations for RA destinations are defined in the
    oc4j-connectors.xml file.
    -->
    <config-property>
    <config-property-name>DestinationName</config-property-name>
    <config-property-value>OEMSJMSDRASubopp-ifs/MyQ</config-property-value>
    </config-property>
    <!--
    DestinationType (string, no default)
    This must be set to the type of the destination named by the above
    "DestinationName" property.
    The EJB 2.1 spec states that this must be set to either javax.jms.Queue or
    javax.jms.Topic. OracleGJRA also allows it to be set to
    javax.jms.Destination (which works for both queues and topics).
    -->
    <config-property>
    <config-property-name>DestinationType</config-property-name>
    <config-property-value>javax.jms.Queue</config-property-value>
    </config-property>
    <!--
    Other activation-spec properties.
    The following activation-spec properties supported by OracleGJRA are optional
    except where otherwise noted:
    -->
    <!--
    ListenerThreadMaxPollInterval (milliseconds, 5000)
    Listener threads "poll" to see if there is a message waiting to be processed.
    The more frequently this polling is performed, the faster (on average) a given
    listener thread can respond to a new message. The price for frequent polling is
    overhead - the resource provider must process a receive request each time it is
    polled.
    Oracle's JMS Connector implementation applies an adaptive algorithm which
    uses shorter polling intervals (high polling rates) during periods of activity
    (once activity is noticed) and longer polling intervals (lower polling rates)
    during periods of inactivity. The ListenerThreadMaxPollInterval property places
    an upper limit on the polling interval used by this adaptive algorithm.
    -->
    <config-property>
    <config-property-name>ListenerThreadMaxPollInterval</config-property-name>
    <config-property-value>5000</config-property-value>
    </config-property>
    <!--
    AcknowledgeMode (string, default = Auto-acknowledge)
    This should be set to Auto-acknowledge or Dups-ok-acknowledge. This
    controls the quality-of-service provided by listener threads which
    consume messages and call the MDB's onMessage method.
    MessageSelector (string, default = no message filtering)
    This is the selector expression used to filter messages sent to the
    MDB's onMessage method. (I.e., this is used as the messageSelector for
    the JMS sessions created for the listener threads.)
    SubscriptionDurability (string, default = NonDurable)
    For topics this should be set to Durable or NonDurable. (This should
    not be set for queues.) This controls the durability of the topic
    consumer used by the listener thread. When SubscriptionDurability is
    set to Durable (and DestinationType is javax.jms.Topic or
    javax.jms.Destination), the SubscriptionName property is required.
    SubscriptionName (string, no default)
    This property is required when SubscriptionDurability is Durable (and
    DestinationType is javax.jms.Topic or javax.jms.Destination). (In all
    other cases it is ignored.) This is the name used when creating the
    durable subscriber used by the listener thread. For a given JMS server,
    a given subscription name should be assigned to at most one MDB (which
    must have most one listener thread).
    ClientId (string, no default)
    If set, connection(s) used by the listener threads will be set to use
    this client ID.
    TransactionTimeout (milliseconds, default = 300,000)
    This limits the amount of time that the JMS Connector will wait for a
    message to arrive before exiting the current transaction. The
    transaction manager limits the amount of time a transaction can last
    (see transaction-timeout in transaction-manager.xml).
    TransactionTimeout should be set such that the transaction manager will
    not timeout the transaction during the onMessage routine unless
    something is wrong. For example, If the transaction mananager timeout
    is set to 30 seconds, and the onMessage routine will never take more
    than 10 seconds unless something is wrong, then this property could be
    set to 20 seconds (20000 milliseconds).
    EndpointFailureRetryInterval (milliseconds, default = 60,000)
    If an endpoint can not be processed (due to the app server WorkManager
    not accepting new work), it will be scheduled to be retried this many
    milliseconds later.
    ReceiverThreads (integer, default = 1)
    This sets the maximum number of listener threads to create for this
    endpoint. For queues, using more than one thread may be useful in
    increasing the rate at which messages can be consumed. For topics this
    value should always be 1. (Each listener thread gets its own session
    and TopicSubscriber. For durable subscribers it would be an error to
    have more than one subscriber with the same subscription name. For
    nondurable subscribers having more than one thread will not help because
    more threads translates into more subscribers which translates into more
    copies of each message.) See also: ListenerThreadMinBusyDuration
    UseExceptionQueue (boolean, default = false)
    When "UseExceptionQueue" is true:
    - Messages that would otherwise be discarded are sent to the
    exception queue. (Currently the only case where this happens is
    when the max delivery count is exceeded. See MaxDeliveryCnt
    property.) Rather than sending the original message directly to
    the exception queue, the following procedure is used:
    o Create a new message of the same type.
    o Copy the properties and body from the original message to the
    new message.
    o If the headers were copied, sending the message to the
    exception queue would cause most of them to be lost
    (over-written by the resource-provider). So instead,
    translate headers in the original to properties in the copy,
    assigning each header obtained via "getJMS{Header}" to
    property "GJRA_CopyOfJMS{Header}". Since
    javax.jms.Destination is not a valid property type, translate
    destination headers into descriptive messages.
    (Currently this same service is not provided for JMSX*
    properties, most notably the JMSXDeliveryCount property.)
    o If some part of the copy process (above) or augmentation
    process (below) fails, do not abort. Attempt to complete the
    rest of the procedure. (For Bytes/Map/Stream message types,
    this can mean that part of the body is copied and the rest is
    not.)
    o If the copy process is 100% successful, add a boolean property
    called "GJRA_CopySuccessful" with the value "true".
    o Add a string property called "GJRA_DeliveryFailureReason" which
    indicates why the message was not delivered.
    o If the MDB onMessage method generated an exception immediately
    prior to the delivery failure, add a string property called
    "GJRA_onMessageExceptions" which contains exception information.
    o Send the resulting message to the exception queue.
    Note that only one attempt is made to send the message to the
    exception queue. Should this attempt fail, the message will
    be discarded without being placed in the exception queue.
    See IncludeBodiesInExceptionQueue property for potential variations
    of the above procedure.
    - The ExceptionQueueName property is required.
    - In addition to being used for the primary destination, the
    connection factory specified by the ConnectionFactoryJndiName
    property will also be used for the exception queue. If the primary
    destination (specified by the DestinationName property) is a topic,
    then the connection factory must support both queues and topics.
    (I.e., the <connectionfactory-interface> [see oc4j-ra.xml] for the
    given connection factory must be either javax.jms.ConnectionFactory
    or javax.jms.XAConnectionFactory.)
    ExceptionQueueName (string, no default)
    This is the JNDI location of the javax.jms.Queue object to use as the
    exception queue. (See UseExceptionQueue property for information about
    the use of the exception queue.) This property is required when
    UseExceptionQueue is true, and ignored when UseExceptionQueue is false.
    IncludeBodiesInExceptionQueue (boolean, default = true)
    This controls whether or not messages sent to the exception queue will
    include a message body. (See UseExceptionQueue property for information
    about the use of the exception queue.) If many messages are sent to the
    exception queue during normal operation and the message body is of no
    use in the exception queue, then this property may be set false to
    improve performance. This property is ignored when UseExceptionQueue is
    false. There are two cases where this property does not apply:
    - If the original message did not have a message body, then the
    message sent to the exception queue will not have one either.
    - If a copy of the original message can not be created for any
    reason, then the original may be sent to the exception queue
    instead. This may result in a message body being sent to the
    exception queue.
    MaxDeliveryCnt (integer, default = 5)
    If a message has the "JMSXDeliveryCount" property and the value of that
    property is greater than MaxDeliveryCnt, then the message will be
    discarded (and not sent to onMessage). If the exception queue is
    enabled (see UseExceptionQueue), a copy of the message will be sent to
    the exception queue. If MaxDeliveryCnt is set to 0, no messages will be
    discarded. (Note that when an MDB responds to a message by throwing an
    exception, the message is not considered delivered and it may be
    redelivered. If the MDB might always respond to a given message by
    throwing an exception, and MaxDeliveryCnt is set to 0 to prevent the
    message from ever being discarded, the result may be an MDB stuck in an
    "infinite loop" - failing to process the same message over and over
    again.)
    -->
    <config-property>
    <config-property-name>MaxDeliveryCnt</config-property-name>
    <config-property-value>0</config-property-value>
    </config-property>
    <!--
    LogLevel (string, no default)
    This controls the level of detail of messages logged by the JMS
    Connector. These messages are primarily intended for debugging the
    JMS Connector itself, but may also be useful when debugging issues
    related to the use of the JMS Connector. This property should not be
    set in production code. (It should only be set temporarily for
    debugging purposes - specific log messages and log levels may be and
    will be added/removed/modified in future versions of the JMS
    Connector.) Currently the allowed values are:
    ConnectionPool
    ConnectionOps
    TransactionalOps
    ListenerThreads
    INFO
    CONFIG
    FINE
    FINER
    FINEST
    SEVERE
    WARNING
    OFF
    ListenerThreadMaxIdleDuration (milliseconds, default = 300,000)
    This is how long a listener thread which is not receiving any messages
    will be kept around. (At least one listener thread will remain as long
    as the endpoint is active.)
    ListenerThreadMinBusyDuration (milliseconds, default = 10,000)
    If a listener thread has just received a message, has not been idle (had to
    wait for a new message to arrive) at any point during the past
    ListenerThreadMinBusyDuration milliseconds, and the current number of
    listener threads for this endpoint is less than ReceiverThreads, then
    (application server willing) an additional listener thread will be created.
    ResUser (string, default = null)
    ResPassword (string, default = null)
    These properties allow a user/password to be passed to the resource
    provider. When neither of these properties are set, connections used for
    this MDB's inbound message handling (as well as for exception queue
    handling, if enabled) are created using the no-argument version of the
    create*Connection method. When one or both of these properties are set,
    they are passed to the create*Connection method as the user/password
    arguments. (If only one property is not set, then 'null' is used for that
    particular create*Connection argument.) The ResPassword property supports
    the standard password indirection options (e.g., using "->joeuser" to
    represent the password of "joeuser").
    Note that the commas used in many of the above default values and examples are
    included here for readability but can not be used in the actual activation spec.
    (I.e., integer/milliseconds values in the activation spec must not include
    embedded commas.)
    -->
    </message-driven-deployment>
    </enterprise-beans>
    <assembly-descriptor>
    <default-method-access>
    <security-role-mapping name="&lt;default-ejb-caller-role>"
    impliesAll="true"/>
    </default-method-access>
    </assembly-descriptor>
    </orion-ejb-jar>

  • Call function from action panel in second frame

    I am starting to learn Adobe Flash. I'm using Flash CS6.
    I have a file called test.fla and another called bikertest.as
    Bikertest has this code:
    package as3.grey{
    import com.grey.utils.Console;
    //import com.grey.utils.ClickTag;
    import flash.display.MovieClip;
    import com.greensock.TweenNano;
    import com.greensock.easing.*;
    import flash.events.*;
    public class bikertest extends MovieClip {
    private var mc:MC;
    private var console:Console; 
    public function ray():void{
    init();
    trace("hi from here");
    mc=new MC 
    ; addChild(mc);
    I tried:
    import as3.grey.bikertest.as; 
    var t = new bikertest(); 
    t.ray();
    I want to be able to call ray() from the Action Panel in the second frame in test.fla . I hope this is clear. How can I do that? /Thanks!

    assuming your fla is in a super directory of as/grey and everything in bikertest is defined, use:
    import as3.grey.bikertest;
    var t:bikertest=new bikertest();
    t.ray();

  • How can I deploy a simple stateless ssion EJB and call it from a standalone client

    Hi,
    I'm creating s simple staless session EJB that has a method that takes a name and prints "Hello" + name. This EJB is in a package called "com.demos.mydemo.ejbs.hello"
    How can I deploy this to OC4J?
    How can I call it from a standalone client(no JSP, no servlets)?
    In Sun's J2EE is very easy to deploy and I don't have to know any XML stuff.
    can I use the .ear file created by the Sun's "deploytool" to deploy my EJB to OC4J?
    This is the code at I'm using and it works on Sun's j2sdkee1.2.1:
    ///////// Remote /////////
    package com.demos.mydemo.ejbs.hello;
    import java.rmi.RemoteException;
    import javax.ejb.EJBObject;
    public interface Hello extends EJBObject {
    public String sayHello(String name) throws RemoteException;
    ///////// Home //////////
    package com.demos.mydemo.ejbs.hello;
    import java.rmi.RemoteException;
    import javax.ejb.EJBHome;
    import javax.ejb.CreateException;
    public interface HelloHome extends EJBHome {
    public Hello create() throws CreateException, RemoteException;
    /////////// Bean class ///////////
    package com.demos.mydemo.ejbs.hello;
    import java.rmi.RemoteException;
    import javax.ejb.SessionBean;
    import javax.ejb.SessionContext;
    import javax.ejb.CreateException;
    import javax.ejb.EJBException;
    import java.sql.Connection;
    import java.sql.SQLException;
    //import java.sql.PreparedStatement;
    import javax.sql.DataSource;
    import javax.naming.NamingException;
    import javax.naming.InitialContext;
    public class HelloEJB implements SessionBean {
    private SessionContext context;
    private Connection con;
    private String dbName =
    "java:comp/env/jdbc/Oracle";
    public HelloEJB() {}
    public void setSessionContext (SessionContext context) {
    this.context = context;
    public void ejbCreate() throws CreateException {
    try {
    makeConnection();
    catch (Exception e) {
    System.err.println("HelloEJB: exception in ejbCreate:" + e.getMessage());
    e.printStackTrace();
    throw new CreateException(e.getMessage());
    public void ejbActivate() {
    public void ejbPassivate() {
    public void ejbRemove() {
    try {
    con.close();
    catch (SQLException ex) {
    throw new EJBException("HelloEJB: exception in ejbRemove: " + ex.getMessage());
    public String sayHello(String name) {
    return "Hello " + name;;
    private void makeConnection() throws NamingException, SQLException {
    try {
    InitialContext ic = new InitialContext();
    DataSource ds = (DataSource) ic.lookup(dbName);
    con = ds.getConnection();
    catch (Exception e) {
    System.err.println("HelloEJB: exception in makeConnection:" + e.getMessage() );
    e.printStackTrace();
    //////////// EJB client that uses a stateless session bean
    package com.demos.mydemo.ejbs.hello;
    import java.io.*;
    import java.sql.*;
    import javax.sql.*;
    import javax.naming.Context;
    import javax.naming.InitialContext;
    import javax.rmi.PortableRemoteObject;
    public class HelloClient {
    public static void main(String[] args) {
    try {
    Context initial = new InitialContext();
    Object objref = initial.lookup("HelloSession");
    HelloHome home = (HelloHome)PortableRemoteObject.narrow(objref,HelloHome.class);
    Hello h = home.create();
    String msg = h.sayHello("John Doe");
    System.out.println(msg);
    //h.remove();
    } catch (Exception ex) {
    System.err.println("Caught an exception." );
    ex.printStackTrace();
    Thanks
    Nabil
    null

    <BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Nabil Khalil ([email protected]):
    I deployed and .ear file created by Sun's J2EE deployment tool on the OC4J. It looks that it was deployed fine -- did not get a deployment error.
    When I run the client I'm getting the following error: Caught an exception.
    javax.naming.CommunicationException: Can't find SerialContextProvider
    at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:60)
    at com.sun.enterprise.naming.SerialContext.<init>(SerialContext.java:79)
    at com.sun.enterprise.naming.SerialInitContextFactory.getInitialContext(SerialInitContextFactory.java:54)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:668)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
    at javax.naming.InitialContext.init(InitialContext.java:222)
    at javax.naming.InitialContext.<init>(InitialContext.java:178)
    at com.equifax.fms.ejbs.hello.HelloClient.main(HelloClient.java:18)
    This makes me think that the client can't see the deployed EJB on the OC4J.
    How can I fix this problem?
    Thanks
    Nabil
    <HR></BLOCKQUOTE>
    Nabil -
    Your standalone client needs to obtain certain server-dependent properties. You can provide them in your code or grab them via a properties file.
    For Orion - you need essentially the following setup, filling in your own information...
    Define your standalone client class with "main" etc (this is orion specific - should work for 9i AS as well - perhaps there are some differences)
    public class SomeClass {
    try {
    Properties p = new Properties();
    p.setProperty("java.naming.factory.initial",
    "com.evermind.server.ApplicationClientInitialContextFactory");
    p.setProperty("java.naming.security.principal","server_admin_name");
    p.setProperty("java.naming.security.credentials","server_password");
    // THEN you can get your intitial context reference
    InitialContext initial = new InitialContext (p);...........
    Then go about your business.....
    A good book to get is called "Professional Java Server Programming J2EE Edition" - there happens to be a reasonable amount of Orion/OCJ4 centric information since one of the authors is Karl Avedal - one of the principals behind Orion. Go out to java.sun.com and look at some of the J2EE tutorials - unfortunately a lot of it is hidden behind the J2EE Deployer, but you will get a good sense of what goes into outside-the-container standalone clients.
    null

Maybe you are looking for