Workflow standalone client?

IS the workflow standalone client downloadable freely from OTN? I have searched so far in vain!

There is no free download for Workflow on the Oracle Site. You can try getting this through Oracle vendor.
null

Similar Messages

  • Issue when a standalone client invoke a method on an EJB

    I do a simple ejb (like SayHello sample) and i create a standalone client that call one method of this EJB.
    When i run the client i have the following error from the eclipse IDE (Error is thrown at lookup):
    Exception in thread "main" java.lang.AssertionError: java.lang.ClassNotFoundException: test.IHelloWorld
         at weblogic.ejb.container.internal.RemoteBusinessIntfGenerator.generateRemoteInterface(RemoteBusinessIntfGenerator.java:57)
         at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.readObject(RemoteBusinessIntfProxy.java:205)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
         at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1849)
         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
         at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
         at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
         at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
         at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:197)
         at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:564)
         at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:193)
         at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:240)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
         at weblogic.jndi.internal.ServerNamingNode_1030_WLStub.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:392)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at client.MainHello.main(MainHello.java:21)
    Caused by: java.lang.ClassNotFoundException: test.IHelloWorld
         at weblogic.ejb.container.deployer.RemoteBizIntfClassLoader.getClassBytes(RemoteBizIntfClassLoader.java:151)
         at weblogic.ejb.container.deployer.RemoteBizIntfClassLoader.loadClass(RemoteBizIntfClassLoader.java:96)
         at weblogic.ejb.container.internal.RemoteBusinessIntfGenerator.generateRemoteInterface(RemoteBusinessIntfGenerator.java:54)
         ... 26 more
    The eclipse IDE is runwith the option -vm D:\bea\jdk160_05\bin\java
    In eclipse, i configure to use the same jdk.
    When i execute the client outside eclipse, all is ok....
    Do you have an idée ?
    This is the ejb code :
    package test;
    public interface IHelloWorld {
    public static final String JNDI_NAME = "HelloWorld";
    public String sayHello( String name);
    package test;
    import javax.ejb.Remote;
    import javax.ejb.Stateless;
    import javax.ejb.TransactionAttribute;
    import javax.ejb.TransactionAttributeType;
    import javax.ejb.TransactionManagement;
    import javax.ejb.TransactionManagementType;
    @TransactionManagement(TransactionManagementType.CONTAINER)
    @TransactionAttribute(TransactionAttributeType.REQUIRED)
    @Stateless( name="HelloWorld", mappedName= IHelloWorld.JNDI_NAME)
    @Remote( IHelloWorld.class)
    public class HelloWorld implements IHelloWorld
    public String sayHello (String name) {
    final String msg = "Hello " + name + ". The world is wonderfull...";
    System.out.println ( msg);
    return msg;
    This is the client code :
    package client;
    import java.util.Hashtable;
    import javax.naming.Context;
    import javax.naming.InitialContext;
    import test.IHelloWorld;
    public class MainHello {
    public static void main (String[] args) throws Exception
    Hashtable<String, String> properties = new Hashtable<String, String> ();
    properties.put (Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    properties.put (Context.PROVIDER_URL, "t3://localhost:7001");
    InitialContext ctx = new InitialContext( properties);
    IHelloWorld hello = (IHelloWorld)ctx.lookup ( "HelloWorld#test.IHelloWorld");
    String result = hello.sayHello ( "franck");
    System.out.println ( result);
    ctx.close ();
    As you can see it is very simple but doesn't work inside eclipse IDE...
    Edited by: user11281761 on 30 juin 2009 07:13

    Oracle software purchases come with a CSI number that allows customers to have people contact support for products they own. If you or the organization you are working with has not purchased the product or have other support arrangements with Oracle (some partners have this), then you probably will not be able to obtain the patch from Oracle.
    You might be able to try a newer release of the product with an OTN evaluation license, WebLogic Server is currently on version 10.3.3, so you are at least 3 releases behind at this point if you are using 10.3.0.

  • Writing a Standalone Client for EJB 3.0 Bean For Weblogic 10

    Steps for Writing a Standalone Client
    Client Code
    package com.client;
    import java.util.Properties;
    import javax.naming.Context;
    import javax.naming.InitialContext;
    import javax.naming.NamingException;
    import javax.rmi.PortableRemoteObject;
    import com.StatelessService;
    public class StatelessClient {
         public static void main(String [] args){
              Context ctx = null;
              try {
                   ctx = getInitialContext("t3://localhost:7001/protossbservice","weblogic","weblogic");
                   Object ref = ctx.lookup("StatelessService#"+StatelessService.class.getName());
                   StatelessService service = (StatelessService)PortableRemoteObject.narrow(ref,StatelessService.class);     
                   System.out.println("StatelessClient.getMessage() ++");
                   String  message = service.getMessage();
                   System.out.println("StatelessClient.getMessage --");
                        System.out.println("Message from Bean "+message);
         } catch (NamingException e) {
                   e.printStackTrace();
         private static Context getInitialContext(String url, String user, String password) throws NamingException {
            Properties h = new Properties();
            h.put(Context.INITIAL_CONTEXT_FACTORY,
                    "weblogic.jndi.WLInitialContextFactory");
            h.put(Context.PROVIDER_URL, url);
            h.put(Context.SECURITY_PRINCIPAL, user);
            h.put(Context.SECURITY_CREDENTIALS, password);
            return new InitialContext(h);
    Business Interface
    package com;
    public interface StatelessService {
         public String getMessage();
    Stateless Session Bean
    package com;
    import javax.annotation.PostConstruct;
    import javax.ejb.Remote;
    import javax.ejb.Stateless;
    * Test Stateless Session Bean
    @Stateless(mappedName="StatelessService")
    @Remote(StatelessService.class)
    public class StatelessServiceBean implements StatelessService {
         public String getMessage(){
              return "I am invoked";

    emekaco wrote:
    Hi,
    I am a trainee although with a good background in java.
    I'm urgently in need of a free ebook for EJB 3.0 with the latest version of Netbean. Pls, help me with one if you have. my email is [email protected]
    http://www.theserverside.com/tt/books/wiley/masteringEJB3/index.tss
    Here's a good free e-book but without Netbean. It covers everything you would need to know about EJBs.
    >
    Again, is container managed bean good for a big project?
    The question is too vague to be answered. It's a design decision that needs more details.

  • Lookup form standalone client  fails with java.lang.ClassNotFoundException

    Hi,
    I have an issue under Weblogic 11g when a standalone client tries to lookup for an ejb deployed in an ear.
    The ear is correclty deployed without any errors and the EJB is correctly defined in the jndi tree (i see it using the jndi browser through the weblogic console).
    When my client tries to lookup the EJB using its correct JNDI name, the client receives the following exception :
    java.lang.AssertionError: java.lang.ClassNotFoundException: com.gemalto.contactless.securearm.services.api.IRepositoryServiceRemote
         at weblogic.ejb.container.internal.RemoteBusinessIntfGenerator.generateRemoteInterface(RemoteBusinessIntfGenerator.java:57)
         at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.readObject(RemoteBusinessIntfProxy.java:205)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
         at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1849)
         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
         at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
         at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
         at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
         at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:197)
         at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:564)
         at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:193)
         at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:240)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
         at weblogic.jndi.internal.ServerNamingNode_1030_WLStub.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:392)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at com.gemalto.contactless.securearm.client.SarmProv.main(SarmProv.java:167)
    Caused by: java.lang.ClassNotFoundException: com.gemalto.contactless.securearm.services.api.IRepositoryServiceRemote
         at weblogic.ejb.container.deployer.RemoteBizIntfClassLoader.loadClass(RemoteBizIntfClassLoader.java:116)
         at weblogic.ejb.container.internal.RemoteBusinessIntfGenerator.generateRemoteInterface(RemoteBusinessIntfGenerator.java:54)
         ... 26 more
    No error found in the server logs !
    If you have an idea that can helps mee ....
    Thank you
    Franck.

    Yes it is in my classpath. You can take a look at my command line generated by my IDE :
    D:\bea11g\jdk160_11\bin\java -Xrunjdwp:transport=dt_socket,address=127.0.0.1:15251,suspend=y,server=n -Dfile.encoding=windows-1252 -classpath "D:\bea11g\jdk160_11\jre\lib\charsets.jar;D:\bea11g\jdk160_11\jre\lib\deploy.jar;D:\bea11g\jdk160_11\jre\lib\javaws.jar;D:\bea11g\jdk160_11\jre\lib\jce.jar;D:\bea11g\jdk160_11\jre\lib\jsse.jar;D:\bea11g\jdk160_11\jre\lib\management-agent.jar;D:\bea11g\jdk160_11\jre\lib\plugin.jar;D:\bea11g\jdk160_11\jre\lib\resources.jar;D:\bea11g\jdk160_11\jre\lib\rt.jar;D:\bea11g\jdk160_11\jre\lib\ext\dnsns.jar;D:\bea11g\jdk160_11\jre\lib\ext\localedata.jar;D:\bea11g\jdk160_11\jre\lib\ext\sunjce_provider.jar;D:\bea11g\jdk160_11\jre\lib\ext\sunmscapi.jar;D:\bea11g\jdk160_11\jre\lib\ext\sunpkcs11.jar;_D:\cless2009\classes\production\SecureARM_;D:\cless2009\classes\production\Util;D:\cless2009\classes\production\Shared;D:\cless2009\CoreBuild\res\gemalto\telecom\FRWK\v4.0\FRWK_4.0_patch07\api\FRWK\ci_api.jar;D:\glassfish\domains\domain1\lib\ext\vbsec.jar;D:\glassfish\domains\domain1\lib\ext\common.jar;D:\glassfish\domains\domain1\lib\ext\container.jar;D:\cless2009\CoreBuild\res\gemalto\telecom\FRWK\v4.0\FRWK_4.0_patch07\api\FRWK\ci_extends.jar;D:\glassfish\domains\domain1\lib\ext\lm.jar;D:\glassfish\domains\domain1\lib\ext\vbjorb.jar;D:\glassfish\domains\domain1\lib\ext\basesystem.jar;D:\cless2009\CoreBuild\res\ext\Log4j\v1.2.13\lib\log4j-1.2.13.jar;D:\cless2009\CoreBuild\res\ext\commons-lang\v2.3\commons-lang-2.3.jar;D:\cless2009\CoreBuild\res\ext\junit\v4.1\junit-4.1.jar;D:\cless2009\CoreBuild\res\gemalto\telecom\OTA_IPInfra\v1.0\OTA_IPInfra_1_0_2_0016_090701_0926\lib\glassfish\api\oti_cmdmgr-api.jar;D:\cless2009\CoreBuild\res\gemalto\telecom\OTA_IPInfra\v1.0\OTA_IPInfra_1_0_2_0016_090701_0926\lib\glassfish\tools\oti_linqusconnector-mock.jar;D:\cless2009\CoreBuild\res\gemalto\telecom\OTA_IPInfra\v1.0\OTA_IPInfra_1_0_2_0016_090701_0926\lib\glassfish\install\OTA_IPInfra_1.0.2.0016_sun.jar;D:\cless2009\CoreBuild\res\gemalto\telecom\OTA_IPInfra\v1.0\OTA_IPInfra_1_0_2_0016_090701_0926\lib\glassfish\api\oti_history-api.jar;D:\cless2009\CoreBuild\res\gemalto\telecom\OTA_IPInfra\v1.0\OTA_IPInfra_1_0_2_0016_090701_0926\lib\glassfish\core\OTAIPInfra.ear;D:\cless2009\CoreBuild\res\gemalto\telecom\OTA_IPInfra\v1.0\OTA_IPInfra_1_0_2_0016_090701_0926\lib\glassfish\api\oti_connectivity-api.jar;D:\cless2009\CoreBuild\res\gemalto\telecom\OTA_IPInfra\v1.0\OTA_IPInfra_1_0_2_0016_090701_0926\lib\glassfish\api\oti_shared-api.jar;D:\cless2009\CoreBuild\res\gemalto\telecom\OTA_IPInfra\v1.0\OTA_IPInfra_1_0_2_0016_090701_0926\lib\glassfish\api\oti_notification-api.jar;D:\cless2009\CoreBuild\res\gemalto\telecom\OTA_IPInfra\v1.0\OTA_IPInfra_1_0_2_0016_090701_0926\lib\glassfish\core\libext.zip;D:\cless2009\CoreBuild\res\gemalto\telecom\OTA_IPInfra\v1.0\OTA_IPInfra_1_0_2_0016_090701_0926\lib\glassfish\api\oti_loginmodule-api.jar;D:\cless2009\CoreBuild\res\gemalto\telecom\OTA_IPInfra\v1.0\OTA_IPInfra_1_0_2_0016_090701_0926\lib\glassfish\core\domain.zip;D:\cless2009\CoreBuild\ECLIPSE_LIB\oti-linqusconnector-jmx-custom.jar;D:\cless2009\CoreBuild\res\gemalto\telecom\OTA_IPInfra\v1.0\OTA_IPInfra_1_0_2_0016_090701_0926\lib\glassfish\api\oti_otagateway-api.jar;D:\cless2009\CoreBuild\res\gemalto\telecom\OTA_IPInfra\v1.0\OTA_IPInfra_1_0_2_0016_090701_0926\lib\glassfish\api\oti_trigsms-api.jar;D:\cless2009\CoreBuild\res\gemalto\telecom\OTA_IPInfra\v1.0\OTA_IPInfra_1_0_2_0016_090701_0926\lib\main\mmserver_ref.zip;D:\bea11g\user_projects\domains\cless\lib\wllog4j.jar;D:\bea11g\user_projects\domains\cless\lib\ojdbc14.jar;D:\bea11g\wlserver_10.3\server\lib;D:\bea11g\user_projects\domains\cless\lib\eclipselink.jar;D:\bea11g\user_projects\domains\cless\lib\log4j-1.2.14.jar;D:\cless2009\classes\production\SharedCustom;D:\cless2009\CoreBuild\res\gemalto\telecom\REUSE\v1.0\REUSE_1_0_b0148_071211_1059\lib\reuse.jar;D:\cless2009\CoreBuild\res\gemplus\telecomtlvtools\v1.0\build1\tlvtools.jar;D:\bea11g\wlserver_10.3\server\lib\wlfullclient.jar;D:\bea11g\wlserver_10.3\server\lib\wljmxclient.jar;C:\Program Files\JetBrains\IntelliJ IDEA 8.1.3\lib\idea_rt.jar" com.gemalto.contactless.securearm.client.SarmProv

  • Jax-ws deployed in standalone client fails with nullpointerexception

    I have a project which has deployed successfully as a standalone client with deployed jar files wlfullclient.jar, etc. When I add the jax-ws functions that I require, the deployed client fails with a nullpointerexception that is generated from the constructor of the Service class. The project runs successfully within the JDeveloper 11.1.1.5 environment and on a weblogic 10.3 server platform, but fails when I deploy as a standalone client with the wlfullclient.jar. I'm using JDK 1.6.0_24. In testing, the error occurs when I replace the {WLHome}\server\lib\weblogic.jar entry in the classpath with the wlfullclient.jar.
    I tested from another angle by creating my jax-ws functions in a standalone deployment, and it works successfully communicates with the webservices. No additional entries on the classpath besides my deployed jar. I then added to my deployment a simple JMS context lookup:
    Hashtable ht = new Hashtable();
    ht.put(Context.INITIAL_CONTEXT_FACTORY, contextFactoryProvider);
    ht.put(Context.PROVIDER_URL, urlString);
    Context context = new InitialContext(ht);
    This test runs without error in the JDeveloper environment. As soon as I add the wlfullclient.jar in the standalone environment, I get the following exception:
    Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/xml/ws/spi/ProviderImpl
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:614)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
    at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
    at javax.xml.ws.spi.FactoryFinder.safeLoadClass(FactoryFinder.java:150)
    at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:30)
    at javax.xml.ws.spi.FactoryFinder.find(FactoryFinder.java:90)
    at javax.xml.ws.spi.Provider.provider(Provider.java:83)
    at javax.xml.ws.Service.<init>(Service.java:56)
    Interestingly, there is a class com/sun/xml/internal/ws.spi/ProviderImpl in the {JAVA_HOME}/jre/lib/rt.jar file, and I suppose this is what is used by the jax-ws classes when the wlfullclient.jar is not present on the classpath.
    So, what is it that I am missing in how to get the jax-ws classes and the jms classes to work in the standalone deployment environment (outside of the JDeveloper environment).
    Edited by: user3653687 on Jan 9, 2012 1:38 PM
    Edited by: user3653687 on Jan 9, 2012 2:49 PM

    Here is how I solved this problem to execute the application from a jar file (using Oracle Fusion Middleware 11.1.1.5.0 distribution). The key seems to be to extract the contents of the wseeclient.zip file into the same directory as the wlfullclient.jar and ws.api_1.1.0.0.jar files and then ensure that these 2 jars are on the classpath.
    In JDeveloper, create a project that has the jms/jax-ws classes.
    Put the following text entries to form the classpath (along with other dependent jars, e.g. org.eclipse.persistence...) into a file which will be included in the manifest for the client jar. Be sure to separate entries with a space.
    lib/wlfullclient.jar lib/wseeclient.jar lib\ws.api_1.1.0.0.jar lib\org.eclipse.persistence_1.1.0.0_2-1.jar
    In the Edit Deployment Profile Properties, select Include Manifest File, specify the main class to execute, and Add the classpath file to be included in the manifest.
    Deploy the jar file.
    In a deployment area, create the directory that will contain all the classpath jars (e.g. ./lib).
    Within the directory ./lib, extract all files from wseeclient.zip (found in {weblogic home}/server/lib)
    Copy wlfullclient.jar into the directory ./lib from the {weblogic home}/server/lib
    Copy ws.api_1.1.0.0.jar into the directory ./lib from {oracle middleware home}modules
    Copy org.eclipse.persistence_1.1.0.0_2-1.jar (for jaxb support) itno the directory ./lib from {oracle middleware home}/modules
    Copy the deployed client jar to the deployment area and execute, e.g.:
    java -jar ClientTest.jar myArguments

  • How to create a JMS standalone client with SAS PE8.2 ?

    HI everyone,
    I use Creator2.1 and I want to write a JMS standalone client that communicate through JMS with a webapp built with Creator.
    My pb is that I dont know how to set up initialContext.
    Hashtable env=new Hashtable();
    env.put(Context.PROVIDER_URL, "mq://localhost:28676/jms");
    env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.enterprise.naming.SerialInitContextFactory");
    context = new InitialContext(env);
    factory = (TopicConnectionFactory) context.lookup(factoryName);
    For example this code doesnt work and I have the following exception when I try to run my client.
    29 sept. 2006 10:31:03 com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
    ATTENTION: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: localhost; port: 3700"
    org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
    at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2257)
    at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2278)
    at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:208)
    at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:221)
    at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:104)
    at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:152)
    at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:146)
    at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:286)
    at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
    at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
    at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:89)
    at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:128)
    at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:288)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at com.orange.clara.Main.main(Main.java:59)
    Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused: connect
    at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:336)
    at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:191)
    ... 12 more
    Caused by: java.net.ConnectException: Connection refused: connect
    at sun.nio.ch.Net.connect(Native Method)
    at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:464)
    at java.nio.channels.SocketChannel.open(SocketChannel.java:146)
    at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:320)
    ... 13 more
    Does anyone had already met this pb ?
    Regards
    R�gis

    Please refer to http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6377822, particularly the evaluation. Could your situation be the same too (i.e server ip address changing dynamically)? Also, which OS are you using and do you have any firewalls setup that prevents access to port 3700?

  • Oracle Workflow Builder Client Installation Error

    Hi,
    I am trying to install Oracle Workflow Builder Client 2.6.3.5.
    After starting the installation I am getting error as cannot create C:\Documents....\oui\Autorun.inf followed by Java Virtual Machine Launcher Window saying Fatal exception occured. program will exit.
    Please help me.
    Thanks,
    Aditya
    Edited by: Adit102 on Sep 5, 2012 9:58 AM

    I have not seen this one .... Ensure that the install directory as well as any init directory use the conventional/old 8 character name, like D:\Work\Oracle. No spaces. I say so because it is suspicious that the error refers to C:\Documents....\
    Hope this helps,
    Alejandro
    Edited by: Alejandro Sosa on Sep 5, 2012 6:29 AM

  • How to lookup EJBs deployed in OC4J from a standalone client application

    Hello all,
    I am trying to lookup an EJB deployed in OC4J 10.1.3 from a standalone client application using the following code:
    Hashtable env = new Hashtable();
    env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
    env.put(Context.PROVIDER_URL, "ormi://localhost:23791");
    env.put(Context.SECURITY_PRINCIPAL, "jazn.com/test");
    env.put(Context.SECURITY_CREDENTIALS, "test");
    Context context = new InitialContext(env);
    Object ref = context.lookup("ejb/Dispatch");
    I get the following error:
    javax.naming.NameNotFoundException: ejb/Dispatch not found
         at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:51)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
    For the lookup string I've also tried:
    "java:comp/env/ejb/Dispatch" and "Dispatch"
    For the Context.PROVIDER_URL property I've also tried:
    opmn:ormi://localhost:6003:instance
    The result is always the same.
    I appreciate if someone could help me with this?
    Thanks,
    Georgi

    Georgi,
    Your question has been discussed many times on this forum. Search the forum archives for "RMIInitialContextFactory".
    The PROVIDER_URL needs to include the name of the deployed application that your EJB is part of, for example:
    env.put(Context.PROVIDER_URL, "ormi://localhost:23791/MyApp");The lookup name has to be the value of the "ejb-name" element in your "ejb-jar.xml" descriptor file.
    Your SECURITY_PRINCIPAL value looks strange to me. Personally, I use "principals" (and not JAZN), so I modified the "application.xml" file (in the "j2ee/home/config" subdirectory) to use "principals". Look for the following comment in that file:
    &lt;!-- Comment out the jazn element to use principals.
          When both jazn and principals are present jazn is used  --&gt;Good Luck,
    Avi.
    Message was edited by:
    Avi Abrami

  • Access java:comp/env from standalone client

    Hi,
    I am using the j2ee applicationserver from Sun.
    I want to access the java:comp/env namespace from a standalone client. When I try to do this I get the following excepton:
    javax.naming.NamingException: java:comp/env namespace is only available from within a J2EE component
    How do I get around this?
    Is it possible?
    Regards
    /Stefan

    Thanks a lot for giving me an answer Bart,
    here is another question if you have the time.
    Since it is not possible to access the the java:comp/env namesapce from a standalone client, how do I access for example a "TopicConnectionFactory" from within a J2EE application when the TopicConnectionFactory is NOT in the java:comp/env namesapce?
    I have made this work but I get a warning like this:
    Warning : Illegal connection factory access to TopicConnectionFactory. J2EE Components should access JMS Connection Factories through a resource-ref in java:comp/env
    If this isn't possible either, then how should I use for example JMS with EJB to send messages to a standalone client?
    Regards
    Stefan

  • Standalone client

    Hi all,
    I'm triying to access an EJB from a JAVA standalone client, but
    where can I know how is the JNDI tree?
    Is the LDAP port the JNDI port?
    Thanks
    Jose R. Diaz

    Hi,
    The JNDI name would be "ejb/<EJB NAME>".
    Please clarify, what did you ask by "Is the LDAP port the JNDI port?"
    Thanks.
    Deepak
    Hi all,
    I'm triying to access an EJB from a JAVA standalone client, but
    where can I know how is the JNDI tree?
    Is the LDAP port the JNDI port?
    Thanks
    Jose R. Diaz

  • Classpath for JMS standalone client

    Hi,
    I observed some problem, when I try to start my JMS client application. If in classpath is oc4j.jar it works, but when I replace oc4j.jar with oc4jclient.jar doesn't
    I notice the message:
    Exception in thread "main" java.lang.NoClassDefFoundError: com/evermind/server/jms/EvermindXAConnectionFactory
    at com.evermind.server.jms.ConnectInfo.getPass(ConnectInfo.java:98)
    at com.evermind.server.jms.EvermindTopicConnectionFactory.createTopicCon
    nection(EvermindTopicConnectionFactory.java:83)
    at sapconnector.MaterialMoverClient.main(MaterialMoverClient.java:52)
    the line no. 52 exactly means:
    TopicConnection connection = factory.createTopicConnection();
    What the OC4J client jar (oc4jclient.jar) is not enough for starting JMS standalone client?
    regards
    Krzysztof

    Hi, thanks for the reply.
    Well, I figured out that problem. It was my jar file. One of the jar file, which is imqjmsra.jar wasn't really the right one and that was giving me the problem. Well, at least that is working not, but I am having new problems.
    Right, I have been trying to make this work for about three days now. The truth is that my standalone JMS does work, when it is running on the same machine where the J2EE Server is located, but I am trying to make my JMS standalone client to connect to J2EE server from different location. Now I am getting connection refused error. Well, I guess I will be keep trying util I get this working.

  • GlassFish v3, EJB 3.1 and Standalone Client

    hi team.
    I'm very glad releasing javaee 6.
    I download netbeans 6.8 with GlassFish v3 and try to write simple ejb 3.1 application.
    ejb module deployed successfully without any problem, after this I've created new simple java application and try to call ejb 3.1 session bean.
    but no success.
    can anybody show me sample code how to call ejb 3.1 from standalone client ??
    I was working with ejb 3.0 and jboss. I had not any problem from standalone client.
    ejb 3.0 standalone client for jboss:
    Properties env = new Properties();
    env.setProperty("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
    env.setProperty("java.naming.provider.url", "localhost:1099");
    env.setProperty("java.naming.factory.url.pkgs", "org.jboss.naming");
    InitialContext ctx = new InitialContext(env);
    SomeSessionInt sBean = (SomeSessionInt)ctx.lookup("SomeSessionBean/remote");can anybody tell me which client jars are required for client application and what is the environment properties should i set ?
    PS.
    Also i tried to make enterprise application with ejb and web module into netbeans. but there wasn't any problem to inject ejb session bean from jsf managed bean. problem is how to lookup ejb from standalone client.
    any ideas will be appreciated.
    Regards,
    Paata Lominadze.

    also i can post my full example with error stacktrace.
    1.session bean (interface not required , as we know from spec.)
    public class MySessBean {
        public String sayHello(String name) throws Exception {
            System.out.println("Method initialized.");
            return "Hello : " + name;
    }2.Standalone java client
    public class Main {
        public static void main(String[] args) {
            try {
                Properties jndiProps = new Properties();
                jndiProps.put("java.naming.factory.initial", "com.sun.enterprise.naming.impl.SerialInitContextFactory");
                jndiProps.put("java.naming.factory.url.pkgs", "com.sun.enterprise.naming");
                jndiProps.put("java.naming.factory.state", "com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl");
                jndiProps.setProperty("org.omg.CORBA.ORBInitialHost", "127.0.0.1");
                jndiProps.setProperty("org.omg.CORBA.ORBInitialPort", "3700");
                Context ctx = new InitialContext(jndiProps);
                System.out.println(ctx.lookup("java:global/MyEJBModule/MySessionBean"));
                MySessionBean mySessionBean = (MySessionBean)ctx.lookup("java:global/MyEJBModule/MySessionBean");
                mySessionBean.sayHello("Paata");
            } catch (Exception e) {
                e.printStackTrace();
    }3. error stacktrace on server side:
    WARNING: "IOP00100006: (BAD_PARAM) Class com.magti.billing.ejb.__EJB31_Generated__MySessionBean__Intf____Bean__ is not Serializable"
    org.omg.CORBA.BAD_PARAM:   vmcid: OMG  minor code: 6 completed: Maybe
            at com.sun.corba.ee.impl.logging.OMGSystemException.notSerializable(OMGSystemException.java:990)4.client side error stacktrace:
    Dec 14, 2009 9:15:13 AM com.sun.enterprise.transaction.JavaEETransactionManagerSimplified initDelegates
    INFO: Using com.sun.enterprise.transaction.jts.JavaEETransactionManagerJTSDelegate as the delegate
    Dec 14, 2009 9:15:18 AM com.sun.enterprise.naming.impl.SerialContext lookup
    SEVERE: enterprise_naming.serialctx_communication_exception
    Dec 14, 2009 9:15:18 AM com.sun.enterprise.naming.impl.SerialContext lookup
    SEVERE:
    java.rmi.MarshalException: CORBA BAD_PARAM 1330446342 Maybe; nested exception is:
            java.io.NotSerializableException: ----------BEGIN server-side stack trace----------
    org.omg.CORBA.BAD_PARAM:   vmcid: OMG  minor code: 6 completed: Maybe
            at com.sun.corba.ee.impl.logging.OMGSystemException.notSerializable(OMGSystemException.java:990)
            at com.sun.corba.ee.impl.logging.OMGSystemException.notSerializable(OMGSystemException.java:1005)
            at com.sun.corba.ee.impl.orbutil.ORBUtility.throwNotSerializableForCorba(ORBUtility.java:753)
            at com.sun.corba.ee.impl.javax.rmi.CORBA.Util.writeAny(Util.java:370)_____________________________
    Regards,
    Paata Lominadze.

  • Getting Sun ONE Initial Context from standalone client

    Hi,
    I'm having problems connecting to Sun One's JNDI from a standalone client ... I've seen other topics raised with similar problems but with no real answers.
    I can connect to what i think is a different JNDI resource with:
    Hashtable env = new Hashtable();
    env.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY,           "com.sun.jndi.cosnaming.CNCtxFactory");
    env.put("java.naming.provider.url", "iiop://localhost:3700");
    jndiContext = new InitialContext(env);
    But this JNDI does not hold my JMS resources (connection factories, queues, etc) ??? Am i connecting to the wrong port??
    I've tried to look at the documentation but with no success.
    Any ideas?
    cheers,
    Chico.

    Where did you get port 58058 from?
    When trying to run:
    java -Dorg.omg.CORBA.ORBInitialHost=localhost -Dorg.omg.CORBA.ORBInitialPort=58058 SimpleJNDITest
    I got this exception:
    Exception in thread "main" javax.naming.CommunicationException: Cannot connect to ORB.
    Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
    This is my JNDI Test source:
    import javax.jms.*;
    import javax.naming.*;
    import java.util.*;
    import org.omg.CORBA.ORB;
    public class SimpleJNDITest {
    public static void main(String[] args) throws Exception {
              SimpleJNDITest t = new SimpleJNDITest();
              t.runTest();
         public void runTest() throws Exception {
              //Invoking -> java -Dorg.omg.CORBA.ORBInitialHost=localhost -Dorg.omg.CORBA.ORBInitialPort=58058 SimpleJNDITest
              // Results in the exception
              // Exception in thread "main" javax.naming.CommunicationException: Cannot connect to ORB.
              // Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
              Context jndiContext = new InitialContext();
    // -----> Alternative 1
              // This gets the JNDI Context, but the JNDI context does not hold JMS resources
              Hashtable env = new Hashtable();
         env.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
         env.put("java.naming.provider.url", "iiop://localhost:3700");
              Context jndiContext = new InitialContext(env);
    // -----> Alternative 2
              // This gets the JNDI Context, but the JNDI context does not hold JMS resources
              String[] orbArgs = {"-ORBInitialPort", "3700", "-ORBInitialHost", "localhost"};
              ORB orb = ORB.init(orbArgs, null);
              Hashtable env = new Hashtable();
         env.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
              env.put("java.naming.corba.orb", orb );
              Context jndiContext = new InitialContext(env);
    // -----> Alternative 3
              /* This gets the following exception:
              Exception in thread "main" javax.naming.CommunicationException: Cannot connect to ORB.
              Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code:     201 completed: No
              String[] orbArgs = {"-ORBInitialPort", "58058", "-ORBInitialHost", "localhost"};
              ORB orb = ORB.init(orbArgs, null);
              Hashtable env = new Hashtable();
         env.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
              env.put("java.naming.corba.orb", orb );
              Context jndiContext = new InitialContext(env);
              StringBuffer sb = new StringBuffer();
              list(jndiContext, sb);
              System.out.println(sb.toString());
         public void list(Context ctx,StringBuffer sb) {
              try {
                   NamingEnumeration enum = ctx.listBindings("");
                   while (enum.hasMore()) {
                        Binding binding = (Binding)enum.next();
                        Object obj = (Object)binding.getObject();
                        if (obj instanceof Context) {
                             sb.append("---> ");
                             sb.append(binding.getName());
                             sb.append(".");
                             list((Context)obj,sb);
                        } else {
                             sb.append(binding.getName()); sb.append("\n");
              } catch (NamingException e) {
                   System.out.println(e);
    Cheers,
    Chico

  • Custom Workflow Service Client

    Dear All,
    I develop custom workflow service client with simple servlet and workflow API, when i finished i deploy it in OAS. I just created simple human task in BPEL and assign it to user jcooper at defaul oc4j realm. I run the servlet but it's has trown exception when i want to create context:
    Exception not handled by the Collaxa Cube system.An unhandled exception has been thrown
    Error in authenticating and creating a workflow context for user jcooper
    exception.30501
    I just read manual i must deploy custom workflow client as child application of the hw_services application. I set it in my jdeveloper and deploy again but this time deployment is failed cause :
    Binding webapp web-module for application WorkflowUI to site default-web-site under context root WorkflowUI
    Exception: NoClassDefFoundError: null
    Operation failed with error:
    java.lang.NoClassDefFoundError
    I don't know what class is missing i already try put all required jar in lib. Just anyone can give me a solution about that?
    Or just anyone has already build custom workflow service client with workflow API + Servlet/JSF ? can i get some tips to develop custom workflow client?
    Thanks Before
    Regards,
    Yohanes W S

    Hi Yohanes,
    You'll probably have more luck checking in on the
    [url
    BPEL
    ]BPEL forum for this one.Best regards,
    John
    Thank for the advise, i will post in BPEL forum

  • 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