ViewController to call deployed EJB JAR on WLS

Hi,
I have Model project containing EJB deployed into WLS as EJB JAR file.
I need to create another application for the View and reference the deployed EJB JAR.
The idea is to call remote EJB without having and any project dependencies.
Can you please advice on how it can be done.
Thank you in advance
Emile

Hi Frank,
The Model is only EJB.
The View only contains ADF Faces (no bindings , no page def , no datacontrol).
Please consider it as urgent
Thank you for your reply
Edited by: ebitar on Oct 12, 2011 9:46 AM

Similar Messages

Deploying ejb jar

[b]I was just wondering why ejb jar files cannot be deployed using OEM.
This feature is supported by many other app servers.

Did you ever deployed this EJB from weblogic console?
Thanks,
Rahul
"Chris" <[email protected]> wrote:
Hi, all
I am using WLS 7.0 ,there are some ejb-jar files in a application
directory:
user_projects\mydomain\application
when I put new ejb-jar files to overwrite the old ones, it seemed that
WLS
still using the old ones, though WLS said "ejb activate complete".
then I delete some temp files . restart the server, it still does not
work
out .
I am sure that I'v set the ProductionModeEnalbed=false.
and at another machine with the same envirenment , it is all OK.
What I$B!!(Bwant to know is where WLS 7 put the jar files , or .class
file that
it
is really and corrently using. Could some one help me ?
Thanks in advance.

Deployed EJB.jar has some classes with zero bytes

Has anyone hit a situation where Windows Jdev 902 puts class files into the ....EJB.jar file with zero bytes? In my case, the eight zero length classes are: seven My...Row.class files and the MyApplicationModule.class file. They all are in the /mypackage/common/ package and are in the ...classes/mypackage/common/ file folder.
I can use PKZIP to delete the zero length classes and add them back into the .jar and everything works as expected.
There are no error messages generated during the deployment that creates the .jar file that has the problem.

This was posted on another thread by jdev team...
We have been following this issue in support TAR 2274825.996. I sent some technical detail to the support rep on July 10, but it looks like that information never got added to the TAR. Well, FWIW, here it is:
The user may be running out of open files. The
stdio library which underlies Win32 programs (like the JVM) has a
limit on the number of files that can be open concurrently. The
limit is around 2000-2100 open files (I tested this on NT, 2000, and
XP), and the limit is on a per-process basis. If the user is running
into this limit because JDev has too many open files, then the utility
methods we use to open JAR files or other streams could be receiving
a java.io.FileNotFoundException exception with the message "Too many
open files". To verify this: go to the Windows Task Manager, go to
View | Select Columns... and be sure the "Handle Count" checkbox is
checked. Does the jdev.exe process have a disproportionately higher
number of handles than other processes? If the Handle Count is above
2000 (approx), JDev might be running out of open files. (I say "might" because
the Handle Count is for many different kinds of Win32 kernel objects,
not just for file handles.) If the Handle Count is the problem, then
it would explain the transient, nondeterministic behavior that the
user is reporting. Because the Handle limit is per-process, it would
explain why the user is able to use PKZIP or WinZip to repair the JAR
file. Try closing editors before deploying and see if that helps.
If the user confirms that the Handle Count is excessive, then we may
have a Handle leak of some kind in the product that will need to be
fixed.
Also try running JDev using "jdev -hotspot" on the command line instead
of just "jdev" and see if the behavior changes.
Hope that helps. We are monitoring the TAR, but no one has been able to reproduce the problem you are reporting, even with the files attached to the TAR, and yours is the only report so far that we've received about this specific problem.
I have added several more entities and views into app module. As I added each one, the list of zero byte jar classes would change, but always about 7-8 bad ones. Now that I am no longer adding new entities/views, the problem has become stable and repeatable. The same classes ALWAYS show up with zero bytes.
I monitored jdevw.exe while doing the deploy, and the number of handles never went above 675. I ran with jdevw.exe -hotspot and the results were exactly the same.
thanks,
Roger

Deploying ejb-jar when DataSource is defined

Hi,
I have an application that I have been deoploying to ear/ejb-jar/war files for some time. But I have found when I added a DataSource for CMP entity beans deployment of the ejb-jar failes with the following error;
WARNING: Skipping deployment step with id 'packaging-sequence' because no concrete deployer was found for platform 'JDBC'
If I remove the data source the deployment works, so it does seem to be the data source not the CMP entity bean that causes the problem.
Does anyone know what this error means and how to fix it!!!
Paul

What does the manual for the OC4J application server have to say about it all?

How to deploy EJB jar file in Weblogic 8.1

Hi,
I have created the EJB jar file, bearing home,remote,ejb and client class aling with the META-INF folder containing ejb-jar.xml and weblogic-ejb-jar.xml.
After all this I am confused where to put this EJB jar file so that the container could deploy it.
I am putting it in application folder of my own created Domain.
Suggest me...

Put it anywhere you like. You can always deploy it using the administrator console. There usually is an auto-deployment directory for the domain. You could find all that information in the Weblogic documentation.

Unable to deploy ejb jar consisting CMP and Stateful in single ejb-jar.xml

Hi
I was able to deploy entity bean and stateless bean saperately but when i am trying to deploy a jar consisting of CMP entity and Stateless within single ejb-jar.xml it shows following errors.
Auto-deploying ejb_SDCurrency.jar (No previous deployment found)... ISDCMCurrencyHome_EntityHomeWrapper4.java:830: 'finally'
wi
finally
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:835: 'try' without 'catch' or 'finally'.
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:838: 'catch' without 'try'.
catch(java.sql.SQLException e)
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:889: '}' expected.
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:893: 'try' without 'catch' or 'finally'.
public com.satyam.icalm.staticdata.currency.ISDCMCurrency findByCode(int argument0, java.lang.String argument1) throws
javax.ej
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:893: Statement expected.
public com.satyam.icalm.staticdata.currency.ISDCMCurrency findByCode(int argument0, java.lang.String argument1) throws
javax.ej
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:961: 'finally' without 'try'.
finally
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:966: 'try' without 'catch' or 'finally'.
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:968: 'catch' without 'try'.
catch(java.sql.SQLException e)
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1017: '}' expected.
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1021: 'try' without 'catch' or 'finally'.
public com.satyam.icalm.staticdata.currency.ISDCMCurrency findAllByCode(int argument0, java.lang.String argument1) throws
javax
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1021: Statement expected.
public com.satyam.icalm.staticdata.currency.ISDCMCurrency findAllByCode(int argument0, java.lang.String argument1) throws
javax
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1371: 'finally' without 'try'.
finally
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1376: 'try' without 'catch' or 'finally'.
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1378: 'catch' without 'try'.
catch(java.sql.SQLException e)
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1427: '}' expected.
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1431: 'try' without 'catch' or 'finally'.
public java.util.Enumeration findAuthorizedRecords(int argument0) throws javax.ejb.FinderException, java.rmi.RemoteException
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1431: Statement expected.
public java.util.Enumeration findAuthorizedRecords(int argument0) throws javax.ejb.FinderException, java.rmi.RemoteException
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1496: 'finally' without 'try'.
finally
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1501: 'try' without 'catch' or 'finally'.
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1504: 'catch' without 'try'.
catch(java.sql.SQLException e)
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1555: '}' expected.
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1559: 'try' without 'catch' or 'finally'.
public java.util.Enumeration findAllRecords(int argument0) throws javax.ejb.FinderException, java.rmi.RemoteException
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1559: Statement expected.
public java.util.Enumeration findAllRecords(int argument0) throws javax.ejb.FinderException, java.rmi.RemoteException
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1624: 'finally' without 'try'.
finally
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1629: 'try' without 'catch' or 'finally'.
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1632: 'catch' without 'try'.
catch(java.sql.SQLException e)
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1683: '}' expected.
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1685: 'try' without 'catch' or 'finally'.
public ISDCMCurrencyHome_EntityHomeWrapper4() throws java.rmi.RemoteException
^
ISDCMCurrencyHome_EntityHomeWrapper4.java:1685: Statement expected.
public ISDCMCurrencyHome_EntityHomeWrapper4() throws java.rmi.RemoteException
^
30 errors
Error compiling C:\oc4jext\j2ee\home\applications\calm6/ejb_SDCurrency.jar: Syntax error in source
com.evermind.compiler.CompilationException: Syntax error in source
at com.evermind.compiler.FileLinkedCompilation.run(FileLinkedCompilation.java:90)
at java.security.AccessController.doPrivileged(Native Method)
at com.evermind.compiler.FileLinkedCompiler.compile(FileLinkedCompiler.java:19)
at com.evermind.compiler.Javac.compile(Javac.java:37)
at com.evermind.server.ejb.compilation.Compilation.compileClasses(Compilation.java:335)
at com.evermind.server.ejb.compilation.Compilation.compile(Compilation.java:256)
at com.evermind.server.administration.ServerApplicationInstallation.finish(ServerApplication
Installation.java:439)
at java.lang.reflect.Method.invoke(Native Method)
at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:80)
at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:62)
Note:The same jar is deployed into Weblogic 5.1 and was working fine .....
so please if any solutions .....
regards,
Sap

Hi sapthapathi,
From the information u have provided, i can only guess, that
the problem is in ur code...Not in ejb-jar.xml....
'coz there is no problem in combining stateless session bean and CMP entity bean information in a single ejb-jar.xml file...i myself have deployed bunch of CMPs with stateless session beans..
So please check ur code once again....
--Venky

Error deploying EJB.jar 40k via console.

Hi,
I have an ejb.jar thats over 40k, containing std_ejb.jar (non ejb-compiled jar) that I am trying to load into WLS6.1 via the console. I copied the file into <wls.home>/../applications dir and when I try to load this file via the console, the console tries to load the file to generate the stubs and skeletons. The process to upload fails after a about 10 secs with a "Read timed out" error and I can see the file I copied to the apps dir, which was originally 45k is now 40k.. Please note that I have an eval version of WLS6.1. Dont know if that impacts uploads ?
thanx
-Ram

Hi,
I have an ejb.jar thats over 40k, containing std_ejb.jar (non ejb-compiled jar) that I am trying to load into WLS6.1 via the console. I copied the file into <wls.home>/../applications dir and when I try to load this file via the console, the console tries to load the file to generate the stubs and skeletons. The process to upload fails after a about 10 secs with a "Read timed out" error and I can see the file I copied to the apps dir, which was originally 45k is now 40k.. Please note that I have an eval version of WLS6.1. Dont know if that impacts uploads ?
thanx
-Ram

Deploying EJB JAR and Application EAR, META-INF directory name

To all:
I had a problem the last couple of days with deploying an EJB and application.
I'm new to WebLogic, maybe this is common knowledge, but I researched it and
didn't find any reference to what I discovered.
I'm using WebLogic Server 7 Service Pack 2 (7.02), on Windows 2000.
My problem was that the application that I was trying to deploy would not deploy
successfully, because a dependent class was not found for the EJB. I tried everything,
but the only thing I could get to work was placing the dependent jar files in
the classpath of the WebLogic server, within the start script. I correctly had
the Class-Path manifest line correct, but the dependent classes were not being
found.
Through trial and error I discovered that the META-INF directory within the JAR
and EAR archives HAS TO BE ALL UPPERCASE for the app server to successfully find
the manifest.mf file and the application.xml file.
As soon as I changed the directory name in both the EJB JAR file and the application
EAR file, the EJB deployed successfully, all dependent classes were then found.
I'm posting this here to help anybody that might have the same problem. There
is not any documentation that I could find that had this directory name requirement
explicitly stated.
Regards,
JD

What does the manual for the OC4J application server have to say about it all?

Error at the time of Deploying EJB jar on JBoss

Hi:
I am going to create web service using EJB3.0.
But at the time deploying file on JBOss i am getting following error:
12:22:51,856 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/home/crayom/projects/tools/jboss-5.0.0.CR2/server/default/deploy/TempConvert.jar state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/home/crayom/projects/tools/jboss-5.0.0.CR2/server/default/deploy/TempConvert.jar
     at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
     at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:175)
     at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1285)
     at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1003)
     at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:944)
     at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
     at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
     at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
     at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
     at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
     at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
     at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
     at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:627)
     at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541)
     at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:265)
     at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:143)
     at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:409)
     at org.jboss.Main.boot(Main.java:209)
     at org.jboss.Main$1.run(Main.java:544)
     at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
     at java.lang.String.substring(String.java:1938)
     at org.jboss.wsf.common.JavaUtils.getPackageName(JavaUtils.java:533)
     at org.jboss.ws.metadata.wsdl.WSDLUtils.getTypeNamespace(WSDLUtils.java:700)
     at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.processWebService(JAXWSWebServiceMetaDataBuilder.java:313)
     at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:107)
     at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:50)
     at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderEJB3.buildMetaData(JAXWSMetaDataBuilderEJB3.java:76)
     at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.start(UnifiedMetaDataDeploymentAspect.java:70)
     at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.start(DeploymentAspectManagerImpl.java:144)
     at org.jboss.wsf.container.jboss50.BareWSFRuntime.start(BareWSFRuntime.java:66)
     at org.jboss.wsf.container.jboss50.deployer.AbstractDeployerHookEJB.deploy(AbstractDeployerHookEJB.java:48)
     at org.jboss.wsf.container.jboss50.deployer.AbstractWebServiceDeployer.internalDeploy(AbstractWebServiceDeployer.java:60)
     at org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerEJB.internalDeploy(WebServiceDeployerEJB.java:115)
     at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
     at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
     ... 18 more
12:22:51,897 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** CONTEXTS IN ERROR: Name -> Error
vfszip:/home/crayom/projects/tools/jboss-5.0.0.CR2/server/default/deploy/TempConvert.jar -> java.lang.StringIndexOutOfBoundsException: String index out of range: -1So, can any body tell me the solution of this problem?
Thank You.

AnupDesai wrote:
Hi:
After adding require packages also i am getting the same error.
Well, if it's not a version problem with either the JDK (installing java 6 on top of a java 5 distribution) or the Jars (like JAXB) , then , as pointed out, you might have written your Web service using a packageless class:
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
     at java.lang.String.substring(String.java:1938)
     at org.jboss.wsf.common.JavaUtils.getPackageName(JavaUtils.java:533)Restart a new project in your IDE with a packaged ws from the start, and see if it works.

Problem calling deployed EJB

I've deployed an ejb but i cant seem to access it, it throws me an exception that it couldnt find a xxxHomeHelper.class which should be in the generated jar file from the deployejb utility. I have the generated file in the classpath which is why i dont understand why it throws this exception.

Hi Everybody here,
All you guys have gone too
far ahead in this EJB, but
I havent even started.
I have succesfully deployed
my EJBs in Weblogic 6. But
now I want to use Oracle's
in-built deployment tool.
Try hard as I could I could
not find a build-an-EJB-
example in the Oracle
documentation site, which
would give me a step-by-
step instruction as to how
to write the code for a
sample EJB (its home,remote
e.t.c and the code for the
client class) and how to
write out the deployment
descriptor and finally how
to deploy using the
deployejb.exe tool.
Anybody got a URL?
Thanks in advance
snodx
I HAVE POSTED THIS AS A REPLY TO SEVERAL
OTHER EJB-RELATED TOPICS HERE

Deployment issues, how is weblogic-ejb-jar.xml linked to ejb-jar.xml

Hey guys,
I'm getting the following error I think because i have something configured incorrectly in my xml files. Instead of yousing activationConfig properties in my MDB I wanted to set them in the ejb-jar.xml file manually. The following error I'm getting is...
Unable to deploy EJB: MyMDB from MDBtest2:
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.
weblogic.deployment.EnvironmentException: [EJB:010176]The resource-env-ref 'inQueue' declared in the ejb-jar.xml descriptor has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor.
 at weblogic.ejb.container.deployer.EnvironmentBuilder.addResourceEnvReferences(EnvironmentBuilder.java:641)
 at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:330)
 at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentFor(EJBDeployer.java:1097)
 at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:991)
 at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1273)
 at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:372)
ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar id="ejb-jar_ID" version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
 <display-name>MDBtest2</display-name>
 <enterprise-beans>
 <message-driven>
 <ejb-name>MyMDB</ejb-name>
 <ejb-class>cms.crown.mdb.MyMDB</ejb-class>
 <transaction-type>Container</transaction-type>
 <message-destination-link>omg</message-destination-link>
 <resource-ref>
 <res-ref-name>weblogic.jms.XAConnectionFactory</res-ref-name>
 <res-type>javax.jms.XAConnectionFactory</res-type>
 <res-auth>Container</res-auth>
 </resource-ref>
 <resource-env-ref>
 <resource-env-ref-name>inQueue</resource-env-ref-name>
 <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
 </resource-env-ref>
 </message-driven>
 </enterprise-beans>
 <assembly-descriptor>
 <container-transaction>
 <method>
 <ejb-name>MyMDB</ejb-name>
 <method-name>onMessage</method-name>
 <method-params>
 <method-param>javax.jms.Message</method-param>
 </method-params>
 </method>
 <trans-attribute>Required</trans-attribute>
 </container-transaction>
 </assembly-descriptor>
</ejb-jar>
weblogic-ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-ejb-jar xmlns:wls="http://www.bea.com/ns/weblogic/10.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">

<wls:message-destination-descriptor>

<wls:message-destination-name>omg</wls:message-destination-name>
<wls:destination-jndi-name>inQueue</wls:destination-jndi-name>
<wls:initial-context-factory>weblogic.jms.XAConnectionFactory</wls:initial-context-factory>
<wls:provider-url>http://localhost:8010</wls:provider-url>
</wls:message-destination-descriptor>
</wls:weblogic-ejb-jar>
Hope this is readable, thanks for any assistance

Hi,
It looks like first thing you are using EJB3 but your XML files are still pointing to version="2.1" and very old.

<ejb-jar id="ejb-jar_ID" version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee "http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
 
*try this: In below "ejb-jar.xml" file*
QCF = your Connection factory JNDI Name
TestQ = your Queue JNDI Name
Transaction Attribute is ByDefault = Required ...so no need to add it here.
<?xml version='1.0' encoding='UTF-8'?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" metadata-complete="true">
<enterprise-beans>
<message-driven>
<ejb-name>MyMDB</ejb-name>
<mapped-name>TestQ</mapped-name>
<ejb-class>cms.crown.mdb.MyMDB</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Container</transaction-type>
<activation-config>
<activation-config-property>
<activation-config-property-name>destinationType</activation-config-property-name>
<activation-config-property-value>javax.jms.Queue</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>connectionFactoryJndiName</activation-config-property-name>
<activation-config-property-value>QCF</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>destinationJndiName</activation-config-property-name>
<activation-config-property-value>TestQ</activation-config-property-value>
</activation-config-property>
</activation-config>
</message-driven>
</enterprise-beans>
<assembly-descriptor></assembly-descriptor>
</ejb-jar>
"weblogic-ejb-jar.xml":
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/weblogic-ejb-jar" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-ejb-jar http://www.bea.com/ns/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd">
 Now u need to Just define the Provider URL here...if you want a remote provider...else not required JNDI names are already defined in the ejb-jar.xml file 
</weblogic-ejb-jar>
Some Links which you can refer:
To Generate the Deployment Descriptors ...in case of EJB3 Applications: *http://jaysensharma.wordpress.com/2010/04/02/generating-ejb3-clientjar/*
MDB3.0 Sample: *http://jaysensharma.wordpress.com/2009/08/17/mdb3-0-sample-for-weblogic-application-server/*
Thanks
Jay SenSharma

Deploying persistence.xml in ejb-jar componts

Hi,
If you are deploying ejb-jar components which are packaged independently and are remote components but they all access the same database, do you put the persistence.xml in the META-INF of each component (ejb-jar). If not, where would it go?
I can find lots of references to having a single persistence.xml with many configurations but if (theoretically) each bean is deployed on a separate JVM/Container how would it access the persistence.xml?
Thanks.

If you are deploying the EJB JARs to different Java EE servers, then yes, each EJB JAR needs its own persistence.xml. You would configure each Java EE server to point to the same JDBC resource.
If you are deploying them all to the same server, you should package the entity classes into a single JAR file, and include that JAR file in an EAR with the other EJB JARs. In that scenario, persistence.xml is in the JAR's META-INF directory. The JAR file can either be in the top-level of the EAR, or in the EAR's library directory. In this case, the scope of the persistence unit is the entire EAR.
-ian

HELP!!! How I can call to EJB from another EJB??

I have two EJBs, for each EJB I have a jar, how I can call to EJB jar to another???
I have tried the following, in the first EJB I have import the second EJB jar and call it with context, lookup, PortableRemoteObject etc.. but the instruction lookup not find the second EJB reference.
The name in the lookup instruction is the JNDI name of the second EJB but not find a reference to it.
Please help me!!! Thanks!!
The error is:
javax.naming.NameNotFoundException: Missing node. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound
     at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:34)
     at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.extract(NotFoundHelper.java:50)
     at org.omg.CosNaming._NamingContextStub.resolve(_NamingContextStub.java:161)
     at com.inprise.j2ee.jndi.java.CorbaContext.resolveName(CorbaContext.java:242)
     at com.inprise.j2ee.jndi.java.CorbaContext.lookup(CorbaContext.java:261)
     at com.inprise.j2ee.jndi.java.javaContext.internal_lookup(javaContext.java:483)
     at com.inprise.j2ee.jndi.java.javaContext.internal_lookup(javaContext.java:493)
     at com.inprise.j2ee.jndi.java.javaContext.internal_lookup(javaContext.java:493)
     at com.inprise.j2ee.jndi.java.javaContext.lookup(javaContext.java:937)
     at com.inprise.j2ee.jndi.java.javaContext.lookup(javaContext.java:942)
     at javax.naming.InitialContext.lookup(InitialContext.java:350)
     at ejbclient.EnterpriseClientBean.addition(EnterpriseClientBean.java:115)
     at ejbclient.EnterpriseClientBean.actionPerformed(EnterpriseClientBean.java:97)
     at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1450)
     at avax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Abstr

ok.. Here it goes.. I am writing a sample code..
public class EJB1LogBean implements SessionBean {
// test is a method of stateless session beam
public void test ( TestVal val )
throws RemoteException{
try {
EJB2LogHome ejb2Home= (EJB2LogHome)getHome("java:comp/env/ejb/EJB2LogHome",1);
EJB2Log ejb2Log = ejb2LogHome.create ( val );
} catch ( CreateException e ) {
     System.out.println("Create Exception occurred ");
     e.printStackTrace();
     } catch ( RemoteException e ) {
     System.out.println( "RemoteException Occured");
e.printStackTrace();
     throw new RemoteException () ;
     } catch(Exception ee) {
ee.printStackTrace();
private EJBHome getHome(String jndiName,int type) {
try {
Context context = new InitialContext();
Object ref = context.lookup( jndiName );
switch(type)
case 1:
EJB2LogHome ejb2LogHome = ( EJB2LogHome )
PortableRemoteObject.narrow( ref, EJB2LogHome.class );
return ejb2LogHome;
} catch ( Exception e ) {
e.printStackTrace();
return null;
}//EJB1LogBean ends
Here as you can see, EJB1LogBean(session bean) is calling a second EJB, EJB2LogBean (entity bean). TestVal is a sample value object passed. It is plain java class and can vary from app to app and it has got nothing to do with ejbs.
"java:comp/env/ejb" is a J2EE standard and while getting a home interface, you have to append the home interface class name to "java:comp/env/ejb". Here I am passing "java:comp/env/ejb/EJB2LogHome" and "1" to getHome method, whose job is to get a reference to a home interface. getHome method is a local method. "1" is passed just to give a flexibility to getHome method as you can have more ejbs to invoked. In that case, you can go on adding different case statements for 2, 3 etc.
The only thing you have to keep in mind is that your deployment descriptor for EJB1LogBean will contain the entires for both the beans i.e. for EJB1LogBean and EJB2LogBean. This is because EJB2LogBean is wrapped by EJB1LogBean.
Hope this helps.
Please let me know if you need anything more.
- Amit

Include reference to ejb-jar in config.xml

Hi
I am deploying an ejb-jar to WLS and everything is fine. But when I try to
run the ejb I get NoClassDefFoundError. As far as I can see the only
solution to this problem is to add a reference to the jar-file in the
command file used to start WLS. Is this true or are there smarter ways to do
this?
Regards
Morten Salomonsen
[email protected]

You mean you get the exception when you access the EJB from the client? Is
the exception a client side exception?
see if this helps
http://e-docs.bea.com/wls/docs61/programming/packaging.html
"Morten S." <[email protected]> wrote in message
news:[email protected]..
Hi
I am deploying an ejb-jar to WLS and everything is fine. But when I try to
run the ejb I get NoClassDefFoundError. As far as I can see the only
solution to this problem is to add a reference to the jar-file in the
command file used to start WLS. Is this true or are there smarter ways todo
this?
Regards
Morten Salomonsen
[email protected]

Classloading [EAR] - [webapp.war+ejb.jar]

Hi.
I've got a problem with the classloader hierarchy in WL 6.0.
When I deploy my war/ejb application as an EAR, everything works fine.
But I want (for several reasons) to deploy
EJB jars and WebApp wars (or exploded Web Apps) seperately.
WL 6.0 EJB classloader doesn't export remote/home interfaces and
helper classes,
so my web app can't find them.
When I include that interfaces/classes in my Web App, I get
occasionally ClassCastExceptions (I assume depending on classloader
caching).
Is there a way to configure the classloader hierarchy, or do you have
any other solution for this?
Thanks,
Roman

Hello,
I have a big application to do.
So, one solution should be to use an EAR for one
module, containing the WAR for the web-tier and the
EJB-JAR for the business-tier.
It would be better doing like this than creating a
big WAR, in order to avoid to deploy a big WAR when a
modification is done in one module.Are you using local EJBs or remote EJBs? The only way for a war to talk to a local EJB is to package the war along with the ejb-jar in an EAR file because they need to be collocated. You can not simply bundle EJB classes in a war file.
If you are using remte EJBs, then you can package the EJB client view classes along with the servlets and JSPs in the war file and deploy the war separately. But again your war will be one big war.
If your EJBs are just entity beans, then Java EE 5 (see http://weblogs.java.net/blog/ss141213/archive/2005/12/using_java_pers.html) allows you some nice options.
>
What about the problem of the session ?
In fact, I have to declare a context-root for one
EAR.
And at each context-root is created an object
HttpSession on the server.
So, I have some questions about this :
- How can I configure my WARs in order to use only
one HttpSession object for every WARs ?
There is no standard way to do this. Relying on any application server specific feature can only make your app non-portable. So I strongly recommend you not to do this.
- Can I put multiple WARs in one EAR ?Of course you can.
If yes, what about the context-root ? This solution would resolve
the session problem.Can't be solved using any standard way. So I suggest you stick to one big war, if that's what your business requirement is.To speed up development-deployment-test cycle, any appserver allows a rapid deployment option where in you can deploy incremental changes to server. Use this facility during development. DON'T sacrifice portability of your app by using any product specific configuration that you may not find any where else.
Thanks,
Sahoo

ViewController to call deployed EJB JAR on WLS

Similar Messages

Maybe you are looking for