You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by David Blevins <da...@visi.com> on 2009/02/13 04:56:58 UTC
Fwd: Cannot instantiate class: org.openejb.client.LocalInitialContextFactory
Fantastic response.
We should throw this one into a wiki page.
-David
Begin forwarded message:
> Resent-From: <db...@visi.com>
> From: Karan Malhi <ka...@gmail.com>
> Date: February 12, 2009 7:09:06 PM PST
> To: users@openejb.apache.org
> Subject: Re: Cannot instantiate class:
> org.openejb.client.LocalInitialContextFactory
> Reply-To: users@openejb.apache.org
>
> Hi,
>
> Here is what you would need to do to make it work. Firstly, you
> would need
> to add the following jars in the root directory of your webapp --
> javaee-api.jar and openejb-client.jar (you can copy these from
> <Tomcat-install>/webapps/openejb/lib ).
> Update the Applet code as shown (notice that we are not using
> LocalInitialContextFactory here)
>
> Properties props = new Properties();
>
> props
> .put
> (Context
> .INITIAL_CONTEXT_FACTORY
> ,"org.apache.openejb.client.RemoteInitialContextFactory");
> props.put(Context.PROVIDER_URL, "
> http://127.0.0.1:8080/openejb/ejb");
> Context ctx = new InitialContext(props);
> Update the HTML as shown -- notice the archive attribute which has
> the comma
> separated list of jars needed by the applet (the version of jars on
> your
> machine might be different than mine- but that should not matter)
> <applet
> codebase = "."
> code = "qdbapplets.MyApplet.class"
> name = "TestApplet"
> width = "400"
> height = "300"
> hspace = "0"
> vspace = "0"
> align = "top"
> archive="openejb-client-3.1.1-SNAPSHOT.jar,javaee-api-5.0-1.jar"
>>
> </applet>
>
>
>
>> What is the
>>> difference between the successful JSP code and the unsuccessful java
>>> applet? I did add the openejb-core-3.1.jar to my classpath, but
>>> this
>>> didn't work. Any ideas?
>>
> JSP is running in the same VM as openejb, hence you can use
> LocalInitialContextFactory. Applet runs in a separate VM, hence it
> would
> need RemoteInitialContextFactory
>
> In order to get more information, please refer to this page --
> http://openejb.apache.org/3.0/clients.html
>
> --
> Karan Singh Malhi
Re: Cannot instantiate class: org.openejb.client.LocalInitialContextFactory
Posted by David Blevins <da...@visi.com>.
Not sure, maybe a new one called "Applet Client" or something?
-David
On Feb 12, 2009, at 8:27 PM, Karan Malhi wrote:
> Could you suggest a page on the wiki?
>
> On Thu, Feb 12, 2009 at 10:56 PM, David Blevins <david.blevins@visi.com
> >wrote:
>
>> Fantastic response.
>>
>> We should throw this one into a wiki page.
>>
>> -David
>>
>>
>> Begin forwarded message:
>>
>> Resent-From: <db...@visi.com>
>>> From: Karan Malhi <ka...@gmail.com>
>>> Date: February 12, 2009 7:09:06 PM PST
>>> To: users@openejb.apache.org
>>> Subject: Re: Cannot instantiate class:
>>> org.openejb.client.LocalInitialContextFactory
>>> Reply-To: users@openejb.apache.org
>>>
>>>
>>> Hi,
>>>
>>> Here is what you would need to do to make it work. Firstly, you
>>> would need
>>> to add the following jars in the root directory of your webapp --
>>> javaee-api.jar and openejb-client.jar (you can copy these from
>>> <Tomcat-install>/webapps/openejb/lib ).
>>> Update the Applet code as shown (notice that we are not using
>>> LocalInitialContextFactory here)
>>>
>>> Properties props = new Properties();
>>>
>>>
>>> props
>>> .put
>>> (Context
>>> .INITIAL_CONTEXT_FACTORY
>>> ,"org.apache.openejb.client.RemoteInitialContextFactory");
>>> props.put(Context.PROVIDER_URL, "
>>> http://127.0.0.1:8080/openejb/ejb");
>>> Context ctx = new InitialContext(props);
>>> Update the HTML as shown -- notice the archive attribute which has
>>> the
>>> comma
>>> separated list of jars needed by the applet (the version of jars
>>> on your
>>> machine might be different than mine- but that should not matter)
>>> <applet
>>> codebase = "."
>>> code = "qdbapplets.MyApplet.class"
>>> name = "TestApplet"
>>> width = "400"
>>> height = "300"
>>> hspace = "0"
>>> vspace = "0"
>>> align = "top"
>>> archive="openejb-client-3.1.1-SNAPSHOT.jar,javaee-api-5.0-1.jar"
>>>
>>>>
>>>> </applet>
>>>
>>>
>>>
>>> What is the
>>>>
>>>>> difference between the successful JSP code and the unsuccessful
>>>>> java
>>>>> applet? I did add the openejb-core-3.1.jar to my classpath, but
>>>>> this
>>>>> didn't work. Any ideas?
>>>>>
>>>>
>>>> JSP is running in the same VM as openejb, hence you can use
>>> LocalInitialContextFactory. Applet runs in a separate VM, hence it
>>> would
>>> need RemoteInitialContextFactory
>>>
>>> In order to get more information, please refer to this page --
>>> http://openejb.apache.org/3.0/clients.html
>>>
>>> --
>>> Karan Singh Malhi
>>>
>>
>>
>
>
> --
> Karan Singh Malhi
Re: Cannot instantiate class: org.openejb.client.LocalInitialContextFactory
Posted by Karan Malhi <ka...@gmail.com>.
Could you suggest a page on the wiki?
On Thu, Feb 12, 2009 at 10:56 PM, David Blevins <da...@visi.com>wrote:
> Fantastic response.
>
> We should throw this one into a wiki page.
>
> -David
>
>
> Begin forwarded message:
>
> Resent-From: <db...@visi.com>
>> From: Karan Malhi <ka...@gmail.com>
>> Date: February 12, 2009 7:09:06 PM PST
>> To: users@openejb.apache.org
>> Subject: Re: Cannot instantiate class:
>> org.openejb.client.LocalInitialContextFactory
>> Reply-To: users@openejb.apache.org
>>
>>
>> Hi,
>>
>> Here is what you would need to do to make it work. Firstly, you would need
>> to add the following jars in the root directory of your webapp --
>> javaee-api.jar and openejb-client.jar (you can copy these from
>> <Tomcat-install>/webapps/openejb/lib ).
>> Update the Applet code as shown (notice that we are not using
>> LocalInitialContextFactory here)
>>
>> Properties props = new Properties();
>>
>>
>> props.put(Context.INITIAL_CONTEXT_FACTORY,"org.apache.openejb.client.RemoteInitialContextFactory");
>> props.put(Context.PROVIDER_URL, "
>> http://127.0.0.1:8080/openejb/ejb");
>> Context ctx = new InitialContext(props);
>> Update the HTML as shown -- notice the archive attribute which has the
>> comma
>> separated list of jars needed by the applet (the version of jars on your
>> machine might be different than mine- but that should not matter)
>> <applet
>> codebase = "."
>> code = "qdbapplets.MyApplet.class"
>> name = "TestApplet"
>> width = "400"
>> height = "300"
>> hspace = "0"
>> vspace = "0"
>> align = "top"
>> archive="openejb-client-3.1.1-SNAPSHOT.jar,javaee-api-5.0-1.jar"
>>
>>>
>>> </applet>
>>
>>
>>
>> What is the
>>>
>>>> difference between the successful JSP code and the unsuccessful java
>>>> applet? I did add the openejb-core-3.1.jar to my classpath, but this
>>>> didn't work. Any ideas?
>>>>
>>>
>>> JSP is running in the same VM as openejb, hence you can use
>> LocalInitialContextFactory. Applet runs in a separate VM, hence it would
>> need RemoteInitialContextFactory
>>
>> In order to get more information, please refer to this page --
>> http://openejb.apache.org/3.0/clients.html
>>
>> --
>> Karan Singh Malhi
>>
>
>
--
Karan Singh Malhi