[Wsf-general] Dataservice implementation details

[Chamil Thanthrimudalige]

hi all,

Implementation needs a new Deployer and a new MessageReceiver. The
new Deployer will be called when a file with extension "dbs" is
dropped in to the directory "db_services". I am not sure whether this
is the best folder name and extension to use. So if some one has any
suggestions please let me know.

The Deployer will read the configuration file for the service and
create a DBInfo object from it with the relevant details. It will
then set this as parameter in the new AxisService object. An instance
of DBMessageReceiver is attached to all the operations that are created.

All processing code will be in a static utility class called DBUtils.

Any feedback about this design is most welcome.

Best Regards,
Chamil Thanthrimudalige

[Sanjiva Weerawarana]

Do you still create a subclass of AxisService? If you're putting all the
state in the AxisService object itself then this sounds fine to me.

Deepal can you take a look please? This is in your domain :).

Sanjiva.

Post by Chamil Thanthrimudalige
hi all,
Implementation needs a new Deployer and a new MessageReceiver. The new
Deployer will be called when a file with extension "dbs" is dropped in
to the directory "db_services". I am not sure whether this is the best
folder name and extension to use. So if some one has any suggestions
please let me know.
The Deployer will read the configuration file for the service and create
a DBInfo object from it with the relevant details. It will then set this
as parameter in the new AxisService object. An instance of
DBMessageReceiver is attached to all the operations that are created.
All processing code will be in a static utility class called DBUtils.
Any feedback about this design is most welcome.
Best Regards,
Chamil Thanthrimudalige
_______________________________________________
Wsf-general mailing list
http://wso2.org/cgi-bin/mailman/listinfo/wsf-general

[Chamil Thanthrimudalige]

Post by Sanjiva Weerawarana
Do you still create a subclass of AxisService? If you're putting
all the state in the AxisService object itself then this sounds
fine to me.

No Sub classes now. I am inserting all stuff into one object and
inserting that into the new AxisService object. [It is easy for me to
access the data that way, as opposed to adding a parameter for each
and every value.]

I had a chat with Deepal about this and he was ok with this new design.

Best Regards,
Chamil Thanthrimudalige

Post by Sanjiva Weerawarana
Deepal can you take a look please? This is in your domain :).
Sanjiva.

Post by Chamil Thanthrimudalige
hi all,
Implementation needs a new Deployer and a new MessageReceiver. The
new Deployer will be called when a file with extension "dbs" is
dropped in to the directory "db_services". I am not sure whether
this is the best folder name and extension to use. So if some one
has any suggestions please let me know.
The Deployer will read the configuration file for the service and
create a DBInfo object from it with the relevant details. It will
then set this as parameter in the new AxisService object. An
instance of DBMessageReceiver is attached to all the operations
that are created.
All processing code will be in a static utility class called DBUtils.
Any feedback about this design is most welcome.
Best Regards,
Chamil Thanthrimudalige
_______________________________________________
Wsf-general mailing list
http://wso2.org/cgi-bin/mailman/listinfo/wsf-general

--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
"Oxygenating the Web Service Platform."

[Deepal Jayasinghe]

Chamil's approach seem fine with me since he store the DBInfo as a
parameter . Any way I would like to see what there in the DBInfo as well
as the Deployer, do you have the code somewhere ?

Thanks
Deepal

Post by Sanjiva Weerawarana
Do you still create a subclass of AxisService? If you're putting all
the state in the AxisService object itself then this sounds fine to me.
Deepal can you take a look please? This is in your domain :).
Sanjiva.

Post by Chamil Thanthrimudalige
hi all,
Implementation needs a new Deployer and a new MessageReceiver. The
new Deployer will be called when a file with extension "dbs" is
dropped in to the directory "db_services". I am not sure whether this
is the best folder name and extension to use. So if some one has any
suggestions please let me know.
The Deployer will read the configuration file for the service and
create a DBInfo object from it with the relevant details. It will
then set this as parameter in the new AxisService object. An instance
of DBMessageReceiver is attached to all the operations that are created.
All processing code will be in a static utility class called DBUtils.
Any feedback about this design is most welcome.
Best Regards,
Chamil Thanthrimudalige
_______________________________________________
Wsf-general mailing list
http://wso2.org/cgi-bin/mailman/listinfo/wsf-general

[Chamil Thanthrimudalige]

hi,

I'l check in the code this weekend.

Best Regards,
Chamil Thanthrimudalige

Post by Deepal Jayasinghe
Chamil's approach seem fine with me since he store the DBInfo as a
parameter . Any way I would like to see what there in the DBInfo as well
as the Deployer, do you have the code somewhere ?
Thanks
Deepal

Post by Sanjiva Weerawarana
Do you still create a subclass of AxisService? If you're putting all
the state in the AxisService object itself then this sounds fine to me.
Deepal can you take a look please? This is in your domain :).
Sanjiva.

Post by Chamil Thanthrimudalige
hi all,
Implementation needs a new Deployer and a new MessageReceiver. The
new Deployer will be called when a file with extension "dbs" is
dropped in to the directory "db_services". I am not sure whether this
is the best folder name and extension to use. So if some one has any
suggestions please let me know.
The Deployer will read the configuration file for the service and
create a DBInfo object from it with the relevant details. It will
then set this as parameter in the new AxisService object. An
instance
of DBMessageReceiver is attached to all the operations that are created.
All processing code will be in a static utility class called
DBUtils.
Any feedback about this design is most welcome.
Best Regards,
Chamil Thanthrimudalige
_______________________________________________
Wsf-general mailing list
http://wso2.org/cgi-bin/mailman/listinfo/wsf-general

--
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"
_______________________________________________
Wsf-general mailing list
http://wso2.org/cgi-bin/mailman/listinfo/wsf-general