Folks, I posted this to the commons-dev [codec] list yesterday, but figured you might have views yourself (as a user of codec). I don't (personally) know the release history of codec, or if you'd mind not being able to compile your CVS HEAD code against older releases (assume any existed where it threw this exception), but one quick fix would be to compile out the try/catch.
Clearly this is to your discretion, and depends upon what codec has released, and what they plan on releasing. If I get an answer on commons-dev I'll post it here. regards, Adam ----- Original Message ----- From: "Adam R. B. Jack" <[EMAIL PROTECTED]> To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]> Sent: Tuesday, May 25, 2004 10:44 AM Subject: [codec] base64Codec.decode and DecoderException > Folks, > > An interested compatibility issue has surfaced from this: > > http://brutus.apache.org:8080/gump/ws-xmlrpc/ws-xmlrpc/gump_work/build_ws-xmlrpc_ws-xmlrpc.html > > /usr/local/gump/public/workspace/ws-xmlrpc/src/java/org/apache/xmlrpc/Defaul > tTypeFactory.java:133: exception org.apache.commons.codec.DecoderException > is never thrown in body of corresponding try statement > [javac] catch (DecoderException e) { > [javac] ^ > > This is the code: > > public Object createBase64(String cdata) > { > try { > return base64Codec.decode(cdata.getBytes()); > } > catch (DecoderException e) { > //TODO: consider throwing an exception here? > return new byte[0]; > } > } > > Now since exceptions are not part of the signature of methods, there is > probably no runtime issue here. If the exception is not going to be thrown > that is the same as it not actually being thrown, I guess. Still, there is a > compile time problem and if one removes the catch they can't compile against > older codec (assuming that was declared to throw it). > > Can somebody provide the background information on this exception, from this > method, and when (releases) it might've been available and removed? If this > exception is never to be thrown again (and better, if it isn't thrown in > currently released code) then maybe we can just ask the ws-xmlrpc folks to > update. > > BTW: I don't think there is a way to turn off this compiler error, is there? > Would that be appropriate, even if possible? > > regards, > > Adam > -- > Experience the Unwired Enterprise: > http://www.sybase.com/unwiredenterprise > Try Sybase: http://www.try.sybase.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
