> import DerivedClass;
You used to be able to do that.
You now need to include DerivedClass in a package.
Main Topics
Browse All TopicsHi
I have a base class in package hub, let me say hub.BasedClass
I have derived class in default package which is DerivedClass.
DerivedClass extends hub.BasedClass in package hub. Is it possible that there is statement in BasedClass: import DerivedClass.
Just like:
package hub;
import DerivedClass;
abstract public class BasedClass {
.......
}
import hub.BasedClass;
public class DerivedClass extends BasedClass {
......
}
Thanks.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hi Guys:
There is nothing wrong that I put 'import hub.BaseClass' in DerivedClass. The weired thing is that before we have DerivedClass, we should already have BaseClass since DerivedClass extends BaseClass but why in BaseClass, there has statement 'import DerivedClass'. This is cross reference which make two classes compiling problem. Actually there are reverse-engineering classes from our previous codes. We need to find out why. If they are in same package, there is no problem but we can't change the package structure (or change the design). If BaseClass is in package hub and DerivedClass is in default package, then DerivedClass extends BaseClass with statement 'import hub.BaseClass'. This is normal. It should not be problem. The stranged is that there is statement 'import DerivedClass' in BasedClass. It is not necessary but I don't know if it is wrong because those classes compile fine. I just don't understand. I hope that you guys catch my points. Thanks.
Business Accounts
Answer for Membership
by: CEHJPosted on 2004-07-13 at 14:12:33ID: 11543400
>>import DerivedClass;
shouldn't be there. The directory structure should reflect the package structure and the classes should be in the right places