Local Interfaces Support in 9.0.2 Release 2?

Does Oracle9iAS 9.0.2 Release 2 support Local Interfaces? The reference I found is as follows:
from http://otn.oracle.com/tech/java/oc4j/htdocs/oc4j-how-to.html:
Please note that some of the How-To's only work with later versions of Oracle9iAS Containers for J2EE. For example Oracle9iAS Containers for J2EE (9.0.2) does not support some aspects of the EJB 2.0 specification, so the Local Interfaces How-To will not work on version 9.0.3. However, do not take the list below as as a list of what features are supported in what version of Oracle9iAS Containers for J2EE. This is simply a list of which How-To has been built and tested with which version of Oracle9iAS Containers for J2EE.
I assume first of all that they really mean to state "so the Local Interfaces How-To will not work on version 9.0.2". But the next sentence states that I should not use this list to show which features are supported and which are not. Does anyone have a definitive answer as this portion of the Oracle website does not seem to provide one?
Thanks in advance as always!!!

Never mind. Sorry for wastin' all your time. Further searching has verified that there is no support for local interfaces in Oracle 9iAS 9.0.2 Release 2.

Similar Messages

RPC web service session beans and local interfaces

I am wondering if it is possible to use EJB 2.0's local
interface (vs remote interface) with 6.1's RPC web service
session beans. Since WLS generates the SOAP servlet that
invokes the RPC session bean and I do not find
a way to some how tell SOAP servlet to use local interface to
get the session bean's local home interface, I am not sure
this can be done.
Any comments would be appreciated.
Thanks.
Peter

Ta. Thanks for the info.
Any idea when Local I/F support is due?
-Nick
"Neal Yin" <[email protected]> wrote:
>
"Nick Minutello" <[email protected]>
wrote
in message news:3d4413a4$[email protected]..
I was just about to post the very same question - but for WLS 7.0.0.1.
There are essentially two questions:
1) (from a functional perspective)
Can I expose Local Interfaces as SOAP using the auto-generation(servicegen ant
tasks)?Local Interfaces support is coming.
2) (from a performance perspective)
Does the generated SOAP implementation go via the (expensive) RemoteInterface
(ie marshalling) - or is the RMI marshalling optimised out (by setting<enable-call-by-reference>true</>)?
You can set this option by yourself on your EJB. Web service runtime
doesn't
do any magic in this area.
Regards,
Nick
"Peter" <[email protected]> wrote:
I am wondering if it is possible to use EJB 2.0's local
interface (vs remote interface) with 6.1's RPC web service
session beans. Since WLS generates the SOAP servlet that
invokes the RPC session bean and I do not find
a way to some how tell SOAP servlet to use local interface to
get the session bean's local home interface, I am not sure
this can be done.
Any comments would be appreciated.
Thanks.
Peter

Does JDev 9.0.3 support EJB Local Interfaces?

Hi everyone, we are very interested in using local interfaces for our EJB's to set up and use a standard set of server beans that will run in each server. I did not see any reference to local interfaces in any of the release notes on version 9.0.3.
Does anyone know? And if not, does anyone know when they might be supported?
TIA for any responses.

Yes. Local interfaces for EJBs are supported.

Creating local interfaces with JDeveloper (release 2)

Hi
Maybe I'm missing something here, but how does one create a local- and a local-home interface with JDeveloper? It only seems to give me the option to create a remote- and a home interface.
I've tried creating the local interfaces by hand and then adding them as <ejb-local-ref> references in the ejb-jar.xml deployment descriptor, but I get the message "local/local-home tag not supported in this version" when trying to test the code with the Embedded OC4J Server.
Now, I've managed to create EJB 2.0-style CMP entity beans by modifying the code and deployment descriptors a little, which made me believe that EJB 2.0 is supported, but that seems to be where it stops.
Am I doing something wrong, or is EJB 2.0 not fully implemented in the Embedded OC4J Server yet?
Hope you can help
Christof

JDeveloper 9.0.2 doesn't have support for local interfaces or any EJB 2.0 features.
Next release of JDeveloper (9.0.3) will have complete support of J2EE 1.3 features including EJB 2.0.
This release is slated for this summer (2002)
raghu
JDev Team

Does OAS9i(oc4j) support EJB Local interface?

Hi, I'm trying to use the petstore 1.3 framework on oc4j. I read the documentation, and know that it supports EJB 2. But I find the ejb local interface isn't supported.
Am I right?

Hi Patrick,
As far as I know, OC4J only partially implements EJB 2.0 -- it
doesn't implement local interfaces. However, there are several,
different versions available. Which version are you using?
If you haven't already found it, there is a version of the pet
store application available for download from:
http://technet.oracle.com/sample_code/tech/java/oc4j/content.html
but it's an implementation of the 1.1.2 version.
Hope this helps,
Avi.

Using local interfaces for EJB (session bean)

Hi,
I�ve a question regarding when to use the Local interfaces(EJBLocal and EJBLocalHome) of a enterprise bean. I understand that calls to enterprise bean can be made locally if the client which is invoking is in the same JVM as that of EJB. I�ve written a web client (servlet) which is packaged in a EAR and this servlet is trying to invoke a session bean which is in a �different� EAR using local interfaces. Both the EARs have been deployed in a single server (websphere 6.0 server). It didn�t work for me this way�..If I package the servlet in the same EAR of session bean then it works fine.
So is this to say that both EARs are not running on the same JVM? Or should it work even if the client and the session bean are in different EARs but in same server?
Can anyone explain me the fundamentals behind this.
Thanks in advance

Local access is only portable within the same .ear. For example, the Java EE SDK and SUN's
application servers have never supported local EJB access from a web/EJB component in a different
.ear. One issue is that local access requires that both the caller and target EJB have the same
classloader. By definition, different Java EE applications have distinct classloaders. In addition,
in Java EE 5 persistence context propagation does not span applications, so it wouldn't work in the
local case.
--ken

Local Data AddressDoes not belong to any of this hosts local interfaces

I'm facing this error when I try to run the Applet from a client that download the applet and try to connect to de ip address of the origin.
When I run localy, there is no error!
Example: On 10.1.0.2, I browse 10.1.0.1/transmitapplet.html, and the error:Local Data AddressDoes not belong to any of this hosts local interfaces occurs.
On 10.1.0.1, I browse 10.1.0.1/transmitapplet.html and the applet run properly.
Anybody knows what is the problem?

Sorry, but I hadn't have this problem till last week. Then I tried out to run my Application as Applet...
The problem is, that a applet is not allowed to read the local IP-Address. I've solved this a little bit strange, by using a dummy SessionManager:
public String getLocalAddress() {
String result = null;
SessionAddress addr = null;
RTPSessionMgr mngrSession = (RTPSessionMgr) RTPManager.newInstance();
if (mngrSession != null) {
SessionAddress sessAddr = new SessionAddress();
// empty address will use standard IP
try {
mngrSession.initialize(sessAddr);
addr = mngrSession.getLocalSessionAddress();
catch (InvalidSessionAddressException e1) {}
if (addr != null) {
result = addr.getDataHostAddress();
mngrSession.closeSession();
mngrSession.dispose();
return result;
else return null;
This method does not support multiple IP-addresses.

EJB Local Interfaces

My understanding is that the concept of local interfaces (i.e.
direct invocation in lieu of an IPC) exist in EJB 2.0. Does
OC4J support this today? If not, will there be support for it
in 9i AS 2.0?
Thanks.

oc4j/orion supports ejb 2.0 as it stood in the second draft.
There have been many changes since then, including dropping DO's
and using Local Interfaces instead.
OC4J/Orion will have a new version by the end of this year or
early next year which will implement ejb 2.0.
Until then, if you want the speed you would get with local
interfaces in oc4j/orion, you can modify your orion-ejb-jar.xml
to use copy-by-value="false". This will give you the same
performance gain as using local interfaces. Its a hack, but what
the heck, it works.
Regards,
the elephantwalker
www.elephantwalker.com

Cmp2.0 /local interface

Hi! I'm trying to deploy the wrox ch16 sample on cmp2.0 and local interfaces and got the following error:
java.lang.InstantiationException: local/local-home tag not supported in this version
Does OC4J ver 9.0.2 supports the new cmp2/cmr and local interfaces?
Thanks.

Pedro -- Local interfaces were not available in v902 but they are available in the OC4J v903 Developer Preview. You can download this from OTN. Please start at http://otn.oracle.com/tech/java/oc4j/content_preview.html to find the download as well as updated documentation and more data about the J2EE compliant version of OC4J.
Thanks -- Jeff

Lookup for local interfaces.

Isn't lookup for local interfaces allowed from web client. I have defined a
ejb-reference for the bean in my web.xml. When I do a lookup as
TestBeanLocalHome home = (TestBeanLocalHome)
ic.lookup("java:comp/env/ejb/TestBeanLocal");
This statement result in an error
javax.naming.NameNotFoundException: Unable to resolve
comp/env/ejb/TestSLSBeanLocal/ Resolved: 'comp/env/ejb'
Unresolved:'TestBeanLocal' ; remaining name ''
at
weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingN
ode.java:887)
at
weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:219)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:183)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:191)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:191)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:191)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:339)
at
weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWr
apper.java:36)
at
weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:124
at javax.naming.InitialContext.lookup(InitialContext.java:345)
at jsp_servlet.__client._jspService(__client.java:108)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:2495)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
The same thing works when lookup is done for remote interface.
Regards,
Rupesh.

You need to use "ejb-local-ref" to refer to local interfaces. I meant
"ejb-local-ref" element was not available in web.xml in Servlet 2.2. They
were added in Servlet 2.3 specification. So unless your app server is
Servlet 2.3 compliant it does not need to support references to local
interfaces in web components (servlets or jsps). Weblogic 6.1 did not seem
to support them last time I tried.
-- Anand
"Rupesh" <[email protected]> wrote in message
news:[email protected]...
what do u mean by local interface in web component? its ejb's local
interfaces and lookups are any way being
done using ejb-ref and ref mapping are given in weblogic.xml.
Where does Servlet spec come into the picture?
Do you mean to say that you can not lookup for local home from a jsp in
WL6.1?
Regards,
Rupesh.
Anand Byrappagari <[email protected]> wrote in message
news:[email protected]...
Are you using Weblogic 6.1? Then local interfaces in web components arenot
supported. Local interfaces were added only in Servlet 2.3 I think.Weblogic
6.1 is not completely compliant with Servlet 2.3.
-- Anand
"Rupesh" <[email protected]> wrote in message
news:[email protected]...
Isn't lookup for local interfaces allowed from web client. I have
defined
a
ejb-reference for the bean in my web.xml. When I do a lookup as
TestBeanLocalHome home = (TestBeanLocalHome)
ic.lookup("java:comp/env/ejb/TestBeanLocal");
This statement result in an error
javax.naming.NameNotFoundException: Unable to resolve
comp/env/ejb/TestSLSBeanLocal/ Resolved: 'comp/env/ejb'
Unresolved:'TestBeanLocal' ; remaining name ''
at
weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingN
ode.java:887)
at
weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:219)
atweblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:183)
atweblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:191)
atweblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:191)
atweblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:191)
atweblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:339)
at
weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWr
apper.java:36)
at
weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:124
at javax.naming.InitialContext.lookup(InitialContext.java:345)
at jsp_servlet.__client._jspService(__client.java:108)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:2495)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
The same thing works when lookup is done for remote interface.
Regards,
Rupesh.

Deploying entity beans with Local interfaces on Jboss

Hi, I'm trying to deploying a simple entity bean on Jboss. The EJB has been developed with Local Interfaces because then I want to access it with a session bean facade.
I get the following error:

23:41:25,984 WARN [verifier] EJB spec violation:
Bean : UsersEJB
Section: 9.2.2
Warning: The entity bean class must not be defined as abstract.
23:41:25,984 WARN [verifier] EJB spec violation:
Bean : UsersEJB
Section: 9.4.7.1
Warning: The primkey-field element must name a public field in the bean implemen
tation class.

I'm following what is wrote in the Professional EJB editeb by wrox?
Is it possible to deploy an entity bean alone with Local interfaces? Is there something I'm missing? It's true that I defined the implementation class as abstract, but because there are abstract getter/setter methods.
Thanks for any help,
Marco

Greetings,
Hi, I'm trying to deploying a simple entity bean on
Jboss. The EJB has been developed with Local
23:41:25,984 WARN [verifier] EJB spec violation:
Bean : UsersEJB
Section: 9.2.2
Warning: The entity bean class must not be defined as abstract.
23:41:25,984 WARN [verifier] EJB spec violation:
Bean : UsersEJB
Section: 9.4.7.1
Warning: The primkey-field element must name a public field in
the bean implementation class.What version of JBoss are you using? These errors indicate container compliance with EJB spec 1.1, not 2.0 to which your CMP beans are written. Download the latest JBoss release version - 3.2.1 - and you should not see this problem.
Is it possible to deploy an entity bean alone with
Local interfaces? Is there something I'm missing? It'sYes it is (no, you are not "missing something" ;). In fact, this is recommended practice in most cases under CMP 2.0 - CMR having been a major impetus to the development of Local interfaces in the specification. ;)
true that I defined the implementation class as
abstract, but because there are abstract getter/setter
methods.No problems. You are "right on track" for CMP 2.0. :)
Thanks for any help,
MarcoRegards,
Tony "Vee Schade" Cook

Accessing Local Interface EJB from Web Container Oracle App Server 9.0.4

Hi,
I am developing a struts based small application, which calls a EJB which uses Local Interface from Struts ActionClass.
I am getting NameNotFoundException. The exact exception is s mentioned below.
05/03/29 16:15:49 javax.naming.NameNotFoundException: LoginRSL not found
The deployment descriptors are as mentioned below.
=============
ejb-jar.xml
<?xml version = '1.0' encoding = 'windows-1252'?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<session>
<description>Session Bean ( Stateless )</description>
<display-name>LoginRSL</display-name>
<ejb-name>LoginRSL</ejb-name>
<local-home>loginApp.model.LoginRHome</local-home>
<local>loginApp.model.LoginL</local>
<ejb-class>loginApp.model.LoginRSL</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<relationships/>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>LoginRSL</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
orion-ejb-jar.xml
<?xml version = '1.0' encoding = 'windows-1252'?>
<!DOCTYPE orion-ejb-jar PUBLIC "-//Evermind//DTD Enterprise JavaBeans 1.1 runtime//EN" "http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd">
<orion-ejb-jar>
<enterprise-beans>
<session-deployment name="LoginRSL"/>
</enterprise-beans>
</orion-ejb-jar>
I also tried adding following code to web.xml
web.xml
<ejb-local-ref>
<ejb-ref-name>LoginRSL</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>LoginRHome</local-home>
<local>LoginL</local>
<ejb-link>LoginRSL</ejb-link>
</ejb-local-ref>
It is quite evident that it is not able to lookup the JNDI name.
Can someone throw light on this? If someone has working sample of this, can you mail it to [email protected]?

Nipun,
WebLogic and OC4J are not the same thing. That's like saying Oracle and SQL Server are the same thing -- or C++ and Java are the same thing.
I recall a posting to a forum (don't remember if it was this one), where the poster was complaining that some feature of the application server he had previously used, was not supported by OC4J. Turned out that the feature he was referring to, contradicted the J2EE specification -- which is why it wasn't available in OC4J. In other words, he didn't like the fact that OC4J was more compliant with the J2EE specification than his "other" application server. Go figure!
So, if you haven't already done so, I suggest you verify that this feature of WebLogic is something that complies with the J2EE specifications -- before expecting OC4J to support the same feature.
And if it's not clear, from the specifications, then every vendor is free to implement this feature (or not).
So if it turns out that WebLogic is a more appropriate application server for you -- then why not just stick with it (and forget the others)?
Good Luck,
Avi.

Remote and local interface on same ejb 3.0 bean instance

Hi,
Is it posible to get remote and local interface on same ejb 3.0 bean instance.
For example get local interface of a bean and than pass it as remote to client.
Both interfaces must operate on same bean instance.
Thanks
Zlaja

yes. You can implement multiple interfaces on a single class, so you can add a local and a remote interface. One trick to avoid duplicate code is to simply make the remote interface extend the local interface; then you only have to add the @Remote annotation and you're done.
For example get local interface of a bean and than pass it as remote to client.You don't pass an instances to a client, a client looks up a remote instance of the bean through JNDI.

Weblogic 10.3.2 EJB3 Local Interface in POJO/Helper classes

Hi,
I have a jar file containing all EJB's in application & some Helper classes. I want to access Local interfaces of EJBs in those helper classes. Is there any way I can do it? I've gone through Maxence Button & Jay SenSharma 's blogs about accessing Local interface. but it doesn't help. May be these two guys can help me more here.. My requirement is very simple. Just to access local interface in POJO/Helper classes that are in same JAR file as EJB's. I can't get reference with @EJB class level annotation as Helper classes are called independently from MBean services.. not from any EJB or Servlert.
Please if anyone can tell me how do I get reference of local interfaces, that would be really good.
my environment is
Weblogic 10.3.2
EJB3
Regards,
Prasad

Hi,
Just check ...If you want something like mentioned in the below Link with a complete Example:
[http://jaysensharma.wordpress.com/2009/08/16/weblogic-10-3-ejb3-local-lookup-sample/|http://jaysensharma.wordpress.com/2009/08/16/weblogic-10-3-ejb3-local-lookup-sample/]
Regards
Jay SenSharma

Group Policy Management | No such interface supported

Running Windows Server 2008 R2 as a Domain Controller and when I open Group Policy Management, click on a GPO, then click on the Settings tab, it pops up an error message that says "No such interface supported". I've found several articles
that talk about registering .dll files and I've done that and nothing. I've uninstalled GPMC and reinstalled and that didn't fix anything. Can anyone help resolve this?

Hi Jason,
Before going further, do we have other domain controllers? If yes, does GPMC work correctly on these domain controller? GPMC reports the error "No Such interface supported" normally is due to a missing or corrupted Windows component.
Besides, do we update the server to the latest? If not, we can update the server to the latest and then reinstall the GPMC to see if the issue persists.
TechNet Subscriber Support
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Best regards
Frank Shen

Local Interfaces Support in 9.0.2 Release 2?

Similar Messages

Maybe you are looking for