I fixed the deadlink -- that's my fault from when I updated the API documentation.
As far as the Java implementation, it was only done as a proof of concept, and hasn't been maintained. Of course, since it's just an API wrapper, there shouldn't necessarily be much development needed, unless the underlying API changes. That said, I think that many of the idioms I used when developing the Java wrapper aren't that natural for Java programmers, and that some serious refactoring would make it more useful. If anyone is interested in taking on that project, I'd be happy to discuss my thoughts on the current implementation's short comings. Nathan Bjorn Wijers wrote: >He guys, > >On http://api.creativecommons.org/docs/ we have a deadlink, the javadoc >link is dead. Who can fix this? > >Another thing is that the Java implementation on sf.net seems to be >quite old. Is the development of this stil going on or is it more or >less dead? > >There are some people that would like to have an easy to implement Java >version of the CC chooser, preferably for mmbase >(http://www.mmbase.org), a content management system used by a lot of >media companies in the Netherlands. Is there something like this >available already? > >grtz >BjornW > >_______________________________________________ >cc-devel mailing list >[email protected] >http://lists.ibiblio.org/mailman/listinfo/cc-devel > > _______________________________________________ cc-devel mailing list [email protected] http://lists.ibiblio.org/mailman/listinfo/cc-devel
