RE: [axis1] more stable version of axis

2006-06-19 Thread michel.lequim
 thanks for all, it help us a lot


Michel Lequim

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Cyrille Le Clerc
Sent: Monday, June 19, 2006 1:41 PM
To: axis-user@ws.apache.org
Subject: Re: [axis1] more stable version of axis

   Hello Michel,

   I confirm you client side timeouts work as expected in Axis 1.4 .

   To set client side socket timeouts, you have to invoke
"myStub.setTimeout(x)" (in millis). Note that you retrieve your stub
calling MyServiceLocator.getMyBinding() and note that setTimeout(x) is
implemented by (org.apache.axis.client.Stub).
   This stub.setTimeout(millis) is used to both set the
socket.setSotimeout(x)  and the socket.connect (endpoint,
timeoutInMillis)

   The default sender (HTTPSender) implements the previously described
configuration settings.

   The CommonsHTTPSender (based on Jakarta Commons HTTP Client)
implements the previous confiiguration settings but you can also
globally define timeouts as defined on the wiki :
http://wiki.apache.org/ws/FrontPage/Axis/AxisCommonsHTTP .

Sample :

HelloWorldBindingStub binding = (HelloWorldBindingStub) new
HelloWorldServiceLocator().gethelloWorldBinding();

// Time out after a minute
binding.setTimeout(6);


   Hope this helps,

   Cyrille

-- 
Cyrille Le Clerc
[EMAIL PROTECTED]
[EMAIL PROTECTED]
+33 6.61.33.69.86

On 6/19/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
> thanks,
>
> I think I will use the 1.4 then,
> I need just to be sure that the time out configuration works for
client,
> could you please confirm ?
>
> Michel Lequim
>
>
>  
>  From:
> [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> On Behalf Of Anne Thomas Manes
> Sent: Friday, June 16, 2006 7:11 PM
> To: axis-user@ws.apache.org
> Subject: Re: [axis1] more stable version of axis
>
>
> The formal release came out quite recently, but the build was produced
quite
> a while ago, and it's the one used in Geronimo.
>
>
> On 6/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > yes but axis 1.4 was released very recently, in april 2006, it is
not too
> risky to use it in production ?
> >
> >
> > Michel Lequim
> >
> >
> > 
>  From:
> [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> ] On Behalf Of Anne Thomas Manes
> > Sent: Friday, June 16, 2006 2:22 AM
> > To: axis-user@ws.apache.org
> > Subject: Re: [axis1] more stable version of axis
> >
> >
> >
> > Axis 1.4 fixes a number of array bugs. I recommend it over 1.2.
> >
> >
> > On 6/15/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]>
wrote:
> > >
> > >
> > >
> > >
> > > Dear axis users,
> > >
> > > we are to plan here to use axis in production but we are not sure
about
> the version we will use, I hope
> > > someone can help us. We think axis 2 is not enough stable, too
recent
> release and some bugs are still found (by example
> > > for the timeout configuration which is a feature we really need).
We
> then hesitate between axis 1.2 to 1.4,
> > > axis 1.4 seems to be also very recent so we plan to use axis 1.3.
> > >
> > > Do you think it is a good choice ?
> > >
> > > thanks in advance
> > >

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


= = = = = = = = = = = = = = = = = = = = = = = = =
Fortis Bank disclaimer :
http://www.fortisbank.be/legal/disclaimer.htm

Fortis Bank privacy policy :
http://www.fortisbank.be/legal/privacy_policy.htm
= = = = = = = = = = = = = = = = = = = = = = = = =




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [axis1] more stable version of axis

2006-06-19 Thread Cyrille Le Clerc

  Hello Michel,

  I confirm you client side timeouts work as expected in Axis 1.4 .

  To set client side socket timeouts, you have to invoke
"myStub.setTimeout(x)" (in millis). Note that you retrieve your stub
calling MyServiceLocator.getMyBinding() and note that setTimeout(x) is
implemented by (org.apache.axis.client.Stub).
  This stub.setTimeout(millis) is used to both set the
socket.setSotimeout(x)  and the socket.connect (endpoint,
timeoutInMillis)

  The default sender (HTTPSender) implements the previously described
configuration settings.

  The CommonsHTTPSender (based on Jakarta Commons HTTP Client)
implements the previous confiiguration settings but you can also
globally define timeouts as defined on the wiki :
http://wiki.apache.org/ws/FrontPage/Axis/AxisCommonsHTTP .

Sample :

HelloWorldBindingStub binding = (HelloWorldBindingStub) new
HelloWorldServiceLocator().gethelloWorldBinding();

// Time out after a minute
binding.setTimeout(6);


  Hope this helps,

  Cyrille

--
Cyrille Le Clerc
[EMAIL PROTECTED]
[EMAIL PROTECTED]
+33 6.61.33.69.86

On 6/19/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:



thanks,

I think I will use the 1.4 then,
I need just to be sure that the time out configuration works for client,
could you please confirm ?

Michel Lequim


 
 From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Anne Thomas Manes
Sent: Friday, June 16, 2006 7:11 PM
To: axis-user@ws.apache.org
Subject: Re: [axis1] more stable version of axis


The formal release came out quite recently, but the build was produced quite
a while ago, and it's the one used in Geronimo.


On 6/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
>
> yes but axis 1.4 was released very recently, in april 2006, it is not too
risky to use it in production ?
>
>
> Michel Lequim
>
>
> 
 From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
] On Behalf Of Anne Thomas Manes
> Sent: Friday, June 16, 2006 2:22 AM
> To: axis-user@ws.apache.org
> Subject: Re: [axis1] more stable version of axis
>
>
>
> Axis 1.4 fixes a number of array bugs. I recommend it over 1.2.
>
>
> On 6/15/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> > Dear axis users,
> >
> > we are to plan here to use axis in production but we are not sure about
the version we will use, I hope
> > someone can help us. We think axis 2 is not enough stable, too recent
release and some bugs are still found (by example
> > for the timeout configuration which is a feature we really need). We
then hesitate between axis 1.2 to 1.4,
> > axis 1.4 seems to be also very recent so we plan to use axis 1.3.
> >
> > Do you think it is a good choice ?
> >
> > thanks in advance
> >


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [axis1] more stable version of axis

2006-06-19 Thread michel.lequim



thanks, 
 
I think I will use the 1.4 then, 
I need just to be sure that the time out configuration 
works for client, could you please confirm ?
Michel Lequim 
 


From: 
[EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On 
Behalf Of Anne Thomas ManesSent: Friday, June 16, 2006 7:11 
PMTo: axis-user@ws.apache.orgSubject: Re: [axis1] more 
stable version of axis
The formal release came out quite recently, but the build was 
produced quite a while ago, and it's the one used in Geronimo.
On 6/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> 
wrote:

  
  
  yes but 
  axis 1.4 was released very recently, in april 2006, it is not too risky to use 
  it in production ? 
   
  Michel Lequim 
   
  
  
  From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] 
  ] On Behalf Of Anne Thomas ManesSent: Friday, June 16, 2006 
  2:22 AMTo: axis-user@ws.apache.orgSubject: Re: [axis1] more 
  stable version of axis
  
  Axis 1.4 fixes a number of array bugs. I recommend it over 
  1.2.
  On 6/15/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: 
  


Dear axis users, 

we are to plan here to use axis 
in production but we are not sure about the version we will use, I hope 
someone can help 
us. We think axis 2 is not enough stable, too recent release and some bugs 
are still found (by example for the timeout configuration which is a feature we really 
need). We then hesitate between axis 1.2 to 1.4, axis 1.4 seems to be also very recent so 
we plan to use axis 1.3. 
Do you think it is a good choice 
? 
thanks in 
advance 
-To 
unsubscribe, e-mail: [EMAIL PROTECTED] For additional 
commands, e-mail: [EMAIL PROTECTED]
  -To 
  unsubscribe, e-mail: [EMAIL PROTECTED] 
  For additional commands, e-mail: [EMAIL PROTECTED]
= = = = = = = = = = = = = = = = = = = = = = = = =
Fortis Bank disclaimer :
http://www.fortisbank.be/legal/disclaimer.htm

Fortis Bank privacy policy :
http://www.fortisbank.be/legal/privacy_policy.htm
= = = = = = = = = = = = = = = = = = = = = = = = =


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [axis1] more stable version of axis

2006-06-16 Thread Anne Thomas Manes
The formal release came out quite recently, but the build was produced quite a while ago, and it's the one used in Geronimo.On 6/16/06, 
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:





yes but axis 1.4 was released very recently, in april 2006, 
it is not too risky to use it in production ? 
 
Michel Lequim 
 


From: 
[EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED]
] On 
Behalf Of Anne Thomas ManesSent: Friday, June 16, 2006 2:22 
AMTo: axis-user@ws.apache.orgSubject: Re: [axis1] more 
stable version of axis
Axis 1.4 fixes a number of array bugs. I recommend it over 
1.2.
On 6/15/06, [EMAIL PROTECTED] <
 [EMAIL PROTECTED]> 
wrote:

  
  
  Dear axis users, 

  we are to plan here to use axis in 
  production but we are not sure about the version we will use, I hope 
  someone can help 
  us. We think axis 2 is not enough stable, too recent release and some bugs are 
  still found (by example for the timeout configuration which is a feature we really need). We 
  then hesitate between axis 1.2 to 1.4, axis 1.4 seems to be also very recent so we 
  plan to use axis 1.3. 
  Do you think it is a good choice ? 
  
  thanks in 
  advance 
  -To 
  unsubscribe, e-mail: [EMAIL PROTECTED] 
  For additional commands, e-mail: [EMAIL PROTECTED]


-To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: [axis1] more stable version of axis

2006-06-16 Thread michel.lequim



yes but axis 1.4 was released very recently, in april 2006, 
it is not too risky to use it in production ? 
 
Michel Lequim 
 


From: 
[EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On 
Behalf Of Anne Thomas ManesSent: Friday, June 16, 2006 2:22 
AMTo: axis-user@ws.apache.orgSubject: Re: [axis1] more 
stable version of axis
Axis 1.4 fixes a number of array bugs. I recommend it over 
1.2.
On 6/15/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> 
wrote:

  
  
  Dear axis users, 

  we are to plan here to use axis in 
  production but we are not sure about the version we will use, I hope 
  someone can help 
  us. We think axis 2 is not enough stable, too recent release and some bugs are 
  still found (by example for the timeout configuration which is a feature we really need). We 
  then hesitate between axis 1.2 to 1.4, axis 1.4 seems to be also very recent so we 
  plan to use axis 1.3. 
  Do you think it is a good choice ? 
  
  thanks in 
  advance 
  -To 
  unsubscribe, e-mail: [EMAIL PROTECTED] 
  For additional commands, e-mail: [EMAIL PROTECTED]
= = = = = = = = = = = = = = = = = = = = = = = = =
Fortis Bank disclaimer :
http://www.fortisbank.be/legal/disclaimer.htm

Fortis Bank privacy policy :
http://www.fortisbank.be/legal/privacy_policy.htm
= = = = = = = = = = = = = = = = = = = = = = = = =


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [axis1] more stable version of axis

2006-06-15 Thread Anne Thomas Manes
Axis 1.4 fixes a number of array bugs. I recommend it over 1.2.On 6/15/06, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:









Dear axis users, 


we are to plan here to use axis in production but we are not sure about the version we will use, I hope 

someone can help us. We think axis 2 is not enough stable, too recent release and some bugs are still found (by example

for the timeout configuration which is a feature we really need). We then hesitate between axis 1.2 to 1.4, 

axis 1.4 seems to be also very recent so we plan to use axis 1.3.


Do you think it is a good choice ? 


thanks in advance




-To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]