Package hierarchy depth limitation

Question

Consider the following:
          Version of WebLogic Server and service pack: 5.1.0 SP5
          Operation system: Solaris 2.7
          JDK version: Solaris_JDK_1.2.2_05a
          I try to instantiate a bean in a JSP which is in a package more than two
          levels deep,
          e.g. in package inventa.clareon.netdaemon.entityBeans
          When I try this, I get the following error:
          Error 500--Internal Server Error
          From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
          10.5.1 500 Internal Server Error
          The server encountered an unexpected condition which prevented it from
          fulfilling the request.
          The same thing happens after if I move the class up to
          inventa.clareon.netdaemon, change the package declaration in the .java
          source to reflect the new package name, recompile and change the class
          spec in the jsp:useBean directive in the .jsp source to reflect the new
          location.
          However, if I change it to two levels deep (doing all of the above) to
          inventa.clareon, it works fine.
          It looks like there is a package hierarchy depth limitation with
          WebLogic 5.1.0 SP5. Has anyone else seen this problem or does anyone
          have any workarounds?
          

Answer 1

Right, but what I was wondering is if an object in a given package that is in a subdirectory (com.company.levelone.leveltwo) of another given package (com.company.levelone) is accessible from that package (com.company.levelone).
But, it was a lazy question, since I could have figured it out for myself, given some time to actually write up the files. Which I did. And for posterity, here is what I discovered:
Just because a package (com.company.levelone.leveltwo) is "within" another package (com.company.levelone), doesn't make those objects available to that package (com.company.levelone objects cannot just access objects in com.company.levelone.leveltwo). Each is technically a separate package even though they may share a directory hierarchy, and each must be imported into the other.
Of course, this all makes sense when you ask yourself -- do the package declarations at the top of the file match? If not, then they are not in the same package.
(PS: this is a self-observation, so if I'm wrong, please correct me!)