Create a folder(directory) in java

i need to create a folder on a certain path on the hard drive from the java code..
does anybody have an idea?

Check out the File class

Similar Messages

Creating a new directory in Java

Can anyone tell me how I can create a directory on the C: drive using java code.
Eg:C:\javacode\workspace

new File("/dev/null").mkdirs()

Folder Directory Create

I recently Migrated our sharepoint from windows 2003 to 2008. In doing so I lost Cold fusion and a directory Wizard, This wizard was put in place to create a folder directory out on our network drive when used. Now I have Coldfusion 10 installed on my new sharepoint server, I have brought over all of these directory wizard files but it still does not work. Its like I am missing a certain link in the chain here. Can anyone shed some light on the topic?
The wizard opens up to the first page, which it says next to continue. You would select a company which the code is written to pull a companies list from the network drive, then it creates a folder directory with files in the on that network drive. Now when you lick the initital next button it buttons and takes us to a The website cannot display the page. I still have all the original code files, placed into the same exact directory on the sharepoint server. The sharepoint server is an identical match, but its like somewhere something isnt lined up correctly.
I also have downloaded Coldfusion builder also.

OKay since page 1 actually doesnt do anything I can skip that, and ill start on page 2 and the other esential code files that actually build the directory.
DIRECTORY.CFM
Unable to Determine Parse Mode!
The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:
in Direct Input mode, no MIME Media Type is served to the validator
No known Document Type could be detected
No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document.
No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the document.
As a default, the validator is falling back to SGML mode.
No DOCTYPE found! Checking with default HTML 4.01 Transitional Document Type.
No DOCTYPE Declaration could be found or recognized in this document. This generally means that the document is not declaring its Document Type at the top. It can also mean that the DOCTYPE declaration contains a spelling error, or that it is not using the correct syntax.
The document was checked using a default "fallback" Document Type Definition that closely resembles “HTML 4.01 Transitional”.
Learn how to add a doctype to your document from our FAQ.
No Character encoding declared at document level
No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.
See this tutorial on character encoding for techniques and explanations.
Using Direct Input mode: UTF-8 character encoding assumed
Unlike the “by URI” and “by File Upload” modes, the “Direct Input” mode of the validator provides validated content in the form of characters pasted or typed in the validator's form field. This will automatically make the data UTF-8, and therefore the validator does not need to determine the character encoding of your document, and will ignore any charset information specified.
If you notice a discrepancy in detected character encoding between the “Direct Input” mode and other validator modes, this is likely to be the reason. It is neither a bug in the validator, nor in your document.
↑ Top
Validation Output: 27 Errors
Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"<HTML>
✉
The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.
Line 3, Column 11: cannot generate system identifier for general entity "I" <TITLE>C&I Engineering - Project Directory Wizard</TITLE>
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 3, Column 11: general entity "I" not defined and no default entity <TITLE>C&I Engineering - Project Directory Wizard</TITLE>
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 3, Column 12: reference to entity "I" for which no system identifier could be generated <TITLE>C&I Engineering - Project Directory Wizard</TITLE>
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 3, Column 10: entity was defined here <TITLE>C&I Engineering - Project Directory Wizard</TITLE>
Line 10, Column 21: there is no attribute "TEMPLATE"<CFINCLUDE TEMPLATE="HEADER.CFM">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 10, Column 33: element "CFINCLUDE" undefined<CFINCLUDE TEMPLATE="HEADER.CFM">
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 11, Column 45: invalid comment declaration: found name character outside comment but inside comment declaration
✉
Line 11, Column 1: comment declaration started here
Line 12, Column 35: element "CFINCLUDE" undefined<CFINCLUDE TEMPLATE="MAINAREA.CFM">
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 16, Column 3: invalid comment declaration: found name character outside comment but inside comment declaration--->
✉
Line 14, Column 1: comment declaration started here<!---
Line 20, Column 28: there is no attribute "HEIGHT"<TABLE WIDTH="100%" HEIGHT="100%" BGCOLOR="#D4D0C8">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 24, Column 21: there is no attribute "ACTION"<CFDIRECTORY action="list" DIRECTORY="\\ci-data\shared\PROJECTS"
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 24, Column 38: there is no attribute "DIRECTORY"<CFDIRECTORY action="list" DIRECTORY="\\ci-data\shared\PROJECTS"
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 25, Column 10: there is no attribute "NAME"    NAME="myDirectory"
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 26, Column 10: there is no attribute "SORT"    SORT="Name ASC">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 26, Column 20: element "CFDIRECTORY" undefined    SORT="Name ASC">
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 27, Column 15: there is no attribute "NAME"<CFPARAM NAME="SELECTEDDIRECTORY" DEFAULT="">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 27, Column 43: there is no attribute "DEFAULT"<CFPARAM NAME="SELECTEDDIRECTORY" DEFAULT="">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 27, Column 45: element "CFPARAM" undefined<CFPARAM NAME="SELECTEDDIRECTORY" DEFAULT="">
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 31, Column 17: there is no attribute "QUERY"<CFOUTPUT QUERY="myDirectory">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 31, Column 30: element "CFOUTPUT" undefined<CFOUTPUT QUERY="myDirectory">
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 32, Column 12: "TYPE" is not a member of a group specified for any attribute<CFIF TYPE IS "Dir">
✉
Line 32, Column 15: an attribute value literal can occur in an attribute specification list only after a VI delimiter<CFIF TYPE IS "Dir">
✉
Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".
Line 32, Column 15: element "CFIF" undefined<CFIF TYPE IS "Dir">
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 33, Column 8: an attribute specification must start with a name or name token <CFIF "#NAME#" IS "#UCASE(SELECTEDDIRECTORY)#">
✉
An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).
Line 33, Column 8: element "CFIF" undefined <CFIF "#NAME#" IS "#UCASE(SELECTEDDIRECTORY)#">
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 35, Column 9: element "CFELSE" undefined <CFELSE>
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 54, Column 40: element "CFINCLUDE" undefined<CFINCLUDE TEMPLATE="ACTIONBUTTONS.CFM">
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 57, Column 7: end tag for "CENTER" omitted, but its declaration does not permit this</BODY>
✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.
Line 7, Column 1: start tag was here<CENTER>

New virtual Directory using JAVA

Hello Friends;
I want to create a folder under SAP j2ee engine and i want to upload my files under new folder and use it like
http://portal:port/Newfolder/mynew_photo.jpg
It is possible in iis. For ex. i can create a folder manuel under
c:\inetpub\wwwroot\new_folder
and after i put my files i can use it
http://iisserver:port/new_folder/new_photo.jpg
I have tried this directories
D:\usr\sap\p50\JC01\j2ee\cluster\server0\apps\sap.com
D:\usr\sap\p50\JC01\j2ee\cluster\server0\apps\
D:\usr\sap\p50\JC01\j2ee\cluster\server0\
and i have create new folder but i couldnt use it.
I hope that i have explained my question.
Thanks in Advance
Best Regards

Dear Eray,
              You can use the following Java code to create the Folder (Directory) in the SAP J2EE Engine and add the contents in the Directory
import java.io.*;
class CreateDirectory
   public static void main(String args[])
      try{
    String strDirectoy ="test";
    String strManyDirectories="dir1/dir2/dir3";
    // Create one directory
    boolean success = (new File(strDirectoy)).mkdir();
    if (success) {
      System.out.println("Directory: " + strDirectoy + " created");
    // Create multiple directories
    success = (new File(strManyDirectories)).mkdirs();
    if (success) {
      System.out.println("Directories: " + strManyDirectories + " created");
    }catch (Exception e){//Catch exception if any
      System.err.println("Error: " + e.getMessage());
Rewards Points if useful..
Regards,
N.Jayanth Kumar

Unable to create a folder through java code on weblogic server 10GR3

Hi,
I have java code which creates a folder and writes an XML file in to it.
File saveDirectory = new File(storePath);
if(!saveDirectory.exists()){
System.out.println("directory doesnt exists");
boolean isDirectoryCreated = saveDirectory.mkdir();
System.out.println("directory doesnt exist creating status :"+isDirectoryCreated);
This code works fine on my local weblogic server.Whereas the one installed on Unix box is not.
saveDirectory.mkdir() is unable to create a directory at the given path.
I feel there is some permission problems.
Please let me know what can be done.
Thanks,

I have my Linux/Unix Admin either add me to a group that can do this or create one that can and add me to it.
If you command prompt can you manually do it now?
Best Regards
mseberg

Creating a folder in web application directory?

Hi
I have a web application which contains some jsps and servlets and i am running it on Apache Tomcat 4.1. The name of my application is MyApp which contains all the servlets and jsps.
In order to deploy the application i have placed the MyApp folder in the 'webapps' folder of Tomcat. Now in one of my servlets i.e. 'DirectoryCreator', i am trying to create a folder i.e. 'Directory' in the MyApp folder. The problem is that i dont want to give an absolute path to the File class constructor. The class files of my servlets are in classes folder i.e. MyApp \ Web-INF \ classes.
I have tried:
File f = new File("/Directory");
f.mkdir();
but this creates the Directory folder in my C drive.
Please tell me how i can avoid giving the absolute path.
Thanks.

if the code to create the directory is a servlet, you can use
String path=getServletContext().getRealPath("/");
//getRealPath("/") will return the actual path on your machine of the base directory
//of the webapp. getRealPath("/SomeDirectory/SomeFile") will return the real
//path of SomeFile
File f=new File(path + "/Directory");
if(!f.exists())
f.mkdir();if the code is in a .jsp file simple replace getServletContext(). with application.

How to create a Folder Tree in Exchange Server from a Java progarm.

hi all,
I am using Microsoft Exchange Server 2000. I have a requirement of creating the following things from a Java program.
1) Creating a Folder Tree
2) Creating a Mailbox Store
3) Creating a Public Store
4) Creating a Recipient Policy
5) Creating a Storage Group
6) Creating a Mail-Enabled Recipient
7) Adding a new UPN suffixes
If any of you have worked on such requirement can you please provide me with some information regarding the same.
Thanks & Regards
Anil

Any luck with this Anil?
I would like to query exchange for the list or recipients on a given mailing list.
Please inform if there is any documentation that may be helpful.

How to create a folder with spaces written in Java under Linux?

Hello,
I have a serious problem
I want to run a Linux command using a Java class with the runtime interface, there is a command to create a folder named eg "My Folder", with a space
For create the Unix command is easy to do either:
mkdir My\ Folder
or
mkdir "My Folder"
But how to translate this in Java, I tried with two commands :
Runtime.exec("mkdir My\\ Folder")
Runtime.exec("mkdir \"My Folder\"")
For example :
import java.io.IOException;
public class CreerDossier {
public static void main(String[] args) throws IOException {
Runtime runtime = Runtime.getRuntime();
runtime.exec("mkdir My\\ Folder");
runtime.exec("mkdir \"My Folder\"");
But it's still not working,
For runtime.exec("mkdir My\\ Folder") it creates two folders My\ and Folder
For runtime.exec("mkdir \"My Folder\"") it creates also two folders "My and Folder"
Are there solutions?
Thank you !

But my real problem is how to apply the chmod 777 on a folder containing spacesSo why not say so in the first place?
Runtime.exec ("chmod 777 My\\ Folder");Runtime.exec(new String[]{"chmod", "777", "My Folder"});
That is why I chose the example of mkdirYour reasoning on this point is incomprehensible. You wanted help with A so you asked about B. Just wasting time.

How do I create a folder in the root directory

Hi
How do I create a folder in the root directory?
Once I do that I need to create a note book file in that folder
Any help would be much appreciated
Thanks
Brian

Hi Brian,
Open Macintosh HD in the Finder, then SHIFT+CMD+n
Root Directory is the top level of the drive.

Creating a folder in current workspace using java code

Hi Experts,
I need to create a folder and some file in the workspace of NWDS user. Can someone please suggest how can i find out the workspace of user using JAVA code.
IWorkspaceRoot is not working in NWDS.
Regards
Pranav

Hi Pranav,
Tell me if you want to create this folder at run time or in NWDS while developing application.
If you want to create it at the time of development just change your perspective to Java perspective and from there you can see the entire project structure and from there you can create desired files / folders.
Ninad

How to: Create a folder directly under the KM content 'Root' directory

I need to create a new folder directly under the 'root' directory of the KM content...
If I go to the KM root directory and click on any of the folders in it, I can create new folders.
For example: clicking on the 'documents' folder. Opening it, I can create new folders by clicking on 'Folder' --> 'New' --> 'Folder'.
However, when I am in the root directory itself, the only option under 'Folder' is 'Clipboard'.
How can I create a new folder under the Root? Am I missing a role?
Cheers,
Edwin.

You cannot create a folder under root directory
all the folders that you are seeing under root are KM Repositories.
You need to create a repository and then in that you can create a folder structure.
As an example Documetns is a standard SAP KM repository. You can also create your own repository under
system admin-> system configuraiton->KM->CM-> Repository Managers
There you can get options of creating the repositories
Hope it is clear
also check the below thread that will help you
http://help.sap.com/saphelp_nw70/helpdata/en/e3/923224b24e11d5993800508b6b8b11/frameset.htm
Raghu
Edited by: Raghavendranath Garlapati on Jul 16, 2009 9:39 AM

How to create a Folder using java.

Hi All,
I have a doubt. I want to create a folder using java.
Inputs are the destination where the folder should be created and the name of the folder. Plz help me in this regard.
thanks and regards,
Vincent .R.

check out javadoc for java.io
File reldir=new File("NewDir");//relatively where your program runs
reldir.mkdir();
File absdir=new File("C:/NewDir");//absolute path
reldir.mkdir();
File newdir=new File(absdir,"SubDir");//defines another dir under absdir
newdir.mkdir();
Gil

How to create a folder through java

Hi All,
Can any one give the solution of my prob.
I want to create a folder in windows m/c through java programe .Is it possible.
If yes then kindly suggest me how...?
Thanks In advance
Vikas

String newFolderPath = "C:\\";
String newFolderName = "MyFolder";
String spoonFeeding = newFolderPath + newFolderName;
File f = new File(spoonFeeding);
f.mkDir();

Creating aVirtual directory Using java

Hai ,
I am Using windows XP Operating system, I know how to create a directory using java,
can you please suggest me a procedure to create a virtual(web share ) directory using java.
waiting for your reply
Thanks & Regards,
Naga Raju

Virtual Programmer is in the to share the directory
over the Internet.No, that's a file/web server. :) I see, it's a Microsoft term.

Code to create a folder in java

Hi friends
I want to know how to create a folder in java using files concept.
Can any one send me the code to create a folder in our system using files concept.
Thanks in advance.

[http://java.sun.com/docs/books/tutorial/essential/io/file.html]

Create a folder(directory) in java

Similar Messages

Maybe you are looking for