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
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?
Hi Sanjiva,
Yes, I am an IBM employee in the WS-Interoperability group.
On 10/22/07, Sanjiva Weerawarana [EMAIL PROTECTED] wrote:
If you really want to have hardcoded endpoints etc. then the solution is
to host those samples somewhere and have some automated execution of those
against Axis2
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
Hi, this sounds good - please see comments inline.
On 19/10/2007, David Illsley [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,
]
**
Jeremy Hughes [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
10/22/2007 11:58 AM
Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org
cc
Subject
Re: [Axis2] Axis2 and WebSphere Interoperability
Hi, this sounds good
Yes they will be.
On 10/20/07, Paul Fremantle [EMAIL PROTECTED] wrote:
Andrew
Are these WebSphere endpoints going to be publicly (internet) accessible?
Paul
On 10/19/07, Andrew Das [EMAIL PROTECTED] wrote:
Hi David,
Thanks for the quick response. The samples we intend to add are
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
I have no objecting on introducing these samples, and I think it is good
to have such a set of samples. But my only worry is I should be able to
run the build off line. Therefore rather than adding to the build
directly let's have a separate maven option to run those sample ,
something like
mvn
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
If you really want to have hardcoded endpoints etc. then the solution is
to host those samples somewhere and have some automated execution of those
against Axis2 nightly builds.
Its not acceptable to commit into the ASF repo some code that is only
designed to work against some WebSphere
Andrew
Are these WebSphere endpoints going to be publicly (internet) accessible?
Paul
On 10/19/07, Andrew Das [EMAIL PROTECTED] 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
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
-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.
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]
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
16 matches
Mail list logo
