Directory structure in a JSC project

Hi, I apologize if this is covered somewhere but I can't find it. I'm trying to set up a JSC project in a directory struture that is already defined. I can't find a way to tell JSC where the source, lib, and web files are relative to the project directory. Is there a way to change these defaults? JSC is not the only IDE in use for this project and rearranging the file tree strustuce to suit JSC is not an option.
Again this should be obvious but I've spent a lot of time trying to get the answer and haven't. Thanks for any pointers.

Hi,
Could you provide a link to the "Jakarta source structure"? I understand the standard for web apps but normal practice is to keep java source and libraries separate from web content. Web content has a fixed structure imposed by the servlet spec and that's fine, however it doesn't include source code as far as I know. Its also pretty standard practice to copy "Lib" files to Web-Inf/lib as part of the build process. Look at the standard WAR task in Ant to see what I am talking about.
I'm not asking for an arbitrary structure just an industry standard one. Currently it is difficult to use this tool in our organization since it will have to coexist with others (Jbuilder and Eclipse for the time being).
Thanks
Jim

Similar Messages

Directory structure for a J2SE+J2EE project: suggestions are very welcome

Hi, I have to start coding and organizing the CVS tree of an already mature project which is J2SE. This J2SE project can be described as a "core engine" for something else, and is a quite large project, and up to now has only a command line User Interface. I organized the dir structure as this:
/build.xml
/src/
/src/java/<package>/...../*.java
/src/demo/<package/...../*.java
/src/test/<package>/....../*.java
when I ant compile, all the .classes will be done in the "build" directory (reflecting the structure in the "src" dir):
/build/
/build/java/<package>/....../*.class
/build/demo/<package/...../*.class
/build/test/<package>/..../*.class
I am happy with this, but now comes the issue: a web interface to use this core engine (it will have the same package namespace) is in developing progess, so I have to put somewhere the *.jsp, the WEB-INF dir with web.xml and servlet sources: how would you do this? And where would you let Ant put the compiled servlet classes?
I can modify the previous directory structure to accomodate the J2EE part, this is really not a problem!
Thanks to who can suggest me a clean solution
Alessio

Create a web-inf folder at the same level of src and
jsp folder inside src
i mean
/build.xml
/src/
/src/java/<package>/...../*.java
/src/demo/<package/...../*.java
/src/test/<package>/....../*.java
/src/jsp
/web-infSo, would you put in /src/jsp only the *.jsp?
And what in /WEB-INF ? What woud you put there? Would you do something like:
/WEB-INF/web.xml
/WEB-INF/src/<package>/..../<my_servlets_and_j2ee_stuff>.java
/WEB-INF/classes/<package>/..../<my_servlets_and_j2ee_stuff>.java
In this manner sources and classes are in the same tree, it does not seem very clean to me, expecially if you consider that probably I must have a "test" directory to unit test some j2ee stuff (as for the j2se stuff in "src"): how would you do that?
Is this directory structure anyway what you meant or not?
alessio

Directory structure for the new Data Services Project

1) I do as prescribed in the manual "Building and deploying
Flex 2 Applications", page 325
"To create a web application make a copy of the /flex
directory and its contents. Rename the copy and store it in the
same location under /servers/default directory."
("flex" is an empty Flex Data Services application that
serves as a template for creating your custom application)
2) I create a corresponding project from Flex Builder 2 :
Project type: Flex Data Services
Root folder: C:\fds2\jrun4\servers\default\MyDS
Root URL:
http://localhost:8700/default/MyDS
Project name: MyDS
Project contents: C:\fds2\jrun4\servers\default\MyDS
2) I build the project
Immediately after "build project" the directory structure at
C:\fds2\jrun4\servers\default\MyDS becomes the following:
.settings
bin
----------------META-INF
----------------WEB-INF
---------------- --------------- classes
---------------- ---------------flex
--------------------------------jsp
--------------------------------lib
-------------------------------sessions
html-template
META-INF
WEB-INF
----------------classes
----------------flex
----------------jsp
----------------lib
----------------sessions
Notice that bin directory now contains another pair of
META-INF and WEB-INF in addition to those already existing in the
template project "flex".
Can anybody comment on this directory structure?
Which META-INF and WEB-INF are supposed to be used for
configuration?
What is the purpose of having two pairs of META-INF and
WEB-INF in the same web app?

Hello -
first, those folders are necessary in deployment - You need
only the contents of the bin folder for deployment, not the
sources. Since you're compiling the application locally in FB2 it
places all of the supporting and necessary files into one location
namely the "bin" folder. You'd deploy the "bin" folder's contents
to the FDS server, perhaps another FDS server that is not your
"development" server -- like a production server. The data and
configuration information that your app needs for FDS services are
stored in the WEB-INF and META-INF folders so these need to travel
with the final product. On the production server you'd just cop the
"bin" folder and it's contents to the /servers/default folder -
where you could then rename your bin folder to "MyDS"
HTH, Bill

Enable AppXRay on a legacy project with unconventional directory structure

I've got a legacy project. My first need is to do remote debugging of JSPs (application will be deployed on an app. server on a remote server).
I imported the existing project into Eclipse/Workshop Studio. When I try to enable AppXRay it popups a Folder Mappings dialog and asks for a folder in the project that corresponds to the '/' URI.
Here's what my directory structure looks like:
project/
--conf/
----web.xml
--htdocs/
----index.jsp
There is no WEB-INF/web.xml in the directory structure. The .war gets built by the Ant war command and just includes the web.xml from the conf/ dir.
If I choose the conf/ dir or the htdocs/ dir I get a warning that information related to web.xml will be missing fron AppXRay.
How do I get Workshop Studio to work in this situation?
As part of the Ant build I can add directories to the existing structure that mimic the structure of the .war that gets deployed if that will make Workshop Studio happy, but I cannot modify the existing directory structure significantly.
Thanks.
Dean

The WFM feature was implemented to support the project structure similar to yours.
Try the following steps to configure the project in Studio:
- The folder mapping for your project would be
project/htdocs => "/"
project/conf => "/WEB-INF"The "/" mapping will be your WebAppFolder (the folder containing web artifacts, like jsps, html...) and "/WEB-INF" would be the web configuration (containing web.xml and/or struts/jsf ... configuration filer).

Project directory structure

I'm do jsp development onto Tomcat and about 3 months ago moved to Jdev. I've set up my project to go against the Tomcat directory structure but am not sure this is the best thing to do when using jdev. Does anybody have a recommended directory structure to use for a project?

I got this worked out.

New Custom OAF project - Directory structure

Hello,
I am a newbie to the OAF. I am trying to set up a totally new custom OAF project (using Jdeveloper 9i)
In our current directory structure under $JAVA_TOP, there is no folder/directory for custom projects. Is there a recommended standard directory structure that needs to be used for custom projects/applications? or is it advisable to set up a new directory and the children directories underneath? If new directory needs to be set up what is the logical structure? Can any one provide an example?
Thanks,

Thank you Gyan for the feedback. One last question about the directory structure:
We have a custom schema in our current Oracle Apps DB (let us say 'zz'). As far as I know there is no specific responsibility associated to this schema. In the current non-OAF prod world, we develop custom forms/reports based of the tables in that schema 'zz'. We tend to think of this schema as a custom module. Eventhough there is no specific responsibility associated to this schema, forms/reports developed of this, would be registered to relavent module. ie., AP, GL, FL, PN etc.
If I want to use the tables from that schema and build OAF projects/pages, would my directory structure be still the same as I mentioned before but with zz as the module? i.e, $JAVA_TOP/xx/oracle/apps/zz/?
Thanks,

Help me out with Directory structure for JSF+SPRING+HIBERNATE Project

Hi frnds ,
My name is Walter working for a startup software company . We are working on Hospital Management System (HMS) project .. MVC Architecture ...using Hibernate Spring and JSF ..we need to design Directory Structure for our project..
plzz help me friends in suggesting MVC Directory structure ...? also plzz help me by directing me with the navigation flow?
Thnxx in advance
Regards
Walter

Thank you so much .. friends ..for your kind replies..thanks to Illu, anguquga and special thanks to BalusC for giving me the advice for hiring EE Artitech ..
Anyways I have discussed with my teammates designing the directory structure
anguquga your directory structure is close to what I have designed ..referiing to a sample application on web..
Hospital Management system MVC architecture Directory structure
This is the way the structure goes on ..
model --> for Hibernate as well as Spring
View --> for JSF
src(-)
|
------(-) java
     |
     -------(-) model
          |
          ------(+) businessobject
          |
          ------(-) dao
          |
          ------(+) hibernate
          |
          ------(+) exception
          |
          ------(-) service
          |
          ------ (+) impl
          |
          ------(+) util
          (-) view
          |
          ------(+) bean
          |
          ------(+) builder
          |
          ------(+) bundle
          |
          ------(+) servicelocator
          |
          ------(+) util
          |
          ------(+) validator
(-) Web or WebRoot
|
----- (-) JSP Files�etc.,
|
----- (-) META-INF
|
     ------     (+) Images
|
     ------     (+) Scripts ==== CSS (cascading style sheets, JavaScript files etc.,)
|
----- (-) WEB-INF =========xml files web.xml, faces-config.xml etc.,
     |
     -----(-) Classes
          |
-----(-) HMS
|
               ----- (+) model
               |
               ----- (+) view
|
----- (+) lib
I am sure you may notice few errors .. if u find any plzz reply me back.... thnxx in advance for replies...and thnxx for giving your valuable replies...
Walter (Kaleem)

Solution Manager - Create Project Directory structure

We're planning to use Solution managare for BW upgrade project and would like to maintain all the documentation (like status report, project presentation, Problem log) in SOLMAN. We would like to have directories and sub-directories so that user can select the directory to upload the document.
Could some one help me on how to create directory structure at project level? I'm familiar with business scenario option. Is it only option to load document? Can I've directory structure at project level instead of business scenario level.
Thanks,
Milind

Hi Milind,
You can create one more project for uploading and storing FS and TS.
If you don't want to use the buss scenario option.
For this new project select the components and from solar01 just create the folder manually by whatever name you want .say for e.g SD-pack1 ,pack2 etc.
Upload the files relevant to each module or so.
Please reward points if it helps.

Sun recommended Java EE project directory structure?

Hello,
It's said that there's a Java EE project directory structure recommended by Sun.
How to get it?
I find a link as following,
http://java.sun.com/blueprints/code/projectconventions.html
The article is my want? Thanks!
a cup of Java, cheers!
Sha Jiang

I got this worked out.

Wireless Toolkit J2ME - changing the directory structure for your projects

When I create a new package in the Sun Java Wireless Toolkit, the toolkit is creating a folder for the application and its subfolders in the following directory:
C:Documents and settings/Owner/j2mewtk/2.5.2/apps/<name_of_project>....
I am trying to change the directory for new and existing projects so that the directory is:
C:WTK2.5.2/apps/<name_of_project>....
The WTK is already installed directly under the C drive (C:WTK2.5.2/ )
Any help would be much appreciated.

I experience the similar problem.
But got success with some mobile models and most of them fail.
I put the following file in the web page.
(test.html, test.jad, test.jar)
Sony Erisson P800, install successful when accessing http://x.x.x.x/test.html, or http://x.x.x.x/test.jar
Nokia 7650, install successful when accessing http://x.x.x.x/test.jar
Nokia 3530 Fail,
Does anyone know how to install java game to Nokia 3530 through Web.

Is it possible to Change Directory structure once the project is developed?

Hello,
I am a Newbee to OAF development, I recently developed a JSP page using the oracle recommended directory structure "<companyname>.oracle.apps.<custom directory>." ie., for ex: "*xxcom*.oracle.apps.xxco.xxco_mapping.server", the page worked perfectly fine when I ran it from jDeveloper.
but when I tried to deployed the same in the server to run from Oracle Applications, I found that our organization's unix directory structure where I need to deploy the files is not the same, they are excluding the "<companyname>" directory in there structure, the directory structure in unix looks like this "$JAVA_TOP.oracle.apps.<custom directory>...." ie., for example: "/u06/appsw/appdevcomn/java/oracle/apps/xxco", so now I cannot deploy the page I have developed.
How do I resolve this issue? can I change the directory structure in jDeveloper now to match that on the server, ie., change it to "oracle.apps.xxco.xxco_mapping.server" instead of "*xxcom*.oracle.apps.xxco.xxco_mapping.server"
Thanks

Yes, it is called refactoring. PLease see the link below:
http://jdeveloperfaq.blogspot.com/2010/04/faq-20-how-to-refactor-adf-components.html
Kristofer Crus

Directory structure question...

I've been w/ three different companies doing Java development now, and each time I've come in once the project is already in progress and the directory structure is set up. What I see is a similarity:
com.<company name>.<project>.<sub-units>
examples:com.delta.kiosk.server
com.delphi.shipping.guiIs this a common way of laying out directories and if so, what is the benefit (other than standardization)?

I always figures that it was primarily a namespace issue.
org.apache.ecs.Attributes
org.xml.sax.Attributes
are examples of class names that would have resulted in a collision without the prefixes. A full class name has the package name before it so
String
java.lang.String
are the same thing, String is just shorthand for the latter. But if there are two of the same class then the prefix will help the compiler know where the class is supposed to come from. com.<company name>.<project>.<class> is a good way to ensure that you will not encounter a collision.

Directory structure for servlets and webservices in one application

hi,
Can any one help me for creating servlets and webservices in one
application and deploying in Jboss 4.2.0.
I want to know exactly what is the directory structure for creating this
application and what are the additional .xml files for deploying this application.
if any one know this answere please tell the answere.

I figured out a solution - it's a problem of policies. In detail: Server1's codebase entry (file:) refers to the class directory of Server1's project. In the simple case of only Client1, which has no codebase entry, it works fine without a file permission on the side of Server1. In the complex case of Client1+Server2, which has to have a codebase entry (file:) refering to the class directory of the Server2's project on a separate machine, for exactly the same method call from Client1 to Server1 a file permission entry on the side of Server1 is needed for Server1's class directory. But WHY ???
It seems to be a little confusing with the codebase entries, many of the posts are contrary to others and to my personal experiences. Some comments given by Adrian Colley throw a little light upon some aspects. Is there anybody, who can explain the whole topic, when, why, and which part of RMI application deals with codebase entries, also in case of not dynamic code downloading ? May be there is also a reference into the java docs, which I didn't found up to now.
Thanks in advance
Axel

An intelligent way to import already existing directory structure to Aperture

Hello,
is there an intelligent way to import already existing big directory structure of photographs (over 2TB) archive into Aperture?
I have my catalogue on a disk created in a way:
date - short shot description (i.e. “2011-02-14 Name Surname (portrait)”)
          Originals
          Converted
          PSD
          Final
I would like, when importing “date - short description”, it to become an Aperture Project with the same name and subfolders Originals, Converted, PSD and Final to become Aperture Albums or Folders in that Project.
The only way I found is to create a Project and Albums in that project manually and then import all the pictures from the corresponding folders, one-by-one, to Aperture’s Albums. I use references only to preserve the current archive structure on a disk as well.
thank you for your time.

You can try and experiment with the various options in File->Import Folders as Projects, specifically the option Import Folders as to see if you get what you are looking for but I doubt you will get exactly what you are looking for.
One way to achieve your goal would be to import the projects and then once that is done create the other entities (either folders or Albums) once and then paste them into each project.
The only way to truly automate this would be to write an Applescript and unless this is an ongoing requirement by the time you developed the script you could have just created the structure and pasted into the projects.

Package and Directory Structure

Hello --
I work in a group that supports 3 web sites. (b2b, b2c, b2e)
We're just beginning to develop Java in-house and
currently using Solaris and JDK 1.2.x.
I need to propose a package and directory structure strategy.
The "reverse the domain name" guideline makes sense to me.
My first thoughts are: ("classes" dir could be created anywhere)
classes/com/ppco/b2X/ <--- for .java and .class files (development)
lib/ <--- for b2X JAR files (ready for test or production)
util/ <--- for our utility classes like DBAccessor
lib/ <--- for our JAR files
sun/ <--- for classes like com.sun.mail pkg
lib/ <--- for JAR files like mail.jar
org/ <--- for classes in org.omg.CORBA pkg
lib/ <--- for JAR files
We need to handle 3rd party classes.
Development would be done in the b2X tree and JAR files would
be installed the lib/ dir for testing and release to production.
Does anyone have recommendations or experiences to share ?
Are there some things to avoid ?
Thanks !
Al

Hello Al,
you are on the right track. A typical convention I follow is:
<project>
bin - for startup scripts, etc. to run your application
build - for build scripts (not necessary if you build using your IDE. See below.)
classes - for my compiled classes
lib - for my 3rd party libraries
src - for my source code
test - for my test code (see http://junit.org/ )
That's the project hierarchy. The src (i.e. the package heirarchy) structure is another story.
As you say, you start with the reverse domain name. This is to give your packages a unique namespace. After that, your best guide is practice. Packages can be larger or smaller, depending on your coding practices. Usually you would have these (exact names may differ), plus others:
com/ppco/client
com/ppco/server
com/ppco/common
com/ppco/db
I think your break down of sun, org, etc. is a bit too much. If you would like to do so, however, I recommend you do the separation under /lib. This way, the top level project directory is not polluted by the different types of libraries in use.
Regards,
Manuel Amago.
From build above: I would suggest you always build your release distribution directly with the JDK, not using any IDE compiler. This is because Sun's JDK is the reference implementation, thus, any compatibility issues are not yours.
An easy way to achieve this is by using ANT (see http://jakarta.apache.ort/ant/ ).

Directory structure in a JSC project

Similar Messages

Maybe you are looking for