You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Jeff Barrett (JIRA)" <ji...@apache.org> on 2006/09/18 19:58:22 UTC
[jira] Created: (AXIS2-1183) Client-side metadata improvements to
create service and use fully qualified service name
Client-side metadata improvements to create service and use fully qualified service name
----------------------------------------------------------------------------------------
Key: AXIS2-1183
URL: http://issues.apache.org/jira/browse/AXIS2-1183
Project: Apache Axis 2.0 (Axis2)
Issue Type: Improvement
Components: jaxws
Reporter: Jeff Barrett
The client-side metadata layer needs to create a named service (not an anonymout service) on which to hang additional service-specific client side configuration. The name of the service should be the fully qualified service QName. Additionally, a method needs to be added to the ConfigurationFactoryBuilder to allow a newly created service to be passed in for any final client-side configuration to be added.
I am working on a patch for this and will submit it shortly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Closed: (AXIS2-1183) Client-side metadata improvements to
create service and use fully qualified service name
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1183?page=all ]
Rich Scheuerle closed AXIS2-1183.
---------------------------------
Resolution: Fixed
> Client-side metadata improvements to create service and use fully qualified service name
> ----------------------------------------------------------------------------------------
>
> Key: AXIS2-1183
> URL: http://issues.apache.org/jira/browse/AXIS2-1183
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: jaxws
> Reporter: Jeff Barrett
> Attachments: 1183_patch.txt
>
>
> The client-side metadata layer needs to create a named service (not an anonymout service) on which to hang additional service-specific client side configuration. The name of the service should be the fully qualified service QName. Additionally, a method needs to be added to the ConfigurationFactoryBuilder to allow a newly created service to be passed in for any final client-side configuration to be added.
> I am working on a patch for this and will submit it shortly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [jira] Updated: (AXIS2-1183) Client-side metadata improvements to create service and use fully qualified service name
Posted by Davanum Srinivas <da...@gmail.com>.
jira please with your sample code to recreate the problm.
thx,
dims
On 9/18/06, sandeep bhojwani <sa...@yahoo.com> wrote:
> I was looking for this feature. I want to configure
> the services on the client side in the same way as is
> done on the server. I tried this. I put .aar files and
> loaded the configuration using the
> FileBasedConfiguration loader. The problem is that
> somewhere deep down, in the code that parses all the
> service definition, there is a flag for isServerSide.
> This flag by default is true and there's no way for
> reseting this flag in the high level api. As a result
> my out-in Operation is actually created as an in-out
> operation.
>
> The ServiceClient has a method which loads services
> from a WSDL url. This method turns off the isServer
> flag first and that's how the ServiceClient is able to
> use the right MEP.
>
> I want to preload services on the client side using
> the configuration instead of loading from the WSDL
> urls.
>
> One way to provide this would be to have a flag in the
> config.xml and have the ConfigurationLoader pass this
> down to the Service Factory that loads the services.
>
> Any comments?
>
> -Sandeep
>
> --- "Jeff Barrett (JIRA)" <ji...@apache.org> wrote:
>
> > [
> >
> http://issues.apache.org/jira/browse/AXIS2-1183?page=all
> > ]
> >
> > Jeff Barrett updated AXIS2-1183:
> > --------------------------------
> >
> > Attachment: 1183_patch.txt
> >
> > Fixed per Description.
> >
> > > Client-side metadata improvements to create
> > service and use fully qualified service name
> > >
> >
> ----------------------------------------------------------------------------------------
> > >
> > > Key: AXIS2-1183
> > > URL:
> > http://issues.apache.org/jira/browse/AXIS2-1183
> > > Project: Apache Axis 2.0 (Axis2)
> > > Issue Type: Improvement
> > > Components: jaxws
> > > Reporter: Jeff Barrett
> > > Attachments: 1183_patch.txt
> > >
> > >
> > > The client-side metadata layer needs to create a
> > named service (not an anonymout service) on which to
> > hang additional service-specific client side
> > configuration. The name of the service should be
> > the fully qualified service QName. Additionally, a
> > method needs to be added to the
> > ConfigurationFactoryBuilder to allow a newly created
> > service to be passed in for any final client-side
> > configuration to be added.
> > > I am working on a patch for this and will submit
> > it shortly.
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > If you think it was sent incorrectly contact one of
> > the administrators:
> >
> http://issues.apache.org/jira/secure/Administrators.jspa
> > -
> > For more information on JIRA, see:
> > http://www.atlassian.com/software/jira
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail:
> > axis-dev-help@ws.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [jira] Updated: (AXIS2-1183) Client-side metadata improvements to create service and use fully qualified service name
Posted by sandeep bhojwani <sa...@yahoo.com>.
I was looking for this feature. I want to configure
the services on the client side in the same way as is
done on the server. I tried this. I put .aar files and
loaded the configuration using the
FileBasedConfiguration loader. The problem is that
somewhere deep down, in the code that parses all the
service definition, there is a flag for isServerSide.
This flag by default is true and there's no way for
reseting this flag in the high level api. As a result
my out-in Operation is actually created as an in-out
operation.
The ServiceClient has a method which loads services
from a WSDL url. This method turns off the isServer
flag first and that's how the ServiceClient is able to
use the right MEP.
I want to preload services on the client side using
the configuration instead of loading from the WSDL
urls.
One way to provide this would be to have a flag in the
config.xml and have the ConfigurationLoader pass this
down to the Service Factory that loads the services.
Any comments?
-Sandeep
--- "Jeff Barrett (JIRA)" <ji...@apache.org> wrote:
> [
>
http://issues.apache.org/jira/browse/AXIS2-1183?page=all
> ]
>
> Jeff Barrett updated AXIS2-1183:
> --------------------------------
>
> Attachment: 1183_patch.txt
>
> Fixed per Description.
>
> > Client-side metadata improvements to create
> service and use fully qualified service name
> >
>
----------------------------------------------------------------------------------------
> >
> > Key: AXIS2-1183
> > URL:
> http://issues.apache.org/jira/browse/AXIS2-1183
> > Project: Apache Axis 2.0 (Axis2)
> > Issue Type: Improvement
> > Components: jaxws
> > Reporter: Jeff Barrett
> > Attachments: 1183_patch.txt
> >
> >
> > The client-side metadata layer needs to create a
> named service (not an anonymout service) on which to
> hang additional service-specific client side
> configuration. The name of the service should be
> the fully qualified service QName. Additionally, a
> method needs to be added to the
> ConfigurationFactoryBuilder to allow a newly created
> service to be passed in for any final client-side
> configuration to be added.
> > I am working on a patch for this and will submit
> it shortly.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of
> the administrators:
>
http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
> http://www.atlassian.com/software/jira
>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail:
> axis-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-1183) Client-side metadata improvements to
create service and use fully qualified service name
Posted by "Jeff Barrett (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1183?page=all ]
Jeff Barrett updated AXIS2-1183:
--------------------------------
Attachment: 1183_patch.txt
Fixed per Description.
> Client-side metadata improvements to create service and use fully qualified service name
> ----------------------------------------------------------------------------------------
>
> Key: AXIS2-1183
> URL: http://issues.apache.org/jira/browse/AXIS2-1183
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: jaxws
> Reporter: Jeff Barrett
> Attachments: 1183_patch.txt
>
>
> The client-side metadata layer needs to create a named service (not an anonymout service) on which to hang additional service-specific client side configuration. The name of the service should be the fully qualified service QName. Additionally, a method needs to be added to the ConfigurationFactoryBuilder to allow a newly created service to be passed in for any final client-side configuration to be added.
> I am working on a patch for this and will submit it shortly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org