You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by Sanjiva Weerawarana <sa...@opensource.lk> on 2006/02/07 18:07:11 UTC
[axis2] VOTE: move tracer to ws-commons
We currently have the HTTP Tracer (aka tcpmon) in Axis2 and have another
version of it in Axis1.
I suggested this many years ago but was voted down. I'd like to move
this to WS commons because this has NOTHING to do with Axis1 or Axis2
and all it is just a damned useful bit of code.
Can we please move it to WS commons?
Here's my vote: +1.
Sanjiva.
p.s.: Thanks to Dims for the recent patch which triggered my memory
about wanting to push for this :).
Re: [axis2] VOTE: move tracer to ws-commons
Posted by Chathura Herath <ch...@gmail.com>.
+1.
I had a hard time selling a big jar to my collegue to use the
TCPmon/HTTPTracer. Having this in commons is gonna help.
Thanks
Chathura.
On 2/8/06, Thilina Gunarathne <cs...@gmail.com> wrote:
> Definitely +1... I'm sure this will increase the fame and usage of our good
> old tool TCPMON.. (IIRC this was a brain child of Dr.Sanjiva to track his
> email in good old days)
>
> ~Thilina
>
>
> On 2/8/06, Srinath Perera <he...@gmail.com> wrote:
> > +1
> >
> > Can we have a WS-commons jar .. as a one build as well for use in
> > Axis2 purposes, I hate having to increase the number of jars ..
> > already too many!!
> >
> > On 2/8/06, Deepal Jayasinghe <de...@opensource.lk> wrote:
> > > +1 from me too
> > >
> > > Eran Chinthaka wrote:
> > >
> > > > +1 from me too.
> > > >
> > > > Now we are accumulating some good things under WS-Commons.
> > > >
> > > > And this proposal will help us to ship a separate tracer jar for
> > > > people to use.
> > > >
> > > > -- Chinthaka
> > > >
> > > > Ajith Ranabahu wrote:
> > > >
> > > >>I would definitley +1 this, since the tracer has no dependency on the
> > > >>Axis2 codebase. If we did this earlier, we would not have to copy code
> > > >>over!
> > > >>
> > > >>
> > > >>On 2/7/06, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> > > >>
> > > >>
> > > >>>We currently have the HTTP Tracer (aka tcpmon) in Axis2 and have
> another
> > > >>>version of it in Axis1.
> > > >>>
> > > >>>I suggested this many years ago but was voted down. I'd like to move
> > > >>>this to WS commons because this has NOTHING to do with Axis1 or Axis2
> > > >>>and all it is just a damned useful bit of code.
> > > >>>
> > > >>>Can we please move it to WS commons?
> > > >>>
> > > >>>Here's my vote: +1.
> > > >>>
> > > >>>Sanjiva.
> > > >>>p.s.: Thanks to Dims for the recent patch which triggered my memory
> > > >>>about wanting to push for this :).
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>
> > > >>
> > > >>--
> > > >>Ajith Ranabahu
> > > >>
> > > >>
> > > >>
> > >
> > > --
> > > Thanks,
> > > Deepal
> > > ................................................................
> > > ~Future is Open~
> > >
> > >
> > >
> >
> >
> > --
> > ============================
> > Srinath Perera:
> > http://www.cs.indiana.edu/~hperera/
> > http://www.bloglines.com/blog/hemapani
> >
>
>
>
> --
> "May the SourcE be with u"
> http://webservices.apache.org/~thilina/
> http://thilinag.blogspot.com/
> http://www.bloglines.com/blog/Thilina
--
Chathura Herath
http://chathurah.blogspot.com/
Re: [axis2] VOTE: move tracer to ws-commons
Posted by Thilina Gunarathne <cs...@gmail.com>.
Definitely +1... I'm sure this will increase the fame and usage of our good
old tool TCPMON.. (IIRC this was a brain child of Dr.Sanjiva to track his
email in good old days)
~Thilina
On 2/8/06, Srinath Perera <he...@gmail.com> wrote:
>
> +1
>
> Can we have a WS-commons jar .. as a one build as well for use in
> Axis2 purposes, I hate having to increase the number of jars ..
> already too many!!
>
> On 2/8/06, Deepal Jayasinghe <de...@opensource.lk> wrote:
> > +1 from me too
> >
> > Eran Chinthaka wrote:
> >
> > > +1 from me too.
> > >
> > > Now we are accumulating some good things under WS-Commons.
> > >
> > > And this proposal will help us to ship a separate tracer jar for
> > > people to use.
> > >
> > > -- Chinthaka
> > >
> > > Ajith Ranabahu wrote:
> > >
> > >>I would definitley +1 this, since the tracer has no dependency on the
> > >>Axis2 codebase. If we did this earlier, we would not have to copy code
> > >>over!
> > >>
> > >>
> > >>On 2/7/06, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> > >>
> > >>
> > >>>We currently have the HTTP Tracer (aka tcpmon) in Axis2 and have
> another
> > >>>version of it in Axis1.
> > >>>
> > >>>I suggested this many years ago but was voted down. I'd like to move
> > >>>this to WS commons because this has NOTHING to do with Axis1 or Axis2
> > >>>and all it is just a damned useful bit of code.
> > >>>
> > >>>Can we please move it to WS commons?
> > >>>
> > >>>Here's my vote: +1.
> > >>>
> > >>>Sanjiva.
> > >>>p.s.: Thanks to Dims for the recent patch which triggered my memory
> > >>>about wanting to push for this :).
> > >>>
> > >>>
> > >>>
> > >>>
> > >>
> > >>
> > >>--
> > >>Ajith Ranabahu
> > >>
> > >>
> > >>
> >
> > --
> > Thanks,
> > Deepal
> > ................................................................
> > ~Future is Open~
> >
> >
> >
>
>
> --
> ============================
> Srinath Perera:
> http://www.cs.indiana.edu/~hperera/
> http://www.bloglines.com/blog/hemapani
>
--
"May the SourcE be with u"
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/
http://www.bloglines.com/blog/Thilina
Re: [axis2] VOTE: move tracer to ws-commons
Posted by Srinath Perera <he...@gmail.com>.
What I mean is to have ws-commmons jar as well in addition to
ws-commons-policy jar ect and use it in Axis2. If I want to set the
classpath for Axis2, too many jars is a nuisance at best
Srinath
On 2/8/06, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> On Wed, 2006-02-08 at 07:30 -0500, Srinath Perera wrote:
> > +1
> >
> > Can we have a WS-commons jar .. as a one build as well for use in
> > Axis2 purposes, I hate having to increase the number of jars ..
> > already too many!!
>
> I'm -1 to a ws-commons.jar idea .. each of these components are likely
> to have issues on their own timeframe and tying everything together
> makes life hard for us to maintain the pieces separately. Using
> -Djava.ext.dirs its not too bad to deal with multiple jars.
>
> Sanjiva.
>
>
>
--
============================
Srinath Perera:
http://www.cs.indiana.edu/~hperera/
http://www.bloglines.com/blog/hemapani
Re: [axis2] VOTE: move tracer to ws-commons
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
On Wed, 2006-02-08 at 07:30 -0500, Srinath Perera wrote:
> +1
>
> Can we have a WS-commons jar .. as a one build as well for use in
> Axis2 purposes, I hate having to increase the number of jars ..
> already too many!!
I'm -1 to a ws-commons.jar idea .. each of these components are likely
to have issues on their own timeframe and tying everything together
makes life hard for us to maintain the pieces separately. Using
-Djava.ext.dirs its not too bad to deal with multiple jars.
Sanjiva.
Re: [axis2] VOTE: move tracer to ws-commons
Posted by Srinath Perera <he...@gmail.com>.
+1
Can we have a WS-commons jar .. as a one build as well for use in
Axis2 purposes, I hate having to increase the number of jars ..
already too many!!
On 2/8/06, Deepal Jayasinghe <de...@opensource.lk> wrote:
> +1 from me too
>
> Eran Chinthaka wrote:
>
> > +1 from me too.
> >
> > Now we are accumulating some good things under WS-Commons.
> >
> > And this proposal will help us to ship a separate tracer jar for
> > people to use.
> >
> > -- Chinthaka
> >
> > Ajith Ranabahu wrote:
> >
> >>I would definitley +1 this, since the tracer has no dependency on the
> >>Axis2 codebase. If we did this earlier, we would not have to copy code
> >>over!
> >>
> >>
> >>On 2/7/06, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> >>
> >>
> >>>We currently have the HTTP Tracer (aka tcpmon) in Axis2 and have another
> >>>version of it in Axis1.
> >>>
> >>>I suggested this many years ago but was voted down. I'd like to move
> >>>this to WS commons because this has NOTHING to do with Axis1 or Axis2
> >>>and all it is just a damned useful bit of code.
> >>>
> >>>Can we please move it to WS commons?
> >>>
> >>>Here's my vote: +1.
> >>>
> >>>Sanjiva.
> >>>p.s.: Thanks to Dims for the recent patch which triggered my memory
> >>>about wanting to push for this :).
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >>--
> >>Ajith Ranabahu
> >>
> >>
> >>
>
> --
> Thanks,
> Deepal
> ................................................................
> ~Future is Open~
>
>
>
--
============================
Srinath Perera:
http://www.cs.indiana.edu/~hperera/
http://www.bloglines.com/blog/hemapani
Re: [axis2] VOTE: move tracer to ws-commons
Posted by Deepal Jayasinghe <de...@opensource.lk>.
+1 from me too
Eran Chinthaka wrote:
> +1 from me too.
>
> Now we are accumulating some good things under WS-Commons.
>
> And this proposal will help us to ship a separate tracer jar for
> people to use.
>
> -- Chinthaka
>
> Ajith Ranabahu wrote:
>
>>I would definitley +1 this, since the tracer has no dependency on the
>>Axis2 codebase. If we did this earlier, we would not have to copy code
>>over!
>>
>>
>>On 2/7/06, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
>>
>>
>>>We currently have the HTTP Tracer (aka tcpmon) in Axis2 and have another
>>>version of it in Axis1.
>>>
>>>I suggested this many years ago but was voted down. I'd like to move
>>>this to WS commons because this has NOTHING to do with Axis1 or Axis2
>>>and all it is just a damned useful bit of code.
>>>
>>>Can we please move it to WS commons?
>>>
>>>Here's my vote: +1.
>>>
>>>Sanjiva.
>>>p.s.: Thanks to Dims for the recent patch which triggered my memory
>>>about wanting to push for this :).
>>>
>>>
>>>
>>>
>>
>>
>>--
>>Ajith Ranabahu
>>
>>
>>
--
Thanks,
Deepal
................................................................
~Future is Open~
Re: [axis2] VOTE: move tracer to ws-commons
Posted by Eran Chinthaka <ch...@opensource.lk>.
+1 from me too.
Now we are accumulating some good things under WS-Commons.
And this proposal will help us to ship a separate tracer jar for people
to use.
-- Chinthaka
Ajith Ranabahu wrote:
>I would definitley +1 this, since the tracer has no dependency on the
>Axis2 codebase. If we did this earlier, we would not have to copy code
>over!
>
>
>On 2/7/06, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
>
>
>>We currently have the HTTP Tracer (aka tcpmon) in Axis2 and have another
>>version of it in Axis1.
>>
>>I suggested this many years ago but was voted down. I'd like to move
>>this to WS commons because this has NOTHING to do with Axis1 or Axis2
>>and all it is just a damned useful bit of code.
>>
>>Can we please move it to WS commons?
>>
>>Here's my vote: +1.
>>
>>Sanjiva.
>>p.s.: Thanks to Dims for the recent patch which triggered my memory
>>about wanting to push for this :).
>>
>>
>>
>>
>
>
>--
>Ajith Ranabahu
>
>
>
Re: [axis2] VOTE: move tracer to ws-commons
Posted by Ajith Ranabahu <aj...@gmail.com>.
I would definitley +1 this, since the tracer has no dependency on the
Axis2 codebase. If we did this earlier, we would not have to copy code
over!
On 2/7/06, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> We currently have the HTTP Tracer (aka tcpmon) in Axis2 and have another
> version of it in Axis1.
>
> I suggested this many years ago but was voted down. I'd like to move
> this to WS commons because this has NOTHING to do with Axis1 or Axis2
> and all it is just a damned useful bit of code.
>
> Can we please move it to WS commons?
>
> Here's my vote: +1.
>
> Sanjiva.
> p.s.: Thanks to Dims for the recent patch which triggered my memory
> about wanting to push for this :).
>
>
--
Ajith Ranabahu
Re: [axis2] VOTE: move tracer to ws-commons
Posted by Dennis Sosnoski <dm...@sosnoski.com>.
Great! +1
- Dennis
Sanjiva Weerawarana wrote:
>We currently have the HTTP Tracer (aka tcpmon) in Axis2 and have another
>version of it in Axis1.
>
>I suggested this many years ago but was voted down. I'd like to move
>this to WS commons because this has NOTHING to do with Axis1 or Axis2
>and all it is just a damned useful bit of code.
>
>Can we please move it to WS commons?
>
>Here's my vote: +1.
>
>Sanjiva.
>p.s.: Thanks to Dims for the recent patch which triggered my memory
>about wanting to push for this :).
>
>
>
AW: [axis2] VOTE: move tracer to ws-commons
Posted by Franz Fehringer <fe...@isogmbh.de>.
In Axis1 the resend functionality of tcpmon does not work.
I issued AXIS-2373 (including cause and workaround).
Is/will this fixed for either Axis1 or Axis2?
Greetings
Franz
-----Ursprüngliche Nachricht-----
Von: Sanjiva Weerawarana [mailto:sanjiva@opensource.lk]
Gesendet: Dienstag, 7. Februar 2006 18:07
An: commons-dev@ws.apache.org; axis-dev@ws.apache.org
Betreff: [axis2] VOTE: move tracer to ws-commons
We currently have the HTTP Tracer (aka tcpmon) in Axis2 and have another
version of it in Axis1.
I suggested this many years ago but was voted down. I'd like to move
this to WS commons because this has NOTHING to do with Axis1 or Axis2
and all it is just a damned useful bit of code.
Can we please move it to WS commons?
Here's my vote: +1.
Sanjiva.
p.s.: Thanks to Dims for the recent patch which triggered my memory
about wanting to push for this :).
AW: [axis2] VOTE: move tracer to ws-commons
Posted by Franz Fehringer <fe...@isogmbh.de>.
In Axis1 the resend functionality of tcpmon does not work.
I issued AXIS-2373 (including cause and workaround).
Is/will this fixed for either Axis1 or Axis2?
Greetings
Franz
-----Ursprüngliche Nachricht-----
Von: Sanjiva Weerawarana [mailto:sanjiva@opensource.lk]
Gesendet: Dienstag, 7. Februar 2006 18:07
An: commons-dev@ws.apache.org; axis-dev@ws.apache.org
Betreff: [axis2] VOTE: move tracer to ws-commons
We currently have the HTTP Tracer (aka tcpmon) in Axis2 and have another
version of it in Axis1.
I suggested this many years ago but was voted down. I'd like to move
this to WS commons because this has NOTHING to do with Axis1 or Axis2
and all it is just a damned useful bit of code.
Can we please move it to WS commons?
Here's my vote: +1.
Sanjiva.
p.s.: Thanks to Dims for the recent patch which triggered my memory
about wanting to push for this :).