• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: WO and Java 'packages'?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WO and Java 'packages'?


  • Subject: Re: WO and Java 'packages'?
  • From: Chuck Hill <email@hidden>
  • Date: Wed, 21 Apr 2004 14:38:51 -0700

On Apr 21, 2004, at 2:12 PM, Jonathan Rochkind wrote:

So I'm still using WO 5.2.1, with Java JRE 1.3.1.

And I must confess, I've never put my code in Java packages. Which I guess means all of my classes are in the default package.

Well, I'm shocked!  :-P


My understanding is that JRE 1.4.x (which newest versions of WO require) pretty much forces me to put my code in explicit packages. Leaving it all in the default package doesn't really work anymore. No problem, I can certainly add a 'package net.whatever.something;" statement to the top of every line of source. (I know better organization would be desirable, but one step at a time).

I thought that was true as well but the default package seems to work just fine. I searched and could find no reference to this requirement. Did we both just hallucinate this?


My question is, how does this effect other WO/EOF stuff that specifies class names as strings? Do I generally need to specify the qualified-with-package class name _everywhere_?
Generally, not if you import the package.


In pageWithName calls?
Only if you have a component with the same name in different packages, otherwise no change is needed.


How about in EOEntity "Class" specifications?
In the EOModel?  Yes, that needs the package.


 What about partial/reusable components?  Does my .wod need to read:
ReusableComponent1: fully.package.qualified.ReusableComponent {
}

How about WOSwitchComponent, do I need to bind it's "WOComponentName" binding to a value that's a package qualified name?

Only if you have a component with the same name in different packages, otherwise no change is needed.


Anything else I'm not thinking of?
KVC won't work with protected / package access ivar if there are no public accessor/mutators.


Some guidance here would be welcome. On generally how moving all of my code into a package (from the unspecified 'default' package) will effect various aspects of the WO/EOF frameworks and my use of them.

The above are the only issues I recall.


Chuck _______________________________________________ webobjects-dev mailing list | email@hidden Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev Do not post admin requests to the list. They will be ignored.


  • Follow-Ups:
    • Re: WO and Java 'packages'?
      • From: Jonathan Rochkind <email@hidden>
References: 
 >WO and Java 'packages'? (From: Jonathan Rochkind <email@hidden>)

  • Prev by Date: Re: WO and Java 'packages'?
  • Next by Date: Re: WO and Java 'packages'?
  • Previous by thread: WO and Java 'packages'?
  • Next by thread: Re: WO and Java 'packages'?
  • Index(es):
    • Date
    • Thread