Re: SOAP in Applets (was: do an Apache SOAP 2.3 release ?)

2002-05-06 Thread richard . kennard


Ahhh. THAT would explain why it seemed to 'come and go' with different
installs of SOAP 2.2 - I didn't notice those Xerces minor releases! :)

Thanks so much,

Richard.



   
 
Mark   
 
Childerson   To: [EMAIL PROTECTED]  
 
Subject: Re: SOAP in Applets (was: do an  
 
         Apache SOAP 2.3 release ?)
 
03/05/2002 
 
11:50 PM   
 
Please 
 
respond to 
 
soap-user  
 
   
 
   
 




The problem was in Xerces 1.4.1 and not Xerces 1.4.4, so just keep track of

your Xerces version and you should be ok.

Mark

At 02:10 PM 5/3/02 +1000, you wrote:
>Guys,
>
>Can I just ask this one again? It's pretty important (to me, at least :)
>
>...
>
>Could I just confirm that the bug to do with accessing a JAXP debug
>security property (I'm sorry I can't remember the exact line) that was
>stopping Apache SOAP working in (non-signed) Java applets, and yet seemed
a
>pretty easy fix, has been
>addressed?
>
>It seems to come and go with different versions of 2.2, but I'd
>just like the peace of mind of knowing that somebody has definitely fixed
>it :)
>
>Many thanks,
>
>Richard.
>
>--
>'Cards etc forms relationship with S2 systems' click
>here http://www.cardsetc.com/news/mediareleases/pr20020425.htm to
>read about Cards etc's success.
>--
>This e-mail is from Cards Etc Pty Ltd (ACN: 069 533 302). It may contain
>privileged and confidential information. It is intended for the named
>recipient(s) only. If you are not an intended recipient, please notify us
>immediately by reply e-mail or by phone on +61 2 9212 7773 & delete this
>e-mail from your system.
>--









Re: SOAP in Applets (was: do an Apache SOAP 2.3 release ?)

2002-05-03 Thread Mark Childerson

The problem was in Xerces 1.4.1 and not Xerces 1.4.4, so just keep track of 
your Xerces version and you should be ok.

Mark

At 02:10 PM 5/3/02 +1000, you wrote:
>Guys,
>
>Can I just ask this one again? It's pretty important (to me, at least :)
>
>...
>
>Could I just confirm that the bug to do with accessing a JAXP debug
>security property (I'm sorry I can't remember the exact line) that was
>stopping Apache SOAP working in (non-signed) Java applets, and yet seemed a
>pretty easy fix, has been
>addressed?
>
>It seems to come and go with different versions of 2.2, but I'd
>just like the peace of mind of knowing that somebody has definitely fixed
>it :)
>
>Many thanks,
>
>Richard.
>
>--
>'Cards etc forms relationship with S2 systems' click
>here http://www.cardsetc.com/news/mediareleases/pr20020425.htm to
>read about Cards etc's success.
>--
>This e-mail is from Cards Etc Pty Ltd (ACN: 069 533 302). It may contain
>privileged and confidential information. It is intended for the named
>recipient(s) only. If you are not an intended recipient, please notify us
>immediately by reply e-mail or by phone on +61 2 9212 7773 & delete this
>e-mail from your system.
>--





SOAP in Applets (was: do an Apache SOAP 2.3 release ?)

2002-05-02 Thread richard . kennard

Guys,

Can I just ask this one again? It's pretty important (to me, at least :)

...

Could I just confirm that the bug to do with accessing a JAXP debug
security property (I'm sorry I can't remember the exact line) that was
stopping Apache SOAP working in (non-signed) Java applets, and yet seemed a
pretty easy fix, has been
addressed?

It seems to come and go with different versions of 2.2, but I'd
just like the peace of mind of knowing that somebody has definitely fixed
it :)

Many thanks,

Richard.

--
'Cards etc forms relationship with S2 systems' click
here http://www.cardsetc.com/news/mediareleases/pr20020425.htm to
read about Cards etc's success.
--
This e-mail is from Cards Etc Pty Ltd (ACN: 069 533 302). It may contain
privileged and confidential information. It is intended for the named
recipient(s) only. If you are not an intended recipient, please notify us
immediately by reply e-mail or by phone on +61 2 9212 7773 & delete this
e-mail from your system.
--





Re: do an Apache SOAP 2.3 release ?

2002-04-26 Thread Mike Williams

On Thu, 2002-04-25 at 23:06, Sanjiva Weerawarana wrote:
> Hello,
> 
> Its been quite a while since we released v2.2 of Apache SOAP. Since then
> about 50 bugs have been fixed and there are about another 50 remaining
> in the queue (most of them are non-bugs or trivial but some a big). 
> 
> I'm interested in doing a v2.3 to try to capture all the fixes that
> have been done since 2.2 into a labeled version. Originally it was
> intended that v2.2 would be the last as Axis was spsed to take over,
> but Axis is now running more than an year late!! However, it looks
> like Axis is finally getting nearer to 1.0 status and so putting out
> Apache SOAP v2.3 would really allow us to say that's the final verdict
> for this codebase.
> 
> I'm willing to serve as release manager and will write up a release 
> plan. The purpose of this note is to gauge interest on this effort.
> 
> Thanks!
> 
> Sanjiva.

Hi Sanjiva,

Definitely +1

Thanks,
Mike
-- 

---
May The Source Be With You!
http://www.mikesbox.com



Re: do an Apache SOAP 2.3 release ?

2002-04-26 Thread richard . kennard


Everyone,

I think this is a great idea, however could I just confirm that the bug to
do with accessing a JAXP debug security property (I'm sorry I can't
remember the exact line) that was stopping Apache SOAP working in
(non-signed) Java applets, and yet seemed a pretty easy fix, has been
addressed? It seems to come and go with different versions of 2.2, but I'd
just like the peace of mind of knowing that somebody has definitely fixed
it :)

Many thanks,

Richard.



   

Raghavan   

Srinivasan   To: [EMAIL PROTECTED]

Subject: Re: do an Apache SOAP 2.3 
release ?  
   

27/04/2002 

03:12 AM   

Please 

respond to 

soap-user  

   

   





Hi Sanjiva ,
   This makes a lot of sense to me . For folks that have been
using / certifying their applications with  the 2.2 release(and have not
yet adopted Axis)  , handling bugs / features introduced in future
builds means having to go through cvs and figure out exactly which files
changed and patch them in .
e.g i am still trying to locate all the files changed  to support the
switching the Current Schema version to 2001 .
Simply changing Constants.java does not solve the problem completely .

This is ugly and when customers are involved , there is the greater risk
that if they make their own
 changes in the 2.2 install to support their own app specific changes  ,
they might overwrite the changes shipped out to them .

Having a 2.3 release will bring in all such changes  over the last year
into one version .

Thanks -
Raghavan



Sanjiva Weerawarana wrote:

>Hello,
>
>Its been quite a while since we released v2.2 of Apache SOAP. Since then
>about 50 bugs have been fixed and there are about another 50 remaining
>in the queue (most of them are non-bugs or trivial but some a big).
>
>I'm interested in doing a v2.3 to try to capture all the fixes that
>have been done since 2.2 into a labeled version. Originally it was
>intended that v2.2 would be the last as Axis was spsed to take over,
>but Axis is now running more than an year late!! However, it looks
>like Axis is finally getting nearer to 1.0 status and so putting out
>Apache SOAP v2.3 would really allow us to say that's the final verdict
>for this codebase.
>
>I'm willing to serve as release manager and will write up a release
>plan. The purpose of this note is to gauge interest on this effort.
>
>Thanks!
>
>Sanjiva.
>









Re: do an Apache SOAP 2.3 release ?

2002-04-26 Thread John Mani

> Its been quite a while since we released v2.2 of Apache SOAP. Since then
> about 50 bugs have been fixed and there are about another 50 remaining
> in the queue (most of them are non-bugs or trivial but some a big). 
> 
> I'm interested in doing a v2.3 to try to capture all the fixes that
> have been done since 2.2 into a labeled version. Originally it was
> intended that v2.2 would be the last as Axis was spsed to take over,
> but Axis is now running more than an year late!! However, it looks
> like Axis is finally getting nearer to 1.0 status and so putting out
> Apache SOAP v2.3 would really allow us to say that's the final verdict
> for this codebase.

Yes. 

thanx
-john





Re: do an Apache SOAP 2.3 release ?

2002-04-26 Thread Raghavan Srinivasan

Hi Sanjiva ,
   This makes a lot of sense to me . For folks that have been 
using / certifying their applications with  the 2.2 release(and have not 
yet adopted Axis)  , handling bugs / features introduced in future 
builds means having to go through cvs and figure out exactly which files 
changed and patch them in . 
e.g i am still trying to locate all the files changed  to support the 
switching the Current Schema version to 2001 .
Simply changing Constants.java does not solve the problem completely .

This is ugly and when customers are involved , there is the greater risk 
that if they make their own
 changes in the 2.2 install to support their own app specific changes  , 
they might overwrite the changes shipped out to them .

Having a 2.3 release will bring in all such changes  over the last year 
into one version .

Thanks -
Raghavan



Sanjiva Weerawarana wrote:

>Hello,
>
>Its been quite a while since we released v2.2 of Apache SOAP. Since then
>about 50 bugs have been fixed and there are about another 50 remaining
>in the queue (most of them are non-bugs or trivial but some a big). 
>
>I'm interested in doing a v2.3 to try to capture all the fixes that
>have been done since 2.2 into a labeled version. Originally it was
>intended that v2.2 would be the last as Axis was spsed to take over,
>but Axis is now running more than an year late!! However, it looks
>like Axis is finally getting nearer to 1.0 status and so putting out
>Apache SOAP v2.3 would really allow us to say that's the final verdict
>for this codebase.
>
>I'm willing to serve as release manager and will write up a release 
>plan. The purpose of this note is to gauge interest on this effort.
>
>Thanks!
>
>Sanjiva.
>





Re: do an Apache SOAP 2.3 release ?

2002-04-26 Thread Bonnie Caballero


Hi Sanjiva,

Please correct me if I'm wrong.  Does soap have the capability
of reusing a Socket instead of creating a new Socket for each
HTTPConnection/post call?  If it doesn't currently, is there a chance
this feature can be added in the next release?

Thanks,
Bonnie H. Caballero





"Sanjiva Weerawarana" <[EMAIL PROTECTED]> on 04/25/2002 11:06:05 PM

Please respond to [EMAIL PROTECTED]

To:   "Apache SOAP" <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
cc:(bcc: Bonnie Caballero/Telcordia)
Subject:  do an Apache SOAP 2.3 release ?



Hello,

Its been quite a while since we released v2.2 of Apache SOAP. Since then
about 50 bugs have been fixed and there are about another 50 remaining
in the queue (most of them are non-bugs or trivial but some a big).

I'm interested in doing a v2.3 to try to capture all the fixes that
have been done since 2.2 into a labeled version. Originally it was
intended that v2.2 would be the last as Axis was spsed to take over,
but Axis is now running more than an year late!! However, it looks
like Axis is finally getting nearer to 1.0 status and so putting out
Apache SOAP v2.3 would really allow us to say that's the final verdict
for this codebase.

I'm willing to serve as release manager and will write up a release
plan. The purpose of this note is to gauge interest on this effort.

Thanks!

Sanjiva.










do an Apache SOAP 2.3 release ?

2002-04-25 Thread Sanjiva Weerawarana

Hello,

Its been quite a while since we released v2.2 of Apache SOAP. Since then
about 50 bugs have been fixed and there are about another 50 remaining
in the queue (most of them are non-bugs or trivial but some a big). 

I'm interested in doing a v2.3 to try to capture all the fixes that
have been done since 2.2 into a labeled version. Originally it was
intended that v2.2 would be the last as Axis was spsed to take over,
but Axis is now running more than an year late!! However, it looks
like Axis is finally getting nearer to 1.0 status and so putting out
Apache SOAP v2.3 would really allow us to say that's the final verdict
for this codebase.

I'm willing to serve as release manager and will write up a release 
plan. The purpose of this note is to gauge interest on this effort.

Thanks!

Sanjiva.