Jaxb+classpath+directory structure

I have generated the files using xjc by giving xjc -b work\ItemList.xjs -dtd work\itemList.dtd -p test.jxml -d work from bin directory...
When i try to compile the generated java files....
" com.sun.xml.bind"...cannot find...like this its giving for all....Think classpath is not properly set or some problem with directory strcture.can someone help me...
my cp is
set JAVA_HOME=C:\j2sdk1.4.2_03
set JWSDP_HOME=C:\jwsdp-1.4
set JAXB_HOME=%JWSDP_HOME%\jaxb
set JAXB_LIBS=%JAXB_HOME%\lib
set JAXP_LIBS=%JWSDP_HOME%\jaxp\lib
set JWSDP_LIBS=%JWSDP_HOME%\jwsdp-shared\lib
set PATH=%JAXB_HOME%\bin;%JWSDP_HOME%\jwsdp-shared\bin;%PATH%
set CLASSPATH=%JAXB_LIBS%\jaxb-api.jar;%JAXB_LIBS%\jaxb-ri.jar;%JAXB_LIBS%\jaxb-xjc.jar;%JAXB_LIBS%\jaxb-libs.jar;%JAXP_LIBS%\jaxb-api.jar;%JAXP_LIBS%\endorsed\xercesImpl.jar;%JAXP_LIBS%\endorsed\xalan.jar;%JAXP_LIBS%\endorsed\sax.jar;%JAXP_LIBS%\endorsed\dom.jar;%JWSDP_LIBS%\jax-qname.jar;%JWSDP_LIBS%namespace.jar;.
According to me classpath i think its ok....Problem regarding directory structure.Pls xplain.
Thanks in advance

Right ... I just realized that %JAXP_LIBS%\jaxb-api.jar doesn't exist.
Run any of the examples with "ant -v" to see what the classpath should be.
-- Ed

Similar Messages

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

Directory structure and files in Oracle Application server 10g and 11g

Hi all,
I am doing a lab migration from 10g to 11g based on the use of JAXB. There were some directory structures used in 10g to store the JAXB jar files and some other custom jar files. I want to know the equivalent folder structures in SOA 11g server. The 10g server directories are mentioned below:-
1.<OracleAS_Home>\webservices\lib.
2. server.xml located at <OracleAS_Home>\j2ee\home\config in 10g. Where can I find the equivalent file to "server.xml" in 11g server?
3. <OracleAS_Home>\bpel\system\classes\com\oracle\bpel\xml\util.
4. <OracleAS_Home> \bpel\system\classes.

Here are the equivalents as per best of my knowledge:
1. <WebLogic Home>\server\lib
For example, D:\Middleware\wls1036\wlserver_10.3\server\lib
2. config,xml located at <Domain_Home>\config\
For example, D:\Middleware\wls1036\user_projects\domains\ArunBaseDomain1036\config\config.xml
3. It should be the same as 10g (instead of OracleAS_Home, it will be ORACLE_Home) if you install the BPEL product. Since, I have not installed BPEL/SOA, I am not very sure.
4. It should be the same as 10g (instead of OracleAS_Home, it will be ORACLE_Home) if you installed the BPEL product.
Also, I would recommend that you consider using ORACLE Smart Upgrade (JDeveloper component) to help you with the upgrade process. It exactly points out these mappings of file/directory structures AND the necessary configuration changes as well.
If you are requirement, is only about making the library jars available to your application, then consider reading the below discussion.
Re: XIncludeAwareParserConfiguration cannot be cast to XMLParserConfiguration
Arun

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

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/

Scenebuilder not seeing controller in Maven directory structure

I'm using maven for my javafx project, I used the javafx maven plugin @ https://github.com/zonski/javafx-maven-plugin/wiki. Everything was created correctly with a typical maven directory structure, the fxml file was created in the resources\fxml folder. When I edit the fxml file Scenebuilder will not see my controller, I have set the <?scenebuilder-classpath-element /> fxml element to the path of the controller source and the controller still cannot be seen by Scenebuilder. I have performed a build and then changed the same element to the generated jar and it still does not work.
So as a work around I keep the fxml file in the same folder as the controller source. I've read that the scenebuilder-classpath-element is used to resolve imports for user written controls, as a suggestion for a Scenebuilder enhancement it would be nice to have the classpath element also used for the declared controller.

Makes sense.
I created http://javafx-jira.kenai.com/browse/DTL-5573 to track that proposal.
Thanks for the suggestion.

Compiling files with nested directory structure

I'm getting "resolve symbol" errors when I try to compile source files which
are in the child directory whose dependent on files from it's parent
directory. Here's my current directory structure:
src
-->a
---->b
------>util
What I'm trying to do is compile files which are in the 'util' directory.
Some of these files use some of the classes in the 'b' directory. My
compile statement is the following:
java -d class -classpath src src\a\b\util\aFile.java
Files in the 'util' directory has a import a.b.* statement on top, but I
don't think that's the problem, let alone necessary.
Any assistance would be appreciated.

Files in the 'util' directory has a import a.b.*
statement on top, but I
don't think that's the problem, let alone necessary.You must import classes that you use if the classes are not in the same package. The classes in src\a\b should have a package statement as the first line of source code and I am guessing it should be "package a.b;" Likewise, the classes in src\a\b\util should have a "package a.b.util" line. It's hard to guess what you have in mind. If you have the package statements, then the classes in a.b.util can import a.b.whatever. This will work.

Best practices for package directory structure?

I've only compiled a few java programs & while I find the language itself very easy to adapt to from C++ and Javascript, I get confused about the directory structure and classpaths & such.
My main method of operation is to build small tools and test projects, and I would like to follow good practices for organizing my directory structure, so it will (a) work well with java, and (b) work well with my source control software.
Let's say I am developing packages named "com.example.test.test1", "com.example.test.test2", "com.example.tools.flapper", and "com.example.tools.spinner".
I know I can use this structure:
/java/test/test1/com/example/test/test1/* (files for com.example.test.test1 including test1.java)
/java/test/test2/com/example/test/test2/* (files for com.example.test.test2 including test2.java)
/java/tools/flapper/com/example/tools/flapper/* (files for com.example.tools.flapper including flapper.java)
/java/tools/spinner/com/example/tools/spinner/* (files for com.example.tools.spinner including spinner.java)
But the directories seem unnecessarily deep & lead to a hassle in source control that makes it difficult to browse.
Can I use this? and if so, how do I run "javac" and "jar" properly to compile/jar-ify each package?
/java/com/example/test/test1/* (files for com.example.test.test1)
/java/com/example/test/test2/* (files for com.example.test.test2)
/java/com/example/tools/flapper/* (files for com.example.tools.flapper)
/java/com/example/tools/spinner/* (files for com.example.tools.spinner)
also is it recommended to leave the .class files in the same dirs as the .java files, or better to have a separate tree for compiled .class files?

hmm, there's a lot to absorb here...
I found these articles online that seem good:
http://www.onjava.com/pub/a/onjava/2003/12/17/ant_bestpractices.html
http://www.kevinboone.com/classpath.html
I'd like to use ant if possible & understand it; I've had troubles with IDEs in the past and would like to just stick with basic build mechanisms.
I guess as a practical example let's say I have two different applications that use the serial port, that I want to release separately, each in separate .jar files. One is called com.example.applications.serial1 and the other is com.example.applications.serial2. They both use rxtx.org's gnu.io.* libraries. Serial1 uses some packages that I have developed: com.example.tools.spinner and com.example.tools.flapper, whereas Serial2 uses com.example.tools.spinner and com.example.tools.flopper
I think I want to organize things this way: (everything below under /java/src/)
com
example
applications
serial1
serial1.java
serial2
serial2.java
tools
spinner
spinner.java
flapper
flapper.java
flopper
flopper.java
and I think I want to compile to /java/classes/:
com
example
applications
serial1
serial1.class
serial2
serial2.class
tools
spinner
spinner.class
flapper
flapper.class
flopper
flopper.class
but I'm sort of lost on where to put the ant buildfiles, which directories to be in to run javac, and how to get the jar files right. From what I've searched for online, the external libraries (RXTX's jar files & .dlls for windows) are "interesting", and the easiest thing is to tell users of my .jar files to put the rxtx libs in the same library as the .jar files so I can set the Class-Path: in the .jar manifest to point to them.

Organize iTunes file list by Directory Structure instead of artist/album?

Hello, I have searched for different audio players for os x which might have this feature but so far have had no luck. What I'm looking for is a feature similar to that of foobar2000 for win32 where I can organize my music by directory structure without the iTunes automatic organization by artist/album. Is there a way I can accomplish this in iTunes with some sort of xml config or hidden options? Thanks.

You don't have to have iTunes move music around on your hard drive (Preferences>Advanced>General, uncheck Keep iTunes Music folder organized and Copy files to iTunes Music folder when adding to library) but I suspect that's not what you're asking. You can't automatically view music from within iTunes by directory structure. iTunes organizes by ID3 tags ("mp3 tags"). You could, I suppose, spend a lot of time replicating your directory structure by using folders and playlists within iTunes but you'd probably have to do it all by hand.
You could check out Doug's Scripts to see if there are some scripts that might help.
http://dougscripts.com/itunes/index.php

How to create a tree based on directory structure

I want to create a hierarchical tree in Forms 6i based upon a file system directory structure (similar to Windows Explorer). How can I populate a tree with this information, is there something that I can call or write that would return the file system structure in a format that I can populate my tree?
Any advice would be greatly appreciated.
Thanks
Richard

Your link does not seem to work.They're re-jigging all the links to accomodate the hot poop on Oracle's latest and greatest, 10G. So at least the website is on schedule even if the actual software delivery dates have slipped :P
We can still get D2KWUTIL from here: http://te chnet.oracle.com/software/products/forms/content.html
Cheers, APC

Directory Structure for multiple applications at one host

Can I have multiple (more than one) WEB-INF directory structures in the public_html directory for different web applications? If I do this, how do setup the url-pattern in the Servlet Mapping tag in the web.xml file? How do I setup the URL that calls the servlet from the HTML that has been send to the user�s browser?

If I understand your question, you want multiple contexts. All App Servers/Web Servers allow you to setup multiple contexts. Normally if your root context is in /home/myhome/app_server/
then you would setup multiple contexts by creating a folder for each context:
/home/myhome/app_server/context1/
/home/myhome/app_server/context2/
Each would have their own full application/website. And the way to reference these would be as such:
if the domain, www.mydomain.com, is mapped to /home/myhome/app_server/
www.mydomain.com/context1/
www.mydomain.com/context2/
I think that is what you were asking. Hope it helps

Is there any way to specify a URL in the servlet-mapping that doesn't need to be in the directory structure?

          I migrated from WebLogic 5.1 to 7.0.2 Something I used to have set-up in 5.1 no
          longer
          works.
          I am using the weblogic.servlet.FileServlet and have the URL "/cxedocs/" mapped
          to this
          servlet. So whenever the URL http://localhost:7001/cxedocs/en_US/index.html
          is used it would use the docHome associated with the /cxedocs/ URL and then append
          the "en_US/index.html" on to it. So let's say d:\temp\en_US\index.html
          But now for WL 7.0.2 it appears that the URL also needs to be in the directory
          structure.
          So it now takes the docHome "d:\temp" adds the URL "/cxedocs/" and then appends
          the
          rest - so d:\temp\cxedocs\en_US\index.html.
          I can't require that the "cxedocs" directory be there. Is there anyway to map
          a certain URL
          without requiring it in the directory structure. I looked at virtual directory
          mapping too but
          it still seemed to require this.
          Any help would be appreciated!
          Thanks!
          -Lori


          I opened up a case with support on this. After some research they came back with
          that
          NO there is no way to do this. In 6.0 it was changed to follow the spec which
          restricts this.
          The URL must be part of the directory path.
          -Lori
          "Lori Ronning" <[email protected]> wrote:
          >
          >I migrated from WebLogic 5.1 to 7.0.2 Something I used to have set-up
          >in 5.1 no
          >longer
          >works.
          >
          >I am using the weblogic.servlet.FileServlet and have the URL "/cxedocs/"
          >mapped
          >to this
          >servlet. So whenever the URL http://localhost:7001/cxedocs/en_US/index.html
          >is used it would use the docHome associated with the /cxedocs/ URL and
          >then append
          >the "en_US/index.html" on to it. So let's say d:\temp\en_US\index.html
          >
          >But now for WL 7.0.2 it appears that the URL also needs to be in the
          >directory
          >structure.
          >So it now takes the docHome "d:\temp" adds the URL "/cxedocs/" and then
          >appends
          >the
          >rest - so d:\temp\cxedocs\en_US\index.html.
          >
          >I can't require that the "cxedocs" directory be there. Is there anyway
          >to map
          >a certain URL
          >without requiring it in the directory structure. I looked at virtual
          >directory
          >mapping too but
          >it still seemed to require this.
          >Any help would be appreciated!
          >Thanks!
          >-Lori

I have copied many photo's from another laptop to my Mac. The older photo's are in directories with names that help me select what I need to view. I would like to have all my imported new photo's also bee added to the directory structure I have in Finder

I have copied many photo's from another laptop to my Mac. The older photo's are in directories with names that help me select what I need to view. I would like to have all my imported new photo's also bee added to the directory structure I have in Finder but my new photo's are all in iPhoto. I want to use directories for storing and iPhoto for viewing. Is this possible or do I need to have all my photo's in iPhoto??
Mitch

iPhoto is not a Photo Viewer. It's a Photo Manager and designed for looking after the files while you organise the Photos. It really works much better if you let it manage those files. If you use iPhoto you never go near those files because iPhoto is your start point for anything you want to do with your Photos - the point of the pplication.
You can run iPhoto in Referenced mode, where it does not copy the files to the Library, but I caution you that you are making life a lot more difficult for yourself by doing that.
How to, and some comments on why you shouldn't, are in this thread
https://discussions.apple.com/thread/3062728?tstart=0
Regards
TD

Export images to a directory structure based on a collection tree?

A question:
Will lightroom have the capability to export images to a directory structure which mirrors a collections logical structure?
The reason I ask this is that when I create websites using third party tools (eg, Jalbum) I typically generate a flash or HTML based site with an menu structure for navigating the images.
So, the image interface is not simply a "flat-file" display as per the templates in Lightroom beta.
To do this, with previous image management tools (eg, iMatch) I create a hierarchy of images based on the categories (or collections) that the images are assigned to, export the images in a folder tree reflecting their categories (or collection), then use, say, Jalbum, to generate the website with the menu tree reflecting the folders/images.
This is extremely useful for more complicated image websites with categories and a large no of images.
If this function was built into Lightroom I guess it would be in the export function such that the "write to folder" box could take an argument {collection name} which would create a folder tree reflecting the collections logical tree which is being exported.
Apologies if this topic has been raised previously. But this function is extremely useful if you are using third party html tools or simply building websites by hand.
Regards
Alistair

I started simmilar thread in Lightroom Feature Requests few months ago, but can't find it anymore since new forum version...
What I can suggest as a new feature is export to directory structure from collections or second option from keywords. Probably more usable and easier to implement would be from collections.
What I need it to export many photos to different directories pretty often, and this would be great help since I could arrange them in collections and collection sets. Then select collection set and export it in a manner that collection set would be main export directory, and each collection within the set would be exported to its own folder within main collection set export folder.
This would be much appreciated feature in near future
Thank you for great product by the way

Creating a Standby Database with the Same Directory Structure

Hello gurus,
I am self-learning the feature Oracle Data Guard, so I am testing it on Oracle 10g R2.
At Oracle documentation there is a section F.4.: Creating a Standby Database with the Same Directory Structure*, that explains how to create a standby database with RMAN but there is something that I don´t understand:
In the standby server, I created a database with the SID equal to production database* with the objetive to have the same directory structure, but when I try to startup nomount the standby database with pfile appear this expected error:
ORA-16187: LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes
So my question is: Is possible have the Same Directory Structure on both: Production and StandBy server?
Thanks in advanced.

Uwe and mseberg: thanks for your quick answers
I have a doubt: How can you have the same directory structure if you have differents SIDs?, for example if you follow the OFA suggestions you would must have:
On Production server: */u01/app/oracle/oradata/PRIMARY/system.dbf*
On StandBy server: */u01/app/oracle/oradata/STANDBY/system.dbf*
Or you created the directory structure manually on StandBy server? For example replacing the string STANDBY* to PRIMARY* before create the database using dbca.
Do you understand my doubt? Excuse me for my english.
Thanks.

Jaxb+classpath+directory structure

Similar Messages

Maybe you are looking for