because each pojo is local and has its own importcontext.

the packagename gets changed via generated-class meta attribute.

if we want to generate both outputs (base class and real class) we probably need a way to control if the importcontext is initialized with the generated-name or just the plain package name.


regarding how much that needs to be done to make dao independent i would need to go through the code for.

sure, why don't you think i'm going to fix that ?

I agree that BasicPojoClass, as a mapping wrapper is a good place for computing the package of the (generated or supplied) pojo class.

Even when we're generating another class, we may need to access it.

But when BasicPojoClass is called for retrieving pojo details, while
generating another class, the (needed) import context is not pojo's.

When we're generating the pojo, then the import context is the package of the pojo. That's particular case where the referred class and the generated class are the same.

When we need to deal with imports, we are concerned with the generated class, not the referred class.

Also when generating *one* class, we need an import context too, should we access BasicPojoClass to get it ?

no, you create your own ImportContext