CORBA Name for EJB

I'm trying to use an EJB from a C++ CORBA client.
The JNDI Name is ejb.SumSessionRemoteHome.
I cannot resolve this name with my C++ client (Orbacus 4.2). When I use a "lsns" utility I don't see "ejb.SumSessionRemoteHome". I do see things like this: SecondApplicationSumProject_jarSumSession_EO.
Is there something special I need to do to bootstrap the name into the naming service? The EJB tests fine with a WebService Project Test .jws.
Thanks
Russ

Russell Krayer <[email protected]> writes:
I'm trying to use an EJB from a C++ CORBA client.
The JNDI Name is ejb.SumSessionRemoteHome.
I cannot resolve this name with my C++ client(Orbacus 4.2). When I use a "lsns" utility I don't
see "ejb.SumSessionRemoteHome". I do see things like
this: SecondApplicationSumProject_jarSumSession_EO.
Is there something special I need to do tobootstrap the name into the naming service? The EJB
tests fine with a WebService Project Test .jws.
The name should be the same as that which you used to
deploy. Do you
see the ejb context? "." is interpreted as a contet
separator.
andy
-- Yes, I see an ejb context and a weblogic context. But, I was able to finally get "ejb.SumSessionRemoteHome" to resolve after discovering a coding error on my part. I resolved the name and invoked methods on my bean although I don't see that name with my lsns utility.
Thanks for the reply.
Russ

Similar Messages

Specify JNDI Name For EJB Module

Hi folks, please I need to know how I can specify the Jndi name for an ejb module I am creating in netbeans 5.0, to be accessed by a web application.
If this can be done using the sun java system application server 9 admin consle (just as for JDBC Resources), i'll also like to know how.
Thanks.

Thanks Jay. I went through the links, it seems that if you have the JNDI name set in the weblogic-ejb-jar.xml, there is no need to set the same in the weblogic admin console. I am using ejb 2.x version. Particularly if you get the WLInitialContextFactory in your code , then there is no need to set the JNDI name in the JNDI tree in weblogic admin console.
Like:-
Context ctx = null;
java.sql.Connection conn = null;
Hashtable<String,String> ht = new Hashtable<String,String>();
ht.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
ht.put(Context.PROVIDER_URL,"t3://localhost:7001");
This will take care of JNDI tree, hence there is no need to set the JNDI name explictly in the weblogic admin console.
Please correct me if i am wrong. Whether for datasource also whether we can do the same, by setting the resource-ref with datasource in the ejb-jar.xml and not set anything in weblogic admin console? Thanks.

Corba Client For EJB

Hello
I am trying to connect Corba Client to EJB deployed in OC4J.
I followed the instructions given on
http://otn.oracle.com/tech/java/oc4j/htdocs/how-to-rmi-iiop.html
But I am not getting success after making tries in different ways.
Can some body tell how to connect to EJB by a corba client using Oc4j.
If OC4J does't support RMI-IIOP , can you suggest other server which supports that.
Thanx in advance.

I'm stuck exactly with the same issue while trying to port my application from weblogic to jboss.
I tried to specify different ORB implementations (JacORB, OpenORB) for jvm option org.omg.CORBA.ORBClass, but JBoss couldn't get them instantiated. Native Sun implementation which is used in JBoss by default and can be instantiated, apparently is not fully compatible with weblogic security module.
So did you manage to find out the solution?
Edited by DigitalDude at 04/09/2008 11:47 PM

Multiple JNDI names for EJB?

If I'm deploying a webapp that references an EJB, do I have to use the same JNDI
name that is configured in the EJB descriptor?
Why can't I reference the EJB using a seperate name (as in some J2EE examples)?
Thanks,
Darren

darren <[email protected]> wrote:
If I use a new JNDI name, rather than the one defined in weblogic-ejb-jar.xml,
it does not show up in the JNDI tree.
Does the JNDI name referenced in weblogic.xml need to be the same as that defined
in weblogic-ejb-jar.xml? No. ejb-ref mechanism allows you to map an actual ejb jndi name to one used by your
application - so, in theory, system administrator can change jndi names without
touching your application code. You do not see it in the global JNDI tree because
this mapping exists only in the context of your application.
<[email protected]> wrote:
That's what ejb-ref in web.xml is for - you can create an ejb-ref in
web.xml
and map it to an actual jndi name in weblogic.xml ejb-reference-description.
Darren <[email protected]> wrote:
If I'm deploying a webapp that references an EJB, do I have to usethe same JNDI
name that is configured in the EJB descriptor?
Why can't I reference the EJB using a seperate name (as in some J2EEexamples)?
Thanks,
Darren--
Dimitri
Dimitri

The manner that JBuilder names for ejb isn't seem canon

below is JBuilder auto produce
abstract public class LockerBean implements EntityBean{
public interface LockerHome extends javax.ejb.EJBLocalHome {
........} //"LockerHome" should correct "LockerLocalHome"
public interface LockerRemote extends javax.ejb.EJBObject {
...........}//"LockerRemote"should correct "Locker"
public interface LockerRemoteHome extends javax.ejb.EJBHome {
............}//"LockerRemoteHome"should correct "LockerHome"
but book says
remote interface names:<bean-name>Home
local interface:<bean-name>LocalHome
remote bean interface:<bean-name>
local bean interface<bean-name>Local
implementation classes:<bean-name>EJB
I have never seen <bean-name>Remote and <bean-name>RemoteHome
but JBuilder can compiler and run above class! why

From a compilation perspective,
It does not matter what you call the interfaces. You could call them larry, moe and curly for the different home interfaces.
All that matters is that they are indicated properly in the descriptors and used appropriately in the code.
Of course from a readability, usablility and maintainability perspective, use appropriate names.
What JBuilder does is a standard for JBuilder. (I think specifically the release of JBuilder you have)
It need not match what is there in your book.
Vijay

Looking up JNDI names for local client

Sir,
I have been trying to look up JNDI name for the local home interface in the client program.But I got only "javax.naming.NoInitialContextException".I want information about to give a JNDI name for EJB and its details.
Thanking you.
Yours,
R K Ramesh

It sounds like you are not specifying the right URL or username/credentials to get an initial context.
A typical example would be something like this:
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
p.put(Context.PROVIDER_URL, "t3://server:port");
InitialContext ic = new InitialContext(p);
(You can also use a properties file or system prpoerties to specify these.)
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Does mapping to JNDI for ejb-refs have a performance impact?

Does mapping to JNDI names for ejb-refs have a performance impact for
WLS6.1?
In the ejb-jar.xml deployment descriptor, you can define an ejb reference as
follows:
<ejb-ref>
<ejb-ref-name>ejb/AccountHomeRemote</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<home>com.package structure.AccountHomeRemote</home>
<remote>com.package structure.AccountRemote</remote>

</ejb-ref>
Now, optionally, you can use the ejb-link element - or - you can, in the
weblogic DD, specify a JNDI name that the ejb-ref maps to.
Using a JNDI name buys you some flexibility. If, for some reason, the jar is
divided, you dont have to convert ejb-link's to JNDI names. The question is:
Is there a performance cost in doing this?
Cheers

Hi Aashish,
Thanks for your quick reply. it was helpful, but i am not using RFC's. Correct me if i am wrong, but i have explained the scenarios in detail below.
Scenario 1. Synchronous
1) PI Picks file from a common folder.
2) PI does a data mapping and sends the data to ECC.
3) ECC contains an inbound interface which receives the data and in which abap proxy code is written.
4) The abap proxy code executes a function module and sends the response as an internal table back to PI.
5) PI receives the response and places it in a text/csv file and places it back to another folder.
I assume that the above would be possible only using BPM. What i understand is that in order for an interface to receive and send data, abstract mappings are to be used, and for this BPM is required. We do not have any conversions etc. its just a simple matter of receiving an internal table from ECC and creating a file to place in the folder.
I also understand that BPM could have bottlenecks due to queue and cache issues, messages might be pending, or lost etc.
Scenario 2. Asynchronous
1) PI Picks file from a common folder.
2) PI does a data mapping and sends the data to ECC.
3) ECC contains an inbound interface which receives the data and in which abap proxy code is written.
4) ABAP Proxy code executes the same function module and calls a seperate outbound interface and passes the values to it. This would be used in sending the response back.
5) PI receives the response from the second interface and places it in a text/csv file and places it back to another folder.
I would like to know which would be the better approach. Documentation/references to support your claims would be much appreciated.
Cheers,
Mz

Options for EJB - Corba - correct?

Hi,
I'm looking at the options for EJB->CORBA and CORBA->EJB method calls in Weblogic Server 5.1 (although we may be moving to 6 soon)
We are currently using CORBA 2.1 C++ code, and are looking for a migration path into EJBs.
I've tried to pull together small list of our options, with apologies to Eduardo Ceballos who wrote most of this text originally, and anyone else who's work is included.
Does any one have the time to read the below, and make any comments on important options that I've missed, or pitfalls that they can see?
Thankyou in advance;
Notes:
-- RMI over IIOP is only available under JDK 1.3
-- if we use a pre Corba 2.3 implementation (as we currently are), only primitive types may be passed (no OBV available).
-- Another option is to use WebLogic Enterprise, but we are currently using WebLogic Server. ‘WebLogic Enterprise Connectivity gives you the ability to create IIOP connection pools to a BEA WebLogic Enterprise, allowing you to execute WebLogic Enterprise CORBA objects from WebLogic Server servlets and Enterprise JavaBeans.’
Calling from a WLS into a CORBA server:
========================================
There are several variations on two ways:
1. expose the CORBA interface;
To expose the CORBA interface, you collocate the ORB of your choice within the WLS instance and bind CORBA stubs into the JNDI tree as needed. The application looks up CORBA objects and uses the CORBA server interfaces as you would regardless of WLS.
This is an example of designing the RMI interface so that it maps in a usable way to the IDL interface.
2. hide the CORBA interface.
To hide the CORBA interface, create a RMI interface and a RMI server class; run 'weblogic.rmic -iiop -idl ...' on that class; take the resulting idl and add it to the interfaces which the CORBA servers implement. To gain access to the CORBA servers, use COSNaming to bind the CORBA servers into the WLS JNDI tree. As above, the application looks up the CORBA servers in the JNDI tree, but in this case the application uses the RMI-IIOP stubs to communicate with the CORBA servers.
This is an example of adding RMI interfaces to existing CORBA servers to establish some level of connectivity.
If you are using an RMI-IIOP implementation of some sort, then you are effectively hiding the CORBA interface, except you'd ignore any of work that would be done at the IDL level.
Note: We should use rmic and the –noValueTypes flag (as we aren’t using Orbix 2.3).
Calling from a Corba server into WLS
======================================
It is possible to host an Orb in the app server, contained within a WebLogic startup class. This will allow Corba calls to be delegated to app-server components (see option 1, above).
Thanks again.

Comments inline....
G Morgan wrote:
Hi,
I'm looking at the options for EJB->CORBA and CORBA->EJB method calls in Weblogic Server 5.1 (although we may be moving to 6 soon)Yes, move to 6.0.
>
>
We are currently using CORBA 2.1 C++ code, and are looking for a migration path into EJBs.
I've tried to pull together small list of our options, with apologies to Eduardo Ceballos who wrote most of this text originally, and anyone else who's work is included.
Does any one have the time to read the below, and make any comments on important options that I've missed, or pitfalls that they can see?
Thankyou in advance;As far as I can tell, pre-2.3 ORBs can not handle type ids that start with "RMI:". So pretty much the only option at the moment with a pre-2.3 ORB is to delegate through a colocated ORB. As with the the previous response, it's a good idea to host the ORB in a WLS client, that way if the ORB goes south, it doesn't take the server with it.
>
>
Notes:
-- RMI over IIOP is only available under JDK 1.3
-- if we use a pre Corba 2.3 implementation (as we currently are), only primitive types may be passed (no OBV available).
-- Another option is to use WebLogic Enterprise, but we are currently using WebLogic Server. ‘WebLogic Enterprise Connectivity gives you the ability to create IIOP connection pools to a BEA WebLogic Enterprise, allowing you to execute WebLogic Enterprise CORBA objects from WebLogic Server servlets and Enterprise JavaBeans.’
Calling from a WLS into a CORBA server:
========================================
There are several variations on two ways:
1. expose the CORBA interface;
To expose the CORBA interface, you collocate the ORB of your choice within the WLS instance and bind CORBA stubs into the JNDI tree as needed. The application looks up CORBA objects and uses the CORBA server interfaces as you would regardless of WLS.
This is an example of designing the RMI interface so that it maps in a usable way to the IDL interface.
2. hide the CORBA interface.
To hide the CORBA interface, create a RMI interface and a RMI server class; run 'weblogic.rmic -iiop -idl ...' on that class; take the resulting idl and add it to the interfaces which the CORBA servers implement. To gain access to the CORBA servers, use COSNaming to bind the CORBA servers into the WLS JNDI tree. As above, the application looks up the CORBA servers in the JNDI tree, but in this case the application uses the RMI-IIOP stubs to communicate with the CORBA servers.
This is an example of adding RMI interfaces to existing CORBA servers to establish some level of connectivity.
If you are using an RMI-IIOP implementation of some sort, then you are effectively hiding the CORBA interface, except you'd ignore any of work that would be done at the IDL level.
Note: We should use rmic and the –noValueTypes flag (as we aren’t using Orbix 2.3).
Calling from a Corba server into WLS
======================================
It is possible to host an Orb in the app server, contained within a WebLogic startup class. This will allow Corba calls to be delegated to app-server components (see option 1, above).
Thanks again.

JNDI Lookup in JSP fails for EJB 3.0

I am new to Java technology. I read the EJB FAQ, NetBeans docs and may forum discussions and I am still confused with the error I am having.
Background:
I have developed a persistance bean and related sessions beans (similar to the customer-cmp-ear application in the Java App Server samples). Now I am trying to access this bean using a JSP. After deploying the war file in the App Server and try to access the page, I get the following error.
javax.naming.NameNotFoundException: No object bound to name java:comp/env/ConsumerSessionLocal
After reading many articles, I understood that I dont have to prepare any descriptors, or JAR files for EJB 3.0.
Environment Details:
Java App Server Ver 9.0
NetBeans 5.5
I normally build the war files using NetBeans.
I use App Server Admin console to deploy the web applications using the above war file.
EJB details:
Persistance EJB : person.java
Session Objects
Consumer.java (this implements ConsumerSessionLocal, ConsumerSessionRemote). This Stateless bean accesses the methods in person.java.
ConsumerSessionLocal.java - local interface
ConsumerSessionRemote.java - remote interface
SearchConsumer.jsp
This JSP page is calling the ConsumerSessionLocal using the JNDI lookup through InitialContext.
Here is the Code snippet:
try {
InitialContext ic = new InitialContext();
Object o = ic.lookup("java:comp/env/ConsumerSessionLocal");
ConsumerSessionLocal consSession = (ConsumerSessionLocal) o;
I am able to see the jsp page in the browser, however, after a submit action, I get the Java Naming Exception error.
javax.naming.NameNotFoundException: No object bound for java:comp/env/ConsumerSessionLocal
I would appreciate your help/any of your thoughts.
Thanks in advance.
-Ram

I did not really solve it. Instead I used some of the tutorials that used JNDI lookup and modified those as my way forward. I did not really find out exactly what I was doing wrong.
/Anders

Difference between narrow() method usage and simple class cast for EJB

Hi,
I have a very simple question:
what is the difference between PortableRemoteObject.narrow(fromObj,
toClass) method usage and simple class cast for EJB.
For example,
1)
EJBObject ejbObj;
// somewhere in the code the home.create() called for bean ...
ABean a = (ABean)PortableRemoteObject.narrow(ejbObj,ABean.class);
OR
2)
EJBObject bean;
// somewhere in the code the home.create() called for bean ...
ABean a = (ABean)ejbObj;
Which one is better?
P.S. I'm working with WL 6.1 sp2
Any help would be appreciated.
Thanks in advance,
Orly

[email protected] (Orly) writes:
Hi,
I have a very simple question:
what is the difference between PortableRemoteObject.narrow(fromObj,
toClass) method usage and simple class cast for EJB.
For example,
1)
EJBObject ejbObj;
// somewhere in the code the home.create() called for bean ...
ABean a = (ABean)PortableRemoteObject.narrow(ejbObj,ABean.class);
OR
2)
EJBObject bean;
// somewhere in the code the home.create() called for bean ...
ABean a = (ABean)ejbObj;
Which one is better?(1) is mandated by the spec. It is required because CORBA systems may
not have sufficient type information available to do a simple case.
P.S. I'm working with WL 6.1 sp2 You should always use PRO.narrow()
andy

How to change JNDI service provider for EJB's?

I need EJBean's home interface to be bound to another JNDI provider, not Weblogic.
How can I do it?
The most simple solution is not working: to specify <jndi-name> in weblogic-ejb-jar.xml
for bean as "xxx:bean_name".
By JNDI rules for such names context factory with name com.sun.jndi.url.xxx.xxxURLContextFactory
will be used. But for Weblogic this does not work. An exception is thrown during
bean deployment -
javax.management.MalformedObjectNameException: ObjectName: Invalid value -> xxx:bean_name
at javax.management.ObjectName.validateAndAdd(ObjectName.java:440) at javax.management.ObjectName.initObjectName(ObjectName.java:409)
at javax.management.ObjectName.<init>(ObjectName.java:254) at weblogic.management.WebLogicObjectName.<init>(WebLogicObjectName.java:196)
at weblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelegate.java:90)
at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:83)
at weblogic.ejb20.internal.BaseEJBHomeMBean.<init>(BaseEJBHomeMBean.java:33) ......................

This is not an answer on my
question - My questions was: how to force a Welogic EJB Container to BIND EJBean's
home interface to another JNDI Service provider, not Weblogic.
But you wrote how to use JNDI in general - I already know how to use it :)))
Phil.
"VSK" <[email protected]> wrote:
Hi
Have a look at the code below
private Context getInitialContext () throws NamingException
String from = "CtxHelper::getInitialContext ";
String webLogicHostUrl = t3://SERVERNAME:9001
Logger.debug(from, "Begin Method", 3);
Hashtable h = System.getProperties();
h.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory
h.put(Context.PROVIDER_URL, webLogicHostUrl);
return new InitialContext(h);
} //end getInitialContext
This way we will get the InitailContext and then do a jndi lookup using
the
Context object as follows
ctx.lookup..........
Now in the above code replace weblogic.jndi.WLInitialContextFactory by
ur
provider.
Hope this helps.
-VKS
"Phil Peshin" <[email protected]> wrote in message
news:[email protected]...
I need EJBean's home interface to be bound to another JNDI provider,not
Weblogic.
How can I do it?
The most simple solution is not working: to specify <jndi-name> inweblogic-ejb-jar.xml
for bean as "xxx:bean_name".
By JNDI rules for such names context factory with namecom.sun.jndi.url.xxx.xxxURLContextFactory
will be used. But for Weblogic this does not work. An exception isthrown
during
bean deployment -
javax.management.MalformedObjectNameException: ObjectName: Invalidvalue -> xxx:bean_name
at javax.management.ObjectName.validateAndAdd(ObjectName.java:440)at
javax.management.ObjectName.initObjectName(ObjectName.java:409)
at javax.management.ObjectName.<init>(ObjectName.java:254) atweblogic.management.WebLogicObjectName.<init>(WebLogicObjectName.java:196)
atweblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelega
te.java:90)
atweblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate
..java:83)
atweblogic.ejb20.internal.BaseEJBHomeMBean.<init>(BaseEJBHomeMBean.java:33)

How to Define a Data Source in a Standard Way for EJB 3.0?

I have an EJB 3.0 project that I want to deploy to different kinds of servers. I got it to work for OC4J, but when I tried to deploy it to JBoss I found out really quick that there are actually no data sources defined in my EJB Jar and that JDeveloper does not (that I am aware of) define data sources by default in a portable way.
I could be wrong on this. Not sure. Any info for explicitly defining data sources for EJB 3.0 in a portable way would be greatly appreciated.
Thank You,
KurzHome

Frank,
Thanks for your response. I will try that.
One thing I am confused about is how to link the EJB and the data source name. Unless I am missing something obvious, I can't find a configuration setting that explicitly states that my Entity EJB uses XYZ data source (when using OC4J). Where is this defined? Also, what configuration do I add to to my EJB or other file to link it to the JBoss defined data source?
Thanks,
KurzHome

Configure security-role and method permission for EJB 3.0 using Jdev 11g

The EJB 3.0 session bean created by Jdev 11g EJB wizard does not have ejb-jar.xml. Where and how can security-role and method permission for the EJB be configured?
For example,
<assembly-descriptor>
<security-role>
<role-name>managers</role-name>
</security-role>
<method-permission>
<role-name>managers</role-name>
<method>
<ejb-name>Employees</ejb-name>
<method-name>setSalary</method-name>
<method-params>
<method-param>java.lang.Long</method-param>
</method-params>
</method>
</method-permission>
</assembly-descriptor>

user516954,
By default annotations are used. However, you can create a new descriptor and that will take presidence over any declared annotation.
--Ric

Problem in creating jar for ejb

hi,
I want just to try to compile and deploy my ejb in the new version of bea weblogic
server (version 8.1 trial version), but I have the problem when using weblogic.ejbc
to create the jar file.
There is no such problem when using weblogic 6.x, I can create the jar package
of my ejb and deploy it within the server.
I did this :
java weblogic.ejbc stage/temp_myejb.jar stage/my_ejb.jar
and I got the error message :
ERROR: Error creating descriptor from jar file stage/temp_myejb.jar:
ERROR: Error from ejbc: 1
java.lang.ArrayIndexOutOfBoundsException: 1
at weblogic.ejb20.dd.xml.DDUtils.createDescriptorFromJarFile(DDUtils.java:222)
at weblogic.ejb20.dd.xml.DDUtils.createDescriptorFromJarFile(DDUtils.java:97)
at weblogic.ejbc20.getDescriptorFromJar(ejbc20.java:698)
at weblogic.ejbc20.runBody(ejbc20.java:459)
at weblogic.utils.compiler.Tool.run(Tool.java:146)
at weblogic.utils.compiler.Tool.run(Tool.java:103)
at weblogic.ejbc.main(ejbc.java:29)
ERROR: ejbc couldn't load descriptor from jar
I do verify that the weblogic-ejb-jar.xml and ejb-jar.xml have been included in
temp_myejb.jar but why the compiler cannot load the descriptor ?
This is my weblogic-ejb-jar.xml :
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 5.1.0 EJB//EN"
"http://www.bea.com/servers/wls510/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
     <weblogic-enterprise-bean>
          <ejb-name>MemberHome</ejb-name>
          <caching-descriptor>
               <max-beans-in-free-pool>20</max-beans-in-free-pool>
               <max-beans-in-cache>100</max-beans-in-cache>
               <idle-timeout-seconds>10</idle-timeout-seconds>
          </caching-descriptor>
          <persistence-descriptor>
               <is-modified-method-name>isModified</is-modified-method-name>
               <delay-updates-until-end-of-tx>false</delay-updates-until-end-of-tx>
          </persistence-descriptor>
          <jndi-name>MemberHome</jndi-name>
     </weblogic-enterprise-bean>
     <security-role-assignment>
          <role-name>EjbClient</role-name>
          <principal-name>RemoteUser</principal-name>
     </security-role-assignment>
</weblogic-ejb-jar>
Is there something I missed ?
Many thanks in advance.
best regards,
Victorianus Kapuangan

hi Deepak,
Thanks for the answer.
I do put the ejb-jar.xml and the weblogic-ejb-jar.xml in the META-INF dir of the
temp_my_ejb.jar file. I use the bmp entity bean so I guess I do not need to put
the weblogic-cmp-rdbms-jar.xml.
Should I missed to put these deployment descriptors in the META-INF, I should
not then be able to deploy my ejb in weblogic 6.x. But in fact I can deploy it
using weblogic 6.x.
TIA.
regards,
Victorianus
"Deepak Vohra" <[email protected]> wrote:
>
The input jar file, temp_myejb.jar should have ejb-jar.xml, weblogic-ejb-jar.xml
& weblogic-cmp-rdbms-jar.xml, for cmp entity bean, in the META-INF dir.
"Victorianus Kapuangan" <[email protected]> wrote:
hi,
I want just to try to compile and deploy my ejb in the new version of
bea weblogic
server (version 8.1 trial version), but I have the problem when using
weblogic.ejbc
to create the jar file.
There is no such problem when using weblogic 6.x, I can create the jar
package
of my ejb and deploy it within the server.
I did this :
java weblogic.ejbc stage/temp_myejb.jar stage/my_ejb.jar
and I got the error message :
ERROR: Error creating descriptor from jar file stage/temp_myejb.jar:
ERROR: Error from ejbc: 1
java.lang.ArrayIndexOutOfBoundsException: 1
at weblogic.ejb20.dd.xml.DDUtils.createDescriptorFromJarFile(DDUtils.java:222)
at weblogic.ejb20.dd.xml.DDUtils.createDescriptorFromJarFile(DDUtils.java:97)
at weblogic.ejbc20.getDescriptorFromJar(ejbc20.java:698)
at weblogic.ejbc20.runBody(ejbc20.java:459)
at weblogic.utils.compiler.Tool.run(Tool.java:146)
at weblogic.utils.compiler.Tool.run(Tool.java:103)
at weblogic.ejbc.main(ejbc.java:29)
ERROR: ejbc couldn't load descriptor from jar
I do verify that the weblogic-ejb-jar.xml and ejb-jar.xml have beenincluded
in
temp_myejb.jar but why the compiler cannot load the descriptor ?
This is my weblogic-ejb-jar.xml :
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic
5.1.0 EJB//EN"
"http://www.bea.com/servers/wls510/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
     <weblogic-enterprise-bean>
          <ejb-name>MemberHome</ejb-name>
          <caching-descriptor>
               <max-beans-in-free-pool>20</max-beans-in-free-pool>
               <max-beans-in-cache>100</max-beans-in-cache>
               <idle-timeout-seconds>10</idle-timeout-seconds>
          </caching-descriptor>
          <persistence-descriptor>
               <is-modified-method-name>isModified</is-modified-method-name>
               <delay-updates-until-end-of-tx>false</delay-updates-until-end-of-tx>
          </persistence-descriptor>
          <jndi-name>MemberHome</jndi-name>
     </weblogic-enterprise-bean>
     <security-role-assignment>
          <role-name>EjbClient</role-name>
          <principal-name>RemoteUser</principal-name>
     </security-role-assignment>
</weblogic-ejb-jar>
Is there something I missed ?
Many thanks in advance.
best regards,
Victorianus Kapuangan

The connection factory name for jobs must be "JobQueueFactory

Hi Experts
Can you plase help me to reslove this issue
Caused by: com.sap.engine.services.deploy.container.DeploymentException: Deployment of jobs in application [backgrounjobear] failed, reason is : [Job "BackGroundJob" of bean "BackGroundJob" does not have a connection factory name. The connection factory name for jobs must be "JobQueueFactory".]
while depling MessageDrivenBean 3.0 getting this.
Any help would Greatly appricated.
Thanks
AB

Hi All,
I am also getting similar error i.e.
Job "TestScheduler" of bean "TestScheduler" does not have a connection factory name. The connection factory name for jobs must be "JobQueueFactory".
Steps that I have followed are bit different from what is mentioned in document "SAP NW Scheduler for Java" as I am working in 7.3
a) Created EJB Project
b) Created Message Driven Bean(JobSchedulerMDB.jav)
c) Created SchedulerJob(TestScheduler.java)
I dont see application-j2ee-engine.xml ; but have
ejb-j2ee-engine.xml
ejb-jar.xml
job-defination.xml
with following xml in them
ejb-j2ee-engine.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-j2ee-engine xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="ejb-j2ee-engine_3_0.xsd">
<enterprise-beans>
    <enterprise-bean>
      <ejb-name>JobSchedulerMDB</ejb-name>
      <jndi-name>JobSchedulerMDB</jndi-name>
      <bean-props>
        <property>
          <property-name>destination-name</property-name>
          <property-value>JobQueue</property-value>
        </property>
        <property>
          <property-name>connection-factory-name</property-name>
          <property-value>JobQueueFactory</property-value>
        </property>
       </bean-props>
    </enterprise-bean>
</enterprise-beans>
</ejb-j2ee-engine>
ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:ejb="http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" version="3.0">
<display-name>
JobSchedulerEJBProject </display-name>
<ejb-client-jar>JobSchedulerEJBProjectClient.jar</ejb-client-jar>
</ejb-jar>
job-defination.xml
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<job-definitions>
<job-definition name="TestScheduler"/>
<enterprise-beans>
<enterprise-bean>
<ejb-name>JobSchedulerMDB</ejb-name>
<jndi-name>JobSchedulerMDB</jndi-name>
<resource-ref>
<res-ref-name>JobQueueFactory</res-ref-name>
</resource-ref>
<message-destination-ref>
<message-destination-ref-name>JobQueue</message-destination-ref-name>
<jndi-name>JobQueue</jndi-name>
</message-destination-ref>
</enterprise-bean>
</enterprise-beans>
</job-definitions>
Please help me in this

CORBA Name for EJB

Similar Messages

Maybe you are looking for