Does anyone have any objections or comments regarding the proposed response? Thanks.
On 10/23/07, Andrew Das <[EMAIL PROTECTED]> wrote: > > The samples will not have any WebSphere specifics, so that should not be > of concern. The primary goal is to demonstrate interoperability with > WebSphere, using Axis2 API's and tools. My responses to Nick's comments [1] > and [2] are below. > > 1. Making the samples generic and vendor neutral would be above and beyond > IBM's immediate goal. However, if most of the work can be done using Axis2 > code generation and packaging tools then it should not be of major concern. > I agree keeping the samples flexible will be of more value to the > community. Also, an independent, off-line, command-line driven test module > would provide further flexibility and autonomy. Therefore, I do not foresee > any problems with Nick's or David's suggestions. Does anyone else have any > objections or comments? > > 2. Again, I agree with Nick. As this item is a bit trickier from a code > management perspective, it seems a lot simpler to have a single interop > module within Axis2, rather than seperately manage and maintain the > samples for each Apache QoS project. If the Apache parties can confirm a > vested interest in this approach, then creating a single interop module > within Axis2 would be the ideal way to go. > > On 10/23/07, Nicholas L Gallardo <[EMAIL PROTECTED]> wrote: > > > > I agree completely with those that have mentioned making this a > > non-automated/non-mandatory module. There shouldn't be anything in the tree > > that prevents building off-line. > > > > Andrew, what if anything is WebSphere specific about the samples that > > you want to integrate? Nothing? Deployment info? Code? > > > > Your stated goal is to: > > > > "test interoperability with the WebSphere WS Feature Pack services[1]. > > Additionally, we are also interested in testing Quality of services[2] > > using the same samples integrated in the Axis2 source." > > > > So, there are two different goals here that will require different > > solutions. I'll separate my comments for each. > > > > [1] To test interop with WebSphere (or any other web service provider > > for that matter) in some semi-automated fashion, the best solution seems to > > be what's been proposed by David below. Create either a new build module or > > a sub component under modules/integration and include the sample there. What > > that sample is can very as to make it effective in testing a variety of > > interop scenarios. > > > > For instance, if your sample included a few WSDL documents, you could > > have the build generate the client/server artifacts using both the Axis2/ADB > > APIs along with a JAX-WS/JAXB version. Then, each of those could be bundled > > up into either an Axis2 deployable AAR or a Java EE 5 deployable EAR. That > > gives anyone the flexibility to take either the client or server and run > > them in a number of environments beyond just Axis2 or WebSphere. This could > > include dropping the server EAR onto a Geronimo install running CXF and > > interoping with Axis2 on the client side. > > > > A generic approach would be of greatest value to the community. > > > > > > > > [2] Any WS-* interop beyond WS-Addressing should not be integrated into > > the Axis2 build in my opinion. That said, it would be useful to have that > > interop where you could leverage the samples built in [1] and > > bundle/configure whatever server's QoS you wanted to do the interop. PMC > > folks, is there room in the Apache WS project for a sub project focused on > > interop? Would there be any value in getting the other Apache parties with a > > vested interop interest (Sandesha, CXF, etc.) to participate? > > > > Regards, > > > > -Nick > > > > > > [image: Inactive hide details for "David Illsley" > > <[EMAIL PROTECTED]>] "David Illsley" <[EMAIL PROTECTED]> > > > > > > > > *"David Illsley" <[EMAIL PROTECTED]>* > > > > 10/22/2007 05:39 PM Please respond to > > axis-dev@ws.apache.org > > > > > > To > > > > axis-dev@ws.apache.org > > cc > > > > > > Subject > > > > Re: Axis2 and WebSphere Interoperability > > <with-IBM-hat-explicitly-removed> > > :-) I don't think you want to put the websphere samples in that > > directory (modile/integration/manual)... I don't think it actually > > builds, and it may not have a long lifespan (see below). > > > > How about you create a module in modules/integration/websphere which > > isn't hooked in to the build by default. My maven2-fu is a little > > rusty but it should be possible for you to include a couple of > > different profiles - one for local axis2 testing and one to test > > against a published endpoint. If that works we could at a later point > > consider integrating that into the build, with the local axis2 profile > > being the default. > > > > I'd warn you up-front that you'll probably have to maintain these > > yourself or they'll quickly break and probably be ignored, and if > > that's the case then after a while (like will probably happen to > > modules/integration/manual when I get a chance) they will be deleted. > > > > I do think that (re?)creating public interop for WS-* is a good thing > > and this seems like a simple (and easily reversed if it doesn't work > > out) thing to do. > > David > > </with-IBM-hat-explicitly-removed> > > > > On 22/10/2007, Andrew Das < [EMAIL PROTECTED]> wrote: > > > We prefer to put in an automated process in Axis2 so that we don't > > have to > > > manage when and where to run the samples. Any developer, including > > internal > > > developers can run our samples against a snapshot or released Axis2 > > build. > > > This will free us from managing and maintaining the test cycles, if > > done > > > internally. Furthermore, it will be a good story for IBM by > > demonstrating a > > > publicized effort to test interoperability. > > > > > > I have also noticed that Sun has introduced their interoperability > > samples. > > > So I do not imagine our request to be unique in any way. Please > > correct me > > > if I am wrong. We could place the samples in the same module as Sun is > > > > > using. For example, the Sun samples I am referring to are under: > > > <root>\Axis2\modules\integration\manual\src\test\interop\sun > > > > > > Thanks Eran. > > > > > > > > > On 10/19/07, Eran Chinthaka < [EMAIL PROTECTED]> wrote: > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > > Hash: SHA1 > > > > > > > > Hi Andrew, > > > > > > > > 1.Why do you want to put them "inside" Axis2? > > > > Until convinced otherwise, I am not sure whether we need to add > > those > > > > interop tests to main build. And also why can not you host that in > > your > > > > end? That question is somewhat related to Q1. > > > > > > > > 2. Where do you want to put them? There is a module inside Axis2, > > which > > > > of course is used to test widely used WSDLs. If you really want, the > > > > > > best place is it. > > > > > > > > Some of our Axis2 devs worked inter-operating with other platforms > > also, > > > > but we never thought of putting them "inside" Axis2. So why do you > > think > > > > we should put those Websphere specific examples inside Axis2? > > > > > > > > Please help us to understand the above concerns. > > > > > > > > Thanks, > > > > Chinthaka > > > > > > > > Andrew Das wrote: > > > > > Hi David, > > > > > Thanks for the quick response. The samples we intend to add are > > > > > specifically designed and customized for WebSphere services. I am > > not > > > > > certain the current Axis2 samples will work. Additionally, I can > > foresee > > > > > future changes to the WebSphere sample clients based on API/spec > > > > > changes, so mucking with the Axis2 samples would not be a good > > idea. > > > > > Finally, our endpoints will be hardcoded and we need to have > > enough > > > > > flexibility to change those in the future. > > > > > > > > > > Not sure if my response helped. As I mentioned earlier, we are > > looking > > > > > for the best way to accomplish WebSphere interoperability. > > Therefore I > > > > > am open to new suggestions if it will help us integrate with Axis2 > > and > > > > > satisfy our goals. > > > > > > > > > > Thanks. > > > > > > > > > > On 10/19/07, *David Illsley* <[EMAIL PROTECTED] > > > > > <mailto:[EMAIL PROTECTED] <[EMAIL PROTECTED]>>> wrote: > > > > > > > > > > Hi Andrew, > > > > > It's not entirely clear to me what you're trying to do... are > > you > > > > > looking to add client and service samples into the axis2 build > > which > > > > > you can then run against WebSphere? If so, how do the existing > > Axis2 > > > > > samples[1] match up to what you're looking for? > > > > > David > > > > > [1] > > > > > > > > http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/samples/ > > > > > > > < > > > http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/samples/ > > > > > > > > > > > > > On 19/10/2007, Andrew Das < [EMAIL PROTECTED] > > > > > <mailto:[EMAIL PROTECTED] <[EMAIL PROTECTED]>>> wrote: > > > > > > Hello, > > > > > > We are looking to identify a strategy to inject basic > > samples into > > > the > > > > > > Apache Axis2 build tree. The purpose of the samples will be > > to > > > test > > > > > > interoperability with the WebSphere WS Feature Pack > > services. > > > > > Additionally, > > > > > > we are also interested in testing Quality of services using > > the > > > > > same samples > > > > > > integrated in the Axis2 source. Could you please advise on > > what's > > > > > the best > > > > > > way to accomplish this? Thanks. > > > > > > > > > > > > -- > > > > > > Regards, > > > > > > Andrew Das > > > > > > > > > > > > > > > -- > > > > > David Illsley - IBM Web Services Development > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: > > > [EMAIL PROTECTED] > > > > > < mailto:[EMAIL PROTECTED]<[EMAIL PROTECTED]> > > > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > < mailto:[EMAIL PROTECTED]<[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Regards, > > > > > Andrew Das > > > > > > > > -----BEGIN PGP SIGNATURE----- > > > > Version: GnuPG v1.4.6 (GNU/Linux) > > > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > > > > > > > > > > iD8DBQFHGUxajON2uBzUhh8RAk3YAJ9QYLZQvqGfDSLKv29PfjqjBEakUQCfahZn > > > > zaMh6kb3ML51NBePFPb8zuA= > > > > =OOgW > > > > -----END PGP SIGNATURE----- > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: > > > [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > -- > > > Regards, > > > Andrew Das > > > > > > -- > > David Illsley - IBM Web Services Development > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > -- > Regards, > Andrew Das -- Regards, Andrew Das
<<graycol.gif>>
<<ecblank.gif>>
