<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]>> 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]>> 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] >
> > >     For additional commands, e-mail: [EMAIL PROTECTED]
> > >     <mailto:[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]

Reply via email to