Case sensitivity in zoneset naming

Very new at this. I embarrassingly created a zoneset with the same name as our active zoneset, except that the name is in lower case, rather than in mixed upper and lower case of the active zoneset. Can I simply enter the syntax: no zoneset name <zoneset name>, and not risk removing the active zoneset?
good zoneset ZoneSet-A-00
bad zoneset zoneset-a-00
Thanks...blush

Good morning,
What you can do is create your own little test case and find out!
1. Create a new vsan
2. add a few ports to the vsan
3. create a new zoneset
4. create another zoneset with upper/lower in the same name
5. delete one and see what happens.
This is one of the best things about vsans. You can do test after test in a completly isolotated environment on the one switch!
Let me know if you need any more info on doing this.
Cheers
Andrew

Similar Messages

  • How can I backup data from a case-sensitive volume to a NON-case-sensitive volume?

    The case-sensitive volume in this instance being a desktop-mounted disk image volume.
    A tragi-comedy in too many acts and hours
    Dramatis Personae:
    Macintosh HD: 27" iMac 3.06GHz Intel Core 2 Duo (iMac10,1), 12 GB RAM, 1 TB SATA internal drive
    TB1: 1 TB USB external drive
    TB2: 2 TB USB to Serial-ATA bridge external drive
    Terabyte: a .dmg disk image and resulting desktop volume of the same name (sorry, I don't know the technical term for a .dmg that's been opened, de-compressed and mounted -- evanescently -- on the desktop)
    Drive Genius 3 v3.1 (3100.39.63)/64-bit
    Apple Disk Utility Version 11.5.2 (298.4)
    Sunday morning (05/08/11), disk utility Drive Genius 3's drive monitoring system, Drive Pulse, reported a single bad block on an external USB2.0 1TB drive, telling me all data would be lost and my head would explode if I didn't fix this immediately. So I figured I'd offload the roughly 300 GB of data from TB1 to TB2 (which was nearly empty), with the intention of reinitializing TB 1 to remap the bad block and then move all its data BACK from TB 2. When I opened TB1's window in the Finder and tried to do a straight "Select All" and drag all items from TB1 to TB2, I got this error message:
    "The volume has the wrong case sensitivity for a backup."
    The error message didn't tell me WHICH volume had "the wrong case sensitivity for a backup," and believe me, or believe me not, this was the first time I'd ever heard that there WAS such a thing as "case sensitivity" for a drive. I tried dragging and dropping some individual folders -- some of them quite large, in the 40GB range -- from TB1 to TB2 without any problem whatsoever, but the majority of the items were the usual few-hundred-MB stuff that seems to proliferate on drives like empty Dunkin' Donuts coffee cups on the floor of my car, and I didn't relish the idea of spending an afternoon dragging and dropping dribs and drabs of 300GB worth of stuff from one drive to another.
    Being essentially a simple-minded soul, I had what I thought was the bright idea that I could get around the problem by making a .dmg disk image file of the whole drive, stashing it on TB2, repairing and re-initializing TB1, and then decompressing the disk image I'd made of TB1, and doing the "drag and drop" of all the files in resulting desktop volume to TB1. So I made the .dmg of TB1, called "Terabyte," stashed that .dmg on TB2 (no error messages this time), re-initialized and then rebooted the iMac from my original Snow Leopard 10.6.1 disks and used Disk Utility to erase and initialize TB1 -- making sure that it was NOT initialized as case-sensitive, and installed a minimal system on TB1 from the same boot. Then I updated that 10.6.1 system to 10.6.7 with System Update, and checked to see that Disk Utility reported all THREE drives -- internal, 1TB, and 2TB -- as Mac OS Extended (Journaled), and no "case sensitive" BS. I also used Drive Genius 3's "information" function for more detailed info on all three drives. Except for the usual differing mount points, connection methods, and S.M.A.R.T. status (only the Macintosh HD internal, SATA 1TB drive supports S.M.A.R.T.), everything seemed to be oojah-***-spiff, all three drives showing the same Partition Map Types: GPT (GUID Partition Table.) Smooth sailing from here on out, I thought.
    Bzzzzt! Wrong!
    When I opened the Terabyte .dmg and its desktop volume mounted, I tried the old lazy man's "Select All" and drag all items from the desktop-mounted drive "Terabyte" to TB1, I got the error message:
    "The volume has the wrong case sensitivity for a backup."
    I then spent the next three hours on the phone with AppleCare (kids -- when you buy a Mac ANYTHING, cough up the money for AppleCare. Period.), finally reaching a very pleasant senior tech something-or-other in beautiful, rainy Portland, OR. Together we went through everything I had done, tried a few suggestions she offerred, and, at the end of three hours, BOTH of us were stumped. At least I didn't feel quite as abysmally stupid as I did at the beginning of the process, but that was all the joy I had gotten after two solid days of gnawing at this problem -- and I mean SOLID; I'm retired, and spend probably 12 hours a day, EVERY day, at the keyboard, working on various projects.
    The AppleCare senior tech lady and I parted with mutual expressions of esteem, and I sat here, slowly grinding my teeth.
    Then I tried something I don't know why I was so obtuse as to not have thought of before: I opened Apple's Disk Utility and checked the desktop-mounted volume Terabyte (Mount Point: /Volumes/Terabyte), the resulting volume from opening and uncompressing the .dmg "Terabyte".
    Disk Utility reported: "Format : Mac OS Extended (Case-sensitive)." Doh!
    Obviously, TB1, the 1 TB USB external drive I'd actually bought as part of a bundle from MacMall when I bought my 27" iMac, and which I had initialized the first day I had the iMac up and running (late November 2009), had somehow gotten initialized as a Case-sensitive drive. How, I don't know, but I suspect the jerk behind the keyboard. Whatever the case, when I created the Terabyte disk image (the drive's original name: when I erased and re-initialized it -- see above -- I renamed it "1TB" for quick identification), the original drive's "Case-sensitive" format was encoded too. So when I tried to drag and drop EVERYTHING from the desktop-mounted volume "Terabyte" to the newly initialized and "blessed" (now THERE's a term from the past!), the system recognized it as an attempt as a total volume backup, and hit me with "The volume [the desktop-mounted volume "Terabyte" -- BB] has the wrong case sensitivity for a backup." And, of course, the reinitialized TB1 was now correctly formatted as NOT "case-sensitive."
    Well, that solved the mystery (BTW, Disk Utility identified the unopened Terabyte.dmg as an "Apple UDIF read-only compressed {zlib}, which is why the .dmg file could be copied to ANY volume, case sensitive or not), but it didn't help me with my problem of having to manually move all that data from the desktop-mounted volume "Terabyte" to TB1. I tried to find a way to correct the problem at the .dmg AND opened-volume-from-.dmg level with every disk utility I had, to no avail.
    Sorry for the long exposition, but others may trip over this "case-sensitive" rock in the road, and I wanted to make the case as clear as possible.
    So my problem remains: other than coal shovel by coal shovel, is there any way to get all the data off this case-sensitive desktop-mounted volume "Terabyte" and onto TB1.
    Not that I know whether it would made any difference or not, one of the things that got me into this situation was my inability to get "Time Machine" properly configured so it wasn't making new back-ups every (no lie) 15 minutes.
    Philosophical bonus question: what's the need for this "case-sensitive," "NOT case-sensitive" option for disk initialization?
    As always, thanks for any help.
    Bart Brown

    "Am I to understand that you have a case-sensitive volume with data that you want to copy to a case-insensitive volume? And the Finder won't let you do it? If that's what the problem is, the reason should be obvious: on the source volume, you may have two files in the same folder whose names differ only in case. When copying that folder to the target volume, it's not clear what the Finder should do."
    Yes, I understand all that... NOW.
    What I had (have) is a USB external 1TB drive (henceforth known as "Terabyte") that I bought with my 27" iMac. I formatted, and put a minimal (to make it bootable) system on Terabyte the same day back in late November 2009 that I set up my 27" iMac. Somehow -- I don't know how -- Terabyte got initialized as "case-sensitive." I didn't even know at the time that there WAS such a thing as "case-sensitive" or "NOT case-sensitive" format.
    Sunday morning (05/08/11), Drive Pulse, a toolbar-resident utility (that's Part of Drive Genius 3) that monitors internal and external drives for physical, problems, volume consistency problems, and volume fragmentation, reported a single bad block on the volume Terabyte, advising me that it would be best if I re-formatted Terabyte ASAP. I thought I could open Terabyte in a Finder window, Select All, and drag everything on the drive to ANOTHER USB external drive of 2 TB capacity (henceforth known as TB2). When I tried to do that, I got an error message:
    "The volume has the wrong case sensitivity for a backup."
    First I'd heard of "case sensitivity" -- I'm not too bright, as you seem to have realized.
    Oddly enough (to me), I could move huge chunks of data, including a folder of 40GB, from Terabyte to TB2 with no problem.
    Then the scenario unfolded per my too-convoluted message: several hours of trying things on my own, including making a .dmg of Terabyte (henceforth to be known as Terabyte.dmg) -- which left me with the exact same problem as described in the previous 4 paragraphs; and my 3 hours on the phone with AppleCare, who at least explained this case-sensitive business, but, after some shot-in-the-dark brainstorming -- tough to do with only one brain, and THAT on the OTHER end of the line --  the very pleasant AppleCare rep and I ended up equally perplexed and clueless as to how to get around the fact that a .dmg of a case-sensitive volume, while not case-sensitive in its "image" form (Terabyte.dmg), and thus able be transferred to TB1 or TB2 with no problems whatsoever, when opened -- either by double-clicking or opening in Disk Utility -- produced a desktop-mounted volume (henceforth known as the volume "Terabyte," the original name of the case-sensitive volume from which TB1.dmg had been made) that had the same case-sensitivity as the original from which it was made.
    In the meantime, having gotten the data I needed to save off the physical USB "case-sensitive" volume Terabyte in the form of Terabyte.dmg, I erased and re-initialized the physical USB "case-sensitive" volume Terabyte, getting rif of the case sensitivity, and renaming it TB1. But it all left me back at square one, EXCEPT I had saved my data from the original "Terabyte" drive, and reformatted that drive to a NON- case-sensitive data now named TB1. The confusion here stems from the fact that problem case-sensitive drive, from which I made Terabyte.dmg, was originally named "Terabyte". When I re-initialized it as a NON case-sensitive drive, I renamed it TB1. I'm sorry about the confusing nomenclature, which I've tried to improve upon from my original message -- usual text-communication problem: the writer knows what he has in mind, but the reader can only go by what's written.
    So, anyway, I still have the same problem, the desktop-mounted volume "Terabyte" still cannot be transferred in one whole chunk to either my internal drive, TB1, TB2, as the Finder interprets it as a volume backup (which it is), and reads the desktop-mounted volume "Terabyte" as case-sensitive, as the original volume -- from which the disk image Terabyte.dmg was made -- had been at the time I made it. 
    "As long as that situation doesn't arise, you should be able to make the copy with a tool that's less fastidious than the Finder, such as cp or rsync."
    I'm afraid I have no idea what "cp or rsync" are. I'd be happy to be educated. That's why I came here.
    Bart Brown
    Message was edited by: Bartbrn
    Just trying to unmuddy the water a bit,,,

  • Print dialog options in case sensitive file system

    Since changing the file system running Lion and Mountain Lion from Mac OS Extended (Journaled) to Mac OS Extended (Case-sensitive, Journaled), certain features in print dialogs have disappeared.
    Particularly the option to print notes with slides in Microsoft Powerpoint are gone. Also, when choosing to print only 1 (or more, but not all) of multiple pages in Microsoft Word, the printer will nevertheless print all pages.
    This problem occurs on printers of different brands, i.e. HP, Lexmark, Brother.
    I was able to determine this problem by reproducing the issue on a cleanly installed Macbook Pro with OS X 10.8 formatted as Mac OS Extended (Case-sensitive, Journaled) vs a cleanly installed Macbook Pro with OS X 10.8 formatted as Mac OS Extended (Journaled), not Case-sensitive.
    Has anyone else had the same problem and maybe a solution?

    I just fixed this on my Mac. It is a bug in Microsoft Office... the Printer Dialog Extension (PDE) for Powerpoint is located in a directory named "Plugins", but PowerPoint is looking for it in "PlugIns". This obviously does not work in a case-sensitive filesystem.
    Here are the steps to fix the issue:
    http://apple.stackexchange.com/a/119974/69562

  • How can I transfer my iphoto library from a Mac OS Extended (Case-sensitive, Journaled) harddrive to a Mac OS Extended (Journaled) hard drive?

    Community,
    Every time I try to transfer my iphoto library from a Mac OS Extended (Case-sensitive, Journaled) harddrive to a Mac OS Extended (Journaled) hard drive, I receive the attached message: "You can't copy 'iPhoto Library' because it has the same name as another ideon on the destination volume, and that volume doesn't destinguish between upper- and lowercase letters in filenames."
    My theory is, if I am able to unpackage my iphoto library, I can transfer each folder one at a time so that I can trouble shoot any "duplicates." Will this work?
    Let's say that works. How can I repackage the library so iphoto recognizes it?
    Is there a better way?
    Thank you,
    Jonathan

    Can we assume that I don't have any naming conflicts? Clearly there are or else I wouldn't get the error I'm getting.
    The error doesn't mean you have name conflicts. It means that the Finder won't take the chance that you might have them.
    You're suggesting that all I would need to do would be to use Carbon Copy Cloner to transfer the files from the case-sensative harddrive to my Extended Journaled harddrive?
    Yes. But I would just use the built-in rsync shell command. First, back up all data if you haven't already done so. Launch the Terminal application by entering the first few letters of its name into a Spotlight search. Copy or drag -- do not type -- the line below into the Terminal window, then press the space bar:
    rsync -aE --delete
    Now drag the iPhoto library you want to copy into the window. You should have something like this:
    rsync -aE --delete /Users/you/Pictures/iPhoto\ Library
    Drag the Pictures folder on the destination volume into the window. Now you have this (line will wrap on the page):
    rsync -aE --delete /Users/you/Pictures/iPhoto\ Library /Volumes/something/Users/you/Pictures
    Press return. The copying operation will start. When it finishes, you'll see a new dollar-sign ("$") prompt below what you entered. If there were no errors, you're done.

  • Case sensitive table names and column names in 8i or 9i databases

    Hi everybody,
    I've got a couple of business-side colleagues who insist that Oracle table and column names are case sensitive. That is, there is a setting in the set up of a database that lets you pick if table and column names are case sensitive. For example, this would mean that there could be a table named EMP in a given schema schema plus a table named emp in that same schema.
    Can this be true? I'd be surprised of course, but I've been surprised before.
    Thanks for any direction.
    -- Bill Loggins

    You can do it, but I would avoid it like the plague.
    SQL> create table "a" (b date);
    Table created.
    SQL> create table "A" (b date);
    Table created.
    I think I would refuse to work on a database where this has been used !

  • Problems retrieving backup from Time Machine, Case-sensitive HD

    Hello.
    I'm trying to manually retrieve the information I got in a Time Machine, but for some reason I kept getting an error saying that there were files that were going to the same location were named in the same way. After checking a couple of things I noticed that, somehow, the external HD was Case-sensitive, so I'm assuming that, instead of +File, File 01 File 02+ it's sorted out like +File, file, filE+, and since the computer's HD is normal it's having a conflict with those file names.
    That being said, is there a way to fix this? What I'm trying to move is an iTunes and iPhoto Library, "probably" iTunes could be done manually, but in iPhoto there's over 10 GB of pictures and I'd probably take a looooong while to fix it manually.
    Any work around?
    Thanks!

    Hi Adrian ...
    Let me see if I can help ...
    I'm trying to manually retrieve the information I got in a Time Machine, ...
    How? With the TM App or from the Finder?
    but for some reason I kept getting an error saying that there were files that were going to the same location were named in the same way.
    It's just letting you know that the original file, on the System HD, still exists and wants your permission to over write the original file with the TM file. Backing up your System HD to TM should not have changed any of the original file names. If TM had changed the Case when backing up from your System then TM Restore would have duplicate these files/folders without even asking you.
    That being said, is there a way to fix this?
    Yes. After you have restored the files/folders that you want to keep you can reformat the TM HD. Or try one of my tricks which is to just reformat the free space. Use the Mac OS X Extended (Journaled).
    Good Luck.
    Buzz

  • File System Case Sensitive - breaks Write-Once

    I don't find a System property that denotes if the file system is case sensitive.
    If I want a FileFilter to behave as the user is expecting - it must know if the file system that it is running on is case sensitive. For example: On a DOS system the file apple.txt should be returned with the file PEACH.TXT by a FileFilter that is accepting *.TXT files. But on a Unix system only the PEACH.TXT would be returned (case sensitive).
    How would I make my FileFilter a true write-once-run-anywhere class?
    What am I missing?
    David

    For a file filter,
    you can get the file name and convert it to lowercase,
    then compare to a lowercase extension. It's not like
    that will rename the file, the file will still have
    whatever name the file has. However for a FileFilter that is case sensitive - there is a difference in what a File.listFiles(new ExtensionFilter("txt")) returns. And one can not just decide that it doesn't matter.
    Here's a specfic example. On a case insensitive system what is the next file in the sequence of:
    File.001, File.002, File.003, file.004
    Answer: fILE.005 - is valid
    But on a case sensitive system if one uses a FileFilter to find all the files that match "File".* then the answer is "File.004" - ONLY ONE answer, and creating this file will not (should not) overwrite the file.004!
    Seems to me one needs to match the FileFilter to the underling OS - because chances are the user is expecting OS file system naming conventions. If the user doesn't know what file system (and can't know - like on a web server app) then the system better be smart enough to not mess up and clober files.
    So it appears to me that a programmer needs to be able to ask the System what it's file system convention is. And sure I could guess based on some other properties (System.os.name or as Sun did based on file.separator) - but I was hopeful that I didn't need to GUESS.

  • CS5 install on case-sensitive file system - can't choose different drive (Mac OS)

    I just upgraded my macbook pro to a new drive and 10.6, and chose 'case sensitive' HFSX, 'cause I'm a heavy command line user and wanted the maximum BASH experience.
    I'm trying to install the CS5 demo to try some web design tools, and the installer immediately says "Installation to case-sensitive drives is not supported. Please choose a different drive location to install." So case-sensitive drives aren't supported; crappy but fair enough.
    The error message leads me to think that I can just choose a non-case-sensitive drive to install to, but I never get a chance to pick one - I click on the installer and it goes straight to the error message.
    So - how do I pick a different drive to install to? Am I just an idoit, is there no way to select a different drive, or will it not install on a system that even BOOTS from a c.s. drive, regardless of the format of the drive that CS5 is installed to?
    I called the support number, and the poor fellow on the other end suggested I re-download the demo, and if the new download fails call Apple support to report my 'drive error'.
    I'm hoping to avoid an entire backup-reformat-restore and lose CLI compatibility just to try some demo software.
    ch

    That is part of why I would prefer case sensitive by default.   I know some server packages do the folding for you, same as some web servers do not differentiate between 'htm' and 'html' when people type in requests, but most of the time the backend server is going to be case sensitive and it is not safe to assume (or hope) that the service will fix things.  Compensating for mistakes is fine, but allowing such silent corruption is not a terribly laudable things and it encourage people be careless.
    Every once in a while I do encounter someone submitting some work where their configuration values and file names do not match, and 'well my laptop silently fixes it for me since it does not care' is a poor excuse.  And if I sent broken filenames upstream or even worse commit them to be used on a server, that is a pretty significant professional failure.
    Back to Adobe specifically, I have been trying the suggestion on poster mentioned in where one installs the Adobe applications to a case insensitive drive then copy over the installed files.  This does not quite work out of the box, but for reasons I would be hard pressed to believe are Apple's fault.
    For instance the first error I encounter is the inability of Bridge to load:
    "@executable_path/../Frameworks/WRServices.framework/Versions/A/WRServices"
    When I go look inside the app directories I can see that in Bridge the file has been named 'awrservices', but in Illustrator it is correctly named AWRServices.   So it looks more like a problem in whatever version control they are using.  The only way I can picture (which my adminitialy limited knowledge of what I am sure is a large and complex project with all sorts of legacy issues) that the installer toolchain factors in as a problem is if they have mismatches in their own scripts/packaging and have been depending on HFS's bad behavior to hide the problem.  I can understand not wanting to invest the time to pay down the technical debt on such an issue, but having such errors in your configuration causes long term headaches.
    And I say this as someone who worked on just such a project, moving a software suite that had legacy code stretching back longer than Adobe has existed as a company.  This conversion included moving from a case insenstive filesystem to a case sensitive one and yeah, there were lots of problems that the old FAT32 system hid from us, but it really paid off over the long run to fix them rather than try to twist the code to compensate.
    Having said that, if the problem is really that they do not want to go update their filenames (in version control or config files), then you can always add folding to your loaders.  I have had to do that a few times due to upstream people developing on case insensitive systems and sending data files with incorrect file names.  This is an old class of problem, and while I can empathize with the struggles project managers have trying to get approval for paying down technical debt, the problem never gets better on its own and usually gets worse.
    Which is why I responded with so much grump to the 'I never needed it' argument since that is exactly the type of customer comment that marketing tends to point to in order to push such things off the schedule.  This is the type of thing where the customer does not really know what they want because they are already accustomed to broken behavior and most of the problems are hidden from their immediate view.  It is easy to cover up the limitations since modern UI (and their search capabilities) can handle this. 
    It is not just arcane developers stuff, and it is the same transition that people have made with things like spaces, quotes, and parentheses, where years ago users believed they had no need for them since they were not using them, but they were only not using them because they did not work.   Today try to tell a modern user they can not put (, ", ) or even ' ' in their filenames and they would rightly question why this piece of obvious functionality is not working since today they are used to it working and no longer automatically compensate for it.
    I also find it ironic that by default OSX hides a number of file extensions, so from the user's perspective you can have multiple files with the exact same name displayed to them, so you can get display issues where 'foo' is the same as 'foO' if both have .txt, but 'foo' and 'foO' are not the same if one has .txt while the other is .pdf.  Add to this confusion cases like 'foo.txt' and 'foo.pdf" both being shortened to 'foo'.

  • What is HFS case sensitive file system

    What is HFS case sensitive file system?

    FlowerChick,
    a HFS case-sensitive filesystem would allow you to have files that differ only by case in the same folder; for example, you could have different files named “FlowerChick” and “flowerchick” in the same folder. On a case-insensitive filesystem, that wouldn’t be allowed.

  • Objects name case sensitive

    Hi Dear;
    to call any object in SDK, i have to write the object name(index) as case sensitive.
    if there any way to call these objects without case sensitive?
    Ex: if i have a UDF named U_BPDrv and i try to get it as U_BPDRV i get an error.
    how can i resolve this error?
    thank you Dear;

    Hi Lita,
    i tried it now. UDF field is named as u_Test.
    When I call SELECT ordr.u_Test so the result is the same as when I call SELECT ordr.U_TESt, so here is it not case sensitive. When I try get result from recordset as rs_ordr.Fields.Item("U_TeSt").Value() it give no error. When I bound result from recordset to matrix as
    column.DataBind.SetBound(True, "@KZ", "u_TEst") - no error as well.
    Everything was tested with no binary collation on db.
    So I`m persuaded, that in this cases it depends on sql server and not on SDK.
    Petr

  • Explorer Search Case Sensitive?

    The search functionality in Explorer is case sensitive.  Is there a way to make the search functionality be case insensitive?

    Hi Karen,
    Thanks for the reply.  This isn't about Bex though it is about Business Objects Explorer.  I originally posted this in the Other Business Objects forum but a forum Admin moved it here because they said I had posted to the wrong forum.  It was in the correct forum to begin with.  If SAP were more thoughtful about how they named products they would not have created this confusion by renaming Polestar to be the same name as an exisating product.
    Tom

  • Wsdl2service exception class: case sensitive problem

    When I run wsdl2service on my .wsdl, file the generated class is a different case than the class name(CatalogException vs catalogException). The exception classes will not compile. Any ideas?
         <wsdl2service
         wsdl="ws_20/CatalogQueryService.wsdl"
         destDir="${src_gen}"
         typeMappingFile="${autotype}/types.xml"
         packageName="mil.dcgs.mdf.webservice"
         generateImpl='true'>
         <classpath refid='project.classpath'/>
         </wsdl2service>
    ================================================
    [wsdl2service] Generating web service from wsdl ws_20/CatalogQueryService.wsdl
    [wsdl2service] C:\views\dib\DIB\src_gen_mort\mil\dcgs\mdf\webservice\catalogException.java:9: class CatalogException is public, shou
    ld be declared in a file named CatalogException.java
    [wsdl2service] public class CatalogException extends java.lang.Exception
    [wsdl2service] ^
    [wsdl2service] C:\views\dib\DIB\src_gen_mort\mil\dcgs\mdf\webservice\dataAccessException.java:9: class DataAccessException is public
    , should be declared in a file named DataAccessException.java
    [wsdl2service] public class DataAccessException extends java.lang.Exception
    [wsdl2service] ^
    [wsdl2service] 2 errors
    [wsdl2service] java.io.IOException: Compiler failed executable.exec
    [wsdl2service] at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:470)
    [wsdl2service] at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
    [wsdl2service] at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
    [wsdl2service] at weblogic.webservice.tools.build.internal.CompilerHelper.compileFiles(CompilerHelper.java:80)

    Windows filenames are not case-sensitive. So you can't have both EventSite.class and eventsite.class in the same directory. What you see there probably also involves Windows 98's habit of messing with the capitalization of file names (try creating a directory with the name of IBM, not Ibm).

  • Apache is so case sensitive

    I have no html on my server so everything is indexed. When you try to get to a specific Volume/Folder you can only do it by typing in everything exactly as it is typed in the file structure with intial caps.
    I cannot duplicate this on two other backup XServers and I need to eliminate it from my production server.
    Any suggestions would be most welcome!

    Thats the way mac OS is. I just tried on my test server to allow me to view the directory on my raid from the web and I got the same error, although i just typed in http://ipaddress, I wonder if I try the whole path if that will work, even though in the config that is where I am pointing it to, so imo no it will not work.
    Sorry to ramble, is there a way to fix this? How is the folder locally? Art or art? have you tried to change that?
    Also here just dug this up in my files:
    How can I make all my URLs case-insensitive with mod_rewrite?
    You can't! The reasons are: first, that, case translations for arbitrary length URLs cannot be done via regex patterns and corresponding substitutions. One needs a per-character pattern like the sed/Perl tr|..|..| feature. Second, just making URLs always upper or lower case does not solve the whole problem of case-INSENSITIVE URLs, because URLs actually have to be rewritten to the correct case-variant for the file residing on the filesystem in order to allow Apache to access the file. And the Unix filesystem is always case-SENSITIVE.
    But there is a module named mod_speling.c in the Apache distribution. Try this module to help correct people who use mis-cased URLs.
    So Mac is built off NIX so no... That should solve it..
    EDIT: You can make SAMBA handle you www requests but I wouldn't for security. Or make a redirector...

  • Installation of Photoshop CS6 (Extended) on Case-Sensitive Drives

    I understand that under the "system requirements" the Adobe website says that you can't install PS CS6 (Extended) on case-sensitive drives (I'm using a MacBook Pro, OS X v. 10.7.4).  This seems to have been the case at least since CS5.
    I didn't see this, and I bought (quite excitedly) the update from CS PS5 (Extended) to PS6.  I had NO PROBLEM installing PS5 on this drive. 
    Of course, as other users have indicated, the installer refuses to let you install on a case-sensitive drive (e.g., no options to install on another disk).  There is also no mention that CS6 must be installed on the boot drive.
    Requiring installation on the boot drive has serious implications for those of us who require case-sensitive drives for other work; I don't want to have to reboot from another drive when I use PS, and switch back and forth -- that's simply foolish.
    From my point of view (as a user, granted), this is lazy programming, and this needs to be fixed ASAP.  At least in my case, I have a $400 lump of software just taking up space, when I want to be up to my eyeballs enjoying PS6 in all it's glory.
    Outside an Adobe fix, I don't see a solution to this problem.  If I wipe my drive, format it as not case-sensitive, then I lose functionality for other critical work.  Further, I'm not sure that the process of  wiping the drive, formating it as non case-sensitive, and restoring everything from TimeMachine would even work (since the backup material is coming from a case-senstive drive and trying to go to a drive that is not case-sensitive).
    The REALLY frustrating part is that I've installed Photoshop 3, 4, and 5 (and from much, much further back) on case-sensitive disks -- all with no problems.  It's only now that the issue smacks me in the face.
    There's got to be a work-around, if not a "real" solution.
    Whatever help you might be able to offer would be greatly appreciated; details can be sent to cdretk at gmail dot com.
    I have hope, and I thank you in advance.

    Whether it is Apple or Adobe's work flow isn't the issue.  Between the two
    of them, if they are going to support both naming variants, then at both
    Adobe and Apple:
    1.  You MUST use the same case file names.  (E.g. FrameWorks and not
    Frameworks) EVERY time.  And refer to them in your programs and
    configuration files the same way EVERY time.
    2.  You may NOT in your development code use different but case invariant
    file names for different files.
    3.  Your libraries must do the Right Thing.
    What gets me is that few others seem to have this problem.  Perhaps Adobe
    needs to abandon Apple development software, and roll their own outside the
    standard system libaries.
    Further searching shows that it is not a problem unique to Adobe.  The
    games BeJeweled, and BZFlag have this issue, as does the Steam game support
    systems.
    In every case I've run down to date, it has been a violation of #1.
    Now there are workarounds:  A script that creates appropriate symlinks on
    case sensitive file systems would be fairly easy.   It would impose some
    minor amount of extra overhead.
    I bought a copy of Adobe Creative Suite.  I returned it unopened.  You lost
    a sale.  Furthermore, until it is fixed, I will mention this at every
    opportuity as an exampled of a combination of sloppy workmanship, and
    customer indifference on the part of Adobe.
    Tell your bosses, Chris, they need to fix this.
    Respectfully,
    Sherwood of Sherwood's Forests

  • Still need help with case sensitive strings

    Hello guy! Sorry to trouble you with the same problem again,
    but i still need help!
    "I am trying to create a scrypt that will compare a String
    with an editable text that the user should type to match that
    String. I was able to do that, but the problem is that is not case
    sensitive, even with the adobe help telling me that strings are
    case sensitive. Do you guys know how to make that comparison match
    only if all the field has the right upper and lower case letters?
    on exitframe
    if field "t:texto1" = "Residencial Serra Verde"then
    go to next
    end if
    end
    |----> thats the one Im using!"
    There were 2 replys but both of them didnt work, and the
    second one even made the director crash, corrupting even previously
    files that had nothing to do with the initial problem..
    first solution given --
    If you put each item that you are comparing into a list, it
    magically
    makes it case sensitive. Just put list brackets around each
    item.
    on exitframe
    if [field "t:texto1"] = ["Residencial Serra Verde"] then
    go to next
    end if
    end
    Second solution given--
    The = operator is not case-sensitive when used on strings,
    but the < and > operators are case-sensitive.
    So another way to do this is to check if the string is
    neither greater than nor less than the target string:
    vExpected = "Residencial Serra Verde"
    vInput = field "t:texto 1"
    if vExpected < vInput then
    -- ignore
    else if vExpected > vInput then
    -- ignore
    else
    -- vExpected is a case-sensitive match for vInput
    go next
    end if
    So any new solutions??
    Thanks in advance!!
    joao rsm

    The first solution does in fact work and is probably the most
    efficient way
    of doing it. You can verify that it works by starting with a
    new director
    movie and adding a field named "t:texto1" into the cast with
    the text
    "Residencial Serra Verde" in the field. Next type the
    following command in
    the message window and press Enter
    put [field "t:texto1"] = ["Residencial Serra Verde"]
    You will see it return 1 which means True. Next, make the R
    in the field
    lower case and execute the command in the message window, it
    will return 0
    (true).
    Now that you know this works, you need to dig deeper in your
    code to find
    what the problem is. Any more info you can supply?

Maybe you are looking for