Hi Dasarath,
you are right that the package structure is probably not the best
possible. At least, it is consistent with the WS-AT parts ;-)
If you don't mind, I'd send you the complete kandula.ba package in one
ZIP instead of splitting it. Even though I verified that every splitted
part compiles cleanly the packaging into patches seems to be a fragile
process :-/
The refactoring of the package structure has influence on the already
checked in parts - config and documentation - so if we modify it now, we
need to patch also these things.
I guess it would be best to first define what the final package
structure should be, and then refactor the classes (AT and BA) to
actually go in there. If it shall be
org.apache.kandula.[at,ba,coordination].[coord,part,initiator,schema]
or the other way round is a decision that needs to be discussed and
made, but does not impact the source code changes that much.
I'd also propose that we put the autogenerated files in separate packages.
Anyways, if we change the package structure, it should be done at the
same time with AT and BA classes. If that is OK with you, we ask you to
commit the current package structure and then start refactoring.
Would the JIRA be a suitable place for patches? As soon as they are
committed they become worthless, so personal email is probably also a
good solution.
Best regards,
-hannes
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
