WO and Java 'packages'?
WO and Java 'packages'?
- Subject: WO and Java 'packages'?
- From: Jonathan Rochkind <email@hidden>
- Date: Wed, 21 Apr 2004 16:12:33 -0500
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.
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).
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_? In pageWithName
calls? How about in EOEntity "Class" specifications? 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?
Anything else I'm not thinking of? 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.
--Jonathan
_______________________________________________
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.