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 Nicholas L Gallardo <nl...@us.ibm.com> on 2008/01/24 21:55:43 UTC
[axis2] proposal: jaxws-integration module
All,
As we start the process of integrating the JAX-WS runtime into the Axis2
deployment model, it seems like a good time to revisit the existing
structure for the jaxws module. I'm specifically interested in improving
the structure of how function or end-to-end tests are added in.
Right now, the modules/jaxws/test bucket is a mix of both unit tests and
function tests. I'd like to split that up and introduce a new module,
jaxws-integration, that has the function tests in a more organized
framework than exists today. This would also allow us to remove the wonky
JAXWSTest driver that exists today, making it easier to drop unit tests in
and run them individually.
As time goes on, if we need a special location for deployment code for
JAX-WS, this module can serve as a repository for that.
Thoughts?
-Nick
Re: [axis2] proposal: jaxws-integration module
Posted by Lahiru Sandakith <sa...@gmail.com>.
+1 for moving the tests in to an independent module jaxws-integration.
Thanks
Lahiru Sandakith
On Jan 25, 2008 2:25 AM, Nicholas L Gallardo <nl...@us.ibm.com> wrote:
> All,
>
> As we start the process of integrating the JAX-WS runtime into the Axis2
> deployment model, it seems like a good time to revisit the existing
> structure for the jaxws module. I'm specifically interested in improving the
> structure of how function or end-to-end tests are added in.
>
> Right now, the modules/jaxws/test bucket is a mix of both unit tests and
> function tests. I'd like to split that up and introduce a new module,
> jaxws-integration, that has the function tests in a more organized framework
> than exists today. This would also allow us to remove the wonky JAXWSTest
> driver that exists today, making it easier to drop unit tests in and run
> them individually.
>
> As time goes on, if we need a special location for deployment code for
> JAX-WS, this module can serve as a repository for that.
>
> Thoughts?
>
> -Nick
>
>
--
Thanks
Lahiru Sandakith
http://sandakith.wordpress.com/
GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: [axis2] proposal: jaxws-integration module
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
definitely worth giving it a shot again :)
- -- dims
Jeff Barrett wrote:
| +1 to moving the tests to a jaxws-integration module and to splitting out
| the tests in JAXWSTest.
|
| Note that spliting out the JAXWSTest may be trickier than it sounds. Dims
| actually tried that some time back, making each test run independently.
| With some JDKs (but not all) and/or on Windows there was a timing problem
| with the server starting and stopping in each test. I forget now if the
| problem surfaced when using different JDKs or if it was a Windows-only
| problem, but in the end the change was reverted because, at that time, we
| couldn't take the time to restructure the test to work everywhere.
|
| 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
|
|
|
| "David Illsley" <da...@gmail.com>
| 01/24/2008 05:59 PM
| Please respond to
| axis-dev@ws.apache.org
|
|
| To
| axis-dev@ws.apache.org
| cc
|
| Subject
| Re: [axis2] proposal: jaxws-integration module
|
|
|
|
|
|
| Sounds good to me. The big JAXWSTest driver has always bugged me, and
| I've always found the JAX-WS tests pretty impenetrable (more so than
| the implementation!)
| David
|
| On Jan 24, 2008 8:55 PM, Nicholas L Gallardo <nl...@us.ibm.com> wrote:
|>
|> All,
|>
|> As we start the process of integrating the JAX-WS runtime into the
| Axis2
|> deployment model, it seems like a good time to revisit the existing
|> structure for the jaxws module. I'm specifically interested in improving
| the
|> structure of how function or end-to-end tests are added in.
|>
|> Right now, the modules/jaxws/test bucket is a mix of both unit tests
| and
|> function tests. I'd like to split that up and introduce a new module,
|> jaxws-integration, that has the function tests in a more organized
| framework
|> than exists today. This would also allow us to remove the wonky
| JAXWSTest
|> driver that exists today, making it easier to drop unit tests in and run
|> them individually.
|>
|> As time goes on, if we need a special location for deployment code for
|> JAX-WS, this module can serve as a repository for that.
|>
|> Thoughts?
|>
|> -Nick
|>
|>
|
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFHmfBsgNg6eWEDv1kRAhM7AJ9OI5OOXmSQ7RiZjJERyF2zIys/nACbBC1B
z6oXmYGBb4xRU1CBBSY5G2Y=
=kzf0
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [axis2] proposal: jaxws-integration module
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
If you need inspiration :)
http://svn.apache.org/viewvc?view=rev&revision=504712
http://svn.apache.org/viewvc?view=rev&revision=505003
- -- dims
Nicholas L Gallardo wrote:
| Thanks guys... I'll get this going and post a note when there's something
| usable.
|
| Cheers,
|
| -Nick
|
|
|
|
|
| Jeff
| Barrett/Austin/IB
| M@IBMUS To
| axis-dev@ws.apache.org
| 01/25/2008 08:14 cc
| AM
| Subject
| Re: [axis2] proposal:
| Please respond to jaxws-integration module
| axis-dev@ws.apach
| e.org
|
|
|
|
|
|
|
|
| +1 to moving the tests to a jaxws-integration module and to splitting out
| the tests in JAXWSTest.
|
| Note that spliting out the JAXWSTest may be trickier than it sounds. Dims
| actually tried that some time back, making each test run independently.
| With some JDKs (but not all) and/or on Windows there was a timing problem
| with the server starting and stopping in each test. I forget now if the
| problem surfaced when using different JDKs or if it was a Windows-only
| problem, but in the end the change was reverted because, at that time, we
| couldn't take the time to restructure the test to work everywhere.
|
| 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
|
|
|
| "David Illsley" <da...@gmail.com>
| 01/24/2008 05:59 PM
| Please respond to
| axis-dev@ws.apache.org
|
|
| To
| axis-dev@ws.apache.org
| cc
|
| Subject
| Re: [axis2] proposal: jaxws-integration module
|
|
|
|
|
|
| Sounds good to me. The big JAXWSTest driver has always bugged me, and
| I've always found the JAX-WS tests pretty impenetrable (more so than
| the implementation!)
| David
|
| On Jan 24, 2008 8:55 PM, Nicholas L Gallardo <nl...@us.ibm.com> wrote:
|>
|> All,
|>
|> As we start the process of integrating the JAX-WS runtime into the
| Axis2
|> deployment model, it seems like a good time to revisit the existing
|> structure for the jaxws module. I'm specifically interested in improving
| the
|> structure of how function or end-to-end tests are added in.
|>
|> Right now, the modules/jaxws/test bucket is a mix of both unit tests
| and
|> function tests. I'd like to split that up and introduce a new module,
|> jaxws-integration, that has the function tests in a more organized
| framework
|> than exists today. This would also allow us to remove the wonky
| JAXWSTest
|> driver that exists today, making it easier to drop unit tests in and run
|> them individually.
|>
|> As time goes on, if we need a special location for deployment code for
|> JAX-WS, this module can serve as a repository for that.
|>
|> Thoughts?
|>
|> -Nick
|>
|>
|
|
|
| --
| David Illsley - IBM Web Services Development
|
| ---------------------------------------------------------------------
| 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
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFHmhY2gNg6eWEDv1kRAj3XAJ0aHJTVnSUak1Vsy3xGt0sozaRUMACgvKIn
Et4LSFflOnzmWDGVWB/u9ZI=
=acYM
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [axis2] proposal: jaxws-integration module
Posted by Nicholas L Gallardo <nl...@us.ibm.com>.
Thanks guys... I'll get this going and post a note when there's something
usable.
Cheers,
-Nick
Jeff
Barrett/Austin/IB
M@IBMUS To
axis-dev@ws.apache.org
01/25/2008 08:14 cc
AM
Subject
Re: [axis2] proposal:
Please respond to jaxws-integration module
axis-dev@ws.apach
e.org
+1 to moving the tests to a jaxws-integration module and to splitting out
the tests in JAXWSTest.
Note that spliting out the JAXWSTest may be trickier than it sounds. Dims
actually tried that some time back, making each test run independently.
With some JDKs (but not all) and/or on Windows there was a timing problem
with the server starting and stopping in each test. I forget now if the
problem surfaced when using different JDKs or if it was a Windows-only
problem, but in the end the change was reverted because, at that time, we
couldn't take the time to restructure the test to work everywhere.
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
"David Illsley" <da...@gmail.com>
01/24/2008 05:59 PM
Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org
cc
Subject
Re: [axis2] proposal: jaxws-integration module
Sounds good to me. The big JAXWSTest driver has always bugged me, and
I've always found the JAX-WS tests pretty impenetrable (more so than
the implementation!)
David
On Jan 24, 2008 8:55 PM, Nicholas L Gallardo <nl...@us.ibm.com> wrote:
>
>
> All,
>
> As we start the process of integrating the JAX-WS runtime into the
Axis2
> deployment model, it seems like a good time to revisit the existing
> structure for the jaxws module. I'm specifically interested in improving
the
> structure of how function or end-to-end tests are added in.
>
> Right now, the modules/jaxws/test bucket is a mix of both unit tests
and
> function tests. I'd like to split that up and introduce a new module,
> jaxws-integration, that has the function tests in a more organized
framework
> than exists today. This would also allow us to remove the wonky
JAXWSTest
> driver that exists today, making it easier to drop unit tests in and run
> them individually.
>
> As time goes on, if we need a special location for deployment code for
> JAX-WS, this module can serve as a repository for that.
>
> Thoughts?
>
> -Nick
>
>
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
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] proposal: jaxws-integration module
Posted by Jeff Barrett <ba...@us.ibm.com>.
+1 to moving the tests to a jaxws-integration module and to splitting out
the tests in JAXWSTest.
Note that spliting out the JAXWSTest may be trickier than it sounds. Dims
actually tried that some time back, making each test run independently.
With some JDKs (but not all) and/or on Windows there was a timing problem
with the server starting and stopping in each test. I forget now if the
problem surfaced when using different JDKs or if it was a Windows-only
problem, but in the end the change was reverted because, at that time, we
couldn't take the time to restructure the test to work everywhere.
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
"David Illsley" <da...@gmail.com>
01/24/2008 05:59 PM
Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org
cc
Subject
Re: [axis2] proposal: jaxws-integration module
Sounds good to me. The big JAXWSTest driver has always bugged me, and
I've always found the JAX-WS tests pretty impenetrable (more so than
the implementation!)
David
On Jan 24, 2008 8:55 PM, Nicholas L Gallardo <nl...@us.ibm.com> wrote:
>
>
> All,
>
> As we start the process of integrating the JAX-WS runtime into the
Axis2
> deployment model, it seems like a good time to revisit the existing
> structure for the jaxws module. I'm specifically interested in improving
the
> structure of how function or end-to-end tests are added in.
>
> Right now, the modules/jaxws/test bucket is a mix of both unit tests
and
> function tests. I'd like to split that up and introduce a new module,
> jaxws-integration, that has the function tests in a more organized
framework
> than exists today. This would also allow us to remove the wonky
JAXWSTest
> driver that exists today, making it easier to drop unit tests in and run
> them individually.
>
> As time goes on, if we need a special location for deployment code for
> JAX-WS, this module can serve as a repository for that.
>
> Thoughts?
>
> -Nick
>
>
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
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] proposal: jaxws-integration module
Posted by David Illsley <da...@gmail.com>.
Sounds good to me. The big JAXWSTest driver has always bugged me, and
I've always found the JAX-WS tests pretty impenetrable (more so than
the implementation!)
David
On Jan 24, 2008 8:55 PM, Nicholas L Gallardo <nl...@us.ibm.com> wrote:
>
>
> All,
>
> As we start the process of integrating the JAX-WS runtime into the Axis2
> deployment model, it seems like a good time to revisit the existing
> structure for the jaxws module. I'm specifically interested in improving the
> structure of how function or end-to-end tests are added in.
>
> Right now, the modules/jaxws/test bucket is a mix of both unit tests and
> function tests. I'd like to split that up and introduce a new module,
> jaxws-integration, that has the function tests in a more organized framework
> than exists today. This would also allow us to remove the wonky JAXWSTest
> driver that exists today, making it easier to drop unit tests in and run
> them individually.
>
> As time goes on, if we need a special location for deployment code for
> JAX-WS, this module can serve as a repository for that.
>
> Thoughts?
>
> -Nick
>
>
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org