Hello Shankar,
comments inline...
In preparation for the Metro-based version of the stocktrader demo I have
crawled around the Java code. A first past plan is (no attempt to
do any code sharing or refactoring at this time):
- Create the service side Java artifacts from the WSDLs at
contrib/stocktrader/java/business_service/resources/META-INF
contrib/stocktrader/java/order_processor/processor-service/resources/[
msec | nosec ]/META-INF/
- Adapt hand-written code at
contrib/stocktrader/java/business_service/src/org/wso2/stocktrader/
contrib/stocktrader/java/order_processor/processor-service/src/org/wso2/stocktrader/
to work with Metro (initially using MSSQL).
In other words, create the services from WSDL then supplying the
business/DB logic using hand-written code (and NOT attempting to use
ANY of the generated code).
Does that plan sound reasonable?
Yes. That is perfect.
Good.
Why checkin a generated file?
After generating the file, we might do some modifications (like giving
policy, giving service class name, etc.) Also, we don't generate code at the
compile time, rather generate beforehand and check in all the generated
files.
I would like to suggest that having generated code does not promote ease-of-use
of the project nor give a good first impression for others. It seems to me that
just have the WSDL and the business logic should suffice with ANT or MAVEN
scripts to generate all the rest. As far as a person building a service or
client is concerned, they should only have to deal with the WSDL and the
business logic. All else is infrastructure.
We will proceed along those lines.
Thanks,
Harold
