Workshop source directory structure

Hi,
I am new at Workshop and would like to know the convention for organizing the
workshop source directory structure. Currently, Workshop seems to have both source
and generated files such as class/jar/ear under the same application/project folder.
Is there way to config Workshop to organize the generated files in a separate
custom specified location outside the application/project folder? The reason
is I would like to easily to check all src files into the repositiory (we are
using CVS) and left out the generated files (class, jar, ear, ...)
Regards,
Bao Nguyen

Bao,
The class files are generated under the .workshop directory under the
application folder. The generated jar file will be placed under the APP-Inf
lib folder.
No new jar/.class files will be copied into the individual project files as
part of the build process. The files are copied into the .workshop folder
and the app-inf/lib folder.
Do you notice a different behavior or do you have different requirements ?
Thanks
Raj Alagumalai
WebLogic Workshop Support
"Bao Nguyen" <[email protected]> wrote in message
news:[email protected]..
>
Hi,
I am new at Workshop and would like to know the convention for organizingthe
workshop source directory structure. Currently, Workshop seems to haveboth source
and generated files such as class/jar/ear under the sameapplication/project folder.
Is there way to config Workshop to organize the generated files in aseparate
custom specified location outside the application/project folder? Thereason
is I would like to easily to check all src files into the repositiory (weare
using CVS) and left out the generated files (class, jar, ear, ...)
Regards,
Bao Nguyen

Similar Messages

How to force Jdeveloper to preserve existing sources directory structure?

Hi all,
I have JDeveloper 9.0.3.4 which I have to use.
I tried to import to project from existing sources and I tried to keep existing sources
directory structure by selection option "Scan source paths to determine project contents" which should (according to documentation) preserve existing directory structure and show it in the Navigator.
But instead I get always (Jdev default?) directory structure:
Sources
HTML Sources
Miscelaneous Files
I changed default settings for Input path in project settings and for default project settings but still I get this Jdev structure.
Is there a way to force JDeveloper to preserve the directory structure of sources it imports from?
Many thanks,
Mile

I'd like to be able to specify the default project directory structure in 10g as well. For example I would like to have under the project root:
build.xml
src\
generatedsrc\
config\
resources\
build\
deploy\
Generating an ant build.xml using the wizard should also take into account the directory structure being used by the JDeveloper project build. I don't see why I should have to modify the build.xml file at all.

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

How to view the directory structure of JS sources in debugger?

I'm a web developer and want to use Firefox, but am used to using Chrome for debugging.
In Chrome debugging tool (hit F12 -> click 'sources' tab in top of the web dev window), you can clearly see the entire Javascript directory structure of the site you're visiting, and can collaps/expand directories nicely. How can I view the javacript directory structure in the Firefox debugging window? I can't do what I do without being able to easily navigate the filestructure of the website, but in the Firefox debugging window, all I can see is what appears to be javascript files in random order.
Thanks!
Josh

Hi Josh,
Thank you for your question. I understand that you would like to see the javascript directory structure in the Firefox debugging window. I am happy to help.
When you open Tools > Web Developer > Web Console and select the "Debugger", there are a list of js files loaded with the current viewed page.
Try [https://getfirebug.com/firstrun#Firebug%202.0.2 Firebug] its script tab has a hierarchy of js files.

Import statement and directory structure

First of all, sorry for such a long post, I believe part of it is because I am unsure of the concept of importing in Java. Secondly, Thanks to anyone who can ultimately enlighten me to the concept of import. I did ask this question before in the "erorr and error handling" forum, and the people who have helped me there did a great job. But, I believe I require a little more clarification and thus have decided to post here.
Anyhow, my question..
Could someone explain to me the concept of the import statement, or direct me to a webpage with sort of explanation for newbies? For some reason, I am having a hard time grasping the concept.
As I understand it, the import statement in Java, is very similar to the namespace keyword in C. That is to say, import doesn't actually "import" any source code, the way that the #include statement does in C.
So I suppose what my question is, say I have a java class file like below:
//filename: sentence.java
//located: c:\school\csc365
package csc365;
class sentence
//some variables here..
//some constructor here..
//some methods here..
And some sample program like the one below which implements the above..
//filename: test.java
//located: c:\school\csc365
import csc365.*;
import java.io.*;
class test.java
//creates some sentence object
//uses the object's methods
//some other things.
As I understand it, the test.java file should not compile because the csc365 package is not in the correct directory. (assuming of course, the classpath is like c:\school\csc365;c:\school )
But, ... where then should the sentence.java be located? In a subdirectory of c:\school called csc365 (i.e c:\school\csc365\) ?
And thus that would mean the test.java file could be located anywhere on the hard drive?
I suppose, I just need a little clarification on the correlation between a package's "name" (i.e package csc365; ) and its corresponding directory's name, and also how the javac compiler searches the classpath for java classes.
..So, theoretically if I were to set the classpath to look in every conceivable directory(provided the directory names were all unique) of the harddrive, then I could compile a test.java anywhere?
As a note: I have been able to get the test.java file to compile, by leaving out the import statement in the test.java file, and also leaving out the package statement for the sentence class, but I assume this is because the files are defaulted to the same package?

Hi Mary,
No, import isn't analogous to C++ namespace - Java package is closer to the namespace mark.
import is just a convenience for the programmer. You can go your whole Java career without ever writing an import statement if you wish. All that means is that you'll have to type out the fully-resolved class name every time you want to use a class that's in a package other than java.lang. Example:
// NOTE: No import statements
public class Family
   // NOTE: fully-resolved class names
   private java.util.List children = new java.util.ArrayList();
}If you use the import statement, you can save yourself from typing:
import java.util.ArrayList;
import java.util.List;
public class Family
   // NOTE: fully-resolved class names
   private List children = new ArrayList();
}import isn't the same as class loader. It does not bring in any source code at all.
import comes into play when you're compiling or running your code. Java will check to make sure that any "shorthand" class names you give it live in one of the packages you've imported. If it can't find a matching fully-resolved class name, it'll give you a message like "Symbol not found" or something like that.
I arrange Java source in a directory structure that matches the package structure in the .class files.
If I've got a Java source file like this:
package foo.bar;
public class Baz
   public static void main(String [] args)
        Baz baz = new Baz();
        System.out.println(baz);
   public String toString()
       return "I am a Baz";
}I'll store it in a directory structure like this:
root
+---classes
+---src
      +---foo
           +---bar
                +---Baz.javaWhen I compile, I go to root and compile by typing this:
javac -d classes foo/bar/*.javaI can run the code from root by typing:
java -classpath classes foo.bar.BazI hope this wasn't patronizing or beneath you. I don't mean to be insulting. - MOD

Dynamic source directory in sender adapter

Hi Experts,
I have a File to File scenario, where my source directory needs to be dynamic. The directory structure is like:
Y:\ParentDrive\<DynamicFolder>\<DynamicFolder>\<DynmicFileName>
And then on the receiver side, I need to create the DynamicFolders and the file.
Please let me know if this can be achieved using modules or if there is any other approach.

hi,
refer my article:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70c89607-e4d9-2910-7280-f6746e964516
it shows using filename. similarly u can use directory attribute.
[reward if helpful]
regards,
latika.

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

I just created a network installer for Q4 Release. We have Developers, Full, and Debug licenses. The DVDs were copied to the VLM computer's harddrive. When I created the Debug configuration, the Network Installer reported the the DVDs did not have to be modified and would copy them directly. When the network installed was done, it did not create the directory structure similiar to what the help file below shows.
LabVIEW 8.0
\_SourceFiles
\Fourth Floor Engineering
\Client
vlmclient.exe
other files
setup.exe
\Applications Group
\Client
vlmclient.exe
other files
setup.exe
Figure 1. Network Installer Directory Structure
I would have expected
LabView 8.6
    \Source Files
    \Debug
        \Client
           vlmclient.exe
         setup.exe
Only the \DISK1, \DISK2, \DISK3, \DISK4 were created. The vlmclient.exe was not created.
Paul
Solved!
Go to Solution.

When you were creating the VLI, did you get a popup message that said the source did not need modification? If you saw that popup, that means VLM was not pointed to a valid source file location, which will cause a direct copy of the files with no additions.
If you select a valid source location, you should not see that message and the Product Name field should automatically populate. If you are using the Dev Suite or Platform DVDs, you will need to follow the steps in the KnowledgeBase article I refered to in my previous post.
Here is an example of what copying the installer directory could look like if you just copy the LabVIEW 8.6 Platform DVD 1:
LabVIEW 8.6 Platform DVD 1\_SourceFiles
                                                        \(the _SourceFiles directory will contain a copy of DVD 1)
                                                \LV PDS (License Set name)
                                                        \setup.exe
                                                        \Client
                                                                 \vlmclient.exe (as well as some other vlm files)
On the client machine, you would want to run "setup.exe" to begin the installation.

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

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

Problem with package and directory structure

Please... I need help with a directory/package structure that I don't understand
why it is not working...
I want to create a custom login SWF which several other SWF movies will use in case they need some kind of login logic (in this case it is a login logic... but the problem doesn't have anything to do with that logic...)
I have created a FLA movie (LOGIN.FLA) and two helper classes (MAINLOGIN.AS and MAINLOGINEVENT.AS)... they are all under the same directory, for example:
c:\
     abc\
          def\
               ghi\
                    login
In LOGIN.FLA, I have included the source path, c:\abc (for example).
MAINLOGIN.AS and MAINLOGINEVENT.AS, have both a package like:
     package def.ghi.login
MainLogin class uses MainLoginEvent (it dispatches events of that type)... but I don't have to import anything as all 3files are in the same directory...
LOGIN.FLA has its class defined as def.ghi.login.MainLogin
And that's all... now comes the problem:
1. If I leave everything as described and try to publis LOGIN.FLA, it throws error 5001 ("The name of the package def.ghi.login.MainLoginEvent doesn't reflect....) for class MainLoginEvent... don't understand why... it is placed exactly as MainLogin and has the same package definition!
2. I have tried several other options, but when I get the SWF to get published, then, the problem comes when trying to use this SWF from another movie:
The way to publish LOGIN.FLA with no errors is: MAINLOGIN.AS and MAINLOGINEVENT.AS with empty package definition ("package" alone...) and LOGIN.FLA with class MainLogin (not def.ghi.login.MainLogin)... LOGIN.FLA doesn't have to include source path to c;\abc in this case. This way, I can publish LOGIN and get LOGIN.SWF.
The problem now is how to use this information from another Movieclip... I want to be able to use and receive events of type MainLoginEvent but can't (it gives error 5001 again, on MainLoginEvent, saying that the name of the package '' doesnt' reflect....)... If I include the path to c:\abc\def\ghi\login on the FLA, then it gives errors in MainLogin when trying to use a class of its library...
Basically, the problem here is that, the movie which wants to use the LOGIN.SWF, is in c:\abc\def, and it is including the source path c:\abc, so if I import def.ghi.login.*
it is when it throws error 5001 (I understand why, but I dont know how to fix it...), but if I dont import def.ghi.login.* then I can't use MainLogin nor MainLoginEvent...
What is the good way of doing this kind of structure... mainly it is creating a SWF, which can be used from other SWF's and which can dispatch events, which the container SWF will capture...
If anyone can please give me a hint... THANK YOU!

Hi kglad , I don't understand the first point... "don't use absolute paths"... I'm not using them (or I don't understand what you mean).
For the second one... the structure is like:
c:\
     abc\
          def\
               LOGINCONTAINER.FLA
               ghi\
                    login\
                         LOGIN.FLA
                         MAINLOGIN.AS
                         MAINLOGINEVENT.AS
In LOGIN.FLA, I include the source path c:\abc, so MAINLOGIN.AS and MAINLOGINEVENT.AS have a package of "def.ghi.login", and the class for LOGIN.FLA is "def.ghi.login.MainLogin"... when trying to publish LOGIN.FLA, Flash throws error 5001 for MAINLOGINEVENT...¿?
What I want to get is a SWF (LOGIN.SWF), which can be loaded from any other SWF (in this example, LOGINCONTAINER.SWF). LOGINCONTAINER.FLA, has a class path "c:\abc" (the same as the other LOGIN.FLA, because of the directory structure), and it has to be able to receive events of type MAINLOGINEVENT... that is why it has to do an import of "import def.ghi.login.*" (for example)
Any idea of why it is not working (or how to organize it correctly)?
Thank you

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/ ).

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).

Using already existing directory structure to create rolls

I'm converting from iView into iPhoto. I have hundreds of directories titled things like 011606.SamuelWasBorn/ with subdirectories in there called /Images /FinishedImages /WebMedium /EmailSmall etc... and then plenty of .tif and .jpegs inside of those.
I've been doing this one Cmd-Shift-I at a time, followed by a Cmd-A t select all, then a Cmd-Shift-N for a new album, followed by retyping in the name and dropping the date.
Sigh. I'm 6 weeks into this now and still only 1/4 of the way through.
Has anyone tried to drag and drop an entire directory structure into iPhoto's directory structure, fire up iPhoto, and have it recognize all that stuff as a whole bunch of new rolls that lack thumbnails? Would that work? Would iPhot then offer to update its thumbnails? And then would I be happy and fully integrated into my new iPhoto life?
I'm just a bit too chicken to give it a try. If nobody's tried this before, I'll create a test library and give it a go, but if someone has experience with doing this, I'd appreciate any pointers.
Thanks.
Oren

Oren:
Welcome to the Apple Discussions. iPhoto creates a roll with the same name for any folder of image files that are imported into it. All you have to do is select your folders of source files and drag them into iPhoto's open window.
If you want to use iPhoto's alias feature you can keep your current source folders and drag them into a library that's setup to not copy the files into it but use alias files. The library works as a conventional library with the exception that if you delete a photo from the library it does not delete the source file. That must be done manually via the Finder. I've created some Tutorials to assist users to convert over to an alias based system or go to an iView based one.
I use iView as my primary image management and iPhoto's alias feature to create a library of the same source files. That way I have the best of both applications. Also, when using the alias method, the importing process is much faster. Good luck.

Populating MX:Tree with Directory Structure using PHP

Hello,
I have written the following php function to return the directory structure :
     public function get_dir_iterative()
          $dir = 'data';
          $exclude = array( 'cgi-bin', '.', '..' );
          $folders = '<?xml version="1.0"?>';
          $folders .= "<node label='Root' path=\"data\">";
          //$folders .= $this->getFolderRecuring("data");
          $exclude = array_flip($exclude);
          $dh = opendir($dir);
          //$stack = array($dh);
          //$level = 0;
                    //closedir(array_shift($stack));
          while(count($stack))
               if(false !== ( $file = readdir( $stack[0] ) ) )
                    if(!isset($exclude[$file]))
                         if(is_dir($dir . '/' . $file))
                              $dh = opendir($dir . '/' . $file);
                              if($dh)
                                   $folders .= "<node label=\"$file\" path=\"$dir/\" isBranch=\"true\" />";
                                   array_unshift($stack, $dh);
                                   ++$level;
                         else
                              $folders .= "<node label=\"$file\" path=\"$dir/\">";
               else
                    closedir(array_shift($stack));
                    --$level;
          $folders .= "</node>";
          return $folders;
When I test this function manually it returns the proper structure.
But when I call it with help of ZendAMF there is nothing returned and the sandclock is spinning infinite ?!
here is the flex part:
private var fms:RemoteObject = new RemoteObject();
protected function initFileManagerService():void
     fms.destination ='zend';
     fms.source='FileManagerService';
     fms.showBusyCursor=true;
     fms.addEventListener( FaultEvent.FAULT, faultListener);
     fms.get_dir_iterative.addEventListener( ResultEvent.RESULT, load_result );
     trace('FileManagerService initialized');
public function load():void
     fms.get_dir_iterative();
     trace('Service / load');
     private function load_result( e:ResultEvent ):void
          trace('result:'+e.result)
My zend setup is working, any idea what could be wrong ?

>if you comment out the php and just return "hello" do you get it back in flex?
Jip, thats working
>is this line right?>fms.get_dir_iterative.addEventListener( ResultEvent.RESULT, load_result );
Yes it is correct, thats the way you listen for a result of a specific function when using the zend framework.
I have other projects running very good like this.

Workshop source directory structure

Similar Messages

Maybe you are looking for