Damitha Kumarage wrote:
Hi,
Currently we have followed axis2 java project folder structure so that
we have
modules
|
|-----------------------------------------------
|
core
----------------|------------------------
| | |
context description engine
I suggest that we replace path beginning from core as engine. Then we
have all core related files in engine.
This is similar to axis c++ folder structure where we have common,
soap, wsdl, engine , xml, util etc
regards
damitha
I also have few problems rationalizing some of the package names in
Axis2 Java.
There was a vote yesterday on Java list on replacing
s/ServiceDescription/AxisService/
s/OperationDescription/AxisOperation/
s/ServiceGroupDescription/AxisServiceGroup/
but when I asked what happen to the package name, no one answered. I can
understand the rationale for class name changes, but that means there is
something wrong with the package name too. May be java code is grown
enough it is hard to change the package names now.
While it is good to have our own names to modules, we also have to keep
in mind that Java code itself is the latest documentation available to
us on Axis2 architecture. So if we are to change the module names we
better document the mapping between our names to the Axis2 architecture
clearly, else if there is a change at some point, we will have trouble
mapping it into our implementation.
Thanks,
Samisa...
