Re: [Axis2]WSDL2Java Code generation option
Hi! - Will Tom's or Sanjiva's suggestion be implemented for Axis2 1.1? - Can you please explain to me what the option -u is all about? The only difference it seems to make is that an interface XXXService is generated and the Stub class contains an additional implements XXXService Why is this option called unpacks databinding classes? Thanks, Thilo Tom Jordahl wrote: +1 for Sanjiva's suggestions: -c client side -s server side -t test case generation. I think -a should be for all, but I assume it is in use already? -- Tom Jordahl Adobe ColdFusion Team -Original Message- From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] Sent: Monday, October 09, 2006 5:13 PM To: axis-dev@ws.apache.org Cc: Thilina Gunarathne Subject: Re: [Axis2]WSDL2Java Code generation option On Mon, 2006-10-09 at 07:54 -0400, Srinath Perera wrote: Hi AJith,All; As far as I understand 1) no options client side only 2) -s server side 3) -sd -ss service side discriptions, this only work with -ss 4) -g all, but no service.xml .. So I put -g -sd ..still none becouse -sd only works with -ss .. so -g -ss and -sd Ouch. Sorry but I feel this is far too complex. shall we change the options for 1.1? for example (Or do we need to me backward compatible with the tool options?) -GClient or nothing for Client -GServer for server with service.xml -GAll for everything -GTest all with test case How about: - -c or nothing for client - -s for service side with services.xml - -g for both client and server (both the above basically) - -g -t for all and test case That is, introduce a -t argument for test case generation. By test case we mean what exactly .. a stub?? In that case its only meaningful for a server side case anyway. Do we have use case for generating server side code without a service.xml file ? Do we have use case for generating service.xml without server side code? (we could at least assume -ss given -sd) +1. So basically same as your proposal except use option names that are closer to what we have now. Sanjiva. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2]WSDL2Java Code generation option
+1 for Sanjiva's suggestions: -c client side -s server side -t test case generation. I think -a should be for all, but I assume it is in use already? -- Tom Jordahl Adobe ColdFusion Team -Original Message- From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] Sent: Monday, October 09, 2006 5:13 PM To: axis-dev@ws.apache.org Cc: Thilina Gunarathne Subject: Re: [Axis2]WSDL2Java Code generation option On Mon, 2006-10-09 at 07:54 -0400, Srinath Perera wrote: Hi AJith,All; As far as I understand 1) no options client side only 2) -s server side 3) -sd -ss service side discriptions, this only work with -ss 4) -g all, but no service.xml .. So I put -g -sd ..still none becouse -sd only works with -ss .. so -g -ss and -sd Ouch. Sorry but I feel this is far too complex. shall we change the options for 1.1? for example (Or do we need to me backward compatible with the tool options?) -GClient or nothing for Client -GServer for server with service.xml -GAll for everything -GTest all with test case How about: - -c or nothing for client - -s for service side with services.xml - -g for both client and server (both the above basically) - -g -t for all and test case That is, introduce a -t argument for test case generation. By test case we mean what exactly .. a stub?? In that case its only meaningful for a server side case anyway. Do we have use case for generating server side code without a service.xml file ? Do we have use case for generating service.xml without server side code? (we could at least assume -ss given -sd) +1. So basically same as your proposal except use option names that are closer to what we have now. Sanjiva. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2]WSDL2Java Code generation option
Hi AJith,All; As far as I understand 1) no options client side only 2) -s server side 3) -sd -ss service side discriptions, this only work with -ss 4) -g all, but no service.xml .. So I put -g -sd ..still none becouse -sd only works with -ss .. so -g -ss and -sd Sorry but I feel this is far too complex. shall we change the options for 1.1? for example (Or do we need to me backward compatible with the tool options?) -GClient or nothing for Client -GServer for server with service.xml -GAll for everything -GTest all with test case Do we have use case for generating server side code without a service.xml file ? Do we have use case for generating service.xml without server side code? (we could at least assume -ss given -sd) thoughts? Thanks Srinath On 10/7/06, Ajith Ranabahu [EMAIL PROTECTED] wrote: Hi, I guess I should say why this style was selected. As for Axis1 the code generator always generates the client code when asked for the server side code. It seemed a bit ugly an somewhat confusing from the users point of view [ I also get a stub when I ask for a skeleton ??] . Hence the option -g to (generate-all) needs to be used to generate both the client and server side code. Ajith On 10/7/06, Dennis Sosnoski [EMAIL PROTECTED] wrote: Try the -g option. - Dennis Davanum Srinivas wrote: :) +1 from me. I tried sneaking this in a couple of times via the testcase generation option. Not sure if it still works. (-ss -sd -t) -- dims On 10/7/06, Srinath Perera [EMAIL PROTECTED] wrote: Hi All; Right now When we codegen for server side with WSDL2Java .. when we give -sd or -ss it create only server side code. However it is very useful if it generate both server and client side code. Axis1.1 use to do that. If you think about it .. 90% of the time user will need to check does his service is working and will generate the client side code as well. Thanks Srinath -- Srinath Perera: http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ajith Ranabahu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Srinath Perera: Indiana University, Bloomington http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2]WSDL2Java Code generation option
Hi, I guess you have a point about -ss and -sd. I mean we can assume that -ss implies -sd Ajith On 10/9/06, Srinath Perera [EMAIL PROTECTED] wrote: Hi AJith,All; As far as I understand 1) no options client side only 2) -s server side 3) -sd -ss service side discriptions, this only work with -ss 4) -g all, but no service.xml .. So I put -g -sd ..still none becouse -sd only works with -ss .. so -g -ss and -sd Sorry but I feel this is far too complex. shall we change the options for 1.1? for example (Or do we need to me backward compatible with the tool options?) -GClient or nothing for Client -GServer for server with service.xml -GAll for everything -GTest all with test case Do we have use case for generating server side code without a service.xml file ? Do we have use case for generating service.xml without server side code? (we could at least assume -ss given -sd) thoughts? Thanks Srinath On 10/7/06, Ajith Ranabahu [EMAIL PROTECTED] wrote: Hi, I guess I should say why this style was selected. As for Axis1 the code generator always generates the client code when asked for the server side code. It seemed a bit ugly an somewhat confusing from the users point of view [ I also get a stub when I ask for a skeleton ??] . Hence the option -g to (generate-all) needs to be used to generate both the client and server side code. Ajith On 10/7/06, Dennis Sosnoski [EMAIL PROTECTED] wrote: Try the -g option. - Dennis Davanum Srinivas wrote: :) +1 from me. I tried sneaking this in a couple of times via the testcase generation option. Not sure if it still works. (-ss -sd -t) -- dims On 10/7/06, Srinath Perera [EMAIL PROTECTED] wrote: Hi All; Right now When we codegen for server side with WSDL2Java .. when we give -sd or -ss it create only server side code. However it is very useful if it generate both server and client side code. Axis1.1 use to do that. If you think about it .. 90% of the time user will need to check does his service is working and will generate the client side code as well. Thanks Srinath -- Srinath Perera: http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ajith Ranabahu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Srinath Perera: Indiana University, Bloomington http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ajith Ranabahu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2]WSDL2Java Code generation option
On Mon, 2006-10-09 at 07:54 -0400, Srinath Perera wrote: Hi AJith,All; As far as I understand 1) no options client side only 2) -s server side 3) -sd -ss service side discriptions, this only work with -ss 4) -g all, but no service.xml .. So I put -g -sd ..still none becouse -sd only works with -ss .. so -g -ss and -sd Ouch. Sorry but I feel this is far too complex. shall we change the options for 1.1? for example (Or do we need to me backward compatible with the tool options?) -GClient or nothing for Client -GServer for server with service.xml -GAll for everything -GTest all with test case How about: - -c or nothing for client - -s for service side with services.xml - -g for both client and server (both the above basically) - -g -t for all and test case That is, introduce a -t argument for test case generation. By test case we mean what exactly .. a stub?? In that case its only meaningful for a server side case anyway. Do we have use case for generating server side code without a service.xml file ? Do we have use case for generating service.xml without server side code? (we could at least assume -ss given -sd) +1. So basically same as your proposal except use option names that are closer to what we have now. Sanjiva. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2]WSDL2Java Code generation option
+1 yep :) That way we can keep most of old options intact Srinath On 10/9/06, Sanjiva Weerawarana [EMAIL PROTECTED] wrote: On Mon, 2006-10-09 at 07:54 -0400, Srinath Perera wrote: Hi AJith,All; As far as I understand 1) no options client side only 2) -s server side 3) -sd -ss service side discriptions, this only work with -ss 4) -g all, but no service.xml .. So I put -g -sd ..still none becouse -sd only works with -ss .. so -g -ss and -sd Ouch. Sorry but I feel this is far too complex. shall we change the options for 1.1? for example (Or do we need to me backward compatible with the tool options?) -GClient or nothing for Client -GServer for server with service.xml -GAll for everything -GTest all with test case How about: - -c or nothing for client - -s for service side with services.xml - -g for both client and server (both the above basically) - -g -t for all and test case That is, introduce a -t argument for test case generation. By test case we mean what exactly .. a stub?? In that case its only meaningful for a server side case anyway. Do we have use case for generating server side code without a service.xml file ? Do we have use case for generating service.xml without server side code? (we could at least assume -ss given -sd) +1. So basically same as your proposal except use option names that are closer to what we have now. Sanjiva. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Srinath Perera: Indiana University, Bloomington http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2]WSDL2Java Code generation option
:) +1 from me. I tried sneaking this in a couple of times via the testcase generation option. Not sure if it still works. (-ss -sd -t) -- dims On 10/7/06, Srinath Perera [EMAIL PROTECTED] wrote: Hi All; Right now When we codegen for server side with WSDL2Java .. when we give -sd or -ss it create only server side code. However it is very useful if it generate both server and client side code. Axis1.1 use to do that. If you think about it .. 90% of the time user will need to check does his service is working and will generate the client side code as well. Thanks Srinath -- Srinath Perera: http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2]WSDL2Java Code generation option
Try the -g option. - Dennis Davanum Srinivas wrote: :) +1 from me. I tried sneaking this in a couple of times via the testcase generation option. Not sure if it still works. (-ss -sd -t) -- dims On 10/7/06, Srinath Perera [EMAIL PROTECTED] wrote: Hi All; Right now When we codegen for server side with WSDL2Java .. when we give -sd or -ss it create only server side code. However it is very useful if it generate both server and client side code. Axis1.1 use to do that. If you think about it .. 90% of the time user will need to check does his service is working and will generate the client side code as well. Thanks Srinath -- Srinath Perera: http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2]WSDL2Java Code generation option
Hi, I guess I should say why this style was selected. As for Axis1 the code generator always generates the client code when asked for the server side code. It seemed a bit ugly an somewhat confusing from the users point of view [ I also get a stub when I ask for a skeleton ??] . Hence the option -g to (generate-all) needs to be used to generate both the client and server side code. Ajith On 10/7/06, Dennis Sosnoski [EMAIL PROTECTED] wrote: Try the -g option. - Dennis Davanum Srinivas wrote: :) +1 from me. I tried sneaking this in a couple of times via the testcase generation option. Not sure if it still works. (-ss -sd -t) -- dims On 10/7/06, Srinath Perera [EMAIL PROTECTED] wrote: Hi All; Right now When we codegen for server side with WSDL2Java .. when we give -sd or -ss it create only server side code. However it is very useful if it generate both server and client side code. Axis1.1 use to do that. If you think about it .. 90% of the time user will need to check does his service is working and will generate the client side code as well. Thanks Srinath -- Srinath Perera: http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ajith Ranabahu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
