Hrm, it is an API change but a minor, single, well-localized one. I
would stay with 1.3.1 for this release. I haven't looked carefully at
the changes, but is there a reason you couldn't wrap API backwards
compatibility by doing something like (in X509CertificateResolver):
public boolean engineCa
Hi,
I'm planning to do a minor release of java xmlsec 1.3.1. The main
reason, is the bug
http://issues.apache.org/bugzilla/show_bug.cgi?id=38605 , that hits
when the library is used in multithreads and use X509 resolvers,
resolving this has change slightly the API of the resolvers (see the
comme
I wonder if people would mistake Santuarium for sanitarium (a variant of
sanitorium/sanatorium), and if they did, whether they might be onto
something. ;-)
"Bema" (http://dictionary.reference.com/search?q=bema) is a related word
that seems unlikely to be trademarked. I'm not sure it has the righ
Sad, I like the name,
Perhaps a translation: Santuario(Spanish), Santuarium(Latin)
or a synonym Tabernaculum...
Just wild guessing..
On 5/3/06, Jesse Pelton <[EMAIL PROTECTED]> wrote:
Good catch. It's a registered trademark, no less, and in a related
field, so I doubt SecureWave would be plea
Good catch. It's a registered trademark, no less, and in a related
field, so I doubt SecureWave would be pleased to have Apache use it for
a project name. Too bad.
-jesse-
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 03, 2006 10:26 AM
To:
Sanctuary is a cool name. However there is a product named Sanctuary by
SecureWave: http://www.securewave.com/endpoint_security_solutions.jsp
--Sean
Berin Lautenbach wrote:
All,
So we have two names that people seem to like
Raksha
Santuary
Any other takers?
We also have a scope of
"...ope
P.S. I have just noticed that your XML document doesn't have declaration for
default namespace.
Try changing this:
http://www.w3.org/2001/XMLSchema-instance";>
into:
http://www.example.org/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
It might help.
_
It seems that DOMOutputter have/had lots of bugs dealing with namespaces. For
example, take a look
into this:
http://www.jdom.org/pipermail/jdom-interest/2004-April/013775.html
You might consider using XMLOutputter, instead.
In short, your problem is that namespace "http://www.w3.org/2000/xmln
