DO NOT REPLY [Bug 39984] New: - Option to collapse whitespace in Sig element

2006-07-06 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

RE: Use of exclusive c14n when encrypting elements in C++ lib

2006-07-06 Thread Scott Cantor
> I was thinking about this during the day. I'm going to add a method to > allow the exclusive use to be turned off and that way it can be > deactivated if it makes sense. I've been wracking my brains to think > about why I used it in the first place, and I know there was a really > good reason b

Re: Feature Request: Option to collapse whitespace in Sig element

2006-07-06 Thread Raul Benito
Good idea, Can you write a bugzilla request, in order not to miss it. Thanks. Raul. On 7/6/06, Glen Smith <[EMAIL PROTECTED]> wrote: Hi Guys, I've noticed in 1.3 when I create a sig, I get an empty \n #text element between each line in the DOM output of the sig. I'd like to throw in a reques

Feature Request: Option to collapse whitespace in Sig element

2006-07-06 Thread Glen Smith
Hi Guys,I've noticed in 1.3 when I create a sig, I get an empty \n #text element between each line in the DOM output of the sig. I'd like to throw in a request to have an option to suppress any whitespace in the output when the DOM elements are generated. Would make things a little easier for one p

Re: XML security seems to be not thread safe...Please Help

2006-07-06 Thread Raul Benito
If you mean by stable no known bugs then it is stable. If you mean real world testing then I don't known. Remember that 1.3 was mark stable with the bug you got. And it goes with several betas & rc. You can see the changelog at the end. But the main changes are thread related, I'm not expecting

Re: Use of exclusive c14n when encrypting elements in C++ lib

2006-07-06 Thread Berin Lautenbach
Scott, I was thinking about this during the day. I'm going to add a method to allow the exclusive use to be turned off and that way it can be deactivated if it makes sense. I've been wracking my brains to think about why I used it in the first place, and I know there was a really good reason but