Skip to Main Content

Java APIs

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Puzzling error from the Javadoc compiler

843810Aug 26 2009
I'm "debugging" Javadoc comments for a couple of packages that my
organization produced. I think I've eliminated all of the errors in my
comments, but a few of the source files yield this error:

java.util.MissingResourceException: Can't find resource for bundle
java.util.PropertyResourceBundle, key doclet.exception_encountered
at java.util.ResourceBundle.getObject(ResourceBundle.java:352)

(there follows a long stack trace)

I researched this on the Web. It appears that the Javadoc compiler
encountered an error, but it couldn't load the property file (the
"resource") that contains the appropriate error message, so it did this
instead. I can't tell what the original error was, or what resource
file Javadoc wants, or where the file is supposed to be.

Can anyone help me diagnose and fix the problem?

Comments

Dude!
Answer

No, "x" does not stand for delete, nor does "wx" mean modify.

Directories normally have execute permission in order to set a directory as a working directory, i.e. to "cd" into it. Setting write permissions (w) but no read (r) on a directory creates a dropbox, where regular users can create, modify and delete files restricted by owner and group permissions, but cannot list directory content.

Base permissions for files are 0666 and 0777 for directories. You also have to consider the umask, which is 0022 for root and 0002 for regular users. Hence the default permissions are 0644 for files and 0755 for directories created by root, and 0664 and 0775 respectively for regular users.

Setting file or directory permissions to 736 (owner/group/all) does not make sense and will give every user read and write access to files, including modify and delete. Setting file or directory permissions to 736 (owner/group/other) does not make sense and will give every user full access who is not owner or matched by group. If you require a more granulated access to files or directories, you need to setup ACL. Please check the man page for setfacl(1).

Marked as Answer by happy10319 · Sep 27 2020
Dude!

I had some doubt and did a few tests. So I wish to correct my previous post:

The permissions are owner, group and other.

However, other permissions apply to everyone unless matched by owner or group.

pastedImage_1.png

For example:

# mkdir box

# chown dude:oinstall box

# chmod 737 box

# ls -ld box

drwx**-wx**rwx. 1 dude oinstall 0 Jun 12 18:13 box

# id oracle

uid=54321(oracle) gid=54321(oinstall) groups=54321(oinstall), etc....

# id toby

uid=54324(toby) gid=54335(toby) groups=54335(toby)

As we can see below group privileges take precedence:

[oracle@localhost ~]$ cd /box

[oracle@localhost box]$ ls

ls: cannot open directory .: Permission denied

[toby@localhost ~]$ cd /box

[toby@localhost box]$ ls

[toby@localhost box]$

Double-check:

# usermod -a -G oinstall toby

# id toby

uid=54324(toby) gid=54335(toby) groups=54335(tobi),54321(oinstall)

[toby@localhost /]$ cd /box

[toby@localhost box]$ ls

ls: cannot open directory .: Permission denied

OS OL 7.6, Filesystem BTRFS.

1 - 2
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Sep 23 2009
Added on Aug 26 2009
0 comments
407 views