> One question this brings to my mind though is, should xmlsec really be tied > to xerces and xalan (the missing class is from xalan)?
In my opinion, no. After this release goes out I plan on starting a discussion about what we want to do/change for 1.5. One of the things on my list is to move to JDK 1.5, and drop compile time Xalan dependencies. Colm. On Wed, Nov 10, 2010 at 12:02 AM, Chad La Joie <[email protected]> wrote: > Okay, false alarm I think. It appears that something was just horked up > with my test env. > > One question this brings to my mind though is, should xmlsec really be tied > to xerces and xalan (the missing class is from xalan)? Looks like there are > about 10 classes that directly use APIs from those two libraries. > > On 11/9/10 5:23 PM, Chad La Joie wrote: >> >> Hey Colm, >> >> There might be a bug. I'm trying to track it down now. I'm getting a >> ClassNotFoundException for the >> org.apache.xml.utils.URI$MalformedURIException class. >> >> This is occurring in a >> org.apache.xml.security.encryption.XMLCipher#getInstance(String) call. >> This also leads me to ask, did any algorithm URIs change in this release? >> >> On 11/8/10 12:55 PM, Colm O hEigeartaigh wrote: >>> >>> Hi, >>> >>> This is a vote to release XML Security (Java) 1.4.4. This distribution >>> was built from the following svn tag: >>> >>> https://svn.apache.org/repos/asf/santuario/tags/J_1_4_4/ >>> >>> The changelog is here: >>> >>> http://people.apache.org/~coheigea/stage/xmlsec/1.4.4/site/changes.html >>> >>> The distribution is here: >>> >>> http://people.apache.org/~coheigea/stage/xmlsec/1.4.4/dist/ >>> >>> The maven artifacts are here: >>> >>> http://people.apache.org/~coheigea/stage/xmlsec/1.4.4/maven/ >>> >>> Here is my +1 (binding). >>> >>> Thanks, >>> >>> Colm. >>> >> > > -- > Chad La Joie > http://itumi.biz > trusted identities, delivered >
