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 Davanum Srinivas <da...@gmail.com> on 2006/12/09 03:37:29 UTC
[Axis2][jaxws] Splitting off building of metadata (org.apache.axis2.jaxws.description package)
Folks,
The description package which builds the metadata model from
annotations etc is pretty much standalone except for some leakage of
jaxws stuff (example jaxws.ClientConfigurationFactory in
ServiceDescriptionImpl.java) and some utility classes. What say we
bite the bullet and split it out? If we do that we could think about
reusing that code to build annotations based metadata for use say in
our RPC*MessageReceiver. Basically the description package deals with
JSR 181 and it would be good to split that out. I can help...
Thanks,
dims
--
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: [Axis2][jaxws] Splitting off building of metadata (org.apache.axis2.jaxws.description package)
Posted by Davanum Srinivas <da...@gmail.com>.
+1 to metadata
On 12/11/06, Nicholas L Gallardo <nl...@us.ibm.com> wrote:
>
>
> Hi Dims,
>
> +1 This sounds good, and was something that we had intended a while back.
>
> Any ideas for the module name? I'd like to propose "metadata" if one
> hasn't been decided already.
>
> -Nick
>
>
>
> *"Davanum Srinivas" <da...@gmail.com>*
>
> 12/08/2006 08:37 PM Please respond to
> axis-dev@ws.apache.org
>
> To
> "Axis developer list" <ax...@ws.apache.org> cc
>
> Subject
> [Axis2][jaxws] Splitting off building of metadata (
> org.apache.axis2.jaxws.description package)
>
>
>
>
>
>
> Folks,
>
> The description package which builds the metadata model from
> annotations etc is pretty much standalone except for some leakage of
> jaxws stuff (example jaxws.ClientConfigurationFactory in
> ServiceDescriptionImpl.java) and some utility classes. What say we
> bite the bullet and split it out? If we do that we could think about
> reusing that code to build annotations based metadata for use say in
> our RPC*MessageReceiver. Basically the description package deals with
> JSR 181 and it would be good to split that out. I can help...
>
> Thanks,
> dims
>
> --
> 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
>
>
>
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
Re: [Axis2][jaxws] Splitting off building of metadata (org.apache.axis2.jaxws.description package)
Posted by Davanum Srinivas <da...@gmail.com>.
Jeff, Nick,
I took a stab and extracted the minimum possible set of files from
jaxws into metadata. Please take a look. Now we need to move files
over from metadata to jaxws (those that don't belong). Added metadata
as a dependency to jaxws of course.
thanks,
dims
On 12/18/06, Davanum Srinivas <da...@gmail.com> wrote:
> fyi, i just split out the specs.
>
> thx,
> dims
>
> On 12/11/06, Davanum Srinivas <da...@gmail.com> wrote:
> > +1 to separate out the specs (javax.jws.* and javax.xml.ws.*)
> > +1 to keep leave references to both the specs under metadata (no need
> > to separate/layer them)
> >
> > -- dims
> >
> > On 12/11/06, Jeff Barrett <ba...@us.ibm.com> wrote:
> > > Actually, let me clarify what I meant by "I would like to leave the JAX-WS
> > > spec'd interfaces in the Description package, along with the JSR-181
> > > spec'd interfaces..."
> > >
> > > I mean I would like to leave references to them in the Description
> > > package, but not necessarily the definitions of the classes themselves. In
> > > other words, I would rather not have to split out all code that references
> > > javax.xml.ws.* classes from the Description package. The definition of
> > > the java.xml.ws.* classes (as well as the javax.jws.* JSR-181 classes)
> > > should probably be in seperate JSRs outside the Description module as well
> > > as the JAX-WS module.
> > >
> > > Thanks,
> > > Jeff
> > >
> > > IBM Software Group - WebSphere Web Services Development
> > > Phone: 512-838-4587 or Tie Line 678-4587
> > > Internet e-mail and Sametime ID: barrettj@us.ibm.com
> > >
> > >
> > >
> > > Jeff Barrett/Austin/IBM@IBMUS
> > > 12/11/2006 01:24 PM
> > > Please respond to
> > > axis-dev@ws.apache.org
> > >
> > >
> > > To
> > > axis-dev@ws.apache.org
> > > cc
> > >
> > > Subject
> > > Re: [Axis2][jaxws] Splitting off building of metadata
> > > (org.apache.axis2.jaxws.description package)
> > >
> > >
> > >
> > >
> > >
> > >
> > > Howdy Dims,
> > >
> > > I think that's a good idea. If possible, I would like to leave the JAX-WS
> > >
> > > spec'd interfaces in the Description package, along with the JSR-181
> > > spec'd interfaces, and split on any JAX-WS implementation-specific classes
> > >
> > > such as the ClientConfigurationFactory you mentioned. What I mean by
> > > JAX-WS spec'd interfaces are essentially the annotation interfaces such as
> > >
> > > javax.xml.ws.WebServiceProvider. If we try to refactor those out, then
> > > we'll have to layer the JSR-181 and JAX-WS annotation processing, and that
> > >
> > > seems like a lot of unnecessary work. In any case, the Description layer
> > > needs to function with only JSR-181 annotations specified (i.e. not rely
> > > on the presence of JSR-224 annotations). There may be some work in that
> > > area.
> > >
> > > There are two other areas of work still remaining in the Description layer
> > >
> > > that I've been trying to get to:
> > > 1) We need a "java reflection to DescriptionBuilderComposite" converter.
> > > This would take java classes and build up the DBC.
> > > 2) Refactor the client-side Description processing to use DBC instead of
> > > direct Java reflection.
> > >
> > > Once (1) is done, it could be used as an example of how to write other
> > > converters, for example to go from some annotation byte-scanner to DBC.
> > > Regarding (2), you'll see in the current Description code that there are
> > > two processing paths, one which uses DBC (this is the server side) and one
> > >
> > > which uses Java reflection (this is the client side); once (1) is done,
> > > then all the code should be refactored to use only DBC.
> > >
> > > Thanks,
> > > Jeff
> > >
> > > IBM Software Group - WebSphere Web Services Development
> > > Phone: 512-838-4587 or Tie Line 678-4587
> > > Internet e-mail and Sametime ID: barrettj@us.ibm.com
> > >
> > >
> > >
> > > "Davanum Srinivas" <da...@gmail.com>
> > > 12/08/2006 08:37 PM
> > > Please respond to
> > > axis-dev@ws.apache.org
> > >
> > >
> > > To
> > > "Axis developer list" <ax...@ws.apache.org>
> > > cc
> > >
> > > Subject
> > > [Axis2][jaxws] Splitting off building of metadata
> > > (org.apache.axis2.jaxws.description package)
> > >
> > >
> > >
> > >
> > >
> > >
> > > Folks,
> > >
> > > The description package which builds the metadata model from
> > > annotations etc is pretty much standalone except for some leakage of
> > > jaxws stuff (example jaxws.ClientConfigurationFactory in
> > > ServiceDescriptionImpl.java) and some utility classes. What say we
> > > bite the bullet and split it out? If we do that we could think about
> > > reusing that code to build annotations based metadata for use say in
> > > our RPC*MessageReceiver. Basically the description package deals with
> > > JSR 181 and it would be good to split that out. I can help...
> > >
> > > Thanks,
> > > dims
> > >
> > > --
> > > 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
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > 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)
> >
>
>
> --
> Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
>
--
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: [Axis2][jaxws] Splitting off building of metadata (org.apache.axis2.jaxws.description package)
Posted by Davanum Srinivas <da...@gmail.com>.
fyi, i just split out the specs.
thx,
dims
On 12/11/06, Davanum Srinivas <da...@gmail.com> wrote:
> +1 to separate out the specs (javax.jws.* and javax.xml.ws.*)
> +1 to keep leave references to both the specs under metadata (no need
> to separate/layer them)
>
> -- dims
>
> On 12/11/06, Jeff Barrett <ba...@us.ibm.com> wrote:
> > Actually, let me clarify what I meant by "I would like to leave the JAX-WS
> > spec'd interfaces in the Description package, along with the JSR-181
> > spec'd interfaces..."
> >
> > I mean I would like to leave references to them in the Description
> > package, but not necessarily the definitions of the classes themselves. In
> > other words, I would rather not have to split out all code that references
> > javax.xml.ws.* classes from the Description package. The definition of
> > the java.xml.ws.* classes (as well as the javax.jws.* JSR-181 classes)
> > should probably be in seperate JSRs outside the Description module as well
> > as the JAX-WS module.
> >
> > Thanks,
> > Jeff
> >
> > IBM Software Group - WebSphere Web Services Development
> > Phone: 512-838-4587 or Tie Line 678-4587
> > Internet e-mail and Sametime ID: barrettj@us.ibm.com
> >
> >
> >
> > Jeff Barrett/Austin/IBM@IBMUS
> > 12/11/2006 01:24 PM
> > Please respond to
> > axis-dev@ws.apache.org
> >
> >
> > To
> > axis-dev@ws.apache.org
> > cc
> >
> > Subject
> > Re: [Axis2][jaxws] Splitting off building of metadata
> > (org.apache.axis2.jaxws.description package)
> >
> >
> >
> >
> >
> >
> > Howdy Dims,
> >
> > I think that's a good idea. If possible, I would like to leave the JAX-WS
> >
> > spec'd interfaces in the Description package, along with the JSR-181
> > spec'd interfaces, and split on any JAX-WS implementation-specific classes
> >
> > such as the ClientConfigurationFactory you mentioned. What I mean by
> > JAX-WS spec'd interfaces are essentially the annotation interfaces such as
> >
> > javax.xml.ws.WebServiceProvider. If we try to refactor those out, then
> > we'll have to layer the JSR-181 and JAX-WS annotation processing, and that
> >
> > seems like a lot of unnecessary work. In any case, the Description layer
> > needs to function with only JSR-181 annotations specified (i.e. not rely
> > on the presence of JSR-224 annotations). There may be some work in that
> > area.
> >
> > There are two other areas of work still remaining in the Description layer
> >
> > that I've been trying to get to:
> > 1) We need a "java reflection to DescriptionBuilderComposite" converter.
> > This would take java classes and build up the DBC.
> > 2) Refactor the client-side Description processing to use DBC instead of
> > direct Java reflection.
> >
> > Once (1) is done, it could be used as an example of how to write other
> > converters, for example to go from some annotation byte-scanner to DBC.
> > Regarding (2), you'll see in the current Description code that there are
> > two processing paths, one which uses DBC (this is the server side) and one
> >
> > which uses Java reflection (this is the client side); once (1) is done,
> > then all the code should be refactored to use only DBC.
> >
> > Thanks,
> > Jeff
> >
> > IBM Software Group - WebSphere Web Services Development
> > Phone: 512-838-4587 or Tie Line 678-4587
> > Internet e-mail and Sametime ID: barrettj@us.ibm.com
> >
> >
> >
> > "Davanum Srinivas" <da...@gmail.com>
> > 12/08/2006 08:37 PM
> > Please respond to
> > axis-dev@ws.apache.org
> >
> >
> > To
> > "Axis developer list" <ax...@ws.apache.org>
> > cc
> >
> > Subject
> > [Axis2][jaxws] Splitting off building of metadata
> > (org.apache.axis2.jaxws.description package)
> >
> >
> >
> >
> >
> >
> > Folks,
> >
> > The description package which builds the metadata model from
> > annotations etc is pretty much standalone except for some leakage of
> > jaxws stuff (example jaxws.ClientConfigurationFactory in
> > ServiceDescriptionImpl.java) and some utility classes. What say we
> > bite the bullet and split it out? If we do that we could think about
> > reusing that code to build annotations based metadata for use say in
> > our RPC*MessageReceiver. Basically the description package deals with
> > JSR 181 and it would be good to split that out. I can help...
> >
> > Thanks,
> > dims
> >
> > --
> > 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
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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)
>
--
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: [Axis2][jaxws] Splitting off building of metadata (org.apache.axis2.jaxws.description package)
Posted by Davanum Srinivas <da...@gmail.com>.
+1 to separate out the specs (javax.jws.* and javax.xml.ws.*)
+1 to keep leave references to both the specs under metadata (no need
to separate/layer them)
-- dims
On 12/11/06, Jeff Barrett <ba...@us.ibm.com> wrote:
> Actually, let me clarify what I meant by "I would like to leave the JAX-WS
> spec'd interfaces in the Description package, along with the JSR-181
> spec'd interfaces..."
>
> I mean I would like to leave references to them in the Description
> package, but not necessarily the definitions of the classes themselves. In
> other words, I would rather not have to split out all code that references
> javax.xml.ws.* classes from the Description package. The definition of
> the java.xml.ws.* classes (as well as the javax.jws.* JSR-181 classes)
> should probably be in seperate JSRs outside the Description module as well
> as the JAX-WS module.
>
> Thanks,
> Jeff
>
> IBM Software Group - WebSphere Web Services Development
> Phone: 512-838-4587 or Tie Line 678-4587
> Internet e-mail and Sametime ID: barrettj@us.ibm.com
>
>
>
> Jeff Barrett/Austin/IBM@IBMUS
> 12/11/2006 01:24 PM
> Please respond to
> axis-dev@ws.apache.org
>
>
> To
> axis-dev@ws.apache.org
> cc
>
> Subject
> Re: [Axis2][jaxws] Splitting off building of metadata
> (org.apache.axis2.jaxws.description package)
>
>
>
>
>
>
> Howdy Dims,
>
> I think that's a good idea. If possible, I would like to leave the JAX-WS
>
> spec'd interfaces in the Description package, along with the JSR-181
> spec'd interfaces, and split on any JAX-WS implementation-specific classes
>
> such as the ClientConfigurationFactory you mentioned. What I mean by
> JAX-WS spec'd interfaces are essentially the annotation interfaces such as
>
> javax.xml.ws.WebServiceProvider. If we try to refactor those out, then
> we'll have to layer the JSR-181 and JAX-WS annotation processing, and that
>
> seems like a lot of unnecessary work. In any case, the Description layer
> needs to function with only JSR-181 annotations specified (i.e. not rely
> on the presence of JSR-224 annotations). There may be some work in that
> area.
>
> There are two other areas of work still remaining in the Description layer
>
> that I've been trying to get to:
> 1) We need a "java reflection to DescriptionBuilderComposite" converter.
> This would take java classes and build up the DBC.
> 2) Refactor the client-side Description processing to use DBC instead of
> direct Java reflection.
>
> Once (1) is done, it could be used as an example of how to write other
> converters, for example to go from some annotation byte-scanner to DBC.
> Regarding (2), you'll see in the current Description code that there are
> two processing paths, one which uses DBC (this is the server side) and one
>
> which uses Java reflection (this is the client side); once (1) is done,
> then all the code should be refactored to use only DBC.
>
> Thanks,
> Jeff
>
> IBM Software Group - WebSphere Web Services Development
> Phone: 512-838-4587 or Tie Line 678-4587
> Internet e-mail and Sametime ID: barrettj@us.ibm.com
>
>
>
> "Davanum Srinivas" <da...@gmail.com>
> 12/08/2006 08:37 PM
> Please respond to
> axis-dev@ws.apache.org
>
>
> To
> "Axis developer list" <ax...@ws.apache.org>
> cc
>
> Subject
> [Axis2][jaxws] Splitting off building of metadata
> (org.apache.axis2.jaxws.description package)
>
>
>
>
>
>
> Folks,
>
> The description package which builds the metadata model from
> annotations etc is pretty much standalone except for some leakage of
> jaxws stuff (example jaxws.ClientConfigurationFactory in
> ServiceDescriptionImpl.java) and some utility classes. What say we
> bite the bullet and split it out? If we do that we could think about
> reusing that code to build annotations based metadata for use say in
> our RPC*MessageReceiver. Basically the description package deals with
> JSR 181 and it would be good to split that out. I can help...
>
> Thanks,
> dims
>
> --
> 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
>
>
>
>
> ---------------------------------------------------------------------
> 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: [Axis2][jaxws] Splitting off building of metadata (org.apache.axis2.jaxws.description
package)
Posted by Jeff Barrett <ba...@us.ibm.com>.
Actually, let me clarify what I meant by "I would like to leave the JAX-WS
spec'd interfaces in the Description package, along with the JSR-181
spec'd interfaces..."
I mean I would like to leave references to them in the Description
package, but not necessarily the definitions of the classes themselves. In
other words, I would rather not have to split out all code that references
javax.xml.ws.* classes from the Description package. The definition of
the java.xml.ws.* classes (as well as the javax.jws.* JSR-181 classes)
should probably be in seperate JSRs outside the Description module as well
as the JAX-WS module.
Thanks,
Jeff
IBM Software Group - WebSphere Web Services Development
Phone: 512-838-4587 or Tie Line 678-4587
Internet e-mail and Sametime ID: barrettj@us.ibm.com
Jeff Barrett/Austin/IBM@IBMUS
12/11/2006 01:24 PM
Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org
cc
Subject
Re: [Axis2][jaxws] Splitting off building of metadata
(org.apache.axis2.jaxws.description package)
Howdy Dims,
I think that's a good idea. If possible, I would like to leave the JAX-WS
spec'd interfaces in the Description package, along with the JSR-181
spec'd interfaces, and split on any JAX-WS implementation-specific classes
such as the ClientConfigurationFactory you mentioned. What I mean by
JAX-WS spec'd interfaces are essentially the annotation interfaces such as
javax.xml.ws.WebServiceProvider. If we try to refactor those out, then
we'll have to layer the JSR-181 and JAX-WS annotation processing, and that
seems like a lot of unnecessary work. In any case, the Description layer
needs to function with only JSR-181 annotations specified (i.e. not rely
on the presence of JSR-224 annotations). There may be some work in that
area.
There are two other areas of work still remaining in the Description layer
that I've been trying to get to:
1) We need a "java reflection to DescriptionBuilderComposite" converter.
This would take java classes and build up the DBC.
2) Refactor the client-side Description processing to use DBC instead of
direct Java reflection.
Once (1) is done, it could be used as an example of how to write other
converters, for example to go from some annotation byte-scanner to DBC.
Regarding (2), you'll see in the current Description code that there are
two processing paths, one which uses DBC (this is the server side) and one
which uses Java reflection (this is the client side); once (1) is done,
then all the code should be refactored to use only DBC.
Thanks,
Jeff
IBM Software Group - WebSphere Web Services Development
Phone: 512-838-4587 or Tie Line 678-4587
Internet e-mail and Sametime ID: barrettj@us.ibm.com
"Davanum Srinivas" <da...@gmail.com>
12/08/2006 08:37 PM
Please respond to
axis-dev@ws.apache.org
To
"Axis developer list" <ax...@ws.apache.org>
cc
Subject
[Axis2][jaxws] Splitting off building of metadata
(org.apache.axis2.jaxws.description package)
Folks,
The description package which builds the metadata model from
annotations etc is pretty much standalone except for some leakage of
jaxws stuff (example jaxws.ClientConfigurationFactory in
ServiceDescriptionImpl.java) and some utility classes. What say we
bite the bullet and split it out? If we do that we could think about
reusing that code to build annotations based metadata for use say in
our RPC*MessageReceiver. Basically the description package deals with
JSR 181 and it would be good to split that out. I can help...
Thanks,
dims
--
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
---------------------------------------------------------------------
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
Re: [Axis2][jaxws] Splitting off building of metadata (org.apache.axis2.jaxws.description
package)
Posted by Jeff Barrett <ba...@us.ibm.com>.
Howdy Dims,
I think that's a good idea. If possible, I would like to leave the JAX-WS
spec'd interfaces in the Description package, along with the JSR-181
spec'd interfaces, and split on any JAX-WS implementation-specific classes
such as the ClientConfigurationFactory you mentioned. What I mean by
JAX-WS spec'd interfaces are essentially the annotation interfaces such as
javax.xml.ws.WebServiceProvider. If we try to refactor those out, then
we'll have to layer the JSR-181 and JAX-WS annotation processing, and that
seems like a lot of unnecessary work. In any case, the Description layer
needs to function with only JSR-181 annotations specified (i.e. not rely
on the presence of JSR-224 annotations). There may be some work in that
area.
There are two other areas of work still remaining in the Description layer
that I've been trying to get to:
1) We need a "java reflection to DescriptionBuilderComposite" converter.
This would take java classes and build up the DBC.
2) Refactor the client-side Description processing to use DBC instead of
direct Java reflection.
Once (1) is done, it could be used as an example of how to write other
converters, for example to go from some annotation byte-scanner to DBC.
Regarding (2), you'll see in the current Description code that there are
two processing paths, one which uses DBC (this is the server side) and one
which uses Java reflection (this is the client side); once (1) is done,
then all the code should be refactored to use only DBC.
Thanks,
Jeff
IBM Software Group - WebSphere Web Services Development
Phone: 512-838-4587 or Tie Line 678-4587
Internet e-mail and Sametime ID: barrettj@us.ibm.com
"Davanum Srinivas" <da...@gmail.com>
12/08/2006 08:37 PM
Please respond to
axis-dev@ws.apache.org
To
"Axis developer list" <ax...@ws.apache.org>
cc
Subject
[Axis2][jaxws] Splitting off building of metadata
(org.apache.axis2.jaxws.description package)
Folks,
The description package which builds the metadata model from
annotations etc is pretty much standalone except for some leakage of
jaxws stuff (example jaxws.ClientConfigurationFactory in
ServiceDescriptionImpl.java) and some utility classes. What say we
bite the bullet and split it out? If we do that we could think about
reusing that code to build annotations based metadata for use say in
our RPC*MessageReceiver. Basically the description package deals with
JSR 181 and it would be good to split that out. I can help...
Thanks,
dims
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][jaxws] Splitting off building of metadata (org.apache.axis2.jaxws.description
package)
Posted by Nicholas L Gallardo <nl...@us.ibm.com>.
Hi Dims,
+1 This sounds good, and was something that we had intended a while back.
Any ideas for the module name? I'd like to propose "metadata" if one
hasn't been decided already.
-Nick
"Davanum Srinivas" <da...@gmail.com>
12/08/2006 08:37 PM
Please respond to
axis-dev@ws.apache.org
To
"Axis developer list" <ax...@ws.apache.org>
cc
Subject
[Axis2][jaxws] Splitting off building of metadata
(org.apache.axis2.jaxws.description package)
Folks,
The description package which builds the metadata model from
annotations etc is pretty much standalone except for some leakage of
jaxws stuff (example jaxws.ClientConfigurationFactory in
ServiceDescriptionImpl.java) and some utility classes. What say we
bite the bullet and split it out? If we do that we could think about
reusing that code to build annotations based metadata for use say in
our RPC*MessageReceiver. Basically the description package deals with
JSR 181 and it would be good to split that out. I can help...
Thanks,
dims
--
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