You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@xml.apache.org by Kartheek Hirode <ka...@centegy.com> on 2000/08/31 21:27:10 UTC
Extending DeploymentDescriptor and ServiceManager
Hello all,
I have a situation where I need to add 2 additional items in the
DeploymentDescriptor
which will be used in rpcrouter. (These are configuration items, hence they
sit well in
DeploymentDescriptor). For this, I am planning to just go ahead and *extend*
DeploymentDescriptor and ServiceManager to create myDD and mySM classes.
Will the stuff hit the fan downstream somewhere where the old DD and SM are
expected? I did a search on all places where DD and SM are used and they are
only used in:
->DD: In RPCMessage.java and RPCRouter
->SM: In Call.java, RPCMessage and RPCRouter
I *do not* want to change Call or RPCMessage, and am planning to leave them
as they are. But am wondering whether these will come back to bite later.
Am feeling slightly short-of brain-width, hence seeking advice.
Thanks much,
--KH
Re: Extending DeploymentDescriptor and ServiceManager
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
I think what you're doing is ok. As Vahe suggested tho you may want
to extend the JSPs that provide a UI for filling some of this too.
Sanjiva.
----- Original Message -----
From: "Kartheek Hirode" <ka...@centegy.com>
To: <so...@xml.apache.org>
Sent: Thursday, August 31, 2000 3:27 PM
Subject: Extending DeploymentDescriptor and ServiceManager
> Hello all,
> I have a situation where I need to add 2 additional items in the
> DeploymentDescriptor
> which will be used in rpcrouter. (These are configuration items, hence they
> sit well in
> DeploymentDescriptor). For this, I am planning to just go ahead and *extend*
> DeploymentDescriptor and ServiceManager to create myDD and mySM classes.
>
> Will the stuff hit the fan downstream somewhere where the old DD and SM are
> expected? I did a search on all places where DD and SM are used and they are
> only used in:
> ->DD: In RPCMessage.java and RPCRouter
> ->SM: In Call.java, RPCMessage and RPCRouter
>
> I *do not* want to change Call or RPCMessage, and am planning to leave them
> as they are. But am wondering whether these will come back to bite later.
> Am feeling slightly short-of brain-width, hence seeking advice.
> Thanks much,
> --KH
>
Re: Extending DeploymentDescriptor and ServiceManager
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
Vahe Amirbekyan writes:
>
> I actually did the same - but the painful truth is that those classes
> are NOT easily extendable, IMHO. Their member attributes are declared on
> "package" level of visibility, so in order to acess them in subclass you
> would have to define your my* classes in the same package -
> org.apache.soap.server. BTW - SOAP developers, I wonder whether it is
> this planned to be changed to 'protected'?
Just did it - all you had to do was ask! :-) My default mode is to
leave fields package level ..
Sanjiva.
Re: Extending DeploymentDescriptor and ServiceManager
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
Vahe Amirbekyan writes:
>
> I actually did the same - but the painful truth is that those classes
> are NOT easily extendable, IMHO. Their member attributes are declared on
> "package" level of visibility, so in order to acess them in subclass you
> would have to define your my* classes in the same package -
> org.apache.soap.server. BTW - SOAP developers, I wonder whether it is
> this planned to be changed to 'protected'?
Just did it - all you had to do was ask! :-) My default mode is to
leave fields package level ..
Sanjiva.
Re: Extending DeploymentDescriptor and ServiceManager
Posted by Vahe Amirbekyan <av...@techone.com>.
Hi Kartheek,
> I have a situation where I need to add 2 additional items in the
> DeploymentDescriptor
> which will be used in rpcrouter. (These are configuration items, hence they
> sit well in
> DeploymentDescriptor).
Is that "configuration item" specific per target? If yes, you are on the
right way, if no - a better idea might be to place it in the
ServiceManager insted. IMHO.
> For this, I am planning to just go ahead and *extend*
> DeploymentDescriptor and ServiceManager to create myDD and mySM classes.
I actually did the same - but the painful truth is that those classes
are NOT easily extendable, IMHO. Their member attributes are declared on
"package" level of visibility, so in order to acess them in subclass you
would have to define your my* classes in the same package -
org.apache.soap.server. BTW - SOAP developers, I wonder whether it is
this planned to be changed to 'protected'?
> Will the stuff hit the fan downstream somewhere where the old DD and SM are
> expected? I did a search on all places where DD and SM are used and they are
> only used in:
> ->DD: In RPCMessage.java and RPCRouter
> ->SM: In Call.java, RPCMessage and RPCRouter
>
> I *do not* want to change Call or RPCMessage, and am planning to leave them
> as they are. But am wondering whether these will come back to bite later.
IMHO - by changing (subclassing) ServiceManager you should also update
the RPCRouterServlet plus the *.jsp files in the admin folder as well as
(possibly) ServiceManagerClient. The same is with DD - The
RPCRouterServlet should be probably changed.
Hope this helps, Vahe
--
(\______________________________________________________/)
__|_| Vahe AMIRBEKYAN, Senior Consultant |_|__
(___o) tel: (510) 729 6750 ext.375 (o___)
(__o) mailto:vahe@techone.com (o__)
(__o) http://www.techone.com (o__)
(_o)____________________________________________________(o_)
Re: Extending DeploymentDescriptor and ServiceManager
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
I think what you're doing is ok. As Vahe suggested tho you may want
to extend the JSPs that provide a UI for filling some of this too.
Sanjiva.
----- Original Message -----
From: "Kartheek Hirode" <ka...@centegy.com>
To: <so...@xml.apache.org>
Sent: Thursday, August 31, 2000 3:27 PM
Subject: Extending DeploymentDescriptor and ServiceManager
> Hello all,
> I have a situation where I need to add 2 additional items in the
> DeploymentDescriptor
> which will be used in rpcrouter. (These are configuration items, hence they
> sit well in
> DeploymentDescriptor). For this, I am planning to just go ahead and *extend*
> DeploymentDescriptor and ServiceManager to create myDD and mySM classes.
>
> Will the stuff hit the fan downstream somewhere where the old DD and SM are
> expected? I did a search on all places where DD and SM are used and they are
> only used in:
> ->DD: In RPCMessage.java and RPCRouter
> ->SM: In Call.java, RPCMessage and RPCRouter
>
> I *do not* want to change Call or RPCMessage, and am planning to leave them
> as they are. But am wondering whether these will come back to bite later.
> Am feeling slightly short-of brain-width, hence seeking advice.
> Thanks much,
> --KH
>
Re: Extending DeploymentDescriptor and ServiceManager
Posted by Vahe Amirbekyan <av...@techone.com>.
Hi Kartheek,
> I have a situation where I need to add 2 additional items in the
> DeploymentDescriptor
> which will be used in rpcrouter. (These are configuration items, hence they
> sit well in
> DeploymentDescriptor).
Is that "configuration item" specific per target? If yes, you are on the
right way, if no - a better idea might be to place it in the
ServiceManager insted. IMHO.
> For this, I am planning to just go ahead and *extend*
> DeploymentDescriptor and ServiceManager to create myDD and mySM classes.
I actually did the same - but the painful truth is that those classes
are NOT easily extendable, IMHO. Their member attributes are declared on
"package" level of visibility, so in order to acess them in subclass you
would have to define your my* classes in the same package -
org.apache.soap.server. BTW - SOAP developers, I wonder whether it is
this planned to be changed to 'protected'?
> Will the stuff hit the fan downstream somewhere where the old DD and SM are
> expected? I did a search on all places where DD and SM are used and they are
> only used in:
> ->DD: In RPCMessage.java and RPCRouter
> ->SM: In Call.java, RPCMessage and RPCRouter
>
> I *do not* want to change Call or RPCMessage, and am planning to leave them
> as they are. But am wondering whether these will come back to bite later.
IMHO - by changing (subclassing) ServiceManager you should also update
the RPCRouterServlet plus the *.jsp files in the admin folder as well as
(possibly) ServiceManagerClient. The same is with DD - The
RPCRouterServlet should be probably changed.
Hope this helps, Vahe
--
(\______________________________________________________/)
__|_| Vahe AMIRBEKYAN, Senior Consultant |_|__
(___o) tel: (510) 729 6750 ext.375 (o___)
(__o) mailto:vahe@techone.com (o__)
(__o) http://www.techone.com (o__)
(_o)____________________________________________________(o_)