Ejb directory structure plz...

hello ,
i am new to ejb and i written my first ejb program ... a stateless session bean program(just a small application) as a part of my acedamic lab exercise.
i have 1 java bean program,1 client program which is jsp, and a home and object interface.now the real problem is i dunno the directory structure of ejb application. i mean to say i dont know wht are the folders required for my above application and in which directory to place which file. i am using weblogic 8.1 version.
wht r the jar files to be placed in my class path to run my application on weblogic 8.1 server.
i tried in google but i havent got the one i m looking.so,please reply to my post
thanxs in advance

Hi
The ejb file must be as same as:
[Root-dir]
--- [META-INF]
ejb-jar.xml
weblogic-ejb-jar.xml
-----[package classes dir]
*.class
packing all using : jar cvf [ejb-name] *
The JSP client must be a war file
In wls 8.1 if you are trying to call an EJB from a war, both of them need to be in an EAR file.
Jin

Similar Messages

What is the directory structure of EJB applications?

I am new to EJB program. I know that after the development is done, we package the EJB components into .jar file, and package the Web components (HTML/JSP/Servlets/JavaBeans) into .war file, and then together we package .jar file and .war file into a single .ear file. Then we just deploy the .ear file into WebLogic's application directory.
But, before the deployment, I mean during the development, what kind of directory structure is good for us to develop our EJB, HTML, JSP, Servlets, and JavaBean components?
Previously, when I was doing JSP/Servlets applications, my directoy structure is:
webapps\
--------myapplication\
-----------------------*.html
-----------------------images\
------------------------------*.jpeg, *.gif
-----------------------jsp\
------------------------------*.jsp
-----------------------WEB-INF\
------------------------------web.xml
------------------------------classes\
-------------------------------------Java Servlets located here
-------------------------------------beans\
-------------------------------------------JavaBeans are located here
Now, I am doing EJB applications, what should be the directory structure?
Thank you very much for your help!
Jingzhi

I have been involved in a few enterprise applications but have not been happy with the packaging structures used and am starting a new one now and am looking for other examples.
this is what I've used before.
web/
classes/
client/
server/
but if a class was used in the client and server it was put under the server/ package. I feel that more separation is needed.

Directory Structure ?s for an Exploded Web Application

We have an application that consists only of JSPs and Servlets, no
EJBs. I am researching whether or not it's worthwhile to start using
EJBs. We're also migrating from Weblogic 5 to 6.1. I've managed to
migrate our application fine and have it up and running on WLS 6.1.
I'm confused about the exploded directory structure, the
application.xml file, where to put the EJBs and whether or not I have
to jar them. Here's our current directory structure:
DefaultWebApp/               JSPs here
DefaultWebApp/WEB-INF          web.xml and weblogic.xml here
DefaultWebApp/WEB-INF/classes     Servlets and other classes here
DefaultWebApp/WEB-INF/lib     do my un-jar-ed EJBs go here?
I've been reading a lot of BEA's documentation, particularly
‘Deploying an Exploded J2EE Application' and a ‘Web Application PDF',
and looking for relevant threads on the weblogic.developer.interest
groups. It looks like the application.xml should go in a new
DefaultWebApp/META-INF directory. But where do the EJBs go?
I also see some directory structures with another /web directory
that's confusing me.
Oh, I've also managed to compile and jar up a trial Stateless Session
EJB. Then I think I ‘auto-deployed' it into the /applications
directory, and Weblogic seems to recognize it. But when I tried to
reference it in a JSP, I got an error message ‘class x is public,
should be declared in a file named x.java'. I'm assuming this is
related to the application.xml, where I need to define the ejb
directory.
Thanks.

To deploy your web app together with your EJBs, you need to create
an "EAR" structure. Both your webapp and your EJB jars will be within
this new structure, at the same level. You may jar up your EJBs, or you
may explode their structure, it's up to you.
The resulting structure should look something like below:
EnterpriseApp/ <-- new top level
EnterpriseApp/META-INF/
EnterpriseApp/META-INF/application.xml
EnterpriseApp/lib/ <-- shared libraries (if any)
EnterpriseApp/EJB/ <-- ejbs go here
EnterpriseApp/EJB/META-INF/ejb-jar.xml
EnterpriseApp/EJB/META-INF/weblogic-ejb-jar.xml
EnterpriseApp/EJB/com/your/ejb/classes/here
EnterpriseApp/WebApp/ <-- move your current app here
EnterpriseApp/WebApp/index.jsp <-- JSPs goes here
EnterpriseApp/WebApp/other.jsp
EnterpriseApp/WebApp/WEB-INF/web.xml
EnterpriseApp/WebApp/WEB-INF/weblogic.xml
EnterpriseApp/WebApp/WEB-INF/lib <-- ui libraries go here
EnterpriseApp/WebApp/WEB-INF/classes <-- servlets go here
The above structure is identical to the structure to an EAR file, only "exploded"
as actual files and directories instead of being "jarred" into a single EAR file.
Your application.xml in this case would specify something like:
<application>
<display-name>EnterpriseApp</display-name>
<description>My Enterprise Application</display-name>
<module>
<ejb>EJB</ejb>
</module>
<module>
<web>
<web-uri>WebApp</web-uri>
<context-root>/yourAppRoot</context-root>
</web>
</module>
</application>
And in config.xml you would have an entry similar to:
<Application Deployed="true" Name="EnterpriseApp"
Path=".\config\mydomain\applications\EnterpriseApp">
<WebAppComponent Name="ui" Targets="myserver" URI="WebApp"/>
<EJBComponent Name="ejb" Targets="myserver" URI="EJB"/>
</Application>
regards,
-Ade

Directory structure of JMS application

either we must follow any directory structure just like servlets and ejb as web-inf and meta-inf in JMS.

No real need - just use the JMS client directly in any JVM.
If you are using MDBs then yes you need to use an EAR just like EJBs - but alternatively just use spring.xml...
http://jencks.org/Message+Driven+POJOs
James
http://logicblaze.com/
Open Source SOA

Web Application directory structure

Please can someone help me with directing me to any online guide as to how webapp could be created and web.xml configuration in Sun Application server 8.
I do not understand the directory structure of sun, unlike Tomcat the webapps contains all the virtual context part with a default ROOT direct set in the server.xml as the default docbase.
Now, where is the default ROOT in Sun server? Where can I put my index file. When I create a web context, where will I put it? Does J2EE has similar WEB-INF structure in Tomcat? Does it have web.xml to configure the webapp
Finally, I have written a simple EJB called Hello World using stateless protocol. I have my Hello.class, HelloHome.class and HelloBean.class. I also have ejb-jar.xml for container configuration. I have jar then up to hello.jar and have deployed them. Now I want to access the beans, Home bean to be precises. I have written a hello.jsp and I put it in the orignal directory where the main index.html file is in Sun server which is /user/Sun/AppServer/domains/domain1/docroot, I got errors.
Could someone shade a light on this please.
Thanks Guys.
NB
Do not point me to online reference
I have awared max point for this question

The developer's guide discusses in pretty clear terms how to deploy a J2EE app from a directory structure.
The tomcat directory structure is really the same as a packaged war which once you read the documentation you will see is basically no different with SJSAS.
You need to deploy an application. See previous posts on how to have docroot be the top level (search for posts by janluehe)

Directory Structure Problem

Hi i am niew to EJB
my directory structure is like this
App
-----JSP,s
-----WEB-INF
--------classes
-------package name
-----------servlet class file
-----PAckage Name
-----------Sesion Bean Class File
my servlet is calling the session bean but when i open this app in weblogic builder it only shows jsp/servlet related setting
what is the correct directory structure
jsp is calling a servlet which in turn calles a session bean
kindly tell me
Puneet

I don't know why but weblogic builder sometimes behaves weird. Anyway, my suggestion is to try out to edit your application.xml manually.
good luck,
Fehmi

Ant Directory structure.

Hi,
We are developing J2EE application that would contain number of components. Each component would be a ear file that would contain EJB jars and war which can be deployed in any J2EE compliant application server.
We are currently using Bedrock framework for applications deployed in Weblogic. It provides a very robust directory structure with most of the ant targets. However it is very custom for Weblogic.
Is there a similar framework that provides a robust directory structure (with built ant targets) which can be delopyed into Orion/Oracle Application Server.
If not, is there any standard directory structure for building J2EE applications? Any recommended source directory structure and why?
Any help is greatly appreciated.
Thanks
Sumanth

ATProject
|
|-->Business
|
|-->Common
|
|-->Ear
|
|-->Ejb
|
|---- . so on
like this the folderers are created for modularizing and also separation of code for
easier maintainance.
the Build.xml for ant i am posting here
<?xml version="1.0" encoding="UTF-8"?>
<project name="MainDeploy" default="development_build">
     <target name="development_build">
          <antcall target="ear">
               <param name="directive" value="development"/>
          </antcall>
     </target>
     <target name="integration_build">
          <antcall target="ear">
               <param name="directive" value="development"/>
          </antcall>
     </target>
     <target name="qa_build">
          <antcall target="ear">
               <param name="directive" value="qa"/>
          </antcall>
     </target>
     <target name="production_build">
          <antcall target="ear">
               <param name="directive" value="production"/>
          </antcall>
     </target>


     <target name="ear" depends="web">
          <echo>Entering the EAR process</echo>
          <ant antfile="ear.xml" target="${directive}"/>
     </target>

     <target name="web" depends="business">
          <echo>Entering the Web process</echo>
          <ant antfile="web.xml" target="${directive}"/>
     </target>

     <target name="business" depends="ats_ejb">
          <echo>Entering the Business process</echo>
          <ant antfile="business.xml" target="${directive}"/>
     </target>

     <target name="ats_ejb" depends="integration">
          <echo>Entering the Prototype EJB process</echo>
          <ant antfile="ejb.xml" target="${directive}"/>
     </target>

     <target name="integration" depends="common">
          <echo>Entering the Integration process</echo>
          <ant antfile="integration.xml" target="${directive}" />
     </target>

     <target name="common" depends="vo">
          <echo>Entering the Common process</echo>
     <ant antfile="common.xml" target="${directive}"/>
     </target>

     <target name="vo">
          <echo>Entering the VO process</echo>
          <ant antfile="vo.xml" target="${directive}"/>
     </target>
</project>
/// End of Build.xml
Start of modular xml.. for examlpe Business.xml
<?xml version="1.0" encoding="UTF-8"?>
<project name="business" default="development">
     
     <property file="global.properties"/>
     <path id="library.path">
          <fileset dir="${localdir}/lib">
               <include name="**/*.jar"/>
               <include name="**/*.zip"/>
          </fileset>
     </path>
     <property name="build" location="${localdir}/business/build"/>
     
     <target name="development">
          <antcall target="create_jar"/>
     </target>
     <target name="integration">
          <antcall target="create_jar"/>
     </target>
     <target name="qa">
          <echo>Creating the business archive for qa</echo>
          <param name="promo" value="qa"/>
          <antcall target="create_jar"/>
     </target>
     <target name="production">
          <echo>Creating the business archive for production</echo>
          <param name="promo" value="production"/>
          <antcall target="create_jar"/>
     </target>
     
     <target name="copy_files">
     <mkdir dir="${localdir}/business/build"/>
     <copy overwrite="yes" todir="${build}">
     <fileset dir="${localdir}/business/src">
          <exclude name="**/*.java"/>
          <exclude name="**/*.class"/>
          <exclude name="**/*.jpx"/>
          <exclude name="**/*.dep2"/>
     </fileset>
     </copy>
     </target>
     
     <target name="compile_source" depends="copy_files">
          <echo>Compiling source</echo>
          <javac srcdir="${localdir}/business/src" destdir="${build}" >
               <classpath refid="library.path"/>
          </javac>
     </target>
     
     <target name="create_jar" depends="compile_source">
          <echo>Creating JAR file from compiled source</echo>
          <jar jarfile="${localdir}/lib/ats_business.jar"
               basedir="${build}"/>
     </target>
</project>
Hope you could get me
Alll The BEst

Web app directory structure

Is there some standard directory structure when building J2EE web application that consists for example JSP pages, servlets, EJB components, pictures etc.

place all your jsps in "jsp" folder under the project folder.
Create a folder called "WEB-INF" under the project folder which contains all your servlets, and web.xml and taglib.tld files. Your servlets that is .class files should be in a folder "classes" under "WEB-INF".
The .html files and picture files are under the project folder.
I hope it will help you some how.
But, the directory structure depends upon the Framework you are using such as Struts, Spring or Axis.

Directory Structures

Hi,
This is about the directory structures to use for development and
deployment under weblogic. By default, as you all know, weblogic comes with
a server called "myserver" whose directory strcuture has within it the
public_html, serverclasses, servletclasses and clientclasses directories,
with the jar files for the examples all residing in the myserver directory.
The general tendency for developers is to use simply use that very structure
as is. I think that may prove to be unwieldy during deployment (especially
when there will be multiple servers running on multiple machines, etc.) as
well as during development (integrating with source code control, etc.)
Here are my questions:
1) How have people weblogic developers organized their directory structures
for deployment? It seems to me that it would make sense to have a directory
structure that has at least a "lib" directory under which the jar files were
put, a "log" directory for log files, a "cert" directory for certificates,
etc.
2) In addition, is there an absloute need for the myserver directory to sit
under the weblogic tree? I would think it would make sense to not have the
deployment directory structures not tied to the weblogic installation's
location.
3) If there are multiple servers that will be deployed (each instantiating
its own set of services that are implemented as session and entity EJBs),
does one introduce an entire directory structure for each server or have a
common directory structure with each server having its own properties file ?
Currently, I have it setup so that each server that is introduced, e.g.,
pricing servers, fulfillment servers, etc. has its own properties file and
that the entire directory tree sits separate from the weblogic installation,
to facilitate tight integration with source code control. Having resolved
the regular issues that arise with the CLASSPATH, ClassCastExceptions, etc.,
we're up and running, but I have had a tough time convincing my developers
about the merits of deviating from the standard development tree stcucture.
Do people have any opinions about this, and are there any experiences they
can share with me? I'd be more than willing to to change course based on
others' experiences.
Sorry for the long-winded message.
TIA,
Prashanth

Prashanth Nandavanam wrote:
>
Hi,
This is about the directory structures to use for development and
deployment under weblogic. By default, as you all know, weblogic comes with
a server called "myserver" whose directory strcuture has within it the
public_html, serverclasses, servletclasses and clientclasses directories,
with the jar files for the examples all residing in the myserver directory.
The general tendency for developers is to use simply use that very structure
as is. I think that may prove to be unwieldy during deployment (especially
when there will be multiple servers running on multiple machines, etc.) as
well as during development (integrating with source code control, etc.)
Here are my questions:
1) How have people weblogic developers organized their directory structures
for deployment? It seems to me that it would make sense to have a directory
structure that has at least a "lib" directory under which the jar files were
put, a "log" directory for log files, a "cert" directory for certificates,
etc.That's how I'd do it. I think that the locations of all the
resources you need are configurable. If they're not, let us know.
2) In addition, is there an absloute need for the myserver directory to sit
under the weblogic tree? I would think it would make sense to not have the
deployment directory structures not tied to the weblogic installation's
location.No, it can be anywhere you like. Make sure you adjust the security
policy
file so Java 2 will let the server access your classes.
3) If there are multiple servers that will be deployed (each instantiating
its own set of services that are implemented as session and entity EJBs),
does one introduce an entire directory structure for each server or have a
common directory structure with each server having its own properties file ?
Currently, I have it setup so that each server that is introduced, e.g.,
pricing servers, fulfillment servers, etc. has its own properties file and
that the entire directory tree sits separate from the weblogic installation,
to facilitate tight integration with source code control. Having resolved
the regular issues that arise with the CLASSPATH, ClassCastExceptions, etc.,
we're up and running, but I have had a tough time convincing my developers
about the merits of deviating from the standard development tree stcucture.The "standard" directory tree exists only for the purpose of running
the examples that are shipped with WLS. The WebLogic development
team does exactly what you propose to do, and for the reasons you
state: to keep our deployment configuration under source control in a
location that keeps it separate from the examples support in myserver
and to make it easy to re-install the server without disturbing our
configuration files. We routinely run WebLogic Server from a
configuration
that completely ignores the WEBLOGICHOME/myserver directory.
Do people have any opinions about this, and are there any experiences they
can share with me? I'd be more than willing to to change course based on
others' experiences.
Sorry for the long-winded message.
TIA,
Prashanth--
Chuck Karish BEA Systems
(415) 402-7692 http://www.bea.com/

JSF appln directory structure..

Hi,
Iam new to JSF. Iam using JSF with tiles..What is the exact directory structure of a JSF application containing multiple modules?
For example, if iam having three modules mod1, mod2, mod3, then where to keep all the files related to them? where to keep the images?
where to keep the tiles? where to place the jsf files?where to place java files? Is one faces-config.xml enough? can we keep more than one faces-config.xml files(ie one f-c.xml for one module)? please some body draw the directory structure containing the modules, tiles, jsf files.. or provide link containing the dir structure in detail for an application containing several modules...
Thanks..

After further reading, I must say I'm more confused than ever before.
I've been looking into the examples provided with Sun's Java EE tutorial and what bothers me is that the only mention of EJB in xmls was in the application.xml where EJB's JAR (along with web app's WAR) was listed as a module:
<module>
<web>
<web-uri>dukesbank-war.war</web-uri>
<context-root>/bank</context-root>
</web>
</module>
<module>
<ejb>dukesbank-ejb.jar</ejb>
</module>,
but what if the web app was not deployed within the same EAR, instead calling the already-deployed EJB? It would have to have a reference to it in it's web.xml, wouldn't it? But, for some reason, I could find no example for this. The only mention of EJBs within web.xml was with <ejb-ref> which seems to be meant for EJB 2 as it requires references to EJB's home and remote interfaces... So, my question would be, what element do I need to add to web.xml to be able to inject an EJB 3 through @EJB annotations, if that particular EJB has already been deployed? Do I need to add anything at all, or is the annotation itself enough (i.e. it stands as a replacement for <ejb-ref>)? Is this app server dependent?
Also, I keep seeing that EJB injection into JSF managed beans is not supported on JBoss, but then again, I keep seeing the opposite... I really need some guidance on this...
If I'm making no sense here, please tell me so...

Using wlappc with split directory structure

I am trying to generate an EAR file of my application using wlappc in WLS8.1sp3.
I am using the split directory structure, I have a src directory containing my
source and xml descriptors, and a output directory containing the compiled classes.
I am using the split structure to deploy to the app server in development, that
is working fine. I use wlcompile to compile the code, that works ok too.
I assume that the purpose of wlappc would be to take a split directory structure
and create an EAR file from it, but there is only one source directory that you
can pass to the ant task. If I pass the src directory, it complains that it cannot
find the classes. If I use the output directory, it complains that it cannot
find the META-INF directory.
Am I missing a step? Do I have to use wlpackage to put everything in one directory,
then wlappc? Do I have to copy the class files or xml files manually first?

Jason Kriese wrote:
I am trying to generate an EAR file of my application using wlappc in WLS8.1sp3.
I am using the split directory structure, I have a src directory containing my
source and xml descriptors, and a output directory containing the compiled classes.
I am using the split structure to deploy to the app server in development, that
is working fine. I use wlcompile to compile the code, that works ok too.Great.
>
I assume that the purpose of wlappc would be to take a split directory structure
and create an EAR file from it, No, wlappc does J2EE code-generation and validation. For instance, it
will do hundreds of checks against your EJBs to make sure they comply
with the spec. It will compile your JSP files into servlets etc. You
just need to pass wlappc the output directory. It will automatically
find the src directory.
When you're ready to deploy to a production or staging server, you can
use wlpackage to put everything into one directory or an archived EAR file.
-- Rob
but there is only one source directory that you
can pass to the ant task. If I pass the src directory, it complains that it cannot
find the classes. If I use the output directory, it complains that it cannot
find the META-INF directory.
Am I missing a step? Do I have to use wlpackage to put everything in one directory,
then wlappc? Do I have to copy the class files or xml files manually first?

Regarding directory structure

hi every one,
any one plz help me to let me know the reason why we need to create the directory strucutre like the doucument root under which the WEB-INF under which the classes and lib directories.I am a beginner in J2EE,so plz let me know why we need to follow this kind of directory structure.
krishna gopal.

Hi,
The files inside WEB-INF is protected and they cannot be accessed without proper request. Thats the main reason.
Publicaly accessible files such as html, jsp, gif files can be placed inside the document root. No need to place these files in the WEB-INF.
All jar files must be placed in the Lib directory, loose class files must be placed in the classes directory.
I hope, it will help you to start your j2ee from scratch
all da best
bye for now
sat

J2EE Enterprise App Directory Structure

Can anyone point me to a resource that descibes the recomended development directory structure for a J2EE app with EJB? MyEclipse create three directories:
J2EEAppName
J2EEAppNameEJB
J2EEAppNameWeb
But I don't know where to put the shared classes, etc. I want to do it right.. Any help would be greatly appreciated.
Paul

For anyone else looking for an answer to the recommended directory structure...
See this link:
http://java.sun.com/blueprints/code/projectconventions.html

Directory Structures in sun one Web Server 6.1

I am struggling to run my j2ee application on newly set up sun one web server 6.1 on my pc.
Can somebody please help me expalining directory structure in detail for sun one web server 6.1?
Where should I place my java beans and it's class files?
what should WEB-INF -> lib folder contains?
I make war file using j2ee deployment tool. Do i need to change anything in web.xml and sun-web.xml?
Thanks in advance.

Thanks chris.
It looks better now. still it gives following errors in error log. I only have java beans not the EJB.
here are the error.
[20/Oct/2003:11:35:59] info ( 632): Internal Info: loading servlet /peoplechannel/SearchLDAPIn.jsp
[20/Oct/2003:11:35:59] warning ( 632): Internal error: newInstance failed (servlet class=_jsps._peoplechannel._SearchLDAPIn_jsp): java.lang.IllegalAccessException: Class com.iplanet.server.http.servlet.NSServletEntity can not access a member of class jsps.peoplechannel._SearchLDAPIn_jsp with modifiers "public"
[20/Oct/2003:11:35:59] warning ( 632): Internal error: Failed to get GenericServlet. (uri=/peoplechannel/SearchLDAPIn.jsp,SCRIPT_NAME=/peoplechannel/SearchLDAPIn.jsp)
what's the syntax to change loading precompiled jsp to force web server to compile jsp?
I really need urgent help.
Thanks,
naimesh

Class reload for split directory structure

I have tried to use the split directory structure in WL 8.1. I have a enterprise
application with 2 EJB modules and 2 WEB modules. I have tried to change one session
bean by just adding a logging statement and then use wlcompile to compile it.
Do I necessary call wldeploy to redeploy it? Or, will WebLogic automatically reload
the class file? Calling redeploy is so slow to me (about 3 minutes). Thus I want
to check if WL can just reload the class automatically.

Hudson Wong wrote:
I have tried to use the split directory structure in WL 8.1. I have a enterprise
application with 2 EJB modules and 2 WEB modules. I have tried to change one session
bean by just adding a logging statement and then use wlcompile to compile it.
Do I necessary call wldeploy to redeploy it? Yes
Or, will WebLogic automatically reload the class file? No, by default it load the EJB in the application classloader, and
everytning in the classloader must change for it to be visible.
Calling redeploy is so slow to me (about 3 minutes). Thus I want
to check if WL can just reload the class automatically.There is a bit of an advanced way in WLS 8.1 to get this to work.
In your weblogic-ejb-jar.xml, you need to set
<enable-bean-class-redeploy>True</enable-bean-class-redeploy>
This tells WLS to load the bean impl class in a sub classloader
then in weblogic.Deployer you have to specify the bean class that changed.
weblogic.Deployer -name myapp -redeploy myEJB/com/foo/MyEJB.class
That works as long as you only make changes to the bean class itself.
-- Rob

Ejb directory structure plz...

Similar Messages

Maybe you are looking for