A more apt comparison would be to have a record outside the sq.
package. That is akin to an entry being outside the spaces package.
There are many dependencies that should be decoupled and many others
that should not be decoupled, and your example of String in
java.lang.* and java.sql.* is one.
I refer you back to my little list of reasons and ways to decouple and
reasons and ways to increase the cohesiveness of classes. There are
different types of dependencies. The decisions must be thought
through and justified.
Mike
On Dec 12, 2008, at 1:04 PM, Gregg Wonderly wrote:
Michael McGrady wrote:
A space is utterly useless without an entry. Yet, Entry is not in
JavaSpaces. That is a serious architectural no-no, I think.
I guess, I'm still at a loss...
java.sql.PreparedStatement.setString() is utterly useless without a
String. Yet String is not in java.sql. Is that a serious
architectural no-no?
Gregg Wonderly
Michael McGrady
Senior Engineer
Topia Technology, Inc.
1.253.720.3365
mmcgr...@topiatechnology.com